IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating to new hardware

Migrating a stand-alone environment to the same version on new hardware

Use this procedure to migrate a stand-alone environment to the same version on new hardware.

Review the Migrating to the same version on new hardware topic.

To migrate a stand-alone environment to new hardware, use the following procedure.

Procedure

1. Install the migration target products on the system that will serve as the target for the migration. You must install the identical product versions and fix packs on the target system as you have on the source system.

   You must either install the target version with the same user ID as that used for installing the source version or have permission to access the configuration and data on the source installation.

   Important: To migrate from source profiles augmented by multiple products, the new version of those products must be installed into the same target installation directory.

   For example, if the source profile is augmented by IBM BPM and IBM Business Monitor, both of those products must be installed into the same target installation directory.

2. Stop the migration source server.

   Stop the migration source server using the stopServer command from the profile_root/bin directory on the migration source system or from the profile's First steps console. 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.

3. Back up the migration source profile.

   Back up the profile configuration on the migration source server using the backupConfig command.

   Use the following syntax to back up a profile named profile1 to /ProfileBackups/profile1.zip:

   • 

     backupConfig.sh /ProfileBackups/profile1.zip -profileName profile1

   • backupConfig.bat c:\ProfileBackups\profile1.zip -profileName profile1

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

4. Back up the migration source product databases.

   Back up the following databases that are configured by the stand-alone profile according to the documentation for your database:

   • Business Process Choreographer database
   • Business Space Database
   • Common database
   • Common Event Infrastructure Database

   • Messaging Engine Database
   • Performance Data Warehouse database

   • Process Server or Process Center database

5. Migrate the stand-alone server profile. Follow the Migrating a profile to the same version on a remote system (new hardware) procedure.

6. Start the migration target server.

   Start the migration target server 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.

Results

The stand-alone environment is migrated to the target version.

What to do next

Perform Postmigration tasks for migrating to new hardware.

Migrating to the same version on new hardware