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

Postmigration tasks for migrating to new hardware

After migrating to new hardware, you might need to change some configuration settings that could not be updated automatically.

Ensure that you have migrated your server or cluster.


Procedure

  1. Review your Java™ virtual machine settings to verify that you are using the recommended heap sizes. See Java virtual machine settings. The information at this link applies to IBM BPM servers as well as to WebSphere Application Server servers.

  2. If you used Business Process Choreographer with people assignment before migrating to new hardware, and you used custom XSL transformation files or applied changes to default transformations that are not located in the INSTALL_ROOT/ProcessChoreographer/Staff directory, copy those transformation files from the source system to the target system.

    If you are unsure, on the source system, check the value of the transformation file path specified in the people directory configuration. If the transformation file path points to the INSTALL_ROOT/ProcessChoreographer/Staff directory, any custom transformation in that directory and any customizations made to the default transformations (EverybodyTransformation.xsl, LDAPTransformation.xsl, SystemTransformation.xsl, VMMTransformation.xsl, and UserRegistryTransformation.xsl) in that directory are migrated automatically.

    If the transformation file path specified in the people directory configuration does not point to INSTALL_ROOT/ProcessChoreographer/Staff, you might have to copy the transformation files from the source system to the target system to make them available.

    Remember: In a clustered environment, the transformation files must be available on the dmgr and on each node that hosts members of the cluster where Business Process Choreographer is configured. Verify that they all use the same version of the transformation file.

  3. Ensure that all clients and tools will access the new system. If the old host name is not redirected to the new hardware, update the URL that is used by clients and tools to point to the new hardware. Consider for example, browser clients, Process Center, Process Designer, and Integration Designer.


What to do next

Perform Verifying migration to new hardware.

Migrating to the same version on new hardware


Related tasks:
Customize the settings used by Process Server to connect to Process Center
Access the Process Center repository (to change the URI used by Integration Designer)