RCG Product Process API - Implementation Template
Deployment
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.
Preparation
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
At a minimum, the following properties must be customized to reflect the target deployment environment.
| Property Name | Description |
|---|---|
| api.autodiscovery-id | Required if using API Manager to secure this API |
| products-prc-api.http-client.client-id | Client Id provided for Products Process API to interact with all System API's |
| products-prc-api.http-client.client-secret | Client Secret provided for Customer Process API to interact with all System API's |
| mdm-sys.host | MDM System API Instance Hostname |
| mdm-sys.port | MDM System API Instance Port |
| mdm-sys.base-path | MDM System API Instance base path |
| salesforce-b2b-products-sys.host | Salesforce System API Instance Hostname |
| salesforce-b2b-products.port | Salesforce System API Instance Port |
| salesforce-b2b-products.base-path | Salesforce System API Instance base path |
| sap-hana-sys-sys.host | SAP S/4 HANA System API Instance Hostname |
| sap-hana-sys.port | SAP S/4 HANA System API Instance Port |
| sap-hana-sys.base-path | SAP S/4 HANA System API Instance base path |
| b2c-commerce-sys.host | B2C Commerce System API Instance Hostname |
| b2c-commerce-sys.port | B2C Commerce System API Instance Port |
| b2c-commerce-sys.base-path | B2C Commerce System API Instance base path |
| ofbiz-products-sys.host | OFBIZ Products System API Instance Hostname |
| ofbiz-products-sys.port | OFBIZ Products System API Instance Port |
| ofbiz-products-sys.base-path | B2C Commerce System API Instance base path |
| salsify-products-sys.host | Salsify System API Instance Hostname |
| salsify-products-sys.port | Salsify System API Instance Port |
| salsify-products-sys.base-path | Salsify System API Instance Base path |
| cgcloud-products-sys.host | Salsify System API Instance Hostname |
| cgcloud-products-sys.port | Salsify System API Instance Port |
| cgcloud-products-sys.base-path | Salsify System API Instance Base path |
| anypoint-mq.server-url | Anypoint MQ URL where the message Exchange, Topics, queues have been created |
| anypoint-mq.client-id | Anypoint MQ Client Id to access messages from MQ |
| anypoint-mq.client-secret | Anypoint MQ Client Secret to access messages from MQ |
Running the application from Anypoint Studio
The following instructions are for running applications from Studio but apply to debugging as well.
- Update the
src/main/resources/config/config-local.yamlfile and provide values for the properties described above. - Right-click the project and select
Run As -> Mule Application (configure) - If hidden deployment properties (e.g., Anypoint MQ credentials) are required, select the
Argumentstab and add the property definitions to theVM argumentssection. For example:-M-Danypoint-mq.client-id=<client id> -M-Danypoint-mq.client-secret=<client secret> - Click
Runto launch the application.
To debug an application, choose Debug As -> Mule Application (configure) in the second step instead.
Next steps
Visit the Data mappings tab to learn more about how the request and response data structures are mapped between the API interface and other API's.