Resolution:
Description:
============
When the domain is using the EMS as the domain transport the secondary server added to the domain has exactly same privileges as primary. However, we can't remove the primary admin server directly using the domainutility->delete an administration domain option as it removes the DB schema and the domain gets deleted. In this case we have to move the primary administrator to a new machine and make that primary.


Cause:
===========
In case of the EMS server even if both the administrator have the same privileges, the primary can't be deleted directly as it deletes the domain DB and the domain gets destroyed. However, the secondary admin server can be deleted safely.

Resolution:
==========
Below procedure should be followed when you require to remove the existing primary admin server for an EMS based domain.

Sample Environment:

SERVER A [Primary]: TRA 5.8.0,Admin 5.8.0 ,BW 5.11.0
SERVER B [Secondary]: TRA 5.8.0,Admin 5.8.0 ,BW 5.11.0
SERVER C [New Server]: TRA 5.8.0,Admin 5.8.0 ,BW 5.11.0
SERVER D [EMS Server]: EMS 7.0.

Test Requirement : We need to decommission Server A and move Primary Admin Domain and BW Application to new server i.e. SERVER C.

Test Case 1:
1.Created Primary Admin Domain "Test_Domain"  with EMS Transport on SERVER A.
2.Created Secondary Admin Domain "Test_Domain"  with EMS Transport on SERVER B.
3.Started Primary and Secondary Admin Domain , deployed sample BW application on Primary Admin Server i.e. on SERVER A.


NOTE: Make sure the installation path and version of Software on Server A and Server C should match.

Test Case 2:
1. Stop Primary Admin Server on SERVER A.
2. Copy <Administrator>/Domain/Test_Domain folder from SERVER A to SERVER C.
3. Copy <TRA>/Domain/Test_Domain folder from SERVER A to SERVER C.
4. Run MoveMachine command from SERVER C.
==========================================.
C:\tibco\tra\5.8\bin>MoveMachine -domain Test_Domain -oldMachine <SERVER A HOST NAME>  -newMachine <SERVER C HOST NAME>
==========================================.

5. There is an existing defect with JIRA ID ADM-5363 due to which the following three parameters don't get replace correctly with the new machine name:

a. Repo.master in tibcoadmin_<Domain_name>.tra file. We change Repo.master  <SERVER C HOST NAME>.

b. -agent_name and -machine_name name under hawkagent.cfg. We changed them manually.

However, ADMachine table and both the properties files gets changed correctly.

Result:

The Primary domain is shifted on the new machine and the previous primary machine is no more in the setup i.e. automatically decommissioned..
The BW Application is also moved to new SERVER C and we are able to start the service from Admin GUI on SERVER C.

How to move the primary admin server to a new machine and decommission the current primary machine in case the domain is EMS based.