This is about the configuration and the implementation details for Administrator Fault Tolerant SetUp.
TIBCO Administrator is widely used to deploy BW processes to different machines in the domain.
If the Administrator server is down for some maintenance or hardware related Issues the deployment cannot happen and roll out dates will be affected.
To over come this problem TIBCO has provided the feature of fault Tolerant setup
1. Product Versions
Fault Tolerant SetUp is provided with TRA Versions 5.2 and above.
The XMLs are available under
$TRA_HOME/5.6/template/domainutility/cmdline folder.(modify the XMLs to the current environment.)
2. Configuration
This section talks about the configuration steps.
1.Install Administrator on the secondary server
2.Run create domain script on the secondary server
cd /apps/tibco/tra/5.6/bin>
. /domainutilitycmd –cmdFile /apps/tibco/CreateDomain.xml
3. Run Add Secondary script on the secondary server
cd /apps/tibco/tra/5.6/bin
. /domainutilitycmd –cmdFile /apps/tibco/ModifyLDAPConfiguration.xml
4.Start Administrator on the secondary server
TIBCO Administrator is widely used to deploy BW processes to different machines in the domain.
If the Administrator server is down for some maintenance or hardware related Issues the deployment cannot happen and roll out dates will be affected.
To over come this problem TIBCO has provided the feature of fault Tolerant setup
1. Product Versions
Fault Tolerant SetUp is provided with TRA Versions 5.2 and above.
The XMLs are available under
$TRA_HOME/5.6/template/domainutility/cmdline folder.(modify the XMLs to the current environment.)
2. Configuration
This section talks about the configuration steps.
1.Install Administrator on the secondary server
2.Run create domain script on the secondary server
cd /apps/tibco/tra/5.6/bin>
. /domainutilitycmd –cmdFile /apps/tibco/CreateDomain.xml
3. Run Add Secondary script on the secondary server
cd /apps/tibco/tra/5.6/bin
. /domainutilitycmd –cmdFile /apps/tibco/ModifyLDAPConfiguration.xml
4.Start Administrator on the secondary server