High-level task flow for migrating business data and applications from IBM BPM Express

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The following diagrams show the high-level migration steps.
  1. Preparing to migrate
    • Verify that your target installation environment fulfills all requirements.
    • Prepare applications for migration, checking for resources (such as data sources, JMS configurations, schedulers, and environment variables), and application-specific authentication aliases.
    Figure 1. Sample environment before migration begins. The source environment is running and transferring data to and from its databases. The deployment environment has three clusters and is configured across two nodes.
    The details of the diagram are provided in the figure caption.
  2. Installing IBM Business Automation Workflow 26.x
    • Prepare the operating system for installation.
    • Install IBM Business Automation Workflow 26.x using Installation Manager.
    • If you are migrating to a different computer, package the remote migration utilities into an image using the BPMCreateRemoteMigrationUtilities command and copy the image back to the source computer.
    Figure 2. Sample environment after 26.x is installed on the target. The source environment is running and transferring data to and from its databases. The target has been created but does not contain a deployment environment.
    The details of the diagram are provided in the figure caption.
  3. Migrating the configuration from the source environment
    • Run the BPMConfig -migrate command to export the configuration information from the source environment and generate the properties file.
    • Copy the output folder to the target environment.
    Figure 3. Sample environment after 26.x is installed on the target and BPMConfig -migrate is run. The output folder is being copied to the target environment. The source environment is running and transferring data to and from its databases. The target has been created but does not contain a deployment environment.
    The details of the diagram are provided in the figure caption.
  4. Configuring IBM Business Automation Workflow 26.x and creating the target deployment environment
    • Open a browser and graphically configure your new deployment environment with the IBM Business Automation Workflow Configuration editor, by loading the properties file and interacting with the topology diagram.
    • Create a new empty database for each new database capability that you added.
    • Validate that all database connections are correctly configured by running the BPMConfig -validate command.
    • Create the target deployment environment using the BPMConfig -create command and the properties file that you configured with the IBM Business Automation Workflow Configuration editor. In addition to creating the deployment manager, creating the nodes and federating the node profiles, and creating the deployment environment, the command generates SQL scripts for upgrading and creating the databases and puts them into the correct directories for you. You will run the scripts in a later step.
    Figure 4. Sample environment after 26.x is configured on the target. The source environment is running and transferring data to and from its databases. The target is not running but contains a deployment environment. The deployment environment has three clusters and is configured across two nodes.
    The details of the diagram are provided in the figure caption.
  5. Upgrading the existing databases
    • To initialize the new database components and upgrade the schemas of the existing databases, run the upgradeSchemaAll_de_name command that you generated previously.
    • To upgrade the data in the source databases to 26.x, run the DBUpgrade command.
    Figure 5. Sample environment after existing schemas and data are updated. The source environment is not running and the databases are not in use. The databases contain updated schemas and data. The target is not running but contains a deployment environment.
    The details of the diagram are provided in the figure caption.
  6. Moving your custom configuration to the target environment
    • Start the deployment manager in the target environment. Start the nodes. Start the clusters.
    • Complete the configuration of IBM Business Automation Workflow.
  7. Restarting the target environment and verifying the migration
    • Stop and restart the target environment.
    • Verify that the migration was successful.
    Figure 6. Sample environment after migration. The source environment is not running. The target environment is running and transferring data to and from its databases.
    The details of the diagram are provided in the figure caption.