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


Appendix C Deployment Tuning : Tuning Interior Server Deployment

Tuning Interior Server Deployment
Deploying the Interior Server on two Subnets
In general, it is recommended that a B2B deployment be located entirely within one single subnet for simplicity. Figure 10 shows deployment on one subnet.
Figure 10 TIBCO BusinessConnect Deployed on One Subnet
In a B2B deployment where the Gateway Server is residing on an isolated and dedicated machine, for security reasons the Gateway Server and the Interior Server are located on different subnets. In this case, it is required to have a pair of RVRDs (TIBCO Rendezvous routing daemons) to pull messages from the Gateway Server into interior subnet (Figure 11).
Figure 11 Gateway Server and Interior Server Deployed on Two Subnets
In addition to deploying the Gateway Server on a separate subnet, it is very common to separate private processes on their own subnet for better de-coupling of functional areas (Figure 12).
Figure 12 Private Processes Deployed on a Separate Subnet
It is also possible to further break up subnet 2 in order to place TIBCO Administrator in its own subnet (Figure 13).
Figure 13 TIBCO Administrator Deployed on a Separate Subnet
In order to ensure that messages are sent and received correctly by the TIBCO BusinessConnect engine, these RVRD processes must be configured to route the following messages: installation_prefix.>
For example, AX.BC.ACME.>
The TIBCO Rendezvous service should follow the value established for the service in Intercomponent Communication > Interior Settings > Service.
Modifying Load Balancing Properties
There are two different RVCM queues used to achieve load balancing:
In addition to specifying load balancing properties using the TIBCO BusinessConnect GUI, you can edit them directly in the following file:
BusinessConnect-Interior_Server.tra
This file is located in the directory such as:
tra_home\domain\domain_name\application\BusinessConnect
(For Windows) C:\tibco\tra\domain\domain_name\application\BusinessConnect
DMZ to Interior Queue
The properties for the DMZ to Interior inbound Queue are as follows:
To override the defaults follow these instructions:
1.
Edit the BusinessConnect-Interior_Server.tra file located in the tra_home\domain\domain_name\application\BusinessConnect directory.
tra_home is the directory where TIBCO Runtime Agent is installed.
domain_name is the name of the domain in which TIBCO BusinessConnect is installed and deployed.
For the definitions of RVCMQ, Worker Weight, Scheduler Weight, and other values used in this document, please refer to the TIBCO Rendezvous Distributed Queue documentation.
2.
Modify the properties in the BusinessConnect-Interior_Server.tra file as required. These properties should be modified in the BusinessConnect-Interior_Server.tra file every time TIBCO BusinessConnect is deployed or redeployed.
Private Process to Interior Queue
The properties for the Private Process to Interior Queue are as follows:
Scheduler Weight for Outbound scheduler
To override the defaults follow these instructions:
1.
Edit the BusinessConnect-Interior_Server.tra file located in the tra_home\domain\domain_name\application\BusinessConnect directory.
tra_home is the directory where TIBCO Runtime Agent is installed.
domain_name is the name of the domain in which TIBCO BusinessConnect is installed and deployed.
For the definitions of RVCMQ, Worker Weight, Scheduler Weight, and other values used in this document, please refer to the TIBCO Rendezvous Distributed Queue documentation.
2.
Modify the properties in the BusinessConnect-Interior_Server.tra file as required. These properties should be modified in the BusinessConnect-Interior_Server.tra file every time TIBCO BusinessConnect is deployed or redeployed.

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