This API implementation template is a component of the MuleSoft Accelerator for Consumer Goods, which accelerate the implementation of essential integration use cases.
The solution includes pre-built APIs, connectors, and integration templates that help unlock business-critical data from external systems and guide you in adopting best practices synthesized from thousands of customer implementations. Use these assets as is or extend them to meet your company’s unique needs.
This integration template implements the Salesforce Volume Management System API specification, It can be used to create, retrieve, and delete baseline data on a weekly or daily frequency, and in either integer or decimal type.
|The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.
Once your workstation has been set up and the application template imported into Anypoint Studio, proceed with the Prerequisites section.
This implementation template has the following dependency:
- Measure templates must be registered in advance by using RCG Salesforce Volume Management System API
Note: In a single transaction, only one type of measurecode can be sent with messages. Separate transactions must be used to send different types of measures.
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. In particular, make sure the common properties for your environment have been provided in the
CloudHub-DEV profile (e.g., Anypoint Platform client ID and secret).
For additional details, please refer to the Application Deployment section of the Getting Started Guide.
Ensure the Maven profile
CloudHub-RCG-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
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. At a minimum, the following properties must be customized to reflect the target deployment environment.
|api.autodiscoveryID||Required if using API Manager to secure this API|
|hyperforce-system.get-token.host||Hostname of of Connected App.|
|hyperforce-system.get-token.grant_type||Grant Type for token service.|
|hyperforce-system.get-token.client_id||Consumer Key of Connected App.|
|hyperforce-system.get-token.client_secret||Consumer Key of Connected App.|
|hyperforce-system.get-token.username||Username of Connected App.|
|hyperforce-system.get-token.password||Password of Connected App.|
|hyperforce-system.generic.host||Hostname of third party integration url.|
|management-api.host||Hostname of the volume management API.|