Moving the deployment environment

To migrate IBM® Business Automation Workflow V19.0.0.3 to the same version on new hardware, export the configuration properties from your existing deployment environment, install Business Automation Workflow on the new hardware, and then create the environment using the exported configuration properties files.

Procedure

To move the deployment environment to new hardware, complete the following steps:

  1. Export the configuration from the current deployment environment. 
    BPMConfig –export –profile profile_name -de de_name -outputDir output_directory
    Important: Specify a different output directory for each deployment environment. In the case where a cell has multiple deployment environments, a unique output directory is required for each deployment environment.
    The output directory contains files similar to the following files, based on your deployment environment type.
    Table 1. Configuration files for each deployment environment
    Sample name Description
    DE_name.properties This properties file contains the configuration properties from your source environment. You use this file when you configure the target environment. For more information about the configuration properties, see the topic Configuration properties for the BPMConfig command.
    fileRegistry.xml If you use a file-based user registry, the user registry file is copied from the source environment to be added to the target environment.
    ltpa.jceks If you use LTPA, the LTPA key file is copied from the source environment to be added to the target environment.
    ldap_additional_properties.xml If you use a federated repository and an unencrypted LDAP connection in the source environment, user-defined additional properties of the LDAP server are copied from the source environment to the output directory, where they are later used automatically to create the target environment.
    Restriction: If you extend the federated repository to use a custom login property (such as userPrincipalName) in addition to the default uid property in the source environment, LDAP is not configured for the target environment, with the following warning: CWMCB0600W: LDAP could not be configured! You may configure LDAP separately after BPMConfig has terminated successfully. If you see this warning, manually configure LDAP with the login properties you want to use after the migration is complete.
    ProcessServer_100SourceCustomMerged.xml and PDW_100SourceCustomMerged.xml If you have XML configuration properties files, they are copied from the source environment. The exported configuration files are merged and renamed to 101CustomMigrated.xml in the target environment.
    Application-config-bpc.xml and resources-bpc.xml If you have Business Process Choreographer configured in the source environment, the configuration files are copied from the source environment to the output directory, where they are later used automatically to create the target environment.
    Support-config-bpc.xml If you have Business Process Choreographer Archive Manager configured on the support cluster in the source environment, the configuration is copied from the source environment to the output directory, where it is later used automatically to create the target environment.

    In addition to the information exported by the BPMConfig –export command, you can use the exportWASConfig.py script to export other WebSphere® Application Server configuration from your source environment to refer to when you create your new deployment environment.

  2. Use the IBM Business Automation Workflow Configuration editor to update the exported properties file to match your requirements for the new deployment environment.
    Make sure the file matches the environment on the new hardware, including the following properties:
    • Host name of the deployment manager and the nodes
    • Installation path
    • Environment type
    • Database properties. If you are not moving your Business Automation Workflow databases, you do not need to update any database properties. However, if you are moving the databases, you must update the connection properties. In either case, you must keep the database schema names and database user names.
    See the instructions in Configuring your environment with the IBM Business Automation Workflow Configuration editor.
    Notes:
    • Keep the same cell name, cell administrator, deployment environment administrator, database schema names, and database user names.
    • Keep the same application cluster name if you are moving an Advanced or AdvancedOnly deployment environment.
    • Make sure that bpm.de.deferSchemaCreation is set to true in the properties file.
    • If possible, use the same LDAP server as the source environment.
    The created deployment environment will have the same topology as your source environment, such as environment type, cluster number, and node number.
  3. Save the updated properties file, keeping it in the same output directory. Copy the output directory to the new hardware that you want to move to.
  4. Install the same version of IBM Business Automation Workflow V19.0.0.3 on all the new servers designated for the nodes and the deployment manager.
  5. On the new deployment manager system, validate that all database connections are correctly configured by running the BPMConfig -validate command.
    Use the following syntax:
    target_install_root/bin/BPMConfig -validate -db configuration_properties_file
    where
    • configuration_properties_file is the full path and name of the properties file that you copied over to the target environment.
    The command checks each connection and displays a message similar to the following message:
    A JDBC connection to the 'BusinessSpaceDb' (CMNDB.bpmadmin) has been successfully established.
    After all connections are checked, you see a message that the command completed successfully.
  6. Create the deployment environment on the new deployment manager system by running the BPMConfig -create command. 
    BPMConfig –create –de output_directory/updated_properties_file

    If any of the new nodes is not on the same physical computer as the new deployment manager, run the command on the node with the same updated properties file.

    A new deployment environment is created on the new hardware with the configuration information that you specified.