IBM Support

ODM interim fix 005 for 8.12.0.0

Download


Downloadable File

File link File size File description

Abstract

IBM ODM interim fix 005 has been made generally available and contains fixes to version 8.12.0.0 including all predecessor fixes.
Identifier: 8.12.0.0-WS-ODM-IF005

Download Description

Table of Contents
Sections Description

The Prerequisites section provides important information to review prior to the installation of this release.

The Components impacted section provides the list of Operational Decision Manager components affected by this interim fix.

The Installation instructions section provides the installation instructions necessary to apply this release into your environment.

the APARs and Known issues resolved

The Download package provides the direct link to the download package for installation in your environment.

Prerequisites

Before downloading the interim fix, perform the following steps:

For on premise installation:

  1. You have installed IBM Installation Manager 1.9 or newer
  2. You have installed Operational Decision Manager 8.12.0.0
For Kubernetes installation:
Add the ODM helm repository to your helm installation: 
helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm

Back to top

Components impacted

The following components in Operational Decision Manager are directly affected by this interim fix:
  • Decision Center
  • Rule Execution Server
  • Rule Designer
  • Build Command

Back to top

Installation Instructions

Before installing this interim fix, download the interim fix to a dedicated location: 8.12.0.0-WS-ODM-IF005.zip

This interim fix includes all fixes from previous versions on the 8.12.0.0-WS-ODM component.

To install the interim fix, ODM on premise instructions :

  • Install the interim fix using one of the following methods:
    • Installation using the IBM Installation Manager UI
      1. Select File > Preferences > Repositories.
      2. Click Add Repository, browse to select the downloaded zip file, and confirm.
      3. Back in the main UI, select Update and follow the instructions.
    • Silent installation using IBM Installation Manager commands
      1. Find the fix ID with the command:
      2. imcl listAvailableFixes com.ibm.websphere.odm.dc.v812_8.12.0.2023 -repositories <zip-location>/com.ibm.odm.<your_app_server>_8.12.0.0-IF005.zip
        or
        imcl listAvailableFixes com.ibm.websphere.odm.ds.rules.v812_8.12.0.2023 -repositories <zip-location>/com.ibm.odm.<your_app_server>_8.12.0.0-IF005.zip
        Both will give the same result but use the correct one depending on DC or DS, as it could impact the uninstall.
        The fix ID has the following pattern:
        com.ibm.odm.<your_app_server>.v812-fix_2.0.0.
      3. Install with the command:
        imcl install <fix ID> -repositories <zip-location>/com.ibm.odm.<your_app_server>_8.12.0.0-IF005.zip -installationDirectory <odm_home>
      4. The ifix zip and fix ID depend on the appserver.

To install the interim fix, ODM on Kubernetes instructions :

  • Using images in registry:
Set $name to the name of the previous release of ODM.
  1. Retrieve helm values for your release:  
    helm get values $name > myodmvalues.yaml
  2. Upgrade helm:  
    helm upgrade odmchart -f myodmvalues.yaml ibm-helm/ibm-odm-prod --version 23.1.5

For ODM on premise, perform the necessary tasks after installation

Once the installation is complete you can close Installation Manager.

Refer to the Problems solved section and perform the necessary steps depending on the impacted component you need to fix.

If your application embeds jars, repackage your application using the modified jars found in ODM_HOME/teamserver/lib and ODM_HOME/executionserver/lib.

Note: The interim fix does not update the Sample Server.

Interim Fix specific steps:

  • For DT236899, we added a system property in order to have the possibility to change the level of the reported error.
    For example -Dcom.ibm.rules.grammarerror.duplicateproduction.severity=error that must be added to the arguments to launch RuleStudio.

Decision Center

Find the Decision Center archive file corresponding to your application server under ODM_HOME/teamserver/applicationservers and redeploy it.

  • jboss/jrules-teamserver-JBOSS.ear
  • tomcat/decisioncenter.war
  • tomcat/decisioncenter-api.war
  • tomcat/decisionmodel.war
  • WLP/decisioncenter.war
  • WLP/decisioncenter-api.war
  • WLP/decisionmodel.war

Rule Execution Server

RES Console

If your are using the Execution Server Console, find the EAR corresponding to your application server under ODM_HOME/executionserver/applicationservers.

  • jboss/jrules-res-management-JBOSS.ear
  • tomcat/res.war
  • WLP/res.war

HTDS

If you are using the HTDS application, redeploy the application located in ODM_HOME/executionserver/applicationservers.

  • joss/jrules-res-htds-JBOSS.ear
  • tomcat/DecisionService.war
  • WLP/DecisionService.war

XU

Find the XU rar corresponding to your application server under ODM_HOME/executionserver/applicationservers and redeploy it.

  • jboss/jrules-res-xu-JBOSS.rar

Testing&Simulation

For testing and simulations in ODM, redeploy the application found in ODM_HOME/executionserver/applicationservers.

  • jboss/jrules-ssp-JBOSS.ear
  • tomcat/DecisionRunner.war
  • WLP/DecisionRunner.war

Rule Designer

To install the fix:

  1. Restart Rule Designer.
  2. Click Help > Check for Updates.
  3. Make sure IBM Decision Server Rule Designer is checked.
  4. Click Next.
  5. Review the terms of the license agreement and Click Finish.
  6. Proceed with the installation.

If you have not installed Rule Designer from ODM_HOME/studio/update-sites/, copy the new update sites into your location before applying the above procedure.

Build Command

For the Build Command command line tool, find the modified jar under
ODM_HOME/buildcommand/rules-compiler/rules-compiler.jar.

If you are using the Build Command Maven plugin, redeploy the plugin in your environment:

  • To deploy to a remote Maven repository, use the following command:
    mvn deploy:deploy-file -Dfile=rules-compiler.jar -DpomFile=rules-compiler-maven-plugin.pom
  • You can also test the plugin locally by running the following command:
    mvn install:install-file -Dfile=rules-compiler.jar -DpomFile=rules-compiler-maven-plugin.pom

For ODM on Kubernetes, perform the necessary tasks after installation

Once the installation is complete you can close Installation Manager.

Refer to the Problems solved section and perform the necessary steps depending on the impacted component you need to fix.

If your application embeds jars, repackage your application using the modified jars found in https://DC_URL/assets/decision-center-client-api.zip

Rule Designer

To install the fix:

  1. Start Eclipse.
  2. Click Help > Check for Updates. You should see listed and checked:
  3. IBM Decision Server Designer Base 8.12.0.0-IF005 IBM ODM for Developers - Rule Designer 8.12.0.0-IF005
  4. Click Next.
  5. In the Install dialog, click Next.
  6. In the Review Licenses dialog, select I accept the terms of the license agreement, and then click Finish. The installation might take a few seconds to complete. If a security warning about the validity of the software opens, click OK to proceed with the installation.
  7. If you are prompted to restart Eclipse, click Yes.

Download Package

Click the link in the Download Options column:
Download Release Date Language Size Download Options
8.12.0.0-WS-ODM-IF005 11 October 2023 Language Independent 3.15 GB
ODM Chart based on ODM 8.12.0.0 IF005 11 October 2023 Language Independent -

Back to top

Problems Solved

Interim fixes include security fixes, those included in this version are detailed in the October security bulletin.

This interim fix delivers images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly.

This interim fix includes fixes for these libraries to address:

CVE-2022-35252, CVE-2022-43552, CVE-2023-27535, CVE-2022-45939, CVE-2023-2491, CVE-2022-2795, CVE-2022-36227, CVE-2023-0361

Previous interim fixes are included in this interim fix.

The following are all the new fixes:

Fixes in interim fix 005 (8.12.0.0-WS-ODM-IF005):

  • DT224750: WEBHOOK EVENTS FORMAT IS INCORRECT
  • DT228835: THE VERTICAL SCROLLBAR IN TEST REPORT RESULTS DOES NOT WORK CORRECTLY IN UP DIRECTION
  • DT238575: TEST REPORT DETAILS MAY NOT DISPLAY THE VALUE OF ALL FIELDS
  • DT238969: RULE PROPERTY VIEW CONTENT NOT EDITABLE
  • DT239109: BUILD COMMAND INCLUDES INACTIVE RULES IN RULESET USING DEFAULT VALIDATOR
  • DT239177: CANNOT RENAME A BRANCH WHEN PERMISSION IS ENFORCED
  • DT242492: UNABLE TO MIGRATE AN ORACLE REPOSITORY
  • DT242587: EXPORT DECISION SERVICE REST-API ENDPOINT RETURNS ERROR CODE
  • DT243179: MERGE CHANGES NOT REFLECTED IN RELEASE WHEN CHANGE ACTIVITIES ADD DELETED RULE ARTIFACTS USING DECISION GOVERNANCE FRAMEWORK (DGF)

The following are all the previous fixes:

Fixes in interim fix 004 (8.12.0.0-WS-ODM-IF004):

  • DT228706: MERGE CHANGES NOT REFLECTED IN RELEASE WHEN CHANGE ACTIVITIES ADD DELETED RULE ARTIFACTS
  • DT236899: THERE IS NO ERROR REPORTED WHEN 2 MEMBERS IN A BOM CLASS VERBALIZED WITH SAME PHRASE
  • DT238184: BUILDING PROJECTS WITH THE BUILD COMMAND LINE FAILS WHENEVER A RULE PACKAGE HAS AN AMPERSAND CHARACTER IN ITS NAME
  • DT238293: CLASSCASTEXCEPTION WHEN DEPLOYING A DECISION ENGINE RULESET
  • DT238726: DEPLOYING A RULEAPP WITH ANT MAY THROW AN EXCEPTION
  • DT238795: UNABLE TO CREATE A BRANCH IS DECISION CENTER
  • It is now possible for a dedicated ruleset to use Decision Warehouse (monitoring.enabled) and the ODM event emitter (bai.emitter.enabled) at the same time..

Fixes in interim fix 003 (8.12.0.0-WS-ODM-IF003):

  • DT238558: Decision Center database setup sequence is failing at install
  • DT238563: About page displays wrong version

Fixes in interim fix 002 (8.12.0.0-WS-ODM-IF002):

  • DT222723: THERE ARE NO SECONDS IN DATE TIME EDITOR IN THE SIMULATION EDITOR
  • DT225197: SLOW PERFORMANCE WHEN DEBUGGING A RULESET
  • DT225452: MISSING ARTIFACTS IN DECISION CENTER AFTER DATABASE MIGRATION
  • DT233519: DC LDAP SYNC FAILS DUE TO 'BRM.LOCK' ERROR

Fixes in interim fix 001 (8.12.0.0-WS-ODM-IF001):

  • DT208408: EXECUTION ORDER IS DIFFERENT WHEN USING CRE VS DE WITH NO MAIN RULEFLOW
  • DT209907: CONTENTION WHEN EXECUTING MULTIPLE NEW RULESETS IN PARALLEL
  • DT211231: DEADLOCK WHEN J2SE CONNECTION POOL PURGE IS ENABLED
  • DT213847: COLLECTIONDOMAIN ANNOTATION DOES NOT WORK WHEN USED IN JAVA COLLECTION TYPES
  • DT213905: TESTING IN DECISION CENTER MAY THROW AN UNEXPECTED ERROR &quot;FAILED TO MIGRATE DVS PREDICATE&quot;
  • DT213909: BOM VERBALISATION UNAVAILABLE WHEN AUTHORING SEMANTIC QUERIES IN BUSINESS CONSOLE
  • DT214728: DECISION CENTER DEPLOYMENT MAY THROW UNEXPECTED BUILD ERROR
  • DT215406: UNABLE TO ENFORCE SECURITY OF DECISION SERVICES WITH SHARED PROJECTS
  • DT215895: WHEN COMPLETING A CHANGE ACTIVITY, CHANGES ARE NOT ALWAYS APPLIED TO RELEASE
  • DT222055: WHEN USING A CLUSTER, A PACKAGE RENAMED IS NOT ALWAYS INCLUDED IN THE RULESET ARCHIVE
  • DT222320: RTSCONFIGMANAGER CANNOT EDIT PROJECT DEPENDENCIES
  • DT222721: CREATOR NAME MAY BE INCORRECT IN RULE VIEW
  • DT224034: PERFORMANCE ISSUE WITH DB2 WHEN BROWSING A SUB-BRANCH

Back to top

Change History

30 Oct 2023: Fix broken download links

Off

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"ARM Category":[{"code":"a8m50000000L1a2AAC","label":"** Other **"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.12.0"}]

Problems (APARS) fixed
New: DT224750, DT228835, DT238575, DT238969, DT239109, DT239177, DT242492, DT242587, DT243179. Previous: DT228706, DT236899, DT238184, DT238293, DT238726, DT238795,DT238558, DT238563.

Document Information

Modified date:
30 October 2023

UID

ibm17035302

Page Feedback