IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Runtime migration subprocedures > Migrating databases

Migrating the Business Space V7.0.x database and data

If you are migrating from V7.0.x, additional steps are required to migrate the Business Space database schema and data to V8.0.1.

When migrating Business Space data to V8.0.1, use the same LDAP that you used for the previous version.


Procedure

  1. Run the preMigrateBusinessSpace700.sql script.

    1. Log on to the database server as a user with read/write access on the database.
    2. Connect to the database.
    3. Locate the preMigrateBusinessSpace700.sql script for your database in the profile for the server or cluster that you most recently configured. By default, the scripts are located in the following directory:

      • Stand-alone server: profile_root/dbscripts/BusinessSpace/ node_name_server_name/ database_product_name/ database_name
      • Cluster: deployment_manager_profile_root/dbscripts/BusinessSpace/ cluster_name/ database_product_name/ database_name

      Important: This script might need to be modified if the default values do not match your environment.

    4. Save the script to a location on the same system with the database.
    5. Change to the directory where you copied the script, and run the preMigrateBusinessSpace700.sql script, as described in the header of the file.

  2. Run the upgradeBSpaceSchema command.

    1. Locate the command upgradeBSpaceSchema.bat (Windows) or upgradeBSpaceSchema.sh (UNIX, Linux, or z/OS) under INSTALL_ROOT/BusinessSpace/scripts.

    2. Run the command with the parameters -profileName/-nodeName/-serverName/-clusterName, designating the -serverName and -nodeName parameters for a stand-alone server or -clusterName for a cluster. In a ND environment, -profileName should be the dmgr profile. On z/OS, the -wasHome parameter is additionally required to specify the WebSphere Application Server home directory.

      Use the following syntax: 

      upgradeBSpaceSchema.bat -profileName  profile -nodeName  node -serverName  server   
      upgradeBSpaceSchema.sh -profileName  dmgr -clusterName  cluster

      Use the following syntax for a stand-alone server: 

      upgradeBSpaceSchema.sh -profileName default -nodeName  node -serverName  server -wasHome  WAS_HOME_dir

      Use the following syntax in a ND environment: 

      upgradeBSpaceSchema.sh -profileName default -clusterName  cluster -wasHome  WAS_HOME_dir
  3. Migrate the Business Space schema.

    1. Log on to the database server as a user with read/write access on the database.
    2. Connect to the database.
    3. Locate the migrateBusinessSpaceSchema700.sql script for your database in the profile that you most recently configured, and save the script to a location on the same system with the database.

      By default, the scripts are located in the following directory:

      • Stand-alone server: profile_root/dbscripts/BusinessSpace/ node_name_server_name/ database_product_name/ database_name
      • Cluster: deployment_manager_profile_root/dbscripts/BusinessSpace/ cluster_name/ database_product_name/ database_name

    4. Change to the directory where you copied the migrateBusinessSpaceSchema700.sql script, and edit the script as follows:

      • If the @SCHEMA@, @TSPRE@, @STOGRP@, @BPINDEX@, and @BPLOB@ variables have not been resolved in the script, replace these variables with the actual schema name, tablespace prefix, storage group, buffer pool for indexes, and buffer pool for large objects.
      • Verify that the correct database name is referenced in the script.

    5. Run the migrateBusinessSpaceSchema700.sql script, as described in the header of the file.
  4. Migrate the Business Space data.

    1. Start your product server or cluster. Depending on your environment and operating system, use one of the following procedures:

      • For a stand-alone environment, start the migration target server by using the startServer command from the profile_root/bin directory of the migration target server or from the target profile's First steps console. The profile_root value is the node that the migration target server belongs to.

        Use the following syntax:

        • startServer.sh server_name

        • startServer.bat server_name

        For more information about the startServer command, see startServer command in the WebSphere Application Server Information Center.

      • For a stand-alone environment, start the migration target server as described in Starting stand-alone servers.
      • For a ND environment, complete the following steps.

        Important: Perform the procedure using one of the following methods, depending on how the ND environment is configured:

        • If the Business Space database being updated belongs to a non-clustered managed node where Business Space is configured, start the node agent and the server on the node.

        • If the Business Space database being updated belongs to a clustered environment, select a node that is participating in the cluster and start the node agent and server on it.

        • For a Business Space clustered environment, the cluster needs to be started.

        1. For a database on a non-clustered managed node:

          Start the migration target node agent using the startNode command from the profile_root/bin directory of the migration target server.

          Use the following syntax:

          • startNode.sh

          • startNode.bat

          For more information about the startNode command, see startNode command in the WebSphere Application Server Information Center.

        2. For a database in a clustered environment:

          Start the migration target server using the startServer command from the profile_root/bin directory of the migration target server or from the profile's First steps console.

          Use the following syntax:

          • startServer.sh server_name

          • startServer.bat server_name

          For more information about the startServer command, see startServer command in the WebSphere Application Server Information Center.

        3. In a clustered environment, start the cluster.

          Start the migration target server using the startServer command from the profile_root/bin directory of the cluster or from the cluster's First steps console.

          Use the following syntax:

          • startServer.sh server_name

          • startServer.bat server_name

          For more information about the startServer command, see startServer command in the WebSphere Application Server Information Center.

      • For a ND environment, start the cluster as described in Starting managed servers.

      You can ignore any messages about not being able to connect to the messaging engine.

    2. On the node for which the target server was started, run the migrateBSpaceData script using the -dbcopy option to copy Business Space data from V7.0.x to V8.0.1. In a clustered environment, run the script on any custom node where Business Space is deployed.

      Use the script for your operating system:

      The script is located in the following directory: INSTALL_ROOT/BusinessSpace/scripts/. For more information about the migrateBSpaceData script, see migrateBSpaceData command-line utility.

    3. Stop the target server. Depending on your environment, use one of the following procedures:

      • For a stand-alone environment, stop the migration target server by using the stopServer command from the profile_root/bin directory on the migration target system. .

        Use the following syntax:

        • stopServer.sh server_name -username user_name -password password

        • stopServer.bat server_name -username user_name -password password

        • If the profile has security enabled, the user name provided must be a member of the operator or administrator role.

        • If security is enabled, the -username and -password parameters do not have to be specified if the server is running as a Windows service. In this case, the parameters are automatically passed into the script that the Windows service uses to shut down the server.

        • If the profile does not have security enabled, the -username and -password parameters are not necessary.

        For more information about the stopServer command, see stopServer command in the WebSphere Application Server Information Center.

      • For a stand-alone environment, stop the migration target server as described in Stopping stand-alone servers.
      • For a ND environment, stop the servers in the target cluster.

        Repeat this step for each server in the cluster.

        Stop the migration target server using the stopServer command from the profile_root/bin directory on the migration source target.

        Use the following syntax:

        • stopServer.sh server_name -username user_name -password password

        • stopServer.bat server_name -username user_name -password password

        If the profile has security enabled, the user name provided must be a member of the operator or administrator role.

        If security is enabled, you do not need to specify the -username and -password parameters if the server is running as a Windows service. In this case, the parameters are automatically passed into the script that the Windows service uses to shut down the server.

        If the profile does not have security enabled, the -username and -password parameters are unnecessary.

        For more information about the stopServer command, see stopServer command in the WebSphere Application Server Information Center.

      • For a ND environment, stop each of the servers in the target cluster, as described in Stopping managed servers.

    4. Modify the oobLoadedStatus.properties file to confirm that the following three values are true: 
      importTemplates.txt=true
importSpaces.txt=true
importThemes.txt=true

      If any of these values are not set, add them.

      For a stand-alone environment, the oobLoadedStatus.properties file is located in: INSTALL_ROOT\profiles\ profile_name\BusinessSpace\ node_name\ server_name\mm.runtime.prof\public\.

      For a ND environment, check all of your nodes for the oobLoadedStatus.properties file (this file will exist on only one of the nodes), and make all modifications: INSTALL_ROOT\profiles\ your_node_profile_name\BusinessSpace\ cluster_name\mm.runtime.prof\public\.

    5. Start the server or the cluster in the target environment. Depending on your environment and operating system, use one of the following procedures:

      • For a stand-alone environment, start the migration target server by using the startServer command from the profile_root/bin directory of the migration target server or from the target profile's First steps console.

        Use the following syntax:

        • startServer.sh server_name

        • startServer.bat server_name

        For more information about the startServer command, see startServer command in the WebSphere Application Server Information Center.

      • For a stand-alone environment, start the migration target server as described in Starting stand-alone servers.
      • For a ND environment, complete the following steps.

        Important: Perform the procedure using one of the following methods, depending on how the ND environment is configured:

        • If the Business Space database being updated belongs to a non-clustered managed node where Business Space is configured, start the node agent and the server on the node.

        • If the Business Space database being updated belongs to a clustered environment, select a node that is participating in the cluster and start the node agent and server on it.

        • For a Business Space clustered environment, the cluster needs to be started.

        1. Start the migration target node agent by using the startNode command from the profile_root/bin directory of the migration target server.

          Use the following syntax:

          • startNode.sh

          • startNode.bat

          For more information about the startNode command, see startNode command in the WebSphere Application Server Information Center.

        2. Start the migration target server by using the startServer command from the profile_root/bin directory of the migration target server or from the profile's First steps console.

          Use the following syntax:

          • startServer.sh server_name

          • startServer.bat server_name

          For more information about the startServer command, see startServer command in the WebSphere Application Server information center.

        3. In a clustered environment, start the cluster.

          Start the migration target server using the startServer command from the profile_root/bin directory of the cluster or from the cluster's First steps console.

          Use the following syntax:

          • startServer.sh server_name

          • startServer.bat server_name

          For more information about the startServer command, see startServer command in the WebSphere Application Server information center.

      • For a ND environment, start the cluster as described in Starting managed servers.

    6. On the node for which the target server was started, run the migrateBSpaceData script using the -dbupgrade option to upgrade Business Space data from V7.0.x to V8.0.1. In a clustered environment, run the script on any custom node where Business Space is deployed.

      Use the script for your operating system:

      The script is located in the following directory: INSTALL_ROOT/BusinessSpace/scripts/. For more information about the migrateBSpaceData script, see migrateBSpaceData command-line utility.

  5. Verify the previous profile migration and data migration steps are all successful.

    1. Check all the migration traces and logs.

    2. Log in to Business Space to check that all the user-created spaces have been migrated.
  6. Remove obsolete database tables by the postMigrateBusinessSpace700.sql script.

    1. Log on to the database server as a user with read/write access on the database.
    2. Connect to the database.
    3. Locate the postMigrateBusinessSpace700.sql script for your database in the profile that you most recently configured, and save it to a location on the same system with the database.

      By default, the scripts are located in the following directory for a stand-alone server: profile_root/dbscripts/BusinessSpace/ node_name_ server_name/ database_product_name/ database_name and the following directory for a cluster: deployment_manager_profile_root/dbscripts/BusinessSpace/ cluster_name/ database_product_name/ database_name. The script is located in the profile for the server or cluster that you most recently configured.

      Important: This script might need to be modified if the default values do not match your environment.

    4. Change to the directory where you copied the script, and run the postMigrateBusinessSpace700.sql script, as described in the header of the file.

    You might receive the following message while running data migration: 

    SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; target Exception=java.net.SocketTimeoutException: Read timed out.
    To resolve this error, modify the com.ibm.SOAP.requestTimeout property by editing the soap.client.props file that is located in the properties subdirectory of the profile_root directory. Change the com.ibm.SOAP.requestTimeout value from 180 to a larger value, such as 1800, which is 30 minutes.


What to do next

If you have an IBM Forms Server configured with IBM BPM or WebSphere Process Server in the earlier releases, you must manually deploy the BSpaceForms.ear after the migration. Deploy the BSpaceForms.ear from the WASHome\installableApps\BusinessSpace directory to the application server.

Migrating databases