Setting up a Prima Solutions connection
Last updated
Last updated
Typically, connectors are defined with endpoints which determine exactly what data is being requested (pull customer records, post product details, etc.). However, the Prima Solutions connector works in a different way, with two generic endpoints:
comwsomhandler
wsomhandler
The actual data required for a request must be passed into the Prima Solutions connection shape, as part of your process flow. You do this via a manual payload shape.
Whatever is defined for the manual payload is passed into the body of the subsequent Prima Solutions connection request.
Finally - once a successful connection is made - the response must be converted from XML to JSON, ready for onward processing.
With this in mind, a process flow that needs to pull data from Prima Solutions will usually require three shapes in the following sequence:
Manual payload shape, which includes the required request data in an XML string
Connection shape, configured with a Prima Solutions endpoint
Script shape, configured with an XML to JSON conversion script
For example:
Request data to be passed into a Prima Solutions connection shape must be based on the Prima Web Services XML Schema Definition. Some examples are shown below.
Before the response from a Prima Solutions request can be be processed, it must be converted to a JSON payload. To do this, you should create an XML to JSON conversion script and add this to a script shape in your process flow.
