Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 TIBCO BusinessConnect Architecture : Private Processes

Private Processes
Private processes in TIBCO BusinessConnect refer to the internal processes within your company. Private processes send data to the TIBCO BusinessConnect server or receive data from the TIBCO BusinessConnect server, and communicate using TIBCO Rendezvous (Rendezvous Certified Messaging RVCM) or JMS.
TIBCO Rendezvous
TIBCO Rendezvous subject names, the aeRvMsg message format, and Rendezvous Certified Messaging (RVCM) are described in the following sections.
TIBCO Rendezvous Subject Names
All TIBCO Rendezvous messages have a unique subject name. This applies to interactions on both the Initiator and Responder side.
The following are the subject name formats:
Example: AX.BC.BC-ACME.EZComm.INITIATOR.REQUEST
Example: AX.BC.BC-ACME.EZComm.INITIATOR.RESPONSE
Example: AX.BC.BC-ACME.EZComm.RESPONDER.REQUEST
Example: AX.BC.BC-ACME.EZComm.RESPONDER.RESPONSE
Example: AX.BC.BC-ACME.EZComm.RESPONDER.ACK
Error notification:
Property name:
errorNotifySubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EZComm.ERROR
TIBCO Rendezvous publishes this message globally, but a private process can also listen to it.
The following is a key to the italicized terms above:
prefix: The product or domain name. The default is AX.BC. This refers to TIBCO BusinessConnect (BC) on TIBCO ActiveExchange (AX). The installation and the prefix uniquely identify messages exchanged between an external private process and TIBCO BusinessConnect.
This is displayed in the Installation Prefix field under BusinessConnect > System Settings > General. For example, AX.BC.
installation: The installation name. This is displayed in the Installation Name field under BusinessConnect > System Settings > General. For example, BC-ACME.
standardID: The business protocol. For example, EZComm.
fixed: TIBCO BusinessConnect determines this internally depending on the type of message. The following are the only possible values:
aeRvMsg Message Format
Messaging between private processes and TIBCO BusinessConnect uses the aeRvMsg format. The aeRvMsg message format is the TIBCO BusinessConnect standard message format. This section provides a brief overview of aeRvMsg. For more information on aeRvMsg, see TIBCO Adapter SDK Concepts.
When a private process or TIBCO BusinessConnect uses the aeRvMsg format to package data before sending the data to each other, the data is packaged in an envelope called the message control block. The ^pfmt^, ^ver^, and ^type^ message control block tags allow these components do extra validation on messages.
The aeRvMsg format is shown in Table 1:
In this message format, the ^pfmt^, ^ver^, and ^type^ tags precede the message, which is carried in the ^data^ tag. In turn, within the ^data^ tag, the actual data is carried in the request or response field.
Rendezvous Certified Messaging (RVCM)
When an internal application, such as an ERP system, generates a document (request, acceptance, or notify), the private process translates the raw Rendezvous message in an appropriate format and forwards it to the TIBCO BusinessConnect server.
The TIBCO BusinessConnect server, in active state and running, waits for any RVCM message that will arrive on the subject name on which it is listening. After the message is received, the server expects it to conform to a certain structure. Therefore, it is the job of the private process to send a message in a proper format so that the server can process it; it is also the job of the private process to receive a RVCM message from the server and process it accordingly.
For more information about RVCM, please refer to the TIBCO Rendezvous documentation about Distributed Queues and Certified Messaging.
JMS Transport
JMS message format and secure JMS transport are described in the following sections.
JMS Message Format
JMS messages consist of several properties and header fields that help a processing agent, such as TIBCO BusinessConnect Palette, to dispatch the messages to the corresponding listeners. The destination of the messages is: PREFIX.INSTALLATION.MESSAGETYPE_SPECIFIC_SUFFIX. For example, AX.BC.MYSERVER.RESPONDER.REQUEST
Notice the following differences compared to TIBCO Rendezvous:
Subject names   JMS destinations are not accompanied with the business protocol name. The suffixes are identical to the corresponding TIBCO Rendezvous message suffixes. Regarding the several different types of miscellaneous messages, the documentation of the individual business protocols provides more details.
JMSType    Mandatory. The format is <the name of the business protocol>. It is defined as standardID in the AE messages encoded by TIBCO Rendezvous.
JMSCorrelationID   Mandatory. It is either global, or the correlationID from the published Responder request message that was expecting a synchronous response.
operationID    Mandatory. This is the operation name of the business message, such as BC/1.0/Notify.
smartID    Optional. It only exists in messages sent from the TIBCO BusinessConnect server towards the private process. If Smart Routing is configured and the incoming message is smart routed, the smartID value is the Smart Routing ID that has been determined by the TIBCO BusinessConnect server during the message processing through the Private Process Smart Routing.
The payload (JMS message body), such as the AE message, is transferred as a serialized java.util.HashMap instance. This instance carries the names of the AE message fields in its key and the corresponding values in their values. The JMS-encoded message type is javax.jms.Object Message.
JMS Transport Types Used for Various Messages
Messages use the following JMS transport types:
See messages sent on destinations with suffixes INITIATOR.REQUEST, INITIATOR.RESPONSE, RESPONDER.REQUEST, and RESPONDER.RESPONSE,.
This behavior has the potential to be overridden by individual business protocols; if it is not specifically mentioned, the explained behavior should be assumed.
Secure JMS Transport
Figure 5 Secure JMS Transport Diagram
The secure JMS transport is closely integrated with the existing JMS transport on both the TIBCO BusinessConnect server and the private process side.
Generally, the capabilities are considered identical to those offered by TIBCO Enterprise Message Service.
The transport utilizes the SSL transport to provide security services (two-way authentication, integrity, and confidentiality) to the business layer. It is assumed that the secure transport configuration on the TIBCO Enterprise Message Service provider has been done prior to using the server and the palette where the secure JMS transport is configured.
To configure the secure JMS transport for TIBCO BusinessConnect, see TIBCO BusinessConnect Interior Server Administration Guide, JMS Transport.
For more guidelines on configuring secure JMS on TIBCO Enterprise Message Service, refer to TIBCO Enterprise Message Service User's Guide, Using the SSL Protocol.
In addition to these sources, details on the client side configuration concepts are available in TIBCO ActiveMatrix BusinessWorks Palette Reference, JMS Palette.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved