Accelerator Salesforce Global Orders System API

(0 reviews)


Each Accelerator implementation template in Exchange includes Bash and Windows scripts for building and deploying the APIs to CloudHub. These scripts depend on repositories, global settings, deployment profiles, and associated properties configured in the Maven settings.xml file.

Many templates can also be run from Anypoint Studio without having to customize the Run/Debug profiles. However, some templates make use of hidden deployment properties to protect sensitive information (e.g., passwords and secret keys). These properties must be supplied to the runtime by updating the configuration profile and adding them as VM arguments.


Ensure the Maven profile CloudHub-DEV has been properly configured in your settings.xml file. In particular, make sure the common properties for your environment have been provided (e.g., Anypoint Platform client ID and secret).

Required property overrides

At a minimum, the following properties must be customized to reflect the target deployment environment.

Property NameDescription
api.autodiscoveryIDRequired if using API Manager to secure this API
sfdc.usernameSalesforce Instance client user Name
sfdc.tokenSalesforce Instance client token
sfdc.passwordSalesforce Instance client password
sfdc.client-idThe Consumer Id of the Connected App in Salesforce
sfdc.client-secretThe Consumer secret of the Connected App in Salesforce

Running the application from Anypoint Studio

The following instructions are for running applications from Studio but apply to debugging as well.

  1. Update the src/main/resources/config/config-local.yaml file and provide values for the properties described above.
  2. Right-click the project and select Run As -> Mule Application (configure)
  3. If hidden deployment properties (e.g., Anypoint MQ credentials) are required, select the Arguments tab and add the property definitions to the VM arguments section. For example:
     -M-Dsfdc.password=<provide sfdc password>
     -M-Dsfdc.token=<provide sfdc token>
     -M-Dsfdc.username=<provide sfdc username>
     -M-Dsfdc.client-id=<provide sfdc client id>
     -M-Dsfdc.client-secret=<provide sfdc client secret>
     -M-Dsfdc.externalIdType=<provide externalId type>
  4. Click Run to launch the application.

To debug an application, choose Debug As -> Mule Application (configure) in the second step instead.

Deployment instructions for CloudHub

The following instructions apply to CloudHub deployments only.

  1. Update the config-dev.yaml properties as described above. You can also choose to add them to your settings.xml file instead.
  2. Use one of the following scripts to deploy application to CloudHub:

    • (Mac/Linux) or packageDeploy.cmd (Windows) - clean, build, and deploy the application
    • (Mac/Linux) or deployOnly.cmd (Windows) - deploy a previously-built application
  3. Bring up the Runtime Manager console in Anypoint and monitor the application for proper startup.

Next steps

Visit the Data mappings tab describes how the request and response data structures are mapped between the API interface and the Global Data DB.


Published by
MuleSoft Solutions
Published onMar 8, 2024
Asset overview

Asset versions for 1.0.x

Asset versions