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


Chapter 3 Private Process Configuration : TIBCO Rendezvous

TIBCO Rendezvous
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 XML string has a single message attribute and looks like this:
<?xml version="1.0" encoding="UTF-8"?>...rest of document in XML.
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.
Configuring TIBCO Rendezvous
To configure TIBCO Rendezvous settings for private processes, do the following:
1.
BC-domain_name.PP_CM (pre-populated)
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.installation_name.standardID.INITIATOR.REQUEST
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.
installation_prefix.installation_name.standardID.INITIATOR.RESPONSE
installation_prefix.installation_name.standardID.RESPONDER.REQUEST
installation_prefix.installation_name.standardID.RESPONDER.RESPONSE
2.
Intercomponent Communication Rendezvous Settings
Intercomponent Communication Rendezvous settings are used within the Interior Server for its various sub-components, such as process starters, poller triggers, and intracomponent communications.
Settings are described in:
Gateway Engine
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.
Interior Server
If there are differences in the network part of the network parameter between TIBCO Administrator and the Interior Server machines, the following properties must be added along with multicast group to each of the Interior Server engine .tra files.
The values entered should follow the same rules used for creating the Rendezvous transport. This is used when other than the default is being set for the network part, and an appropriate value is set for the network parameter.
Following properties must be added and configured appropriately for the Interior Server Engine .tra files.
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/network=<nic|hostname|ip>;<multicast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/service=<value>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/daemon=<value>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh/network=<nic|hostname|ip>;<multicast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh/service=<value>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh/daemon=<value>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz/network=<nic|hostname|ip>;<multicast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz/service=<value>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz/daemon=<value>
TIBCO Administrator to Interior Server Peer Update Settings
TIBCO Administrator is not required to run on the same physical machine as the Interior Server and, in certain other usage scenarios, TIBCO Administrator could be running on a separate subnet not related to the subnets in which the Interior Servers are running (this includes TIBCO BusinessConnect Gateway and TIBCO BusinessConnect Interior Servers).
The Intercomponent JMS settings in the deployment UI will be used by TIBCO Administrator machine to send peer change to the TIBCO BusinessConnect Interior Server engines whenever there are changes made in the Administrator UI.
TIBCO Hawk, fault tolerant or default TIBCO Rendezvous parameters might need valid values set for the TIBCO BusinessConnect Server to start. Below are the parameters:

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