Use the Developer Studio to migrate the Source BPM Studio applications to the Target Developer studio applications.
The application migration is applicable to the following scenarios:
From Savvion BPM Studio 7.6.x to Developer Studio 11.3.0. In this case, Savvion BPM Studio 7.6.x is the Source and Developer Studio 11.3.0 is the Target.
From Savvion BPM Studio 8.0 to Developer Studio 11.3.0. In this case, Savvion BPM Studio 8.0 is the Source and Developer Studio 11.3.0 is the Target.
To migrate the Savvion BPM Studio applications to Developer Studio 11.3.0:
1. Open Start > All Programs > Progress > OpenEdge 11.3 > Developer Studio - Clean.
Developer Studio appears.
2. To migrate workspace to OpenEdge 11.3.0:
To migrate your Savvion 7.6.x workspace to OpenEdge 11.3.0 workspace, do the following:
1. Open migrateWorkspace.bat from <DLC_HOME>/oebpm/studio/migration/76to113 (typically, the OpenEdge installation location, DLC_HOME, is <drive>:\progress\Openedge\).
2. Specify values for the following variables:
Variable
Description
SAVVION_BPMSTUDIO_WORKSPACE
Specifies the Savvion BPM Studio workspace directory.
OEBPM_WORKSPACE
Specifies the new Developer Studio workspace directory that you use as the default workspace for OpenEdge 11.3.0.
OE_DLC_HOEME
Specifies the Progress Developer Studio for OpenEdge 11.3.0 installation directory. For example, C:\Progress\OpenEdge.
PDS_HOME
Specifies the Eclipse installation directory. For example, C:\Progress\OpenEdge\oeide\eclipse.
3. Run the migrateworkspace.bat file.
To migrate your Savvion 8.0 workspace to OpenEdge 11.3.0 workspace, do the following:
1. Open migrateWorkspace.bat from <DLC_HOME>/oebpm/studio/migration/80to113 (typically, the OpenEdge installation location, DLC_HOME, is <drive>:\progress\Openedge\).
2. Specify values for the following variables:
Variable
Description
SAVVION_BPMSTUDIO_WORKSPACE
Specifies the Savvion BPM Studio workspace directory.
OEBPM_WORKSPACE
Specifies the new Developer Studio workspace directory that you use as the default workspace for OpenEdge 11.3.0.
OE_DLC_HOEME
Specifies the Progress Developer Studio for OpenEdge 11.3.0 installation directory. For example, C:\Progress\OpenEdge.
PDS_HOME
Specifies the Eclipse installation directory. For example, C:\Progress\OpenEdge\oeide\eclipse.
3. Run the migrateworkspace.bat file.
3. Use File > Import > Archive File to import the archive file that you exported from Savvion 7.6.x/8.0.
Importing a project into OpenEdge 11.3.0 automatically builds those projects. However, before you can publish the imported projects.
After you import your projects, for each project you must manually perform the following:
Users who want to migrate their simulation projects from Savvion 7.6/8.0 to Progress OpenEdge 11.3.0 should first create a simulation project after installing OpenEdge 11.3.0 and copy the js folder from the Savvion directory ${WORKSPACE}\ .com.savvion.studio\simulation\reports and paste it in the {Simulation project}/reports folder.
This folder will be available in Progress OpenEdge 11.3.0 workspace only after a sample simulation project is created. For instructions on how to create a simulation project, refer to Creating a Simulation Project in OpenEdge Getting Started: Developing BPM Applications with Developer Studio.
Import all the Business Objects, Channels, and Messages
If you have migrated your Savvion 7.6.x/8.0 workspace to OpenEdge 11.3.0 as per Step 2, you do not need to manually import the Business Objects, Channels, and Messages. Proceed with Convert to Multiple Process project.
Use the Developer Studio menu bar options, OpenEdge > Tools > Business Objects/Channels/Messages, and import Business Objects to Developer Studio 11.3.0.
Convert to Multiple Process project
Before publishing projects imported from BPM Studio 7.6.x to Developer Studio 11.3.0, you must manually convert each single-process project into a multiple-process project. To convert the projects, do the following:
Right-click the project, and select Progress OpenEdge > Move and Convert to a Multiple Process BPM Project. Follow the wizard to convert the project to a multiple-process BPM Project.
Migrate savvion datatypes to OpenEdge ABL datatypes
Savvion datatypes from Savvion 7.6.x/8.0 are deprecated in OpenEdge 11.3.0. Therefore, when you open your Business processes (SPT) and custom adapters (Java/JavaScript) in OpenEdge 11.3.0, in the Problems view, you receive warnings about the usage of Savvion datatypes in the SPT files.
You can access the Problems view using the menu option, Window > Show views > Others… > Progress OpenEdge Editor > Problems .
Although Savvion datatypes continue to work in OpenEdge 11.3.0, Progress Software recommends that you migrate Savvion datatypes to OpenEdge NDT or ABL datatypes to fix any warnings/errors that you might receive. Progress Software recommends that you migrate all the Savvion datatypes to OpenEdge NDT types as future product releases are likely to support only the OpenEdge NDT datatypes. Refer to the table in Points to remember to understand the mapping between Savvion and ABL datatypes.
Update the Managed adapters in your business processes (SPT files)
Migrate unsupported adapters to custom adapters: Your projects cannot be published if they consist of unsupported adapters. Therefore, for every project imported to OpenEdge 11.3.0, you must replace any unsupported adapters in the project with the custom adapters.
In your business process (SPT files), all the unsupported adapters appear with a cross symbol.
If you attempt to publish a business process with any unsupported adapter, you will receive error messages regarding the usage of unsupported adapters in the Problems view, which must be fixed before publishing a process.
You can access the Problems view using the menu option Window > Show views > Others… > Progress OpenEdge Editor > Problems.
Update all Managed adapters
For all supported managed adapters in your business processes (SPT), you must delete the maps folder in the adapter. When you build your project, an updated and OpenEdge 11.3.0-compatible maps folder is created automatically.
Update OpenEdge Managed Adapter’s configuration
If your business processes (SPTs) have OpenEdge a managed adapter in them, perform the following:
1. Select the managed adapter, and then select the Properties > Configuration > Configure... button.
The Configuration dialog box appears.
2. Re-select the procedure (.p) file for the Input file field. Edit the Procedure Details section, if required.
3. Change the value for Application service from sbmbroker1 to bpsbroker1.
4. Click OK.
5. Select the menu option Project > Build All to rebuild the project.
After changing the managed adapter configuration or any configurations in the project, you must build the project to generate the new artifacts.
Edit rules in Java/JavaScript code
All your Java/JavaScript code continues to work in OpenEdge BPM 11.3.0. However, you can only edit the files using the GEL Editor but you cannot use any drag-and-drop functionality from the pallets such as the Data Operations pallet and the Value Expression pallet.
You access the GEL editor to edit Java/JavaScript code using Properties > Advanced > Add/View script.
Edit Business Metric rules
All your applications containing business metric rule continues to work in OpenEdge 11.3.0. However, an application containing business metric rule on one of the activity configured with more than one condition fails to publish with compilation errors. This occurs due to an extra "(" generated between the conditions by the rule wizard. You must remove the extra "(" from between the conditions to make the application compile and publish in OpenEdge 11.3.0. Perform the following:
1. Open the business metric rule file from <project_name>\<process_template_name>\rules\<business_metric_rule_file.bps>.
2. Search for the additional “(“ present between the conditions. The below sample illustrates an extra “(“ generated between two conditions (marked in bold):
rule MyBusinessMetricRule_MYRULE activated by EVT_1 of
BizLogic::PI_COMPLETED {WORKSTEPNAME : "Activity 1",
PROCESSTEMPLATENAME : "doub_str"}
{
val piName = toString(EVT_1.context.PROCESSINSTANCENAME);
if ( (
doub_str::BM_MyBusinessMetricRule_Activity_b1_data::metric_ip[1][
1].num1_Sum >= 0 )
and ( (
doub_str::BM_MyBusinessMetricRule_Activity_b1_data::metric_ip[1][
1].num1_Maximum >= 100 )
)
3. Delete the extra “(“ and save the rules file.
4. Re-deploy the application.
Rebuild BPM Forms
All imported BPM forms must be re-built using the menu option Project > Build All before you re-install the business process in OpenEdge 11.3.0.
Your projects can then be published using OpenEdge 11.3.0.
4. Deploy Web, Common Resources, and BPM projects. Progress Software recommends that you deploy these projects with the Reinstall option.
5. To migrate applications published as Web services:
a. Copy the SBM_SOURCE_HOME\webapps\deploy\sbm\<ApplicationName>.jws file to the OEBPS_JBOSS\webapps\deploy\sbm folder.
b. Copy the SBM_SOURCE_HOME\webapps\deploy\sbm\wsdl\<ApplicationName>.wsdl file to the OEBPS_JBOSS\webapps\deploy\sbm\wsdl folder.
c. Copy the SBM_SOURCE_HOME\webapps\deploy\sbm\WEB-INF\jwsClasses folder to the OEBPS_JBOSS\webapps\deploy\sbm\WEB-INF folder.
From Savvion BPM Studio 7.6.x to Developer Studio 11.3.0. In this case, Savvion BPM Studio 7.6.x is the Source and Developer Studio 11.3.0 is the Target.