Process Flows and Activity Types

This section describes in detail how TIBCO BusinessConnect™ Container Edition - RosettaNet Protocol processes PIP request or notify messages initiated by private processes as well as external trading partners.

Processing Private Process–Initiated PIPs

The following steps occur when TIBCO BusinessConnect Container Edition - RosettaNet Protocol processes trading private process–initiated PIP:

  1. A private process publishes a message of class BCRequestFromPP on an implementation of Java Message Service (JMS), such as TIBCO Enterprise Message Service.
  2. TIBCO BusinessConnect Container Edition - RosettaNet Protocol performs the following functions:
    • Retrieves the message from JMS.
    • Verifies the PIP code, PIP transaction ID, and participant data specified in the BCRequestFromPP message.
    • If configured, validates the XML-formatted request document.
    • Verifies the XML data in the request action against its configuration store and determine if the outbound request.
    • Constructs a RosettaNet request action message using information provided by the private process or from its configuration store, including the host and partner’s participant information, digital signature, and so on.
    • Wrap the RosettaNet request action message along with any attachments into a MIME-formatted envelope.
    • Establishes a connection at the trading partner’s URL with the appropriate transport protocol based on the business agreement settings, and posts the RosettaNet action message.
  3. TIBCO BusinessConnect Container Edition - RosettaNet Protocol waits for the request signal message (receipt acknowledgment) and resends the request action if necessary.
  4. Upon receiving the request signal from the trading partner, TIBCO BusinessConnect Container Edition - RosettaNet Protocol performs the following functions:
    • Decrypts and authenticates the request signal.
    • If configured, validates the XML-formatted request signal.
    • Verifies the XML data in the request signal (except for the Supply Chain Code and Partner Classification Code elements).
    • Completes the transaction (in a notify transaction) or continutes waiting for the response action message from the trading partner (in a request-response transaction).
  5. Upon receiving the response action message, TIBCO BusinessConnect Container Edition - RosettaNet Protocol performs the following functions:
    • Decrypts and authenticates the response action.
    • If configured, validates the XML-formatted response action.
    • Verifies the XML data in the response action (except for the Supply Chain Code and Partner Classification Code elements).
    • Establishes a connection at the trading partner’s URL with the appropriate transport protocol based on the business agreement settings, and sends a response signal message (receipt acknowledgment) to the trading partner.
    • Formats the response into a BCResponseToPP message and publishes the message on JMS.
    • Completes the transaction.
  6. The private process retrieves the BCResponseToPP message from JMS and processes it.
Note: If an error occurs at any point in the process, TIBCO BusinessConnect Container Edition - RosettaNet Protocol terminates the transaction and sends an ErrorNotify message on JMS for the private process with the error information.

Processing Trading Partner–Initiated PIPs

When TIBCO BusinessConnect Container Edition - RosettaNet Protocol processes trading partner–initiated PIP, the following actions occur:

  1. Upon receiving a PIP request action message, TIBCO BusinessConnect Container Edition - RosettaNet Protocol performs the following functions:
    • Decrypts and authenticates the request action.
    • If configured, validates the XML-formatted request action.
    • Verifies the XML data in the request action against its configuration store and determine if the inbound request is allowed (except for the Supply Chain Code and Partner Classification Code elements).
    • Establishes a connection at the trading partner’s URL with the appropriate transport protocol based on the business agreement settings, and sends a request signal message (receipt acknowledgment) to the trading partner.
    • Formats the request action into a BCRequestToPP message and publishes the message along with attachments on JMS.
  2. For a notify transaction, TIBCO BusinessConnect Container Edition - RosettaNet Protocol completes the transaction. For a request-response transaction, it waits for a BCResponseFromPP message from the private process.
  3. The private process retrieves the BCRequestToPP message from JMS and processes it. If the request action is for a request-response transaction, it must respond by publishing a BCResponseFromPP message on JMS.
  4. TIBCO BusinessConnect Container Edition - RosettaNet Protocol retrieves the response from JMS and performs the following functions:
    • Verifies the PIP code, PIP transaction ID, and participant data specified in the BCResponseFromPP message.
    • If configured, validates the PIP response document in the message.
    • Verifies the XML data in the response action against its configuration store.
    • Constructs a RosettaNet response action message using information provided by the private process or from its configuration store, including the host and partner’s participant information, digital signature, and so on.
    • Wrap the RosettaNet response action message along with any attachments into a MIME-formatted envelop.
    • Establishes a connection at the trading partner’s URL with the appropriate transport protocol based on the business agreement settings, and sends the response action message to the awaiting trading partner.
    • Waits for a response signal message (receipt acknowledgment) from the trading partner and resends the response action message if necessary.
  5. Upon receiving the response signal message, TIBCO BusinessConnect Container Edition - RosettaNet Protocol performs the following functions:
    • a. Decrypts and authenticates the response signal.
    • b. If configured, validates the response signal.
    • c. Verifies the XML data in the response signal against its configuration store (except for the Supply Chain Code and Partner Classification Code elements).
    • d. Completes the transaction.
Note: If an error occurs at any point in the process, TIBCO BusinessConnect™ Container Edition - RosettaNet Protocol terminates the transaction and sends an ErrorNotify message on JMS for the private process with the error information.