IBM Support

ODM interim fix 003 for 9.0.0.0

Download


Downloadable File

File link File size File description

Abstract

IBM ODM interim fix 003 has been made generally available and contains fixes to version 9.0.0.0 including all predecessor fixes.
Identifier: 9.0.0.0-WS-ODM-IF003

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 Known issues resolved

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

Prerequisites

Installation Instructions

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

This interim fix includes all fixes from previous versions on the 9.0.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.v90_9.0.0 -repositories <zip-location>/com.ibm.odm.<your_app_server>_9.0.0.0-IF003.zip
        or
        imcl listAvailableFixes com.ibm.websphere.odm.ds.rules.v90_9.0.0 -repositories <zip-location>/com.ibm.odm.<your_app_server>_9.0.0.0-IF003.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>.v90-fix_3.0.0.IFxxx
      3. Install with the command:
        imcl install <fix ID> -repositories <zip-location>/com.ibm.odm.<your_app_server>_9.0.0.0-IF003.zip -installationDirectory <odm_home>
      4. The ifix zip and fix ID depend on the appserver.

To install the interim fix, ODM on Kubernetes instructions :

  • Install the interim fix using one of the following methods:
    • Using images in registry:

      Set $name to the name of the ODM deployment.

      1. Retrieve helm values for your deployment:
        helm get values $name > myodmvalues.yaml
      2. Upgrade your deployment with helm:
        helm upgrade $name -f myodmvalues.yaml ibm-helm/ibm-odm-prod --version 24.0.3
    • Air gap installation:

      Set $name to the name of the ODM deployment.

      1. Update your mirror images following the Mirroring images to a private registry documentation.
      2. Retrieve helm values for your deployment:
        helm get values $name > myodmvalues.yaml
      3. Upgrade your deployment with helm:
        helm upgrade $name -f myodmvalues.yaml \
                         --set image.repository=$TARGET_REGISTRY/cp/cp4a/odm/ \
                         --set image.pullSecrets=pull-secret \
                         ~/.ibm-pak/data/cases/$CASE_NAME/$CASE_VERSION/charts/ibm-odm-prod-24.0.3.tgz

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. If you don't need them you can delete old versions of third party jar files.

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

Interim Fix specific steps:

  • .

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
  • WLP/decisioncenter.war
  • WLP/decisioncenter-api.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:
    IBM Decision Server Designer Base 9.0.0.0-IF003
    IBM ODM for Developers - Rule Designer 9.0.0.0-IF003
  3. Click Next.
  4. In the Install dialog, click Next.
  5. 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.
  6. If you are prompted to restart Eclipse, click Yes.

Download Package

Click the link in the Download Options column:
Downloads
Download Release Date Language Size Download Options
9.0.0.0-WS-ODM-IF003 13 September 2024 Language Independent -
ODM Chart based on ODM 9.0.0.0 IF003 13 September 2024 Language Independent -

Problems Solved

Interim fixes include security fixes, those included in this version are detailed in the September 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:

In interim fix 003: CVE-2024-2398, CVE-2024-34397, CVE-2024-37371, CVE-2024-38808, CVE-2024-6923, CVE-2022-26336, CVE-2024-37370, CVE-2024-39331

Previous interim fixes are included in this interim fix.

The following are all the new fixes:

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

  • DT392338: IN RULE DESIGNER V9 MAVEN M2E PLUGIN IS UNUSABLE
  • DT392428: ERROR MESSAGES REGARDING DOMAIN VALUES IN BOM TO XOM MAPPING
  • DT396432: NULLPOINTEREXCEPTION EXECUTING A QUERY

The following are all the previous fixes:

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

  • DT387048: RULEAPP GENERATION FAILS WHEN USING CONCURRENTHASHMAP

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

  • DT244599: DECISION CENTER DOES NOT ALLOW RULESET NAME WITH UNICODE LETTERS
  • DT257907: MISSING OBSERVED VALUES IN TEST SUITE REPORT
  • DT365362: INCOMPATIBLECLASSCHANGEERROR WHEN EXECUTING A CUSTOMEXCEPTIONHANDLER
  • DT381037: DECISION CENTER GOVERNANCE FRAMEWORK (DGF) - ONE CHANGE ACTIVITY COMPLETION IS REVERTING PREVIOUSLY APPROVED CHANGE ACTIVITY CHANGES IN THE RELEASE
  • DT381870: JAVA.UTIL.NOSUCHELEMENTEXCEPTION DURING BUILD
  • DT383182: JBOSS STARTUP MESSAGE MISSING WHEN DECISION CENTER IS DEPLOYED
  • DT383370: IN BUILD COMMAND LITERAL ORDERING DOES NOT WORK CORRECTLY WHEN THERE ARE DIFFERENT RULE TYPES IN THE SAME PACKAGE
  • DT386484: ERROR WHEN BUILDING RULES USING ISBETWEEN
  • DT387135: WHEN BUILDING A RULE PROJECT WITH SIMILAR RULES IN A FASTPATH TASK AN EXCEPTION MIGHT BE THROWN
  • DT387169: CANNOT CREATE BRANCH WHEN PROJECT NAME CONTAINS AN APOSTROPHE
  • DT387424: EXCEPTION WHEN IMPORTING A PROJECT WITH REST API
  • DT387661: EXCEPTION WHEN CONNECTING FROM RULE DESIGNER TO DECISION CENTER USING OLD SCHEMA VERSION
  • DT389452: ADDING NEW TAGS USING QUERIES IN DECISION CENTER IS NOT POSSIBLE WHEN SOME ALREADY EXIST
  • DT389739: CANNOT OPEN DEPLOYMENTS TAB AFTER DELETION OF A BRANCH OR ACTIVITY
  • DT389858: ERROR MESSAGE ON RELEASE DELETION
  • DT390866: ACTIVE ATTRIBUTE DEPRECATED MESSAGE IN RULE DESIGNER

Off

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"ARM Category":[{"code":"a8m50000000L1a2AAC","label":"** Other **"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0.0"}]

Problems (APARS) fixed
New: DT392338, DT392428, DT396432. Previous: DT387048,DT244599, DT257907, DT365362, DT381037, DT381870, DT383182, DT383370, DT386484, DT387135, DT387169, DT387424, DT387661, DT389452, DT389739, DT389858, DT390866.

Document Information

Modified date:
07 October 2024

UID

ibm17166207