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 > Postmigration tasks

Postmigration tasks for IBM BPM

After migration, you might need to check some configuration settings, or further configure the V8.0.1 server.

Ensure that you have migrated your server or cluster and verified that the migration was successful.

Perform the following tasks, if applicable to your environment:

• If you did not have administrative security enabled before migrating to V8.0.1, you must enable it by performing the actions described in Configure administrative and application security.
• Examine any Lightweight Third Party Authentication (LTPA) security settings that you might have used in an earlier version, and make sure that V8.0.1 security is set appropriately.
• Check the BPMMigrateProfile. profile_name. timestamp.log file in the logs directory for details about any JSP objects that the migration tools did not migrate.

  If V8.0.1 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.

• 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.

• After migrating to V8.0.1, check your WebSphere Adapter properties to ensure that they are properly configured for the new installation location. Some adapter properties might need to be altered during migration in a way that would be unknown to an automated migration.

• If you had uninstalled applications using Websphere Adapters before migration as mentioned in Runtime premigration checklist, you can use IBM Integration Designer to update the applications to use Websphere Adapter V8.0.1 and install them in the V8.0.1 target environment. You can install these updated applications using the administrative console. See Migrating applications using previous adapter levels for more information.

• To support the migration of version 6.2.0.x of the WebSphere Adapter for SAP to IBM BPM V8.0.1, you must migrate the previous version of the application in IBM Integration Designer before it can be deployed onto IBM BPM V8.0.1.

• After migrating to V8.0.1, be aware that the default value for the target significance property changed from V7.5.1, 7.5, 7.0, or 6.2.0. In V8.0, the default value was changed from targetSignificance=prefered to targetSignificance=required. The new default value is set in the JMS activation specifications and connection factories that are part of the IBM BPM configuration.

  You must determine whether to change the target significance value in the migrated environment.

• After migrating to V8.0.1, check that your ports are mapped correctly to make sure that the Remote Artifact Loader can access the security port on the application cluster when the global security is turned on. To verify that your ports are configured correctly, use the following procedure:

  1. In the administrative console, navigate to Environment > Virtual Hosts.

  2. Select default_host > Host Aliases.
  3. Check if the application cluster security port ( WC_adminhost_secure or WC_defaulthost_secure) is mapped to "*" which means "all hosts." If it is not, change it to "*" by clicking New, then entering "*" in the Host Name field and the port number of the application cluster in the Port field.
  4. Save your changes by clicking Apply or OK, and then select Save.

• After migrating to V8.0.1, be aware that authorization for actions on processes and tasks now gets enforced correctly in cases where it was not enforced previously. Before V8.0.1, if you use the Expose to start setting in a BPD to restrict who can start a process, this setting is ignored, and anyone can start a process. If you want to retain this behavior in V8.0.1, create a new version of your process, and change the Expose to start setting so that all users can start the process.

• After migrating to new hardware using the remote migration procedure, check the configuration of data sources and endpoints for references to tags like localhost and make sure the configuration is still valid.

  For example, if the data source points to localhost and after remote migration that database is still on the previous version machine, the data source must be updated to the previous version machine name for the system to work correctly.

• If you are migrating a standalone profile, add the new default users for IBM BPM to the custom-based federated user repository. The default users bpmAuthor and admin are required for administration of IBM BPM.

• If you are migrating a ND environment, add users and groups to the custom-based federated user repository. The previous version of the default user registry does not contain the default users that are required for IBM BPM; you must add the new default users to the custom-based federated user repository. The default users bpmAuthor and admin are required for administration of IBM BPM. In addition, you must add the other default user accounts, as described in the topic Default users and groups.

The migration tools convert appropriate command-line parameters to Java virtual machine settings in the process server definition. Most settings are mapped directly, but some settings are not migrated because their roles differ in WebSphere Application Server version 8.0. In such cases, the configuration settings might not exist, they might have different meanings, or they might have different scopes. See the following topics in the WebSphere Application Server information center for more information about changing the process definition settings or JVM settings:

• Process definition settings
• Java virtual machine settings

• Registering IBM BPM widgets in IBM Case Manager (post-product migration)
  

  If you have migrated from IBM BPM V7.5 and you use the widgets with IBM Case Manager, you must register the widget catalog and endpoints in the V8.0.1 environment before you can use the widgets.

Postmigration tasks

Related tasks:
Migrating applications using previous adapter levels