BPMMigrationPreValidation command-line utility

The BPMMigrationPreValidation command is used to check for migration readiness. This command makes sure that your source environment is in the correct state for migration. It also makes you aware of changes that you will have to make after migration.

The BPMMigrationPreValidation command is in the BPM_home_8.5/bin directory.

If you installed the new version of the product on a different computer and copied the migration files to the source environment, the command is found in remote_migration_utility/bin on the source computer.
Note: Make sure that the deployment environment or stand-alone server is running before you run this command.

Syntax

BPM_home_8.5/bin/BPMMigrationPreValidation -propertiesFile path_to_migration_properties_file -reportDir path_to_report_package

Description

The BPMMigrationPreValidation command finds potential issues in the source environment that must be fixed before you can migrate, and also makes you aware of changes you must make after you migrate. This command performs the following validation:
  • 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
    • Performs the following checks:
      • Whether any existing service integration bus (SIB) message is in a transaction
      • Whether too many SIB messages are stuck in a queue
      • Whether any failed events are not processed
    • 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. Refer to Security configuration properties 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
      • Lightweight Third-Party Authentication (LTPA) key file
      • 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

After you have run the command, go to the report directory that you specified and open the index.html file in a browser to view the report. If you see validation errors or warnings, click the row to see the details of the problem and the steps that you must take to fix it before migration.

Required parameters

-propertiesFile
Specifies the full path to the source migration properties file in which you specify the configuration information for the source environment.
  • If you installed the new version of the product on the same computer as the source environment, the sample file is found in BPM_home_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 found in remote_migration_utility/util/migration/resources/migration.properties.

You must check all the properties in this file, and edit them if required.

-reportDir
Specifies the path to the directory where the validation report will be stored.

Optional parameters

-help
Provides the command usage.

Examples

  • For Linux operating systemFor UNIX operating systemBPMMigrationPreValidation.sh -propertiesFile /opt/BPM85/util/migration/resources/source_migration.properties -reportDir /BPM751_precheck_report
  • For Windows operating systemBPMMigrationPreValidation.bat -propertiesFile "C:\bpm 85\util\migration\resources\source_migration.properties" -reportDir E:\BPM751_precheck_report

Problem determination

If you are not using the remote migration utility, the log file is in BPM_home_8.5/logs/migration.

If you are using the remote migration utility, the log file is in remote_migration_utility/logs/migration.