System integration patterns
note
This article describes the legacy service Norce [Storm] Event, and how it works.
For the Norce Commerce Event feature, check the new article.
Get data from Norce Commerce
When you want to create or update data in other target systems based on data in Norce Commerce, Norce Commerce Query and [Storm] Event is used. The integration is triggered from Norce [Storm] Event, that your integration subscribes to for the event types you are interested in. What you get is a small message containing only identifiable information for the item that is created or changed, and you must then lookup the data in Norce Commerce Query. Read about calling Norce Commerce Query here and using Norce [Storm] Event here.
Responsibilities of your integration
The integration is responsible for:
- Receive events and handle commit and/or cancel the transaction from Azure Service bus
- Map and pass data to the target system
- Look up relevant data from Norce using Norce Commerce Query, in a way that makes the solution perform well
Subscribe and listen to Norce Commerce Event's
In the Admin UI you can configure the event types you are interested in, see here.
The message you receive has the event metadata described in the event detail tab in admin. This is commonly the clientId and applicationId (where it is applicable). The specific identifiers for the item you are interested in, for example CustomerId or product PartNo. These lets you lookup the information you need from Norce Commerce query. Lastly you also get an EntityChanged property, that describes a bit more what has happened that makes the event trigger.
Note
- Read about using Norce [Storm] Event .
- Read about the Norce Commerce Event Setting and EntityChanged property here .
Lookup item data in Norce Commerce Query
Norce Commerce Event will give out the item id’s (whereas it is Customer, Product or anything else) for you to use when fetching the data from Norce Commerce Query. With Norce Commerce query, you are able to only fetch the data your target system needs instead of handling large complex contracts of information.
- Use local cache when appropriate to have a high performing solution.
- Use the examples in the Postman collection to get you started setting up the integration.
Note
- Read about Calling Norce Commerce Query .
- Examples on Norce Commerce Query for different use cases are here .
Map and send data to target system
After fetching the data from Norce Commerce Query, the next step is to pass it to the target system(s). How this is done is left to the integration developer dependent on how the target system needs the data.