Skip to content

W-23851984-pce-4.3-docs-kt - #427

Open
kevintroller wants to merge 3 commits into
v4.2from
W-23851984-pce-4.3-docs-kt
Open

W-23851984-pce-4.3-docs-kt#427
kevintroller wants to merge 3 commits into
v4.2from
W-23851984-pce-4.3-docs-kt

Conversation

@kevintroller

Copy link
Copy Markdown
Contributor

Summary

  • Add StorageClass mode documentation for PCE 4.3 shared filesystem (from @W-24000146 Add storageclass mode for PCE 4.3 #425), reframing NFS docs to cover both NFS and StorageClass modes across install, verify, troubleshoot, upgrade, and backup/DR pages.
  • Add a deploy landing page for Mule apps on PCE, with paths for Anypoint Code Builder and Anypoint Studio.
  • Add pages to configure Anypoint Code Builder for PCE and to develop, package, and deploy Mule apps using ACB and MuleSoft Vibes Skills.
  • Update nav and Managing hub to surface the new deploy and ACB topics.

Replaces #426 (recreated to resolve CLA issues from brought-in commits).

Test plan

  • Confirm local Antora/build renders updated pages without broken xrefs
  • Spot-check nav hierarchy: Shared Filesystem Prerequisites, Deploying Mule Applications, and nested ACB pages
  • Verify install checklist and workflow steps match product behavior for StorageClass mode
  • Confirm upgrade and backup/DR wording still accurate for NFS vs StorageClass framing
  • Review ACB config and deploy pages for correct prerequisites, CLI plugin install steps, and Runtime Manager flow
  • Confirm Studio path on the deploy landing page points to config + export + Runtime Manager (not Deploy to CloudHub)

Document StorageClass shared filesystem mode, Anypoint Code Builder setup and deploy flows, and a deploy landing page covering ACB and Studio paths.
@kevintroller
kevintroller requested a review from a team as a code owner September 9, 2026 17:44
@kevintroller kevintroller changed the title W-23851984: PCE 4.3 documentation W-23851984-pce-4.3-docs-kt Sep 9, 2026
Follow these steps to develop, package, and deploy Mule applications to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) using Anypoint Code Builder and MuleSoft Vibes Skills:

. xref:#connect-acb[Connect Anypoint Platform PCE with Anypoint Code Builder]
. xref:#develop-mule-app[Develop Mule Application]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Develop a Mule Application
or
Develop Mule Applications


. xref:#connect-acb[Connect Anypoint Platform PCE with Anypoint Code Builder]
. xref:#develop-mule-app[Develop Mule Application]
. xref:#package-export[Package and Export the Mule Application]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. xref:#package-export[Package and Export the Mule Application]
. xref:#package-export[Package and Export Your Mule Application]

To connect Anypoint Platform PCE with Anypoint Code Builder, follow the instructions in xref:config-code-builder.adoc[].

[[develop-mule-app]]
== Develop Mule Application

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment above



[[package-export]]
== Package and Export the Mule Application

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
== Package and Export the Mule Application
== Package and Export Your Mule Application


Manually create the deployable Mule application artifact:

. In the VS Code Explorer, right-click your `mule-artifact.json` file or any XML file in `src/main/mule`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. In the VS Code Explorer, right-click your `mule-artifact.json` file or any XML file in `src/main/mule`.
. In the VS Code explorer, right-click your `mule-artifact.json` file or any XML file in `src/main/mule`.


* xref:deploy-apps.adoc[]
* xref:config-code-builder.adoc[]
* xref:anypoint-code-builder::int-developing-integrations.adoc[Developing Integrations]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* xref:anypoint-code-builder::int-developing-integrations.adoc[Developing Integrations]
* xref:anypoint-code-builder::int-developing-integrations.adoc[]

* xref:deploy-apps.adoc[]
* xref:config-code-builder.adoc[]
* xref:anypoint-code-builder::int-developing-integrations.adoc[Developing Integrations]
* xref:runtime-manager::deploying-to-your-own-servers.adoc[Deploying to Your Own Servers]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* xref:runtime-manager::deploying-to-your-own-servers.adoc[Deploying to Your Own Servers]
* xref:runtime-manager::deploying-to-your-own-servers.adoc[]


Before you deploy, ensure that:

* Your servers are registered and running in Runtime Manager. See xref:runtime-manager::managing-servers.adoc[About Servers, Server Groups, and Clusters].

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Your servers are registered and running in Runtime Manager. See xref:runtime-manager::managing-servers.adoc[About Servers, Server Groups, and Clusters].
* Your servers are registered and running in Runtime Manager. See xref:runtime-manager::managing-servers.adoc[].

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Globally) avoid hard-coded text

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants