Inbound and Outbound Document Flow
The inbound document flow for a CIDX document through Sterling B2B Integrator is as follows:
- Inbound Sequence
- Description
- 1
- A CIDX message is received using HTTP.
- 2
- The RN HTTP Server adapter is configured to invoke the Bootstrap business process when a message arrives.
- 3
- The RNIF Deenvelope business process invokes the RN Parsing service to construct the header elements into process data and extract the service content.
- 4
- The RNIF Parsing service parses and validates the entire message.
- 5
- Based on the result of the parsing, the RNIF Parsing service decides either to send an acknowledgement or exception. Additionally, the RNIF Parsing Service sends a HTTP Response status code to the initiator of the message (via HTTP).
- 6
- The Transaction Responder Private business process is invoked to determine if the message is a two-action PIP.
- 7
- If the transaction is a two-action PIP, the responder sends the response Action Message to the initiator.
The outbound document flow for a CIDX document through Sterling B2B Integrator is as follows:
- Outbound Sequence
- Description
- 1
- Using a compiled map, the translator creates the CIDX document and this document is used as primary document.
- 2
- The Transaction-specific Initiator Private business process is invoked by setting the PIP/Transaction code and any other Contract information.
- 3
- The RNIF Envelope business process is invoked to construct the Message Header elements.
Note: Message building refers to creating message headers and bundling them with the actual payload (the service content of the message).
- 4
- The RNIF Message Builder service is invoked to create the actual message using the header elements that were created, the primary document.
- 5
- The RNIF HTTP Send business process is invoked to send the message to the responder using the RN HTTP Server adapter.