Points to remember

OEBPM 11.3.0 does not support migration of live instances. Therefore, you must ensure that all active instances are completed and that the servers are stopped before migration.

You cannot migrate a previous non-OpenEdge database to an OpenEdge database. You can only migrate a previous version of an OpenEdge database to an OpenEdge 11.3.0 database.

You cannot migrate a previous non-JBOSS server to a JBOSS server. OpenEdge 11.3.0 only supports JBOSS server.

OpenEdge 11.3.0 does not support BusinessManager clusters.

Process Asset Manager (PAM) is deprecated in OpenEdge 11.3.0. If you have any process or artifacts in PAM, you must export them to the local file system using your existing BPM Studio before migrating to OpenEdge 11.3.0. Artifacts that are exported to the local file system can be re-imported to Progress Developer Studio for OpenEdge 11.3.0.

BizStore data is not migrated.

ABL Business Objects in Savvion 7.6.x are automatically migrated to the corresponding OpenEdge 11.3.0 Native datatypes (NDT). Savvion data types from Savvion 7.6.x/8.0 to OpenEdge 11.3.0 must be manually mapped as per data type mapping:

While migrating from Savvion 7.6/8.0 to Progress OpenEdge 11.3.0, the file names in the location <Progress_Savvion>\SBM\conf DLC\oebpm\server\conf change. Remember to update the file names wherever they are referred in your code. A few examples of modified file names are provided in the following table: