Salesforce Integration using Azure Integration Services

In this Blog, it shows the detailed information for integration between SAP B1 to Salesforce. The AIS Interface is intended to Extract, Transform and Route the data from SAPB1 to Salesforce. The steps for integration would be same for different entities.

Event Scenario

Pre-Requisites:

1. Create API management and create APIs for specific entities.
2. Create Service Bus and Subscriptions inside Service Bus.
3. Create Function App and Service Bus topic triggered function app.
4. Create App Configuration.
5. Create Application insight for monitoring the logs.
6. Create Storage Account.

Process Steps:

1. SAP B1 authenticates with AIS using Bearer Token and sends a HTTP request for different entities data using PUT method to AIS endpoint.
2. Based on Policies configured in AIS the message (along with Method, Entity and Payload) is routed to specific subscription of a service bus topic.
3. A Service Bus Topic Triggered Azure Function listens to the Topic Subscription on active messages being present in it.
4. This Azure Function converts it into a specific consumer format and sends it to Consumer i.e. Salesforce endpoint.
5. Consumer in turn returns the status code back to Azure Function.

On Demand Load Scenario

Pre-Requisites:

1. Create Logic App.
2. Create API management and create APIs for specific entities.
3. Create Service Bus and Subscriptions inside Service Bus.
4. Create Function App and Service Bus topic triggered function app.
5. Create App Configuration.
6. Create Application insight for monitoring the logs.
7. Create Storage Account.

Process Steps

1. Based on an on-demand triggered Logic App a HTTP request is sent to SAP B1 endpoint in order to get entity data at a time.
2. SAP B1 returns the specific entity data. Sends a HTTP request for different entities data using PUT method to AIS endpoint.
3. Based on Policies configured in AIS the message (along with Method, Entity and Payload) is routed to a specific subscription of a service bus topic.
4. A Service Bus Topic Triggered Azure Function listens to the Topic Subscription on active messages being present in it.
5. This Azure Function converts it into a specific consumer format (composite request) and sends it to Consumer i.e., Salesforce endpoint.
6. Consumer in turn returns the status code back to Azure Function.

Based on the above Integration scenarios Azure Developer can easily navigate for the integration implementation and they can choose between Event Driven or On-Demand based on the business requirement.

We are just getting started with Azure Integration Services and stay tuned for more in this series.