It is important to select the best-suited integration technology for each of the identified integration requirements. The earlier section describes the different integration technologies and tools with recommendations on their use cases. Depending on the requirements for each integration, different technologies can be used. The following table explains the integration points shown earlier and the recommended integration technologies:
|
Integration point |
Description |
Recommended solution |
|
Product |
Products and attributes will be stored in operations and synced nightly with an e-commerce application as a flat file. |
Reccuring integration to on-premise flat file or common data services to synchronize product master.
|
|
Product on-hand |
Product on-hand needs to be shared with the e-commerce application in real time. |
RESTful Odata Services |
|
Price list |
The price list will be mastered in Finance and Operations and will be updated on the e-commerce application on a nightly basis as a flat file. |
Reccuring integration to on-premise flat file or common data services |
|
Customers |
The customer can be created or updated either on the e-commerce website (such as address) or updated in Finance and Operations (such as credit limit), and synced in both the systems. |
Common Data Service integration model |
|
Sales orders |
Sales orders will be created in the e-commerce application and created or updated to Finance and Operations. Sales order status updates such as shipment confirmation, invoices, and payment application need to be synced to the web application. |
Reccuring integration via RESTful APIs using Logic app or common data services |