--- schema_version: "1" id: 1a02510a8f3c5f651d19d62fb2e68e43c0a532a0562393e92adf98d3f8809298 title: Deploying Mule Applications Using Anypoint Code Builder collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/private-cloud/latest/deploy-apps-code-builder.md canonical_url: https://docs.mulesoft.com/private-cloud/latest/deploy-apps-code-builder source_site: docs.mulesoft.com content_type: documentation content_hash: f3cfacff9eb5d30112b7794edb0db877a84d9cce85a240e36ed87af34fdb27d0 description: MuleSoft Documentation Site release: "4.3" latest: true --- --- product: Anypoint Platform Private Cloud Edition version: 4.3 is-latest-version: true --- # Deploying Mule Applications Using Anypoint Code Builder > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Follow these steps to develop, package, and deploy Mule applications to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) using Anypoint Code Builder in VS Code. You can complete this workflow without MuleSoft Vibes by following the standard Anypoint Code Builder documentation. MuleSoft Vibes is optional. 1. [Connect Anypoint Platform PCE with Anypoint Code Builder](#connect-acb) 2. [Develop Mule Application](#develop-mule-app) 3. [Package and Export the Mule Application](#package-export) 4. [Deploy to Runtime Manager](#deploy-runtime-manager) 5. [Publish to Exchange](#publish-exchange) 6. [Validate the Deployment](#validate-deployment) ## Connect Anypoint Platform PCE with Anypoint Code Builder To connect Anypoint Platform PCE with Anypoint Code Builder, follow the instructions in [Configuring Anypoint Code Builder for Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/config-code-builder). Private cloud mode connects Anypoint Code Builder on your machine to the Anypoint Platform PCE control plane. Sign-in uses OAuth or OIDC with the identity provider hosted by Anypoint Platform PCE. Anypoint Code Builder keeps application metadata in your network and blocks standard cloud telemetry. ## Develop Mule Application Build the Mule application in VS Code with Anypoint Code Builder. You can create the specification, the flow, DataWeave transformations, and security configuration without MuleSoft Vibes. Follow the standard Anypoint Code Builder documentation: - [Designing API Specs and Fragments](https://docs.mulesoft.com/anypoint-code-builder/des-designing-api-specs) - [Developing Integrations](https://docs.mulesoft.com/anypoint-code-builder/int-developing-integrations) MuleSoft Vibes is optional. If you use it, Vibes skills can generate the specification, the flow, DataWeave transformations, and security configuration. These skills are available in the skill pack: - `build-mule-integration` generates integration flows, configures endpoints, and scaffolds orchestration. - `secure-mule-app` scans the configuration for security risks, applies encryption, and suggests logging. - DataWeave skills generate transformations and map payload schemas. You can add organization-specific skills that enforce naming conventions, header standards, and logging policies. Package those skills in a repository and use them with Anypoint Code Builder. 1. In VS Code, open the Command Palette and run `MuleSoft: Design an API` to create the API specification. Anypoint Code Builder validates the specification locally. 2. To mock the API on your machine, use the API Console. 3. Run `MuleSoft: Implement an API Specification` to stub the interface and connect the services. 4. To create a project from the canvas instead, select the Anypoint Code Builder icon in the primary side bar, select `Develop an Integration`, and create a Mule project. 5. To import an asset from Exchange, run `MuleSoft: Import Asset From Exchange`. Select the asset type and add it to the project. 6. Develop the flow, DataWeave transformations, and security configuration in Anypoint Code Builder. If you use MuleSoft Vibes, you can use natural language prompts for flow logic, DataWeave mappings, and the `secure-mule-app` skill. 7. Create and run MUnit tests in the project before you package the application. 8. Run a local debug session from the **Run and Debug** sidebar to test the logic before packaging. ![Anypoint Code Builder in VS Code, with the command palette open to MuleSoft: Login to Anypoint Platform, a Mule flow on the canvas, and the local runtime in the terminal](/mulesoft/current/en-us/private-cloud/latest/_images/pce-acb-vibes.png) ## Package and Export the Mule Application Manually create the deployable Mule application artifact: 1. In the VS Code Explorer, right-click your `mule-artifact.json` file or any XML file in `src/main/mule`. 2. Select **MuleSoft: Export Mule Project**. 3. Choose **Deployable JAR** and select **Include project sources**. Including project sources enables you to re-import the project later if needed. 4. Save the JAR to your local machine. ## Deploy to Runtime Manager Upload the JAR to your hybrid server. The server must be registered and in the **Running** state. 1. Log in to Anypoint Platform PCE and navigate to **Runtime Manager**. 2. Select the correct environment, and then click **Deploy Application**. 3. Set the **Deployment Target** to your hybrid server or cluster. 4. Click **Choose File** > **Upload File** and select the JAR you exported. 5. Click **Deploy Application**. After the application status is **Started**, apply API Manager policies to the endpoints. Use API Manager in Anypoint Platform PCE, or the Anypoint CLI API Manager plugin from [Configuring Anypoint Code Builder for Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/config-code-builder). ## Publish to Exchange Publishing an asset directly from Anypoint Code Builder to Exchange in Anypoint Platform PCE has partial support. Publish the deployable JAR from Exchange in Anypoint Platform PCE: 1. In Anypoint Platform PCE, navigate to **Exchange**. 2. Click **Publish New Asset**. 3. Provide an asset name and select **Mule Application** as the asset type. 4. Upload the same JAR file. This publishes the project to your organization’s private library. ## Validate the Deployment To validate the deployment, follow these steps: 1. In Runtime Manager, wait until the application status is **Started**. 2. Use an API client such as Postman or the VS Code Thunder Client to send a request to the server IP and the port defined in your HTTP Listener. For example: `[http://10.x.x.x:8081/api/test](http://10.x.x.x:8081/api/test)` 3. Check the **Logs** tab in Runtime Manager to verify that the request was processed successfully. ## See Also - [Deploying Mule Applications to Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/deploy-apps) - [Configuring Anypoint Code Builder for Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/config-code-builder) - [Developing Integrations](https://docs.mulesoft.com/anypoint-code-builder/int-developing-integrations) - [Using Skills with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-skills) - [Deploying to Your Own Servers](https://docs.mulesoft.com/runtime-manager/deploying-to-your-own-servers) - [Managing Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/operating-about)