Inbound and Outbound Document Flow

The inbound (responder) document flow for a RosettaNet document through the Sterling B2B Integrator is as follows:

Inbound Sequence: Description
1: A RosettaNet message is sent 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 RosettaNet Message Parser service to construct the header elements into process data and extracts the service content and attachments.
4: The RosettaNet Message Parser service parses and validates the entire message.
5: Based on the result of the parsing, the RNIF Parsing service decides whether to send an Acknowledgment or an exception.
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 (initiator) document flow for a RosettaNet document through the Sterling B2B Integrator is as follows:

Outbound Sequence: Description
1: Using a compiled map, the translator translates the document in the Sterling B2B Integrator format to the RosettaNet document and creates a Primary Document.
2: The initiator invokes a business process that assigns any Attachment Files.
3: The Transaction Initiator Private business process is invoked by the initiator business process to set the PIP/Transaction code and any other Contract information.
4: The RNIF Envelope business process is invoked to construct the Message Header elements.
5: The RNIF Attachment business process is invoked to loop through the attachment files and construct the necessary attachment elements.
6: The RosettaNet Message Builder service is invoked to create the actual message using the header elements that were created, the primary document, and the attachment file information.
7: The RNIF HTTP Send business process is invoked to send the message to the responder using the RN HTTP Server adapter.