Checking for migration readiness
Before you begin
If the source environment is a network deployment environment, ensure that the deployment manager, nodes, and deployment environment have been started. If the source environment is a stand-alone environment, ensure that the stand-alone server has been started.
About this task
The BPMMigrationPreValidation command validates your applications, data sources, and messaging engines. It generates a report that shows the current status of your source environment. You can see the changes that you must make so that migration can proceed smoothly, as well as the changes that you must make after migration.
Procedure
- Copy the migration.properties sample file and rename
it to source_migration.properties. Update the file with the configuration
information for the source environment. Check all the properties and edit them if required, following the
instructions in the sample file.
- If you installed the new version of the product on the same computer as the source environment, the sample file is in install_root_8.5\util\migration\resources\migration.properties.
- If you installed the new version of the product on a different computer and copied the migration files to the source environment, the sample file is in remote_migration_utility\util\migration\resources\migration.properties.
Leave the cluster name parameters empty.- source.application.cluster.name=
- source.messaging.cluster.name=
- source.support.cluster.name=
- source.web.cluster.name=
- admin.username
- admin.password
- bpm.home
- profile.name
For admin.username and admin.password, use the WebSphere primary administrative user name. You can find the primary administrative user name in the administrative console by going to Users and Groups > Administrative user roles.
The bpm.home parameter is the installation root of your source product. Make sure that the file separators are forward slashes (/). Use the full path. Do not use the tilde character (˜) to stand for the home directory. For example:
bpm.home=C:/IBM/BPM
- Optional: Update other configuration
files in the install_root_8.5\util\migration\resources directory,
following the instructions in the files.
- Update the soap.client.props file to change the com.ibm.SOAP.requestTimeout property if the SOAP invocation is timing out at the current setting.
- Update the ssl.client.props file to change the keystore and truststore.
- Update the logging.properties file to set the default logging level to FINEST if you need to capture more detail in the log.
- Run the command to check for migration
readiness.
- If you installed the new version of the product on the same computer
as the source environment, run the following command in the target
environment. The properties in the source_migration_properties_file must
point to the source environment.
install_root_8.5\bin\BPMMigrationPreValidation.bat -propertiesFile source_migration_properties_file -reportDir path_to_report_package
- If you installed the new version of the product on a different
computer and copied the migration files to the source environment,
run the following command in the source environment on the computer
where the deployment manager or stand-alone server is deployed. The
properties in the source_migration_properties_file must
point to the source environment.
remote_migration_utility\bin\BPMMigrationPreValidation.bat -propertiesFile source_migration_properties_file -reportDir path_to_report_package
- source_migration_properties_file is the full
path to the migration properties file in which you specified the configuration
information for the source environment (the file that you updated
in Step 1). Put double quotation marks around the value if there are
spaces. For example:
BPMMigrationPreValidation.bat -propertiesFile "C:\bpm 85\util\migration\resources\source_migration.properties" -reportDir E:\BPM751_precheck_report
- path_to_report_package is the full path to the directory where the validation report will be stored
This command finds potential issues in the source environment that must be fixed before you can migrate, and also makes you aware of changes that you must make after you migrate. The command performs the following checks:- Profile validation:
- Validates that the source product and version is supported for migration
- Validates the status of IBM® BPM applications
- Validates the connection status of all IBM BPM data sources
- Validates the status of IBM BPM messaging engines
- Notifies you of changes that you must make after you migrate,
including the following changes:
- Authentication aliases that are not migrated because you added them in the source environment
- Data sources that are not migrated because you added them in the source environment
- Notifies you of the key changes that occur during migration, including
the following changes:
- Security changes
- Changes to XML configuration properties files. Some XML security configuration properties are moved to the WebSphere® Application Server configuration files automatically. These properties are exported to the properties file and will be moved to the WebSphere Application Server configuration files when you run the command. See the table in WebSphere Lombardi Edition XML configuration properties that are migrated to WebSphere Application Server configuration files for a list of the properties that have been moved.
- Notifies you of current configuration that you might need to
fix after migration, including the following configuration:
- XML configuration properties files
- Topology information
- Database validation:
- Notifies you if the volume of data will increase the downtime required for migration
- Checks for customized indexes
- Analyzes the tables for migration impact and, if required, recommends actions that you can take before migration
- Checks that the log file size is sufficient and, if not, provides the command that you should run to update it
The command displays each validation rule as it runs. After all the validation rules are finished, you see a message similar to the following message:Generating the report for migration prevalidation... Migration prevalidation was completed. You can review the report in: C:\reports
- If you installed the new version of the product on the same computer
as the source environment, run the following command in the target
environment. The properties in the source_migration_properties_file must
point to the source environment.
- If the report does not open automatically, go to the report directory that you specified and open the index.html file in a browser to view the report. View each of the areas in the report. Wherever you see an error or warning, you can click it for more information.
- Investigate the warnings and fix the problems. Run the BPMMigrationPreValidation command again and make sure that all problems are fixed before you proceed with the migration.