Академический Документы
Профессиональный Документы
Культура Документы
• 1. Use RVRD binaries to transfer the domain related RV messages (for an RV based domain) between the
different subnets.
• 2. Use EMS as the domain transport.
• 3. Have the machines on the remote subnet connect to an RV daemon on the Administrator subnet.
Note that option 3 is NOT recommended and is included in the above list for completeness.
This option has a number of known issues which include:
• The tibhawkhma binary will not start on one of the machines so the status of that machine will not be
reported correctly.
• Inappropriate microagents will be loaded if the two machines are using different operating systems.
Using RVRD
There needs to be at least one RVRD binary running on the Admin network and one running
on each separate remote network. However, it is recommended to have two RVRD binaries
running on each network, one for domain Hawk traffic and one for domain data traffic.
There are details about setting up RVRDs in the TIBCO Rendezvous Administration
documentation - chapter 5, Routing Daemon.
_HAWK.>
com.tibco.repo.>
com.tibco.pof.>
If a secondary server is used within the domain (on a different subnet from the primary
Admin server)
_RVFT.>
_RVCM.>
_RVCMQ.>
If there are applications listening/sending on specific subjects then these will also need to be
imported/exported.
Using EMS
If EMS is used as the transport then no additional setup is required above what would
normally be needed for adding a machine to an EMS based domain. Note however, that
client machines do need to be able to access both the EMS server and the database that
stores the domain data.
Document References
TIBCO Rendezvous documentation (this can be found in the directory
<TIBCO HOME>/tibrv/doc
Troubleshooting
• Diagnosing communication issues
For an RV based domain, try using tibrvlisten/tibrvsend, which can be found in the
RV_HOME/bin directory. Test each of the subjects listed previously and try sending
messages in both directions across the RVRD bridge.
• Stopping timeout messages from occurring when trying to deploy to a remote machine.
<Admin Home>/domain/<domainName>/bin/tibcoadmin_[domainName].tra
You can check the setup of the RVRD configuration by running the command:
The output will look similar to the content in the text box below.
2009-02-10 16:33:43 rvrd: Logging: Connections - On, Subject Interest - Off, Subject Data
- Off.
If there is a communication issue within the domain then open an SR with TIBCO Support
and upload the following:
• If RVRD is in use, the RVRD xml configuration, which can be obtained from the RVRD user interface, and
the results of using tibrvlisten/tibrvsend between the two subnets.
• The RVRD store file, the location and name of which will be defined on the RVRD command line.
• <TRA HOME>/domain/<domainName>/logs/administrator.log
• The Administrator console output.
• <TRA HOME>/domain/<domainName>/logs/hawk.log
• <TRA HOME>/domain/<domainName>/logs/hawkagent.log
• <TRA HOME>/domain/<domainName>/logs/tsm.log
• <TRA HOME>/domain/<domainName>/logs/administrator.log