![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
When using TIBCO Rendezvous, messaging is performed through RVCM (TIBCO Rendezvous Certified Messaging) using the TIBCO BusinessConnect aeRvMsg standard message format (see TIBCO BusinessConnect Concepts, aeRvMsg Message Format).The request or response field in a message that a private process sends or receives contains an unparsed message.An unparsed non-XML message can have any form. For example, in an aeRvMsg request message, the ^data^ tag contains the following fields:
• transactionID Describes the transaction ID.
• operationID Describes the operation ID.
• request Describes the request itself. This is usually an XML string representing the message body or a TIBCO Rendezvous representation of an XML file. This is the original message that was first generated by the private process when it was contacted by the Initiator’s application.
• closure Describes a closure object to be copied from the private process to the response.
PP_CM.ldg (pre-populated BC-domain_name.pp-cmq See TIBCO Rendezvous Concepts, Scheduler Parameters for more details. See TIBCO Rendezvous Concepts, Scheduler Parameters for more details. installation_prefix and installation_name are configured under BusinessConnect > System Settings > General tab. The standard ID is the protocol ID, such as EZComm, SOAP, and so on. Communication between the Gateway Engine and Interior Server is configured at the BusinessConnect > Gateway > Gateway Tokens tab in the Advanced section, where each file carries the intercommunication JMS.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |