Resolution:
If you want to migrate an existing TIBCO BusinessWorks Collaborator (BWC) setup from one machine to another and want to use the same database so that new BWC setup can use previously existing data in the database, you need to ensure the following during BWC WF server migration.

- Use the same Server ID to do the dummy install as is in SERVER_NAMES.SERVER_ID of the data you will import. You also need to copy over the IC repositories files.

- The database on the different machine where you are copying from needs to be the same version.

- Before importing the data you should save SERVER_NAMES.HOST and GLOBAL_ID from the dummy install. After you import the data you will need to restore these two items. The GLOBAL_ID is used when forming a server group.

- The server ID in the database must match what is in the icconfig.xml file.

- Using the same server ID means you do not have to change the icconfig.xml file so it is the easiest way for the user to get the database migration correct. You could update the server ID in the icconfig.xml.

The global ID is used by the EAD, Sleep Agent and Notifier to form separate RVFT groups. You can see it in the IC debug log at startup by the subjects they listen to. Note that they do this even if there is not an additional server group that they are joining.

Migrating TIBCO BusinessWorks Collaborator (BWC) WF server from one machine to a another.