Migrating from JRules to ODM

It is always recommended to use the latest available version to benefit from the latest released features.

First of all, you will need to verify that your configuration is still supported with the new version in
our online ODM system requirement page. Migration to a more recent version of ODM may require you to upgrade your databases and/or application servers.


For instructions to install the distribution of the new product, see Installing WebSphere Operational Decision Management (WODM) V7.5 and WebSphere Operational Decision Management V8.0 Download Document.


It is also recommended to use the latest fix pack for the version you are using. Applying a modification or a fix pack does not require to migrate your code nor your data.

Applying a modification or fix pack only requires to:

• install it,
• update your client application JRules/ODM libraries,
• redeploy the up-to-date versions of product Java EE modules you will have after running the fix pack installers (including the application server bundle in the case of JRules, see technote Upgrading JRules to the latest V7.1 fix pack).

Refer to the content below for details on those specific steps.

Here are the steps you will typically need to consider (if applicable in your case) and the order in which you should proceed to migrate your applications and data to the new version of WODM/ODM you installed:

1. Rule model extensions
2. Authoring & rule management extensions
3. Eclipse projects
4. ODM applications
5. Database data
6. Client applications

You can refer to section WebSphere Operational Decision Management V7.5 > Migrating from JRules > Migrating from JRules V7 > How to migrate from JRules V7 of the documentation to help you identify which of the above steps apply to your use of the product.

If migrating from JRules V6.x, you will first need to migrate your code and data to JRules V7.1. To do so, follow the steps below by substituting the module names 'Rule Designer' and 'Decision Center' respectively for 'Rule Studio' and 'Rule Team Server'. Also refer to the technotes for migrating rule projects to V7.1 and migrating to Rule Team Server V7.1 for more details.

---

1. Rule model extensions

If you extended the rule model, to add custom properties for example, you will need to add the same model extensions to the default extension model/data files of the new version you are migrating to.

Do not re-use the files of the previous version.

To obtain the new extension files, click "File > New > Other... > Rule Designer > Rule Model Extension > Extension [Model/Data]" in Rule Designer.

You will then need to apply those extensions on Rule Designer (in the new workspace preferences) and Decision Center (through the Installation Settings Wizard when creating the new tables) before you migrate the data.

Read more about on the rule model in the documentation under Decision Center V7.5 > Customizing > Customizing the rule model.

Back to the top

2. Authoring & rule management extensions

The code for the Rule Designer extensions, applied as plug-ins, and Decision Center extensions, deployed by repackaging the Decision Center application, will need to be re-built in the new Rule Designer version and updated (if you have deprecation warnings/errors).

You will then apply those according to the documented steps for the new version. Same for Rule Solutions for Office, when applicable.

See sections Decision Server Rules V7.5 > Developing rule projects in Rule Designer > Configuring the BOM for rule authoring > Customizing business rule authoring and management and Decision Center V7.5 > Customizing > Integrating business rule authoring extensions for more information on how to apply the updated extensions to the new Rule Designer and Decision Center.

Note that the Decision Center Business console, introduced in V7.5, currently only supports the value editor authoring extension. On the other hand. the Decision Center Enterprise console, formerly called Rule Team Server, supports all documented authoring & rule management extensions of previous versions.

Back to the top

3. Eclipse projects

Rule projects must be imported in a new workspace and re-built.

You will first apply your model and authoring extensions, if any (see step 1 & 2 above), and also ensure that Rule Designer is given sufficient memory by changing the default -Xmx512m to the
recommended -Xmx1024m in the <installDir>\ODM\eclipse.ini. You may need to give it more memory, depending on your configuration and the size of your rule projects.

If you are migrating from V7.1 and wish to deploy additional resources along with each of your Rule projects to Decision Center, you need to manually add a resource folder to your migrated project.

See section Decision Center V7.5 > Synchronizing and storing rules > Introducing synchronization > Rule project items of the documentation for more information on the feature, and section WebSphere Operational Decision Management V7.5 > Migrating from JRules > Migrating from JRules V7 > Migrating rule projects to include the resource folder for more details on manually creating the resource folder.

Back to the top

4. ODM applications

Those are essentially the product Java EE modules (EARs/WARs) you have deployed to your servers: the Decision Center/Rule Execution Center consoles, the eXecution Unit, the DVS SSP, the Transparent Decision Services…

You will first need to apply the same changes to the descriptors of the new modules that you had applied on the previous version:

• additional roles for Decision Center
• any custom settings

After applying your customizations, if any, you will deploy the new Java EE modules following the documentation for the corresponding application server.

See Decision Server Rules V7.5 > Configuring Decision Server > Configuring Rule Execution Server and Decision Center V7.5 > Configuring Decision Center for the detailed steps.

Back to the top

5. Database data

For the Decision Center rule projects, scripts are provided to migrate the data into a new database schema. Refer to the documentation at WebSphere Operational Decision Management V7.5 > Migrating from JRules > Migrating from JRules V7 > Migrating the Rule Team Server database for more details.

For the Rule Execution Server RuleApps, no data migration is required between V7.X/V8.X versions.

Only when migrating from V6.X will the RuleApps need to be migrated, as explained in technote Migrating RuleApps.

If migrating from V7.1 and want to use the new managed XOM feature introduced in V7.5, you need to extend the database to include the XOM repository.

You will either do so through the Installation Settings Wizard that you will be prompted when accessing the new Rule Execution Server console the first time, or by running the xomrepository_<DatabaseName>.sql script, found in new product distribution directory <InstallDir>/executionserver/databases, on the existing database schema.

For more information on the managed XOM feature, see section Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Deploying Java XOMs of the documentation.

For the Decision Warehouse trace, you may need to run a SQL script (<InstallDir>/executionserver/databases/migrate_trace_<database_name>_from_<version>.sql) on the existing database schema that you can re-use. See WebSphere Operational Decision Management V7.5 > Migrating from JRules > Migrating from JRules V7 > Migrating the Decision Warehouse database and Operational Decision Manager V8.0.1 > Migrating and upgrading your applications > Migrating from WebSphere Operational Decision Management > How to migrate from WebSphere Decision Server and WebSphere Decision Center for more details.

Back to the top

6. Client applications

To migrate client code for Rule Execution Server or Decision Center, you will need to re-build it with the new product client libraries, fix any deprecated warnings (possibly errors, if migrating across several versions) to use the new APIs, repackage your application(s) with your up-to-date classes and the new product libraries, before re-deploying your application(s) to the servers.

Back to the top

For more details on migration and specific use cases, please refer to the below links.