![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO Rendezvous Subject Names
• Request from Initiator’s private process to the local TIBCO BusinessConnect:
Property name: requestFromPPSubject=prefix.installation.standardID.fixedExample: AX.BC.BC-ACME.EZComm.INITIATOR.REQUEST
• Response to Initiator’s private process from the local TIBCO BusinessConnect:
Property name: responseToPPSubject=prefix.installation.standardID.fixedExample: AX.BC.BC-ACME.EZComm.INITIATOR.RESPONSE
• Request to a Responder’s private process from the local TIBCO BusinessConnect:
Property name: requestToPPSubject=prefix.installation.standardID.fixedExample: AX.BC.BC-ACME.EZComm.RESPONDER.REQUEST
• Response from Responder’s private process to the local TIBCO BusinessConnect:
Property name: responseFromPPSubject=prefix.installation.standardID.fixedExample: AX.BC.BC-ACME.EZComm.RESPONDER.RESPONSE
• Acknowledgment of receipt of asynchronous request/response message:
Property name: ackToPPSubject=prefix.installation.standardID.fixedExample: AX.BC.BC-ACME.EZComm.RESPONDER.ACK
• Example: AX.BC.BC-ACME.EZComm.ERROR
TIBCO Rendezvous publishes this message globally, but a private process can also listen to it.
• 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:
− 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.
Table 1 The aeRvMsg Format 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.For more information about RVCM, please refer to the TIBCO Rendezvous documentation about Distributed Queues and Certified Messaging.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
• 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.
• See messages sent on destinations with suffixes INITIATOR.REQUEST, INITIATOR.RESPONSE, RESPONDER.REQUEST, and RESPONDER.RESPONSE,.
• Miscellaneous messages, such as error advisories with the suffix ERROR, use a JMS topic transport type, except for the RESPONDER.ACK advisory which uses a JMS queue transport type.Figure 5 Secure JMS Transport Diagram
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 |