SPS_SHIP Message
An SPS_SHIP message is configured for shipments originating within PRECISION. This message is sent into Highway. As part of this message, you specify the workflow used to process the shipment. The shipment type drives the denied parties and keywords to be checked when these form part of the compliance workflow task. These compliance partner types are set up in ZS, as described in the section
Shipment Types for the DPL Check.
<TRAXWorkflow>Z3</TRAXWorkflow>
<TRAXPrinter />
<TRAXLocale>QPSLBB</TRAXLocale>
<ShipmentType>Z3</ShipmentType>
You also specify the workflow task to use to run compliance. The workflow task referenced here—SOA_COMP— contains the list of tasks to run and details of the Highway configuration. At this point, the system builds another message named processcompliance.xml for the compliance engine.
<Parameters>
<Parameter>
<Name>TASK-ID</Name>
<Value>SOA_COMP</Value>
</Parameter>
</Parameters>
</Action>
<Action>
<Sequence>20</Sequence>
Specify the compliance results task to run and choose a result format. The result format set up here should match the result format in the workflow task.
<Type>COMPLIANCE-RESULTS</Type>
<Parameters>
<Parameter>
<Name>RESULT-FORMAT</Name>
<Value>SHORT</Value>
A response message—SPS_Response— is then sent back with embedded compliance results in the selected result format.
Note: For the createshipment.xml message to be processed successfully, the Progress 4GL listener must be enabled and polling the correct Highway endpoint where the compliance message is moved for processing. In the default setup provided, the message is moved to the endpoint SPSBB where it is picked up by the Progress 4GL listener.