IBM Support

ODM Interim Fix 002 for 8.10.5.2

Download


Downloadable File

File link File size File description

Abstract

IBM ODM iFix 8.10.5.2-WS-ODM-IF002 has been made generally available and contains fixes to version 8.10.5.2 including all predecessor fixes.

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.10.5.2

For Kubernetes installation:

  1. You must have an initial 8.10.5.2 version of ODM on Certified Kubernetes already installed.
  2. Download the interim fix for the appropriate OS to a dedicated location.

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.10.5.2-WS-ODM-IF002.zip

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

ODM on premise installation

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.v810_8.10.5002 -repositories <zip-location>/com.ibm.odm._8.10.5.2-IF002.zip
      or
      imcl listAvailableFixes com.ibm.websphere.odm.ds.rules.v810_8.10.5002 -repositories <zip-location>/com.ibm.odm._8.10.5.2-IF002.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..v810-fix_1.5.2.IFXXX
    3. Install with the command:
      imcl install <fix ID> -repositories <zip-location>/com.ibm.odm._8.10.5.2-IF002.zip -installationDirectory <odm_home><odm_home>
    4. The ifix zip and fix ID depend on the appserver.

ODM on Kubernetes installation

  1. Obtain and save to your disk the ifix ppa file corresponding to the 8.10.5.2 version of ODM on Certified Kubernetes: odm_on_icp_8.10.5.2-IF002-.tar.gz
  2. Extract the charts and images directories from this package:  
    tar xvzf odm_on_icp_8.10.5.2-IF002-.tar.gz
  3. Log in to Docker.:  
    docker login REGISTRY_URL
    When prompted, enter your Docker user name and password.
  4. Load the new ODM images into your internal Docker registry.  
    for name in images/*.tar.gz; do echo $name && docker image load --input $name; done
  5. Now that the ppa file corresponding to the 8.10.5.2-IF002 ifix is deployed on the cluster, upgrade the release.
  • Apply a helm upgrade to all of the deployed releases.
  • helm upgrade RELEASE_NAME charts/ibm-odm-prod-22.1.0.tgz --reuse-values
    RELEASE_NAME: The name of the release that you want to upgrade. (name that was given during image installation)
Your upgrade is complete once all the pods have re-started. Traffic will not be redirected to the new version until the pods are started.

ODM on premise, required 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 DT261812, download the setup script DT261812.zip and execute the script for your database to enable background branch/project deletion.

Decision Center

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

  • weblogic/jrules-teamserver-WL.ear
  • websphere/jrules-teamserver-WAS.ear
  • jboss/jrules-teamserver-JBOSS.ear
  • tomcat/decisioncenter.war
  • tomcat/decisioncenter-api.war
  • tomcat/decisionmodel.war
  • WLP/decisioncenter.war
  • WLP/decisioncenter-api.war
  • WLP/decisioncentermodel.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.

  • websphere/jrules-res-management-WAS.ear
  • weblogic/jrules-res-management-WL.ear
  • 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.

  • websphere/jrules-res-htds-WAS.rar
  • weblogic/jrules-res-htds-WL.ear
  • 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.

  • weblogic/jrules-res-xu-WL.rar
  • websphere/jrules-res-xu-WAS.rar
  • jboss/jrules-res-xu-JBOSS.rar

Testing&Simulation

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

  • websphere/jrules-ssp-WAS.ear
  • weblogic/jrules-ssp-WL.ear
  • jboss/jrules-ssp-JBOSS.ear
  • tomcat/DecisionRunner.war
  • WLP/DecisionRunner.war

Rule Designer

Installation Manager updated the required plug-ins in <InstallDir>/studio/update-sites, but you must manually install the update-site into your Rule Designer, as follows:

  1. Restart Rule Designer.
  2. Click Help > Install New Software.
  3. Add the sites to install:
    1. In the Install wizard, next to the Work with field, click Add.
    2. In the Add Repository dialog, click Archive.
    3. Browse to the <InstallDir>/studio/update-sites directory, click Open, and select designer-base-update-site.zip.
    4. In the Name field, enter a name for the site, and then click OK.
    5. Repeat to add the rule-designer-update-site.zip update site.
  4. Select IBM Decision Server Rule Designer.
  5. Click Next.
  6. Review the terms of the license agreement and Click Finish.
  7. Proceed with the installation.

Note: If Eclipse shows the message "The Eclipse executable launcher was unable to locate its companion shared library", it is because the eclipse.exe file was deleted from its location in <InstallDir>. Proceed as follows:

  1. Show the properties of the Rule Designer shortcut in the installation menu.
  2. Go to the location shown in the Start in' field, for example "C:\Users\rulesadm\AppData\Local\Temp\1\Operational Decision Manager V8.10.5 com.ibm.sdp.eclipse.ide_320b46855f80_92e7753c35b\C\Program Files\IBM\ODM8105"
  3. Move eclipse.exe from this location to the root of <InstallDir>

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

ODM on Kubernetes, required tasks after installation

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.

Interim Fix specific steps

For DT261812, download the setup script DT261812.zip and execute the script for your database to enable background branch/project deletion.

Rule Designer

To install the fix:

  1. Start Eclipse.
  2. Click Help > Install New Software.
  3. Click Add and enter:
    • Name: ODM
    • Location: https://raw.githubusercontent.com/ODMDev/ruledesigner/8.10.5/p2/
  4. Click OK.
  5. In the Available Software page, uncheck "Show only the latest version of available software"
  6. Select IBM Decision Server Designer Base 8.10.5.2-IF002
  7. Click Next.
  8. In the Install dialog, click Next.
  9. 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.
  10. 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.10.5.2-WS-ODM-IF002 27 June 2024 Language Independent -
8.10.5.2-WS-ODM_K8S-LIN_X86-IF002 27 June 2024 Language Independent -
8.10.5.2-WS-ODM_K8S-PPC64LE-IF002 27 June 2024 Language Independent -
8.10.5.2-WS-ODM_K8S-LIN_S390-IF002 27 June 2024 Language Independent -

Back to top

Problems Solved

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

The following are all the new fixes:

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

  • DT244599: DECISION CENTER DOES NOT ALLOW RULESET NAME WITH UNICODE LETTERS
  • DT365362: INCOMPATIBLECLASSCHANGEERROR WHEN EXECUTING A CUSTOMEXCEPTIONHANDLER
  • DT378830: PERFORMANCE ISSUE RUNNING MERGE OPERATION AND CLOSING ACTIVITIES
  • DT387807: MODIFIED ELEMENTS IN DELETED CHANGE ACTIVITY DISAPPEAR FROM OTHER BRANCHES

The following are all the previous fixes:

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

  • DT211118: DECISION RUNNER IS SLOW WITH LARGE NUMBER OF SCENARIO
  • DT233519: DC LDAP SYNC FAILS DUE TO 'BRM.LOCK' ERROR
  • DT260080: MANAGED XOM URI PROPERTY MAY REFERENCE A LIBRARY THAT DOES NOT EXIST
  • DT260471: NULLPOINTEREXCEPTION WHEN INTERCEPTOR ENABLED IN HTDS
  • DT260519: CLIENT PROJECT FOR DECISION SERVICE GENERATION FAILS
  • DT261812: UNABLE TO PERFORM LONG-RUNNING DECISION SERVICE DELETION FROM BUSINESS CONSOLE WITHOUT TIMEOUT

Back to top

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":"8.10.5"}]

Problems (APARS) fixed
New: DT244599, DT365362, DT378830, DT387807. Previous: DT211118, DT233519, DT260080, DT260471, DT260519, DT261812.

Document Information

Modified date:
27 June 2024

UID

ibm17148786

Page Feedback