Integration Patterns

When using the DXO to move data between various backend systems, there are several integration patterns that can be employed. Depending on your use cases, you may use one or more of these. Some of the common scenarios include the following:

Syndicate product data from ERP and/or PIM to Commerce Engine
Push order data from commerce engine to OMS in real-time
Update the search index with changes from the pricing or inventory service
Send an email notification to the customer when an order is submitted
Update the CRM when a new customer is added through the Commerce Engine

Here are the various ways in which Conscia supports these scenarios.

Scenario	Update Type	Source	Destination	Conscia Process	Example Scenario	Details
1.1	Full	S3 Bucket, SFTP, or any other file system	Conscia Bucket	Conscia receives the file in the Bucket	Create a data extract from the ERP and push it to Conscia for further processing.	Customer pushes the file from source to Conscia bucket using Conscia API
1.2	Full	File in Conscia Bucket	File in Conscia Bucket	File gets dropped to Conscia Bucket, Job processes file and outputs to another file in the Conscia buckets after some data transformation.	The extract from ERP needs to be transformed before it is pushed to an external webservice. You want to see the output of the transformation before you send it to an external system.	Take a file from the bucket, transform it and write the new file to a bucket using this job type
1.3	Full	File in Conscia Bucket	External Webservice Endpoint	Job processes file and writes to an external webservice endpoint. There is an ability to transform data on the way out.	Load product data directly into commerce engine, without first loading into the DX Graph for analysis and validation.	"Done in two steps 1) Load data to a file (see above). 2) Write data to a webservice using Call Webservice Job Type
1.4	Full	File in Conscia Bucket	DX Graph Collection	File gets dropped to Conscia Bucket, Job processes file and writes to a DX Graph.	Download data from PIM and load it into the DX Graph for further enrichment and validation.	Learn how to load data into the DX Graph from a file here
1.5	Full	External Webservice Endpoint	File	Job pulls data from a webservice endpoint and writes to a file in a bucket.	Full product catalog download from PIM	Learn how to pull data from a webservice endpoint to a file here
1.6	Full	External Webservice Endpoint	DX Graph Collection	Job pulls data from a webservice endpoint and writes to DX Graph.	Full product catalog download from PIM	Learn how to pull data from an external webservice and import it into the DX Graph collection here
1.7	Full	DX Graph Collection	File	Job exports data from DX Graph Collection and Writes to a File.	Export invalid records from the DX Graph to a file so that the data owners can correct the issues in the source systems.	Learn how to export data from the DX Graph Collection to a file here
1.8	Full	DX Graph Collection	External Webservice Endpoint	Job pulls from DX Graph Collection and Writes to the Webservice Endpoint.	You want to validate the product information from the ERP before writing it to a downstream commerce engine or a search index.	Two Steps: 1) Pull Data from Webservice to a file 2) Push from file to a webservice using the 'Process Data File with Webservice' job type
2.1	Partial	DX Graph Collection Event	Webservice Endpoint	DX Graph 'Record Updated Trigger' initiates a DX Engine Job Type, which can then write the record to an external system.	Update Search index if a product record gets updated in DX Graph	Define a Trigger for the 'Record Updated' Event Type. Specify the 'Call DX Engine' Job Type. Create a DX Engine template that implements the orchestration flow for updating the external system with the updated record. Note: If there is no need to transform the record first, you can use the 'Call Webservice' job type instead and call the external system endpoint directly.
2.2	Partial	External Webhook	DX Engine Listener	External Webhook calls the DX Engine Listener which then processes the updated record.	The record is updated in the Commerce Engine.	Create a listener in Conscia, Configure a webhook in the commerce engine to call that listener, Use the listener to call a specific Orchestration template.
2.3	Partial	DX Graph API	DX Graph	DX Graph API is called and the record within a DX Graph Collection is updated.	An External process such as an inventory service calls the DX Graph API with a CRUD operation.	Call DX Graph API directly.
2.4	Partial	DX Engine	External Webservice Endpoint	The Orchestration Template in the DX Engine writes a record to an external endpoint.	Order record updated in commerce engine -> Webhook calls Conscia Listener -> Conscia DX Engine writes to OMS.	External Webhook calls Conscia Listener -> Conscia DX Engine writes to an External Webservice.