MFG SAP Event Listener - Implementation Template

This asset is used in the following MuleSoft Accelerators:

• MuleSoft Accelerator for Manufacturing

The solution unlocks rich data between SAP, Salesforce Manufacturing Cloud, Salesforce Rebate Management, Amazon Redshift, Tableau, and Salesforce Service Cloud with pre-built APIs, templates, reference architecture, and additional technical assets for manufacturing companies. 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.

---

Overview

The Manufacturing SAP Event Listener application is used to listen on for customer, order and product outbound event messages. The outbound message is converted to appropriate object in CIM format and published to Anypoint MQ to sync the necessary changes to other systems.

Getting started

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.

Prerequisites

This implementation template has the following dependencies:

• Anypoint MQ Destinations
• SAP HANA Products System API

Please review the use cases described on the MuleSoft Accelerator for Manufacturing solution pages for more information about dependencies on other APIs and services.

API dependencies

The following table lists all endpoints used by this API (assuming all syncronization targets are enabled).

Anypoint MQ destinations

In addition to the Anypoint MQ client application credentials, the following destinations must be created and made accessible to this API:

1. mfg-slsorder-update-exchange
2. mfg-slsorder-update-dl-queue
3. mfg-customer-update-exchange
4. mfg-customer-update-dl-queue
5. mfg-product-update-exchange
6. mfg-product-update-dl-queue

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. 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.

Preparation

Ensure the Maven profile CloudHub-MFG-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.

Additional resources

• The Data mappings describes how the request and response data structures are mapped between the API interfaces.
• Refer to the Accelerators documentation home for more information about the MuleSoft Accelerators.