Products | Versions |
---|---|
TIBCO BusinessWorks Collaborator | - |
Not Applicable | - |
2). Undeploy all BWC application from the domain. Unregister the BWC component. Stop the BWC server.
3). Make backup of all IC tables including Oracle Sequences.
5). Copy all repository files (<bwc-home>/server/<Repository-name>/) from the first server to the new server repository directory.
6). Point the new BWC 5.x to the existing database by modifying the TWO_TASK setting in env.csh and icconfig.xml (<bwc-home>/server/<server-name>/config).
7). Update SERVER_NAMES.GLOBAL_ID and HOST from the old host name to have the new host name using an SQL command.
8). If the logical name of the InConcert servers is different, then that should be updated in the database. In SQL*PLUS do "update SERVER_NAMES set SERVER_NAMES='<name of target server>';" .
9). Make sure the BWC servers start successfully.
10). Use IcBatchRegistry to update LOCATION and PARTITION. Refer to IC BatchRegistry guide->Chap 3 BatchRegistry commands.
11). The new BWC 5.x shuld be running, pointing to the existing IC database. Stop the BWC server if its running.
12). Upgrade BWC 5.5.0 TRA/Admin/BW/FB version on new machine.
13). Upgrade the new BWC 5.x to 5.5.0 using the BWC 5.5.0 installation. Make sure you select the "Upgrade" option during the BWC 5.5.0 installation.
14). Upgrade BWC 5.5.0 to 5.5.1 using the BWC 5.5.1 installation. Apply the latest BWC 5.5.1 hotfix.
15). Make sure the BWC servers start successfully.
16). Open the BWC application in Designer. Validate the project and export the workflow.
17). Stop the BWC servers if they are running.
18). Install Tomcat (5.5.20).
19). Register the BWC component and Tomcat into the domain and create a shared archive.
20). Start the BWC servers from the Admin GUI and Tomcat from the script created in the domain.
21). Try "Sync Workflow" user from the Admin GUI.