---
schema_version: "1"
id: dac8981eb5a5a0805b141fe924a916868524bc11440d1b0de98a905bcbffa478
title: Configure the Java Module Using Anypoint Code Builder
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/java-module/latest/configure-java-module-acb.md
canonical_url: https://docs.mulesoft.com/java-module/latest/configure-java-module-acb
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a7993de3ca9e435054a57130762366aa99de050295c271f83a8caac63c903e66
description: MuleSoft Documentation Site
release: "2.0"
latest: true
---
---
product: Java Module
version: 2.0
is-latest-version: true
---

# Configure the Java Module Using Anypoint Code Builder

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Define custom Java code using the Java module to use in your Anypoint Code Builder project. To use
Anypoint Code Builder to configure the Java module, create a basic integration project in Anypoint
Code Builder, add connectors and other components to your Mule application to process your business
logic, and then configure the attributes for the Java Module.

## Before You Begin

Before creating an Anypoint Code Builder integration project, you must:

- [Set up and access the Anypoint Code Builder web or desktop IDE](https://docs.mulesoft.com/anypoint-code-builder/start-acb).

- Have credentials to access Anypoint Platform.

- Ensure that the Extension Pack for Java (from Microsoft) is installed in Visual Studio Code.

## Creating a New Integration Project

To create a new integration project:

1.  In the activity bar of the IDE, click the
    ![Anypoint Code Builder icon](/mulesoft/current/en-us/connectors/_images/acb-icon-ms-logo.png) (**Anypoint Code
    Builder**) icon.

2.  From **Quick Actions**, click **Develop an Integration**:

    ![Develop an Integration link highlighted in the Getting started section](/mulesoft/current/en-us/anypoint-code-builder/_images/develop-integration-option-mat.png)

3.  Complete the following in the **Develop an Integration** form:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Attribute</th><th>Value</th></tr></thead><tbody><tr><td><div><div><p><strong>Project Name</strong></p></div></div></td><td><div><div><p>Unique name for your project.</p></div><div><p>This name is used as the title and name of the integration project file. For example, if the project name is "Salesforce Integration," the project file name is <code>salesforce-integration</code>.</p></div></div></td></tr><tr><td><div><div><p><strong>Project Location</strong></p></div></div></td><td><div><div><p>Your home directory or another directory you create. Click <strong>Browse</strong> to select a different directory for the integration project.</p></div><div><p>Don’t create the project within another project directory.</p></div><div><p>See <a href="https://docs.mulesoft.com/anypoint-code-builder/start-add-folders">Adding Folders to Your Home Directory</a>.</p></div></div></td></tr></tbody></table>

4.  Select the type of project to create by selecting either the **Empty Project** or **Template or
    Example** card.

5.  Select the **Mule runtime** and **Java Version** for your app.

6.  Click **Create Project**.

When you create a new integration project, Anypoint Code Builder creates the `src/main/java` and
`/src/test/java` folders in the project. For existing projects, you can manually create these
folders.

## Adding Components to Your Project

Add components to your integration project to build a flow:

1.  In the **Explorer** view, open the XML file for your project, such as `my-project-name.xml`.

2.  Select **Build a Flow** from the start card to create an empty flow:

    ![Anypoint Code Builder canvas with starting cards with the options to start from scratch, build a flow, or build a subflow](/mulesoft/current/en-us/connectors/_images/acb-build-flow.png)

3.  Change the name of the flow:

    1.  Click **Flow**.

    2.  Click the edit icon.

        ![Arrow pointing to the flow name edit pencil icon](/mulesoft/current/en-us/connectors/_images/acb-change-flow-name.png)

    3.  Enter the flow name, and click the checkmark.

    4.  In the canvas UI, click the
        ![Add component icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add component**)
        icon.

    5.  In the **Add Component** panel, search for and select your component from the results. The
        following example shows the **Listener** component from the **HTTP** search results:

        ![Listener component highlighted in the Add Component section](/mulesoft/current/en-us/anypoint-code-builder/_images/main-tutorial-add-first-listener.png)

        The configuration XML file now includes the XML for the HTTP Listener into the `<flow/>`
        element, for example:

        ```XML
        <flow name="getFlights" >
          <http:listener path="" config-ref="" doc:name="Listener" doc:id="ojzfry" />
        </flow>
        ```

## Configuring the Component Attributes

After you add components to your integration project, configure the attributes in the component UI,
or configure the attributes directly in the XML code editor.

Connector XML tags start with a namespace followed by an operation, following the syntax
`namespace:operation`, such as `<db:select/>` for a **Select** operation in Anypoint Connector for
Database (Database Connector).

You can use autocomplete from an expression (**fx**) field for a component to select DataWeave
functions from the Core module and other values accepted in this field.

## Configure a Trigger for the Flow

A trigger (source) starts the flow when specified conditions are met. If a connector has its own
associated sources, you can use a connector-specific trigger to initiate the flow. Each connector
trigger has a unique configuration.

You can configure the following sources for this connector:

- **HTTP > Listener**

  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**

  Initiates a flow when a time-based condition is met

### Configuring the New Operation

Create a new class instance by using the **New** operation of the Java module. The identifier of a
constructor includes the class and constructor names, and the constructor has a full description of
its signature, including the types of each parameter.

For example, if you invoke the constructor `Me(String name, int age)`, which belongs to the
`org.bar.Me` class, then the identifier of the method is `Me(String,int)`.

To configure the attributes for **New** in the Anypoint Code Builder UI:

1.  Click the **New** component on the canvas.

2.  On the **General** tab:

    1.  In **Class**, select the Java class that contains the method to use.

        You can search for all the available Java classes for your project, including classes you
        create and native Java classes.

    2.  In **Constructor**, search and select the constructor to use.

        > [!NOTE] If this field is blank, click the refresh icon to populate it.

3.  Select the **Advanced** tab to configure the following attributes:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>UI Field</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Target variable</p></td><td><p>Name of the variable to assign the class instance to.</p></td><td><p>No</p></td></tr><tr><td><p>Target value</p></td><td><p>Expression that evaluates the operation’s output. The expression outcome is stored in the target variable.</p></td><td><p>No</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Custom error types that you map to Mule error types. The mappings can help you further differentiate and group errors in your app. Configure this attribute in the XML editor. See <a href="https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept">Mule Errors</a>.</p></div></div></td><td><p>No</p></td></tr></tbody></table>

4.  Select the **Input/Output** tab to filter and view input and output variables stored in
    DataWeave.

After you add your class instance, [configure the **Invoke** operation](#configuring-invoke).

### Configuring the Invoke Operation

Invoke methods with the provided arguments using a specified class instance. The identifier of the
method to invoke includes the class and method names.

To configure the attributes for **Invoke** in the Anypoint Code Builder UI:

1.  Click the **Invoke** component on the canvas.

2.  On the **General** tab:

    1.  Select the class **Instance** for invoking the method.

        This value is the target variable assigned to the **New** operation.

    2.  In **Class**, select the Java class that contains the method to use.

        You can search for all the available Java classes for your project, including classes you
        create and native Java classes.

    3.  In **Method**, search and select the method to use.

        Only the static methods from the class are displayed.

        > [!NOTE] If this field is blank, click the refresh icon to populate it.

3.  Select the **Advanced** tab to configure the following attributes:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>UI Field</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Output MIME type</p></td><td><p>MIME type of the payload this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Parameters</p></td><td><p>Parameters appended to the value of the <strong>Output MIME type</strong> attribute as key-value pairs for a reader property. Multiple key-value pairs are allowed.</p></td><td><p>No</p></td></tr><tr><td><p>Output encoding</p></td><td><p>Encoding of the payload that this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Target variable</p></td><td><p>Name of the variable that stores the operation’s output.</p></td><td><p>No</p></td></tr><tr><td><p>Target value</p></td><td><p>Expression that evaluates the operation’s output. The expression outcome is stored in the target variable.</p></td><td><p>No</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Custom error types that you map to Mule error types. The mappings can help you further differentiate and group errors in your app. Configure this attribute in the XML editor. See <a href="https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept">Mule Errors</a>.</p></div></div></td><td><p>No</p></td></tr></tbody></table>

4.  Select the **Input/Output** tab to filter and view input and output variables stored in
    DataWeave.

### Configuring the Invoke Static Operation

Invoke static methods with the arguments you provide.

To configure the attributes for **Invoke Static** in the Anypoint Code Builder UI:

1.  Click the **Invoke Static** component on the canvas.

2.  On the **General** tab:

    1.  In **Class**, select the Java class that contains the method to use.

        You can search for all the available Java classes for your project, including classes you
        create and native Java classes.

    2.  In **Method**, search and select the method to use.

        Only the static methods from the class are displayed.

        > [!NOTE] If this field is blank, click the refresh icon to populate it.

3.  Select the **Advanced** tab to configure the following attributes:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>UI Field</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Output MIME type</p></td><td><p>MIME type of the payload this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Parameters</p></td><td><p>Parameters appended to the value of the <strong>Output MIME type</strong> attribute as key-value pairs for a reader property. Multiple key-value pairs are allowed.</p></td><td><p>No</p></td></tr><tr><td><p>Output encoding</p></td><td><p>Encoding of the payload that this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Target variable</p></td><td><p>Name of the variable that stores the operation’s output.</p></td><td><p>No</p></td></tr><tr><td><p>Target value</p></td><td><p>Expression that evaluates the operation’s output. The expression outcome is stored in the target variable.</p></td><td><p>No</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Custom error types that you map to Mule error types. The mappings can help you further differentiate and group errors in your app. Configure this attribute in the XML editor. See <a href="https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept">Mule Errors</a>.</p></div></div></td><td><p>No</p></td></tr></tbody></table>

4.  Select the **Input/Output** tab to filter and view input and output variables stored in
    DataWeave.

### Configuring the Validate Type Operation

Validate that the class instance is an instance of (`instanceof`) the expected class using the
**Validate Type** operation.

To configure the attributes for **Validate Type** in the Anypoint Code Builder UI:

1.  Click the **Validate type** component on the canvas.

2.  On the **General** tab:

    1.  Select the **Class** the instance belongs to.

    2.  Enter the name of the class **Instance** to validate.

    3.  Select **Accept subtypes** to accept subtypes of a class.

        Deselect this option if the class instance must be of the same class.

## Example

### Creating a Java Class

Create Java classes containing methods to use in your application flows. The classes you create in
your project are not available to other projects in your Anypoint Code Builder workspace.

1.  In your Anypoint Code Builder project, create a new Java package called `com.me` under
    `src/main/java`.

2.  Create a new Java class called `TaxCalculator.java`, and add the implementation, for example:

    ```java
    package com.me;

    public class TaxCalculator {

        private Double percentBaseTax = 7.0;

        public Double calculateTax(Double price, Integer percentAdditionalTax) {
            return price * (this.percentBaseTax + percentAdditionalTax) / 100;
        }

        public Boolean isTaxFree(Double price) {
            if (price < 10) {
                return true;
            }
            return false;
        }
    }
    ```

In this example code, there are two methods:

- `calculateTax`, which receives the `price` and `percentAdditionalTax` parameters.

- `isTaxFree`, which receives the `price` parameter.

### Configure an HTTP Trigger

1.  Click the **Listener** component on the canvas UI.

2.  Optionally, click the edit icon to change the name of the **Listener** component.

3.  Select the configuration file for the connector, or add the HTTP configuration to the XML
    outside of the flow, for example:

    ```xml
    <mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    	xmlns:http="http://www.mulesoft.org/schema/mule/http"
    	xmlns:java="http://www.mulesoft.org/schema/mule/java" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
    	http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
    	http://www.mulesoft.org/schema/mule/java http://www.mulesoft.org/schema/mule/java/current/mule-java.xsd">
      <http:listener-config name="HTTP_listener_config">
        <http:listener-connection host="0.0.0.0" port="8081" />
      </http:listener-config>
      <flow name="name1">
        <http:listener path="/calculatePath" config-ref="HTTP_listener_config" doc:name="Listener" doc:id="511e4743-a5ed-4e74-8174-ead32ff575ea" allowedMethods="POST" />
      </flow>
    </mule>
    ```

4.  On the **General** tab, enter `/calculateTax` in the **Path** field.

5.  On the **Advanced** tab, set the **Allowed methods** to `POST`.

### Create a New Class Instance

You must create a new class instance because the method used in this example is non-static :

1.  Click the **New** component on the canvas.

2.  On the **General** tab:

    1.  Select the **Class** that contains the method to use, in this case, `com.me.TaxCalculator`.

    2.  Select the **Method** to use: `TaxCalculator()`.

        > [!NOTE] If this field is blank, click the refresh icon to populate it.

3.  On the **Advanced** tab, assign the new class instance to a target variable called
    `taxCalculator`.

    Your code now looks similar to this:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:java="http://www.mulesoft.org/schema/mule/java" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
  http://www.mulesoft.org/schema/mule/java http://www.mulesoft.org/schema/mule/java/current/mule-java.xsd
  http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
  http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

  <http:listener-config name="HTTP_Listener_config">
    <http:listener-connection host="0.0.0.0" port="8081" />
  </http:listener-config>

  <flow name="java1">
    <http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/calculateTax" allowedMethods="POST"/>
    <java:new class="com.me.TaxCalculator" constructor="TaxCalculator()" target="taxCalculator" />
  </flow>
</mule>
```

### Add an Invoke Operation

To call your method, add an **Invoke** operation:

1.  Click the **Invoke** component on the canvas.

2.  On the **General** tab:

    1.  Enter `#[vars.taxCalculator]` as the class **Instance** for invoking the method.

    2.  Select the **Class** that contains the method to use, in this case, `com.me.TaxCalculator`.

    3.  Select the **Method** to use: `calculateTax(java.lang.Double,java.lang.Integer)`.

        The methods shown are the standard non-static Java methods and the methods you created.

3.  On the **Advanced** tab, assign the Invoke operation to a target variable called `taxResult`.

4.  In the XML editor, add the Java arguments as a DataWeave expression:

    ```xml
    <java:args>#[{
            arg0: payload:price,
            arg1: payload:percentAdditionalTax
          }]</java:args>
    ```

Your XML code looks similar to this now:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:java="http://www.mulesoft.org/schema/mule/java" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
  http://www.mulesoft.org/schema/mule/java http://www.mulesoft.org/schema/mule/java/current/mule-java.xsd
  http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
  http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

  <http:listener-config name="HTTP_Listener_config">
    <http:listener-connection host="0.0.0.0" port="8081" />
  </http:listener-config>

  <flow name="java1">
    <http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/calculateTax" allowedMethods="POST"/>
    <java:new class="com.me.TaxCalculator" constructor="TaxCalculator()" target="taxCalculator" />

    <java:invoke instance="#[vars.taxCalculator]" class="com.me.TaxCalculator" method="calculateTax(Double, Integer)" target="taxResult">
      <java:args>#[{
        arg0: payload.price,
        arg1: payload.percentAdditionalTax
      }]</java:args>
    </java:invoke>
  </flow>
</mule>
```

### Add the Set Payload Transformer

To update the payload of the message, use the Set Payload (`set-payload`) component. The payload can
be a literal string or a DataWeave expression.

1.  In the canvas UI, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add
    component**) icon.

2.  In the **Add Component** panel, search for `Set Payload` and select it.

3.  Click the **Set Payload** component.

4.  On the **General** tab enter `#[vars.taxResult as String]` for the **Value**.

5.  For **Encoding**, select **ISO 10646/Unicode(UTF8)**.

6.  For **Mime type**, select **text/plain**.

Your XML code looks similar to this now:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:java="http://www.mulesoft.org/schema/mule/java" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
  http://www.mulesoft.org/schema/mule/java http://www.mulesoft.org/schema/mule/java/current/mule-java.xsd
  http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
  http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

  <http:listener-config name="HTTP_Listener_config">
    <http:listener-connection host="0.0.0.0" port="8081" />
  </http:listener-config>

  <flow name="java1">
    <http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/calculateTax" allowedMethods="POST"/>
    <java:new class="com.me.TaxCalculator" constructor="TaxCalculator()" target="taxCalculator" />

    <java:invoke instance="#[vars.taxCalculator]" class="com.me.TaxCalculator" method="calculateTax(Double, Integer)" target="taxResult">
      <java:args>#[{
        arg0: payload.price,
        arg1: payload.percentAdditionalTax
      }]</java:args>
    </java:invoke>

    <set-payload value="#[vars.taxResult as String]" doc:name="Set payload" doc:id="kyujdh" mimeType="text/plain" encoding="UTF-8"/>
  </flow>
</mule>
```

### Run Your Application in Debug Mode

After setting up your debug conditions, run a debug session and evaluate your Mule application at
each breakpoint:

1.  Open the Run and Debug panel.

    Show me how

    - Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-run-debug.png) (**Run and Debug**) icon
      in the activity bar.

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+d

      - Windows: Ctrl+Shift+d

    - Select **View** > **Run**.

2.  Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-start-debug.png) (**Start Debugging
    (F5)**) icon for **Debug Mule Application**.

    Alternatively, if the **Start Debugging (F5)** icon is not present:

    1.  Click **Run and Debug**.

    2.  If a **Select debugger** dropdown menu appears, select **Mule Xml Debugger** to initiate the
        debugging session:

        ![Run and Debug button and Mule XML Debugger menu item](/mulesoft/current/en-us/anypoint-code-builder/_images/run-debug-imported-folder.png)

        When the application deploys successfully, you see a `DEPLOYED` log message in the output
        panel:

        \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
        \* - - + DOMAIN + - - \* - - + STATUS + - - \*
        \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
        \* default \* DEPLOYED \*
        \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

> [!NOTE] Selecting **Run** > **Start without Debugging** produces an error.

Anypoint Code Builder packages your application and deploys the application to the embedded Mule
runtime engine. A terminal opens so you can view the status:

![Debugging status in a terminal window](/mulesoft/current/en-us/anypoint-code-builder/_images/deb-terminal-running.png)

The terminal displays a message and the status bar turns red to indicate that the application is
running.

Use buttons on the debug toolbar to control debugging of Mule applications.

## See Also

- [Anypoint Code Builder Overview](https://docs.mulesoft.com/anypoint-code-builder/)

- [Creating Integrations](https://docs.mulesoft.com/anypoint-code-builder/int-create-integrations)

- [Using Anypoint Code Builder to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-acb)

- [Anypoint Code Builder Components and Commands Reference](https://docs.mulesoft.com/anypoint-code-builder/acb-reference)

- [Defining and Securing Properties for a Mule Application](https://docs.mulesoft.com/anypoint-code-builder/int-create-secure-configs)

- [Triggering Flows in Your Development Environment](https://docs.mulesoft.com/anypoint-code-builder/int-trigger-flows)

- [Configuring Components](https://docs.mulesoft.com/anypoint-code-builder/int-configure-components)

- [Debugging Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps)

- [Salesforce Help](https://help.salesforce.com)

[Java Module Reference](https://docs.mulesoft.com/java-module/latest/java-reference)