![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
•
• Each secondary administration server must run on a different machine and have its own tibcoadmin_domain-name.tra file.
• If you make updates to the configuration using either the TIBCO Domain Utility (recommended) or by editing the tibcoadmin_domain-name.tra files, you must restart the administration server on each machine so the changes take effect.For example, if a TIBCO BusinessWorks process uses HTTP or HTTPS to communicate with TIBCO Administrator, when the primary administration server is unavailable, the process will be unable to communicate with the secondary server as it has different IP or hostname. In this case, the tibco.repourl property in the BusinessWorks process .tra file must be changed to point to the secondary server machine’s IP address or hostname.
• By default, all machines within an administration domain are expected to be in the same network subnet. You can, however, set up your system to use the TIBCO Rendezvous rvrd daemon so the server can communicate with machines on different subnets. See Administration Domain Spanning Subnets.
•
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |