Verifying migration to new hardware

Verify that your migration to new hardware was successful by checking the log files and the error files for each migration step, and checking operation with the administrative console.

1. Run the BPMMigrationStatus command for each machine that participated in the migration process. This command displays the status of each migration step and whether it was successful or failed.
2. Check the migration log files for any failures or messages.
   • backupDirectory/logs/BPMSnapshotSourceProfile.profilename.timestamp.log
   • backupDirectory/logs/BPMCreateTargetProfile.ProcSrvMig01.timestamp.log
   • backupDirectory/logs/BPMMigrateProfile.profileName.timestamp.log
   • backupDirectory/logs/BPMProfileUpgrade.profilename.timestamp.log
   Note: backupDirectory is the directory in which migrated data was first stored and later retrieved from during the migration process, as specified in the migration wizard or the BPMSnapshotSourceProfile or BPMMigrateProfile commands.
   Note: profileName is the name of the new profile you created in V8.0.1 of IBM® Business Process Manager.
   All of these log files must indicate success, as described by these messages, for you to consider the migration successful.
3. Check the profile's log files for erroneous profile creation or augmentation errors. Profile log files are located in the following directory: install_root/logs/manageprofiles. The log files contain the profile name in them, for example: create <profile name>.log.
4. Check the server log files.
   1. Navigate to the profile_root/logs/server_name directory corresponding to the migrated profile.
   2. Review the SystemOut.log file and make sure there are no unrecoverable errors.
   3. Review the SystemErr.log file and make sure there are no unrecoverable errors.
   4. Check the logs for a stand-alone server in the /WebSphere/Server1/AppServer/profiles/default/logs directory.
5. Check the error files.
   1. Navigate to the snapshot directory and check the error files. Errors for each migration step are logged in separate files whose names begin with commandname and end with .error.
   2. The error files should be empty. If you find an error, look in the log file and follow the sequence that leads to the error.
6. Check operation with the administrative console.
   1. Open the administrative console (Integrated Solutions Console).
   2. Select Applications > Enterprise Applications from the navigation panel.
   3. In the right corner panel, verify that all of the applications listed have started, shown by the green "started" icon.
   4. From the navigation panel, select Resources > JDBC > Business Integration Data Sources.
   5. For each IBM Business Process Manager data source listed on this panel, select the check box and then select Test connection.
      Note: Test connection does not work for ME datasources. To verify the connection for ME datasources, make sure there are no errors in the logs after the servers are started.
   6. For each data source, you should receive a message similar to the following: "The test connection operation for data source WPS_DataSource on server Dmgr1 at node Dmgr1Node1 was successful."