IBM Support

Detailed steps to successfully migrate WebSphere Partner Gateway V6.2.1.4 profiles on WebSphere Application Server V6.1/V7.0 ND to V8.5.5 ND

Troubleshooting


Problem

WebSphere Partner Gateway 6.2.1.4 supports WebSphere Application Server 7.0 and 8.5.5. Perform the below steps only in case if you want to upgrade your profiles to WAS ND 8.5.5 in the same machine. In case if you are planning to setup WPG hub using the latest WAS version in a different machine, you may directly install 6.2.1.4 pointing to WAS ND 7.0 / 8.5.5 using the refreshed WPG v6.2 installer media. The existing WebSphere Partner Gateway 6.2.1.4 profiles on WebSphere Application Server 6.1/7.0 can be migrated to WebSphere Application server 8.5.5 using the WAS migration wizard. The detailed steps are provided below based on the deployment mode. Please note that WebSphere Application Server 8.5.5 is supported with WPG v6214. In order to migrate WebSphere Partner Gateway v6.2.1.4 profiles to WAS ND 8.5.5, first upgrade to WPG 6.2.1.4, run the SFTPMigration Scripts (http://www-01.ibm.com/support/docview.wss?uid=swg27027527) and then migrate the Profiles to WAS855. Note: Profile migration fails if you do not perform the SFTP Migration scripts mentioned above

Resolving The Problem

Steps to migrate the WebSphere Partner Gateway using migration wizard for distributed deployments.

To migrate WebSphere Partner Gateway v6.2.1.4 profiles from WAS ND 6.1 to WAS ND v7.0, please refer the link below :

http://www-01.ibm.com/support/docview.wss?uid=swg21462226

From WAS6.1 to WAS 8.5.5

1. Stop all WebSphere Partner Gateway clusters, servers, node agents and the deployment manager.

2. Follow the steps to migrate deployment manager profile using migration wizard -

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70dm.html?cp=SSAW57_8.5.5%2F3-4-0-2-4-0

Note: 1) Provide the profile name as bcgdmgr for the new profile.

3. From <WPG_DMGR_HOME>/bin location, run bcgDmgrMigrate.bat for Windows and bcgDmgrMigrate.sh for non-Windows. You need not run this script if you are not using deployment manager installed using WPG installer and using an existing cell

For Windows, run bcgDmgrMigrate.bat <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME>.

For example, bcgDmgrMigrate.bat "C:\Program Files\IBM\bcghub-dmgr" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\Program Files\IBM\WebSphere\AppServer855\profiles" "bcgdmgr" "bcgdmgr".

For non-Windows, run bcgDmgrMigrate.sh <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME> <USER_NAME> <USER_GROUP>. The script has to be run as root user.

For example, bcgDmgrMigrate.sh /opt/IBM/bcghub-dmgr /opt/IBM/ WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgdmgr bcgdmgr bcguser bcggroup.

4. Start the Deployment manager before you proceed to the next step.

Start the deployment manager from <WPG_DMGR_HOME>/bin, run bcgStartServer.bat for Windows or bcgStartServer.sh for non-Windows.

Alternatively, from the NEW_DMGR_PROFILE_LOCATION>/bin location, run startManager.sh for non-Windows and startManager.bat for Windows.

Note: Start as bcguser on non-Windows

5. Run syncNode.bat for Windows and syncNode.sh for non-Windows from

<WPG_Hub_HOME>/wasnd/profiles/bcgprofile/bin. The parameters are <DMGR HOSTNAME/DMGR-IPADDRESS> and <DMGR SOAP PORT>.

For Windows, run syncNode.bat <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGR SOAPPORT>.

For non-Windows, run syncNode.sh <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGR SOAP PORT>.

Note.

a) Run the above script as bcguser

b) Perform this in all the hub machines in case of multi node installation.

6. Follow this link to migrate the WebSphere Partner Gateway application server profiles. This step has to be performed in all the machines in case of multi node installation.

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70mas.html?cp=SSAW57_8.5.5%2F3-4-0-2-4-1

7. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-distrib" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-distrib/opt/IBM/WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgprofile bcguser bcggroup.

Note: Run this script as root user.

8. Start the node agent - from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows with "node" as the parameter for the script.

Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startNode.sh for non-Windows and startNode.bat for Windows.

Note: Run as bcguser in the non-Windows platform.

From WAS7.0 to WAS 8.5.5.

1. Stop all WebSphere Partner Gateway clusters, servers, node agents and the deployment manager.

2. Follow the steps to migrate deployment manager profile using migration wizard -

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70dm.html?cp=SSAW57_8.5.5%2F3-4-0-2-4-0

Note: 1) Provide the profile name as bcgdmgr for the new profile.

3. Take the Backup of <WPG_DMGR_HOME>/bin Folder. Now rename the bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak which is available in <WPG_DMGR_HOME>/bin Folder.

Note : Renaming of bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak is must, if not done, migration script will not be able to execute successfully and lead to inconsistent system state.

4. From <WPG_DMGR_HOME>/bin location, run bcgDmgrMigrate.bat for Windows and bcgDmgrMigrate.sh for non-Windows. You need not run this script if you are not using deployment manager installed using WPG installer and using an existing cell.

For Windows, run bcgDmgrMigrate.bat <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> NODENAME>.

For example, bcgDmgrMigrate.bat "C:\Program Files\IBM\bcghub-dmgr" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\Program Files\IBM\WebSphere\AppServer855\profiles" "bcgdmgr" "bcgdmgr".

For non-Windows, run bcgDmgrMigrate.sh <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME> <USER_NAME> <USER_GROUP>.

The script has to be run as root user.

For example, bcgDmgrMigrate.sh /opt/IBM/bcghub-dmgr /opt/IBM/ WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgdmgr bcgdmgr bcguser bcggroup.

5. Start the Deployment manager before you proceed to the next step.

Start the deployment manager from <WPG_DMGR_HOME>/bin, run bcgStartServer.bat for Windows or bcgStartServer.sh for non-Windows.

Alternatively, from the NEW_DMGR_PROFILE_LOCATION>/bin location, run startManager.sh for non-Windows and startManager.bat for Windows.

Note: Start as bcguser on non-Windows

6. Run syncNode.bat for Windows and syncNode.sh for non-Windows from <WPG_Hub_HOME>/wasnd/profiles/bcgprofile/bin. The parameters are <DMGR HOSTNAME/DMGR-IPADDRESS> and <DMGR SOAP PORT>.

For Windows, run syncNode.bat <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGR SOAP PORT>.

For non-Windows, run syncNode.sh <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGR SOAP PORT>.

Note.

a) Run the above script as bcguser

b) Perform this in all the hub machines in case of multi node installation.

7. Follow this link to migrate the WebSphere Partner Gateway application server profiles. This step has to be performed in all the machines in case of multi node installation.

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70mas.html?cp=SSAW57_8.5.5%2F3-4-0-2-4-1

8. Take the Backup of <WPG_Hub_HOME>/bin Folder. Now rename the bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak , which is available in<WPG_Hub_HOME>/bin Folder.

Note : Renaming of bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak is must, if not done, migration script will not be able to execute successfully and lead to inconsistent system state.

9. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-distrib" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-distrib/opt/IBM/WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgprofile bcguser bcggroup.

Note: Run this script as root user.

10. Start the node agent from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows with "node" as the parameter for the script.

Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startNode.sh for non-Windows and startNode.bat for Windows.

Note: Run as bcguser in the non-Windows platform.

Steps to migrate the WebSphere Partner Gateway using migration wizard for simple mode

From WAS6.1 to WAS8.5.5

1. Stop the server.

2. Follow the steps in this link to migrate the WebSphere Partner Gateway profile -

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70sas.html?cp=SSAW57_8.5.5%2F3-4-0-2-3-0

3. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-simple" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-simple /opt/IBM/WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgprofile bcguser bcggroup.

Note: Run this script as root user.

4. Start the server - from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows. Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startServer.sh for non-Windows and startServer.bat for Windows.

Note: Run as bcguser in the non-Windows platform.

From WAS7.0 to WAS8.5.5

1. Stop the server.

2. Follow the steps in this link to migrate the WebSphere Partner Gateway profile -

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/tmig_to70sas.html?cp=SSAW57_8.5.5%2F3-4-0-2-3-0

3. Take the Backup of <WPG_Hub_HOME>/bin Folder. Now rename the bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak , which is available in<WPG_Hub_HOME>/bin Folder.

Note : Renaming of bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak is must, if not done, migration script will not be able to execute successfully and lead to inconsistent system state.

4. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-simple" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-simple /opt/IBM/WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgprofile bcguser bcggroup.

Note: Run this script as root user.

5. Start the server - from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows. Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startServer.sh for non-Windows and startServer.bat for Windows.

Note: Run as bcguser in the non-Windows platform.

Steps to migrate the WebSphere Partner Gateway using command line utility for Simple distributed and Fully distributed modes

From WAS6.1 to WAS8.5.5

1. Stop all WebSphere Partner Gateway clusters, servers, node agents and the deployment manager.

2. Use the WebSphere Application Server Version 8.5.5 Profile Management tool or the manageprofiles command to create a application server or custom profile.

For pre-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPreUpgrade.html?cp=SSAW57_8.5.5

For post-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPostUpgrade.html?cp=SSAW57_8.5.5

Note: Do not use the option "-appInstallDirectory" during post upgrade.

3. From <WPG_DMGR_HOME>/bin location, run bcgDmgrMigrate.bat for Windows and bcgDmgrMigrate.sh for non-Windows. You need not run this script if you are not using deployment manager installed using WPG installer and using an existing cell.

For Windows, run bcgDmgrMigrate.bat <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME>.

For example, bcgDmgrMigrate.bat "C:\Program Files\IBM\bcghub-dmgr" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\Program Files\IBM\WebSphere\AppServer855\profiles" "bcgdmgr" "bcgdmgr".

For non-Windows, run bcgDmgrMigrate.sh <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME> <USER_NAME> <USER_GROUP>. The script has to be run as root user.

For example, bcgDmgrMigrate.sh /opt/IBM/bcghub-dmgr /opt/IBM/ WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgdmgr bcgdmgr bcguser bcggroup.

4. Start the Deployment manager before you proceed to the next step. Start the deployment manager from <WPG_DMGR_HOME>/bin, run bcgStartServer.bat for Windows or bcgStartServer.sh for non-Windows.

Alternatively, from the <NEW_DMGR_PROFILE_LOCATION>/bin location, run startManager.sh for non-Windows and startManager.bat for Windows.

Note: Start as wpguser on non-Windows

5. Run syncNode.bat for Windows and syncNode.sh for non-Windows from <WPG_Hub_HOME>/wasnd/profiles/bcgprofile/bin. The parameters are <DMGR HOSTNAME/DMGR-IPADDRESS> and <DMGR SOAP PORT>.

For Windows, run syncNode.bat <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGRSOAP PORT>.

For non-Windows, run syncNode.sh <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGRSOAPPORT>.

Note.

a) Run the above script as wpguser

b) Perform this in all the machines in case of multi node installation.

6. Follow the link to migrate application server profile using migration command line utility.

Note: Use the WebSphere Application Server Version 8.5.5 Profile Management tool or the manageprofiles command to create a application server or custom profile, but do not federate the node.

For pre-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPreUpgrade.html?cp=SSAW57_8.5.5

For post-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPostUpgrade.html?cp=SSAW57_8.5.5

Note: Do not use the option "-appInstallDirectory" during post upgrade

7. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-distrib" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-distrib/opt/IBM/WebSphere/AppServer7 /opt/IBM/WebSphere/AppServer7/profilesbcgprofile bcguser bcggroup.

Note: Run this script as root user.

8. Start the node agent - from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows with "node" as the parameter for the script.

Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startNode.sh for non-Windows and startNode.bat for Windows.

Note: Run as wpguser in the non-Windows platform.

From WAS7.0 to WAS8.5.5

1. Stop all WebSphere Partner Gateway clusters, servers, node agents and the deployment manager.

2. Use the WebSphere Application Server Version 8.5.5 Profile Management tool or the manageprofiles command to create a application server or custom profile.

For pre-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPreUpgrade.html?cp=SSAW57_8.5.5

For post-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPostUpgrade.html?cp=SSAW57_8.5.5

Note: Do not use the option "-appInstallDirectory" during post upgrade.

3. Take the Backup of <WPG_DMGR_HOME>/bin Folder. Now rename the bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak , which is available in <WPG_DMGR_HOME>/bin Folder.

Note : Renaming of bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak is must, if not done, migration script will not be able to execute successfully and lead to inconsistent system state.

4. From <WPG_DMGR_HOME>/bin location, run bcgDmgrMigrate.bat for Windows and bcgDmgrMigrate.sh for non-Windows. You need not run this script if you are not using deployment manager installed using WPG installer and using an existing cell

For Windows, run bcgDmgrMigrate.bat <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME>.

For example, bcgDmgrMigrate.bat "C:\Program Files\IBM\bcghub-dmgr" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\Program Files\IBM\WebSphere\AppServer855\profiles" "bcgdmgr" "bcgdmgr".

For non-Windows, run bcgDmgrMigrate.sh <WPG_DMGR_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <NODENAME> <USER_NAME> <USER_GROUP>. The script has to be run as root user.

For example, bcgDmgrMigrate.sh /opt/IBM/bcghub-dmgr /opt/IBM/ WebSphere/AppServer855 /opt/IBM/WebSphere/AppServer855/profiles bcgdmgr bcgdmgr bcguser bcggroup.

5. Start the Deployment manager before you proceed to the next step. Start the deployment manager from <WPG_DMGR_HOME>/bin, run bcgStartServer.bat for Windows or bcgStartServer.sh for non-Windows.

Alternatively, from the <NEW_DMGR_PROFILE_LOCATION>/bin location, run startManager.sh for non-Windows and startManager.bat for Windows.

Note: Start as wpguser on non-Windows

6. Run syncNode.bat for Windows and syncNode.sh for non-Windows from <WPG_Hub_HOME>/wasnd/profiles/bcgprofile/bin. The parameters are <DMGR HOSTNAME/DMGR-IPADDRESS> and <DMGR SOAP PORT>.

For Windows, run syncNode.bat <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGRSOAP PORT>.

For non-Windows, run syncNode.sh <DMGR-HOST NAME/DMGR-IPADDRESS> <DMGRSOAPPORT>.

Note.

a) Run the above script as wpguser

b) Perform this in all the machines in case of multi node installation.

7. Follow the link to migrate application server profile using migration command line utility.

Note: Use the WebSphere Application Server Version 8.5.5 Profile Management tool or the manageprofiles command to create a application server or custom profile, but do not federate the node.

For pre-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPreUpgrade.html?cp=SSAW57_8.5.5

For post-upgrade refer to - http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPostUpgrade.html?cp=SSAW57_8.5.5

Note: Do not use the option "-appInstallDirectory" during post upgrade

8. Take the Backup of <WPG_Hub_HOME>/bin Folder. Now rename the bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak , which is available in <WPG_Hub_HOME>/bin Folder.

Note : Renaming of bcgSetupCmdLine.sh.bak/bcgSetupCmdLine.bat.bak is must, if not done, migration script will not be able to execute successfully and lead to inconsistent system state.

9. From <WPG_HUB_HOME>/bin location, run bcgHubMigrate.bat for Windows and bcgHubMigrate.sh for non-Windows.

For Windows, run bcgHubMigrate.bat <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME>.

For example, bcgHubMigrate.bat "C:\Program Files\IBM\bcghub-distrib" "C:\Program Files\IBM\WebSphere\AppServer855" "C:\ProgramFiles\IBM\WebSphere\AppServer855\profiles" "bcgprofile".

For non-Windows, run bcgHubMigrate.sh <WPG_HUB_HOME> <WASv855_HOME> <WPG_WASv855_PROFILE_HOME> <PROFILE_NAME> <USER_NAME> <USER_GROUP>.

For example, bcgHubMigrate.sh /opt/IBM/bcghub-distrib/opt/IBM/WebSphere/AppServer7 /opt/IBM/WebSphere/AppServer7/profilesbcgprofile bcguser bcggroup.

Note: Run this script as root user.

10. Start the node agent - from <WPG_HUB_HOME>/bin, run bcgStartServer.bat for Windows and bcgStartServer.sh for non-Windows with "node" as the parameter for the script.

Alternatively, from the <NEW_bcgProfile_Location>/bin location, run startNode.sh for non-Windows and startNode.bat for Windows.

Note: Run as wpguser in the non-Windows platform.

Revert migrating the profiles to WebSphere Application Server 6.1 or 7.0

Follow the below steps if you want to migrate the WebSphere Partner Gateway profiles back to WebSphere Application Server 6.1 or 7.0

1. Ensure that all WebSphere Partner Gateway transactions are completed and no messages exist in the messaging engine(s).

2. Stop the clusters and node agents of WebSphere Partner Gateway on WebSphere Application Server v7 or v855 (on non -Windows execute this step as wpguser).

3. Stop the Deployment manager of WebSphere Partner Gateway on WebSphere Application Server v7 or v855 (on non -Windows execute this step as wpguser).

4. Run the bcgHubRevertMigrate.bat/sh (run as root on non-Windows ).

5. Run the bcgDmgrRevertMigrate.bat/sh (run as root on non-Windows ).

6. Optionally, remove the WebSphere Partner Gateway profiles on WebSphere Application Server v7 or V855.

<WAS_V7_HOME>/bin: ./manageprofiles.sh -delete -profileName <profilename>

Note: This step is not mandatory to revert WebSphere Partner Gateway from WebSphere Application Server v7 or v855 to WebSphere Application Server v6.1.

7. Backup the MAS database / schema. Refer individual database documentation for steps to take backup.

8. Connect to the MAS database / schema as bcgmas user and drop the SIB tables.

DB2 :

db2 connect to bcgmas user bcgmas using <password>

db2 drop table SIB000

db2 drop table SIB001

db2 drop table SIB002

db2 drop table SIBCLASSMAP

db2 drop table SIBKEYS

db2 drop table SIBLISTING

db2 drop table SIBOWNER

db2 drop table SIBOWNERO

db2 drop table SIBXACTS

Oracle :

sqlplus bcgmas/<password>@<sid>

SQL> drop table SIB000

SQL> drop table SIB001;

SQL> drop table SIB002;

SQL> drop table SIBCLASSMAP;

SQL> drop table SIBKEYS;

SQL> drop table SIBLISTING;

SQL> drop table SIBOWNER;

SQL> drop table SIBOWNERO;

SQL> drop table SIBXACTS;

9. If the "create tables" option for the Message Store in the Messaging Engine (WAS Admin console) is not checked, go through this additional step.

DB2 :

Connect to bcgmas as instance owner and execute the script sibddl_db2.sql under <BCGMASDB>/Scripts/DB2 location.

db2 connect to bcgmas user db2inst1 using <password>

db2 -td! -f sibddl_db2.sql

Oracle:

Execute the script sibddl_ora.sql under <BCGMASDB/Scripts/Oracle location connected as sys user.

sqlplus -L "sys/<password>@<sid> as sysdba" @sibddl_ora.sql

10. Start the node agents / Clusters of WebSphere Partner Gateway on WebSphere Application Server v6.1 or v7.0

[{"Product":{"code":"SSDKJ8","label":"WebSphere Partner Gateway Enterprise Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2.1.4","Edition":"Advanced;Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21701462

Page Feedback