This asset is a component of the following MuleSoft Accelerators:
These solutions accelerate the implementation of essential integration use cases with pre-built APIs, templates, and reference architectures. Our foundational assets are expertly designed to jumpstart your top integration and business initiatives so that IT teams can spend more time innovating and less time building from scratch.
This integration template implements the RCG SAP S/4 HANA Products System API specification. It can be used to retrieve, create, and update Products.
|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.
Please review the use cases described on the MuleSoft Accelerator for Retail and MuleSoft Accelerator for Consumer Goods solution pages for more information about dependencies on other APIs and services.
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|
|sap.hana.url||SAP S/4HANA URL|
|sap.hana.user||SAP S/4HANA Username|
|sap.hana.password||SAP S/4HANA Password|
|sap.businessUser||SAP S/4HANA Business user|