WebSphere Operational Decision Management for z/OS: Migrating from V7.5 to V8.0

News


Abstract

WebSphere Operational Decision Management V8.0 introduces significant changes from WebSphere Operational Decision Management V7.5. Before you migrate your projects, you must assess the impact of the changes on your application.

Content

When you migrate from one release to another, you must be aware that each release is a complete installation with a new distribution structure. Keep an installation of a previous version of WebSphere Operational Decision Management during your migration to ensure that you migrate the most up-to-date version of your rule projects.
When you first install WebSphere Operational Decision Management V7.5 for z/OS, you create various artifacts which need to be considered during migration. These can include some or all of the following:

  • Working data sets
  • Work paths
  • CICS work paths
  • A Decision Server for z/OS database
  • A Decision Center for z/OS database
  • An events runtime for z/OS database
  • Various files if using FILE persistence

You should back up the above artifacts before migration, and you should try the migration in a test environment first.

To migrate from WebSphere Operational Decision Management (WODM) V7.5, complete the steps for all installations, and then follow the sections required by your own topology.

For all installations
1. Backup the <V7.5 HBRWORKDS>.SHBRPARM(HBRINST) member, work data sets, and work path.
2. Populate the <V8.0 HBRHLQ>.SHBRPARM(HBRINST) member (or a copied version of it), using some of the values from your V7.5 installation to help.
Note
The HBRINST member from V7.5 is incompatible with V8.0. V8.0 includes new variables, and it is likely to have different values for several of the current variables. Use the previous installation variable values from V7.5.
3. Run <V8.0 HBRHLQ>.SHBRJCL(HBRUUPTI) to produce the new WORKDS datasets.
4. Back up the databases (Decision Center, Decision Server and Events) used for the V7.5 installation. The details of these are dependent on your environment, and the configuration of your setup.
5. Backup any files that you are using in FILE persistence. These are located in the directory indicated in HBRFILEPATH.

For Rule Designer
Follow the steps under the title 'Design Migration' at How to migrate from Decision Server and Decision Center V7.5

You must update your projects with any updated JARs that have been included from V7.5. If you are upgrading other products at the same time, such as WebSphere Application Server, you must consider the files that have been included from these projects as well.

For zRule Execution Server for z/OS (Decision Server for z/OS)
When working with a Rule Execution Server for z/OS, if you use the same subsystem ID name for the new release, the same PROCLIB member is required. As a result, you can only start one instance of zRule Execution Server for z/OS. You must consider this when completing the steps below.

1. Create the working data sets and work paths for V8.0. The structure has changed compared with V7.5, so you need to transfer the work path to the new structure (logs, deployment history). The process is defined in Performing the initial configuration.
2. Create the new databases using the new schemas. The process is defined in Configuring a DB2 persistence layer.
3. Deploy your rules (RuleApps) and Execution Object Models (XOMs) to the new persistence layer.

For Rule Execution Server (Decision Server for z/OS) running on WebSphere Application Server for z/OS
To migrate Rule Execution Server running on WebSphere Application Server, you must remove V7.5 before you install V8.0. The steps below will guide you through the uninstall and indicate the V8.0 installation process.

1. Create the working data sets and work paths for V8.0. The structure of these has changed, so you must transfer the work path to the new structure (logs, deployment history). The process is defined in Performing the initial configuration.
2. Create the new databases using the new schemas. The process is defined in Step 5: Configuring a DB2 persistence layer.
3. Uninstall the following applications from WebSphere Application Server:
- ILOG Rule Execution Server
- jrules-res-htds-WAS7
4. Uninstall the following Resource adapter from WebSphere Application Server:
- ILOG RES XU Resource Adapter
5. In WebSphere Application Server, point the data source for Rule Execution Server at the new schema to be used. This is found in Resources > JDBC > Data sources > [DataSource name] > Additional Properties > Custom properties.
6. Restart WebSphere Application Server.
7. Set up a new version of Rule Execution Server by completing steps 6 – 10 in Configuring Rule Execution Server on WebSphere Application Server for z/OS with DB2.
At step 8, correct the location to the jrules-mbean-descriptors.jar to the V8 location.
8. Verify the configuration as specified in Verifying the configuration.
9. Deploy your rules (RuleApps) and Execution Object Models (XOM)s to the new persistence layer for your business rules.

For CICS JVM and CICS Standalone:
After you have migrated the Rule Execution Server for z/OS instances, you can migrate the CICS configurations by following this set of instructions:

1. In the CICS system initialisation table, change the START parameter to INITIAL and take note of its original value.
2. Stop your CICS region.
3. Submit the V8 version of ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSD) job to redefine the resources required by CICS.
4. Edit the CICS JCL to update the Rule Execution Server for z/OS data sets to the V8 datasets:
a. Modify the ++HBRHLQ++.SHBRAUTH library in the STEPLIB concatenation to point at the V8 version.
b. Modify the ++HBRHLQ++.SHBRCICS library in the DFHRPL concatenation to point at the V8 version.
c. Modify the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSD) and ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCMMN) libraries in the HBRENVPR concatenation to point at the V8 versions.
d. If you are running CICS JVMServer, also modify the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSJ) library in the HBRENVPR concatenation to point at the V8 version.
e. If you are running CICS Standalone, also modify the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSZ) library in the HBRENVPR concatenation to point at the V8 version.
f. If you plan to run the Miniloan sample application to verify your configurationm, modify the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRSCEN) library in the SCENARIO concatenation to point at the V8 version.
5. If you are running CICS Standalone, start the zRule Execution Server for z/OS instance and the Rule Execution Server console.
6. Start the CICS region.
7. Test the configuration by running the HBRC transaction to connect CICS to zRule Execution Server for z/OS. If CICS succeeds in connecting to the server, message GBRZC9001I is issued. If CICS fails to connect to the server, message GBRZC9000E is issued with a return code containing diagnostic information.
8. In the CICS system initialisation table, set the START parameter back to it original value. It is likely that it was set to AUTO.

For Decision Center for z/OS
Decision Center for z/OS must be removed from WebSphere Application Server for z/OS and the V8.0 version installed in its place. New working data sets, paths and the database must be created. The steps below will guide you through this installation.

1. Create the working data sets and work paths for V8.0. The structure of these has changed, so the work path must be transferred to the new structure (logs, deployment history). The process is defined in Performing the initial configuration.
2. Create the new databases using the new schemas, using the process defined in Step 4: Creating the Decision Center DB2 database.
3. Archive the previous Decision Center database if you do not require history data to be preserved and want to configure the new installation by only deploying projects.
4. Uninstall the following application from WebSphere Application Server for z/OS:
ILOG Rule Team Server
jrules-ssp-WAS7 (if present)
5. In WebSphere Application Server Administrative console, point the data source for Decision Center for z/OS at the new schema to be used. This can be found in Resources > JDBC > Data sources > [DataSource name] > Additional Properties > Custom properties > currentSchema.
6. Restart WebSphere Application Server for z/OS.
7. Install the V8 version of Decision Center by completing steps 8 and 9 specified in Configuring the Decision Center consoles on WebSphere Application Server for z/OS with DB2
8. If Decision Validation Services is required, then install the V8 version by completing step 1 in Configuring Decision Validation Services on WebSphere Application Server for z/OS
9. If you want to preserve the history of your previous repository configure the new Decision Center Enterprise console to connect to the repository used by V7.5. If you do not want to preserve the history, publish the migrated projects in Rule Designer and Event Designer to a new Decision Center repository.

For the events runtime on z/OS (Decision Server for z/OS)
The events runtime V8 is not compatible with previous versions.
If you decide that you want to install the events runtime V8 on the same WebSphere Application Server for z/OS as a previous version, then it is necessary to uninstall the old version first. The steps below guide you through the uninstall, and point you to the installation for V8.

1. In your original configuration directory (<Component Directory>/config), run the following scripts:
1. Remove the messaging configuration by running <Component Directory>/config/was/configure_messaging.sh -undo
2. Remove the bus configuration by running <Component Directory>/config/was/configure_bus.sh -undo
3. To remove the application, run <Component Directory>/config/was/install_app.sh -undo
4. Remove the modified wbe properties by running <Component Directory>/config/wbe/update_wbeprops.sh -undo
5. Remove the data source by running <Component Directory>/config/was/configure_wbe_datasource.sh -undo
6. Destroy the links to the V7.5 WBE installation by running <Component Directory>/config/was/delete_wbe_links.sh
2. Restart WebSphere Application Server for z/OS.
3. Install the events runtime as specified in :
Configuring the event runtime on z/OS

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Operational Decision Manager for z/OS

Software version:

7.5, 8.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

1597528

Modified date:

2012-06-08

Translate my page

Machine Translation

Content navigation