Private Processes

Microsoft BizTalk 2009 Accelerator for RosettaNet (BTARN) implements business processes that are internal to an organization as private processes. Public processes handle business processes that involve integration with trading partners. BTARN isolates service-content processing and back-end integration (in the private process) from RosettaNet Implementation Framework (RNIF) handling (in the public process).

BTARN implements private processes as long-running BizTalk orchestrations. BTARN uses one private-process orchestration on the initiator side and one on the responder side. Each private process interprets and processes the service-content message part, either incoming or outgoing. The private process sends the service content to, or receives it from, the public process. A private process does not handle headers, and does not perform RNIF processing. It leaves that to the public process.

In an enterprise scenario, there would typically be one private process for each PIP message schema. However, the BTARN SDK includes two private-process orchestrations that can process any PIP message. One orchestration is for the initiator process (PrivateInitiator.odx, see PrivateInitiator Sample [RN3]) and one is for the responder process (PrivateResponder.odx, see PrivateResponder Sample [RN3]). You will have to customize the private processes to adapt BTARN to your specific business processes.

The SDK also includes a process that implements a PIP-specific private responder process incorporating a business rule (PIP3A4PrivateResponder.odx, see 3A4 Private Responder Orchestration Using a Business Rule).

The private process changes the format of the service content from the back-end line-of-business (LOB) format to XML. As soon as it is in XML format, BTARN processes the service content, and the public process adds RNIF-compliant headers to the service content for transmission.

The private process connects to the back-end line-of-business applications through the MessageToLOB and MessagesFromLOB tables in the BTARNDATA SQL Server database. This database handles the communication between BTARN and the LOB applications. The LOB application uses an interface to gain access to the database tables.

Community Additions