Knowledge Collection: Migration for IBM Business Process Manager (BPM)

Content

Knowledge Collections are navigation aids that organize content to help users quickly find relevant information. Knowledge Collections are not designed to be an all-inclusive list of all documents dealing with the specific theme. The applicable version is included in each entry.

Other Knowledge Collections are available for the IBM Business Process Manager.
If you need technical support, see the Support section for information on what IBM Software Support needs to investigate the issue.


YouTube: High-level steps for migrating business data and applications from IBM BPM Advanced V8.x or V7.5x



ORA-25137 exception occurs when accessing the Performance Admin Console after migrating from WebSphere Lombardi Edition V7.1 to IBM Business Process Manager (BPM) V8.5.5 with an Oracle database (1675478)
Version: 8.5.5
After you migrate from WebSphere Lombardi Edition V7.1 using an Oracle database, you see a CWLLG2229E exception when you click "View Statistics" in the Performance Admin Console.

User synchronization SQL exception is received after migrating from Lombardi TeamWorks 6.2 to IBM Business Process Manager (BPM) 8.5.5 with an SQL Server (1675951)
Version: 8.5.5
After migrating from Lombardi TeamWorks V6.2 to IBM Business Process Manager (BPM) 8.5.5 with an SQL Server, you attempt to access ProcessAdmin -> User Synchronization -> Existing User Synchronize. This action results in an SQL exception.

'The system cannot find the path specified' error is received after migration when running the upgradeSchemaAll_MyWPS.bat command in IBM Business Process Manager (BPM) (1677033)
Version: 8.5.5
After migrating, if you configured the Business Process Choreographer (BPC) Archive on your source environment, the BPC Archive database schema is not upgraded by the upgradeSchemaAll.sh/bat command in IBM Business Process Manager.

Acccessing process inspector after changing the Deployment Environment administrator results in the CWTBG0019E error in IBM Business Process Manager (BPM) V8.5 (1678371)
Versions: 8.5.5 and 8.5.0 Fix Pack 1
After changing the Deployment Environment administrator alias, you receive the CWTBG0019E error when you check a running process instance from the web based process inspector.

Widgets in Business Space are not working after migrating to IBM Business Process Manager (BPM) Standard or IBM Business Process Manager Express (1674803)
Versions: 8.5.5 and 8.5
After migrating, widgets that are available only in IBM Business Process Manager Advanced are visible in IBM Business Process Manager Standard or IBM Business Process Manager Express, but they do not work. When out-of-the-box Business Spaces are composed using IBM Business Process Manager Advanced widgets, those Business Spaces also do not work.

IBM Business Process Manager (BPM) migration to V8.5.x does not have the option to migrate a non-clustered network deployment environment (1674801)
Versions: 8.5.5 and 8.5
When you migrate to IBM Business Process Manager V8.5.x, you cannot enter the cluster information in the migration.properties file if your source environment is a network deployment environment configured without a cluster.

The Upgrade_6x script for the IBM Business Process Manager (BPM) results in failed to initialize the ORB exception while building mapping file (1670772)
Version: 8.5
When you run the upgrade_6x script you get a failed to initialize the ORB exception while building the mapping file.

IBM Business Process Manager (BPM) Advanced migration errors fail to load default Process Portal templates and spaces (1638941)
Version: 8.5
After you migrate IBM Business Process Manager servers and the IBM Business Process Manager database to V8.5.0, the following errors are reported when the server starts: com.ibm.mm.server.persistence.rdbms.dao.ibatis.BaseDaoreadPathByPath BMWSD0429E: An SQLException was encountered while communicating with the database.  Error code: 0, SQL State:  null, Message:  Error: executeQueryForObject returned too many results.

Business Process Choreographer task instances fail after migration to IBM Business Process Manager (BPM) (1638908)
Versions: 8.5
If your source environment uses both active and historical LTPA keys, after you migrate to IBM Business Process Manager, executing a Business Process Choreographer task instance that uses historical keys will cause an error.

IBM Business Process Manager (BPM) Advanced properties that are customized in the source environment are not available in the target environment after migration (1638895)
Version: 8.5
In IBM Business Process Manager V8.5.0, database and security properties were moved from the 99Local.xml and 100Custom.xml configuration files to the WebSphere Application Server configuration files. These properties are no longer configurable using the 99Local.xml and 100Custom.xml configuration files. If you modified properties in the configuration files in the source environment, the customized properties are not available in the target environment after migration.

Migration to IBM Business Process Manager (BPM) V8.5 from IBM Business Process Manager or WebSphere Process Server V7.0.0.x augmented with IBM Business Monitor fails (1639714)
Version: 8.5

The upgrade_6x script for IBM Business Process Manager (BPM) results in a java.lang.ClassNotFoundException error (1668180)
Version: 8.5
When you attempt to upgrade Lombardi Teamworks V6.2 in-flight instances to IBM Business Process Manager Advanced V8.5, you see a "java.lang.ClassNotFoundException" message.

Migrating IBM Business Process Manager (BPM) Advanced V8.0 Clustered Process Center to IBM Business Process Manager Advanced V8.5 Clustered Process Center on Linux (7040213)
Versions: 8.5 and 8.0
This scenario describes an IBM Business Process Manager migration in a SuSE Linux and Oracle database environment.

The BPMMigrate.sh command for IBM Business Process Manager (BPM) Advanced results in a "SOAPException:java.net.SocketTimeoutException: Read timed out error" message (1668006)
Versions: 8.5 and 8.0
When you attempt to upgrade from IBM Business Process Manager Advanced V8.0 to Version 8.5, you encounter a "SOAPException:java.net.SocketTimeoutException: Read timed out error" message when you run the BPMMigrate.sh command.

SCA transaction behavior changes when migrating from WebSphere Process Server (WPS) V6.x (1653991)
Versions: 8.5, 8.0.1, 8.0, 7.5.1, 7.5
The SCA global transaction behavior changed beginning with WebSphere Process Server V7.x and IBM Business Process Manager (BPM) Advanced. When you migrate an application from WebSphere Process Server V6.x, some use cases in the error handling for an application might behave differently.

Other spaces (globe) icon in Process Portal does not work after migrating from IBM Business Process Manager (BPM) Advanced V8.0 (1638907)
Versions: 8.5 and 8.0.1
After you migrate from IBM Business Process Manager Advanced V8.0 to a later release or fix pack, the other spaces (globe) icon in Process Portal does not work to navigate to other Process Portal spaces.

Migrating to IBM Business Process Manager (BPM) results in log errors within the chart converter section of the migration log file (1616688)
Versions: 8.5 and 8.0.1
After you migrate to IBM Business Process Manager, the migration log contains errors in the chart converter section labeled as "Unknown" and "CWLLG3405I: The color '' is invalid."

Database migration from WebSphere Lombardi Edition (WLE) Version 7.1 to IBM Business Process Manager (BPM) fails with column length errors from the database upgrade script (1645813)
Versions: 8.5, 8.0.1, 7.5.1, and 7.5
When you attempt to migrate a database from WebSphere Lombardi Edition V7.1 to IBM Business Process Manager, it fails with a "ORA-01441: cannot decrease column length because some value is too big" error message.

The migration process for IBM Business Process Manager (BPM) fails with a TWU-0038 message while updating the LSW_OPTIMIZER_DATA.STRING_VALUE table (1648774)
Versions: 8.5, 8.0.1, 8.0, 7.5.1, and 7.5
You attempt to migrate your database from Lombardi Teamworks 6.2 or WebSphere Lombardi Edition 7.2.x to IBM Business Process Manager V7.5 or later. However, you see the following message: "TWU-0038: Original size of LSW_OPTIMIZER_DATA.STRING_VALUE in the source database has been changed."

IBM Business Process Manager (BPM) runtime migration support (1610883)
Versions: 8.5, 8.0.1, 8.0, 7.5.1, and 7.5
What versions of WebSphere Process Server and WebSphere Lombardi Edition can you migrate to the IBM Business Process Manager products using migration tools?

The Deployment Environment page in the WebSphere Integrated Solutions Console for IBM Business Process Manager (BPM) is blank and a NullPointerException message is thrown (1664300)
Versions: 8.0.1 Fix Pack 2, 8.0.1 Fix Pack 1, and 8.0.1
You migrate from WebSphere Process Server V7.0.0 Fix Pack 5 to IBM Business Process Manager (BPM) 8.0.1 Fix Pack 1 running with a DB2 database. When you click the Deployment Environment overview page in the WebSphere Integrated Solutions Console, the page is blank. In addition, a NullPointerException message is seen in the SystemOut.log of the Deployment Manager.

The upgradeProcessData command for IBM Business Process Manager (BPM) fails to recognize the Process Server database (1624173)
Versions: 8.0.1, 8.0, and 7.5.1
The upgradeProcessData command fails to recognize the Process Server database. The command fails with the following exception in the upgrade log files: "The configured Process Server database does not appear to be a Teamworks Process Server database."

A CWMCO0908E error message is seen when the upgraded cluster does not match the node level for IBM Business Process Manager (BPM) Advanced (1584411)
Versions: 8.0.1 Fix Pack 1 and 7.5.1
You cannot start the cluster member after upgrading from IBM Business Process Manager (BPM) Advanced V7.5.0 to 7.5.1

The profile for IBM Business Process Manager (BPM) Standard is incorrect when you migrate the same version to new hardware (1670813)
Versions: 8.0.1 and 8.0
You attempt to migrate your IBM Business Process Manager Standard profile to new hardware without changing the product version. You follow the information in the "Migrating to the same version on new hardware" topic within the IBM Business Process Manager product documentation. However, the profile that is created on the target hardware uses the incorrect profile template.

A CWLLG2229E BPDInstance is not found exception is seen after upgrading to IBM Business Process Manager (BPM) V8.0 (1620656)
Versions: 8.0.1 and 8.0
You migrate the Process Server database to IBM Business Process Manager Version 8.0 from a previous version. After migrating, you find multiple "CWLLG2229E: BPDInstance with ID BPDInstance.XXXX not found" exceptions in the SystemOut.log file when you start the server for the first time.

The upgradeProcessData or upgrade7x command for IBM Business Process Manager (BPM) fails with an AM_TASKS error (1632592)
Versions: 8.0.1 and 8.0
When you attempt to upgrade IBM Business Process Manager from previous version using the upgradeProcessData or upgrade7x command, you might encounter a SQLCODE=-204, SQLSTATE=42704, SQLERRMC=.AM_TASKS error.

The profile for IBM Business Process Manager (BPM) Standard is incorrect when you migrate the same version to new hardware (1670813)
Versions: 8.0.1 and 8.0
You attempt to migrate your IBM Business Process Manager Standard profile to new hardware without changing the product version. You follow the information in the "Migrating to the same version on new hardware" topic within the IBM Business Process Manager product documentation. However, the profile that is created on the target hardware uses the incorrect profile template.

The upgrade6x command hangs when migrating your database from Lombardi Teamworks V6.1 to IBM Business Process Manager (BPM) V7.5.1 (1620021)
Versions: 8.0.1, 8.0, and 7.5.1
When you migrate a Lombardi Teamworks V6.x Microsoft SQL database to IBM Business Process Manager V7.5.1, the upgrade6x command might hang after a large number of instances are processed.

The upgrade database command fails to clean up the SIBus tables during a database upgrade for IBM Business Process Manager (BPM) (1579275)
Versions: 8.0.1, 8.0, 7.5.1, and 7.5
The upgrade7x command or the upgradeProcessData fails during the SIBus tables cleanup task while upgrading the Process Server database to IBM Business Process Manager

The IBM Business Process Manager (BPM) BPMMigrateCluster command fails to run with the Oracle RAC database (1643703)
Versions: 8.0.1, 8.0, 7.5.1, and 7.5
You attempt to migrate the runtime from WebSphere Process Server (WPS) to IBM Business Process Manager with the Oracle RAC database. However, the process fails when the BPMMigrateCluster command attempts to migrate the App cluster application and the configuration information.

A NameNotFoundException occurs in the sca/WLE_/ActivationSpec log file after migrating to IBM Business Process Manager (BPM) (1626780)
Versions: 8.0.1, 8.0, and 7.5.1
If APAR JR44382 is not applied prior to migrating the WebSphere Process Server (WPS) Version 7.0 environment to IBM Business Process Manager, you will see a javax.naming.NameNotFoundException sca/WLE_cluster_name/ActivationSpec error after starting the migrated servers.

The upgradeProcessData.sh script for IBM Business Process Manager (BPM) fails to run on the AIX operating system (1633073)
Version: 8.0.1
When you migrate IBM Business Process Manager from a previous version to V8.0.1, the upgradeProcessData.sh script fails to run. This issue only happens on the AIX operating system.

A registry initialization error occurs after migrating to IBM Business Process Manager (BPM) Advanced for z/OS V8.0.1 (1619826)
Version: 8.0.1
After you migrate an IBM Business Process Manager Advanced for z/OS Network Deployment cell from Version 7.5.x to 8.0.1 and start the migrated servers, the registry might fail to initialize.

A java.lang.NullPointerException error occurs after migrating to IBM Business Process Manager (BPM) Advanced for z/OS V8.0.1 (1620031)
Version: 8.0.1
After you migrate an IBM Business Process Manager Advanced for z/OS Network Deployment cell from Version 7.5.x to 8.0.1 and start the migrated servers, a java.lang.NullPointerException error might occur.

A DB2 SQL Error SQLCODE=-478?SQLSTATE=42893 occurs when migrating from WebSphere Lombardi Edition (WLE) Version 7.2 to IBM Business Process Manager (BPM) Version 8.0 (1622266)
Version: 8.0
You are migrating WebSphere Lombardi Edition Version 7.2 to IBM Business Process Manager Version 8.0. When you use the upgrade_7x command with IBM DB2 V9.7.5, you encounter a DB2 SQL Error: SQLCODE=-478, SQLSTATE=42893.

IBM Business Process Manager (BPM) in-flight instance migration fails if the running instances have tokens on the business process definition (BPD) or service-level components are removed in the new snapshot (1615128)
Versions: 8.0, 7.5.1, and 7.5
When running instances that are being migrated have tokens on the BPD or service-level components are removed in the new version might fail.

The Enterprise Content Management (ECM) Server option is missing in the server settings after migrating to the IBM Business Process Manager (BPM) V8.0 products (1608611)
Versions: 8.0 and 7.5.1
After you migrate to an IBM Business Process Manager Version 8.0 environment, it does not contain the option to select an ECM Server.

The upgrade7x command fails when the number of characters used for performance data is greater than 64 characters for IBM Business Process Manager (BPM) (1597545)
Versions: 8.0, 7.5.1, and 7.5
You might have extended the maximum number of characters beyond the default of 64 characters in performance data. However, you might not have made the same change to the new environment before running the upgrade7x command.

Process Server and Process Center communication errors occur after upgrading to IBM Business Process Manager (BPM) Version 7.5.1 Fix Pack 1 (1615816)
Version: 7.5.1 Fix Pack 1
You might see communication exceptions between the Process center and Process server. You might see communication exceptions between the Process center and Process server. You might also see errors when you add new online or offline process server after you upgrade to Version 7.5.1 Fix Pack 1.

A CRIMC1020E error occurs when upgrading from IBM Business Process Manager (BPM) V7.5.1 to V7.5.1 Fix Pack 1 (1642038)
Version: 7.5.1 Fix Pack 1
When you attempt to upgrade from IBM Business Process Manager Version 7.5.1 to V7.5.1 Fix Pack 1, Installation manager cannot find the com.ibm.bpm.panel.invoke_7.5.0.110316 Java archive (JAR) file.

A stored procedure error occurs after upgrading an Oracle database for IBM Business Process Manager (BPM) V7.5.1. (1578872)
Version: 7.5.1
A compile error for the LSW_ERASE_TASK stored procedure occurs within the Oracle database after upgrading it from IBM Business Process Manager Version 7.5.0.x to Version 7.5.1

Performing an installation using a network deployment topology can cause problems during a WebSphere Lombardi Edition, Version 6.x migration (1500904)
Version: 7.5
An installation that implements a network deployment (ND) topology uses a different default password for the tw_admin user account than the password that is used for a stand-alone installation. This password also varies from previous releases of the custom security provider.

Back to top

Support

Back to top

Other Knowledge Collections for IBM Business Process Manager

• Knowledge Collection: Database documents for the IBM Business Process Manager (BPM) products (7036941)
• Knowledge Collection: Installation and configuration documents for the IBM Business Process Manager (BPM) products (7024590)
• Knowledge Collection: Performance documents for the IBM Business Process Manager (BPM) products (7037045)
• Knowledge Collection: Security documents for the IBM Business Process Manager (BPM) products (7036942)

Back to top