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 : Migrating to OpenEdge 11.3.0 : Database migration : Using the Data Migration tool
 
Using the Data Migration tool
Perform the following to migrate your data from Savvion 7.6.x/8.0 to OpenEdge 11.3.0:
1. From $DLC/oebpm/server/migration (on UNIX) or %DLC%\oebpm\server\migration (on Windows), extract the OpenEdge BPM Data Migration Utility, PROGRESS_OEBPM_DATA_MIGRATION_UTILITY_ALL.zip file, to a new folder on the computer on which OpenEdge 11.3.0 is installed. Then extract PROGRESS_OEBPM_DATAMIGRATION_7.6.X_OR_8.X_TO_11.3.zip in the same folder.
2. Open the PROGRESS_OEBPM_DATAMIGRATION_7.6.X_OR_8.X_TO_11.3\bin folder of the migration utility and set the environment variables in the setenv.cmd/sh file.
User the forward slash ('/') for specifying folder paths.
Property name
Description
Expected value
JAVA_HOME
Specify the location of the JRE/JDK installation folder.
—
OEBPS_TARGET_HOME
Specify the Business Process Server (BP Server location)
$DLC\oebpm\server
OEBPS_SOURCE_VERSION
Specify the version of the source Business Manager (BM)
7.6.x or 8.0
MIGRATION_HOME
Specify the location of the migration tool
$DLC\oebpm\server\migration
3. Open the PROGRESS_OEBPM_DATAMIGRATION_7.6.X_OR_8.X_TO_11.3\conf folder of the migration utility and set the environment variables in the migration.properties file.
Property name
Description
Expected value
oebps.target.home
Specify the location of the OpenEdge Business Process Server.
$DLC\oebpm\server
oebps.target.version
Specify the OpenEdge Business Process Server versions.
11.3ALPHA
oebps.target.webapp.folder
Specify the location of webapp folder of your Business Process Server.
$DLC\oebpm\jboss\webapps
oebps.target.admin.userid
Specify the user name of the OpenEdge database administrator.
admin
oebps.source.version
Specify the version of the source business manager.
7.6.x or 8.0
oebps.migration.home
Specify the location of the migration tool.
$DLC/oebpm/server/migration
oebps.migration.​continueonerror
Retain false if you want migration to discontinue if an error occurs.The default value is false.
false or true
oebps.migration.verbose
Specify true if you want verbose logs during migration.
false or true
oebps.db.provider
Specify the database provider.
openedge
oebps.db.driver
Specify the name of the OpenEdge driver.
com.ddtek.jdbc.openedge.​​OpenEdgeDriver
oebps.db.multibyteschema
Specify true for multi-byte language support.
false or true
oebps.db.target.url
Specify the database URL.
jdbc:datadirect:openedge:​//localhost:​<port-number>;DatabaseName=sbmdb
oebps.db.target.user
Specify the name of your database user, which you specified when installing and configuring OpenEdge Database during the OpenEdge 11.3 installation.By default, the name is dmadmin.
—
oebps.db.target.password
Specify the password of the database user, which you specified when installing and configuring the OpenEdge Database during the OpenEdge 11.3 installation.By default, the name is dbadmin.
—
4. If you have any deployed applications in Savvion 7.6.x/8.0, then you must copy them to the corresponding OpenEdge 11.3.0 installation. To copy your installation application to OpenEdge 11.3.0:
a. Open the SBM_HOME\ebmsapps folder of your Savvion 7.6.x/8.0 installation. Copy all the application folders except Com, Common, OpenEdgeDDLOperationHandler and any other product shipped folders to the corresponding OpenEdge 11.3.0 installation, <drive>:\Progress\OpenEdge\oebpm\ebmsapps.
If you have defined your BPM application specific files and folders in the Common folder of your Savvion 7.s6.x/8.0 installation, you must copy these artifacts to your OpenEdge 11.3.0 installation in <drive>:\Progress\OpenEdge\oebpm\ebmsapps\Common.
b. Open the SBM_HOME\webapps\deploy\sbm.war\ebmsapps folder of your Savvion 7.6.x/8.0 installation. Copy all the application folders except Com, Common, and OpenEdgeDDLOperationHandler to the corresponding OpenEdge 11.3.0 installation, <drive>:\Progress\OpenEdge\oebpm\jboss\webapps\deploy\sbm.war\ebmsapps.
Ensure that the Com, Common, and OpenEdgeDDLOperationHandler folders in the OpenEdge 11.3.0- installation are not replaced with the corresponding Savvion 7.6.x/8.0 folders.
5. If any application have rules, you must compile the application using the RuleCompiler utility, as below:
a. At the command prompt, type cd OEBPS_TARGET_HOME\bin, and then press ENTER.
b. At the <drive>:\OEBPS_TARGET_HOME\bin> prompt, type RuleCompiler -a AppName -blapi_lib -all, and then press ENTER.
6. Open the PROGRESS_OEBPM_DATAMIGRATION_7.6.X_OR_8.X_TO_11.3\bin folder of the migration utility and execute oebpsmigration.cmd/sh.
If the migration is unsuccessful, view the error message and troubleshoot accordingly. Optionally, you can also view the success/errors/warnings in the migration.log file in the directory OEBPS_HOME\logs.