Try OpenEdge Now
skip to main content
Migrating to OpenEdge 11.7
Migrating OpenEdge Business Process Management : Savvion 7.6.X/8.0 to Progress OpenEdge 11.3.0 Migration Process : Before you begin

Before you begin

Do the following before beginning the Savvion 7.6.x/8.0 to OpenEdge 11.3.0 migration process:
1. Take a backup of the following:
a. Progress Developer Studio for OpenEdge workspace
Manually copy the BPM Studio workspace folder to any another location in your computer.
b. OpenEdge Database
Before you start the backup process, stop the AppServers/JBOSS Server and the database by using,, and respectively.
Your schema can become corrupt during the conversion or the migration process. If the conversion/migration fails, your database cannot be recovered. Therefore, you must take a backup of your database if you have to restore the database and begin the conversion/migration again.
probkup Db-nameDevice-name
Name of your database.
Directory structure of the location where you want to back up the data.
For example, if your Db-name is sbmdb and your Device-name is sbmdb.bkp file, then you must execute the following probkup command:
probkup sbmdb sbmdb.bkp
For more information on using the probkup utility, see Progress OpenEdge Data Management: Database Administration.
2. Export the following:
a. All the Savvion 7.6.X/8.0 projects and their artifacts.
In Savvion BPM Studio, select File > Export > General > Archive File to export all your OpenEdge BPM projects as an archive file to your computer.
As part of the migration, the archive file is imported to OpenEdge 11.3.0.
b. Savvion 7.6.x/8.0 Business Objects
*In Savvion BPM Studio, select OpenEdge > Tools > Business Objects. The Business Object Manager/Channel Manager/Message Manager dialog box appears.
*Select the available Business Objects, and then click Export. The file system dialog box appears.
*Specify the location in which you want to store your Business Objects, and then click OK.
Perform the above three steps to export Channels and Messages using the options OpenEdge > Tools > Business Objects and OpenEdge > Tools > Channels respectively.
3. The files that you store in your file system are imported to OpenEdge Developer Studio 11.3.0 as part of the migration. Ensure that BizStore and BizPulse process all the events; the values for last EventID in the BIZSTOREEVENTCOUNTER and BIZPULSEEVENTCOUNTER tables must match the maximum value of EventID in the BIZEVENT table.
4. When you install Target Progress Developer Studio for OpenEdge, specify the same administrator user name and password that you used in the Source BusinessManager (BM) installation. If you install the Target BusinessManager with a different administrator user name then, after the Target BM installation is complete, open the User Configuration tool and specify the Source BM administrator user and password for BusinessManager Admin Credentials.
5. For proper migration, both Source BM and Target BM must be configured with the same User Management Realm. If not, all the BusinessManager users will not be migrated. Your BusinessManager administrator must create the users.
6. If you are migrating from BusinessManager 7.6.3, run setupsbm -c ProcessViews.
Ignore this step, if you performed it as a part of the BusinessManager 7.6.3 installation.
7. Back up the Source BM database.
8. Back up the file system of BusinessManager installation folder.
9. Install Target BM with a fresh database instance. Do not execute repository setup from the First steps console (or using the setupsbm command) with the Target BM installation. Ensure that no database objects (such as table and sequence) exist in this instance.
10. Perform an export dump of the Source BM database. Import it to the database instance that is configured with Target BM.
11. Ensure that there are no adapters in active state in the Source BM.
12. Ensure that all the JMS messages in BusinessManager specific Topics and Queues are processed in Source BM.
13. After importing the database dump of Source BM to the database instance of Target BM, drop the following application-server-specific tables into the migrated database manually.
In the case of JBoss EAP 5.1, drop the following tables into the migrated database: