Known Limitations in WebSphere Operational Decision Management V7.5.0.2

Technote (FAQ)


Question

What are the known limitations in WebSphere Operational Decision Management V7.5.0.2? This web page lists the limitations found in the product, and provides a comment or workaround for each limitation.

Note: If you are looking for a specific module and it is not listed below, no limitation has been reported for it.

Last updated 30 May 2014.

Answer

Rule Designer

Rule Designer
Limitation Comment or workaround
Inconsistent return value for IlrUserRuntimeException.isInConditions() and IlrUserRuntimeException.isInActions() in different execution modes. It has been noted that IlrUserRuntimeException.isInConditions() and IlrUserRuntimeException.isInActions() do not return the same value in RetePlus and sequential modes. This apparent inconsistency comes from sequential and Fastpath modes both performing a deep compilation of the rules. Under these circumstances the condition and action parts of a rule are not distinguished at run time. Any exception thrown by a rule executed in the sequential or Fastpath mode is already wrapped into an IlrUserRuntimeException, but the isInConditions() and the isInActions() methods of the exception class always return false.
When running Rule Designer on a Solaris platform, the Rule Project Map is empty and the error log shows the following entry:
org.eclipse.swt.SWTException: Unable to load graphics library [Cairo is required]
This is a known SWT issue. See http://www.eclipse.org/swt/faq.php#nographicslibrary.
The Rule Project Map relies on Draw2D, which comes with SWT. However, with some advanced features, Draw2D uses a graphic library called Cairo, which the user might have to install separately on certain platforms.
On Linux systems, Rule Designer terminates abruptly after starting, or does not start at all. Install a version of XULRunner compatible with Eclipse 3.6 and configure Rule Designer to use it.
The drop-down completion menu in the Intellirule editor might contain items from several domains in your BOM. To resolve the problem, see Unexpected values in domain drop-down.

Event Designer

Event Designer
Limitation Comment or workaround
Existing customers should run HBRCSD.jcl. HBRCSD.jcl has been updated. Users should run it again, or alter HBRC, HBRD, HBRCCON and HBRCDSCO from the User key to Cics key.

zRule Execution Server

zRule Execution Server
Limitation Comment or workaround
When starting zRule Execution Server with z/OS APAR PM87944 applied, you receive the following error message:

BPXP029I OPEN ERROR FOR FILE PATH /usr/lpp/zDM/VxRxMx/zexecutionserver/msg/En_US.IBM-1047/hbrmpmsg.cat

APAR PM87944 changes the behavior of the catopen() function to restrict the message catalog files that can be used by APF-authorized or z/OS UNIX set-user-ID and set-group-ID privileged programs. The message catalogs for these environments now require the program-controlled attribute to be set.

Mount the ODM HBRINSTPATH as a read-write file system and modify the attributes of the message catalog files. For example, use the command "extattr":
extattr +p /usr/lpp/zDM/VxRxMx/zexecutionserver/msg/En_US.IBM-1047/hbrmpmsg.cat
Repeat this command for all message catalogs in the /usr/lpp/zDM/VxRxMx/zexecutionserver/msg directory.

Decision Validation Services

Decision Validation Services
Limitation Comment or workaround
When using Decision Validation Services, Excel spreadsheets that contain dates prior to 1900 or 1904 produce test errors. Excel does not support dates prior to 1/1/1900 or 1/1/1904, depending on the Excel settings. See XL: The 1900 Date System vs. the 1904 Date System.

To use an older date, such as 6/15/1850, enter 15/06/1850 00:00:00:000 +0200 to use the internal date format of Decision Validation Services.

Decision Center

Decision Center
Limitation Comment or workaround
You cannot deploy an Event project with rtsUser rights if you have the Create a baseline for this deployment option selected. Deploy with rtsConfigManager rights instead. For the tutorial, sign in with rtsConfig/rtsConfig.
The drop-down completion menu in the Intellirule editor might contain items from several domains in your BOM. To resolve the problem, see Unexpected values in domain drop-down.

Rule Authoring

Rule Authoring
Limitation Comment or workaround
In complex operations where the order of parameters infers on the type, the BigDecimal cast fails. Verbalize a casting methods through B2X.

Rule Solutions for Office

Rule Solutions for Office
Limitation Comment or workaround
You can change the formatting of decision table cells (for example, colors and fonts) in Excel and Rule Solutions for Office. However, the formatting is not synchronized into Decision Center, and the cells are displayed in their default format. If Rule Designer was previously used to format the decision table cells, the formatting of the cells returns to the format that was defined in Rule Designer.
Use only Rule Designer to edit a decision table cell format, and use this format throughout the lifecycle of the rule.

Installation

Installation
Limitation Comment or workaround
On z/OS, configure_wbe_datasource.sh does not set currentSQLID when it creates the Events runtime data source. Use the WebSphere Application Server administrative console to set currentSQLID to SCHEMA when you create Events database tables from data source custom properties.
The Events installation does not set the database driver classpath correctly. You need to provide the full path for the JAR. The following comment in <events-dir>/config/db/setenv.sh is not correct:
For z/OS only specify the directory containing the required jars and omit the jar name. E.g /usr/lpp/db2910/classes.
WinZip might corrupt TAR files during extraction. The product files are delivered as compressed TAR files. You must decompress the files into the same directory to install them.

If you use WinZip to extract the TAR files, deselect TAR file smart CR/LF conversion:
  1. Open WinZip Classic.
  2. Select Options > Configuration, and click the Miscellaneous tab.
  3. Clear the TAR file smart CR/LF conversion check box.
  4. Unzip and import the data.

To avoid problems with the extraction of the TAR files, decompress them to the same folder at the root of your hard drive.
An "OutOfMemory" error message might open when you install or update WebSphere Operational Decision Management 7.5.X.X software. The default heap size for IBM Installation Manager is not big enough to load all the repositories proposed by default.
It is recommended that you select only the Decision Server and Decision Center repositories in the menu File > Preferences > Repositories.

To avoid any further issues, edit Installation Manager's IBMIM.ini configuration file in the folder IBM\Installation Manager\eclipse. Add the line -Xmx1024m to the end of the file.

After you restart Installation Manager, you can perform the update.

Documentation

Documentation
Limitation Comment or workaround
Rule Execution Server documentation: In WebSphere Application Server, make sure that the jdkLoggingEnabled XU property is set to false. For WebSphere Application Server, the default value of the jdkLoggingEnabled XU property is true, whereas it is false for the other supported application servers. As a consequence, the procedures described in the following topics in the Information Center make sense only if the user first makes sure that the jdkLoggingEnabled XU property is set to false:
  • Decision Server Rules V7.5 > Configuring Decision Server > Configuring Rule Execution Server > Configuring Rule Execution Server on WebSphere Application Server 7.0 > Troubleshooting > Activating the XU log in WebSphere Application Server
  • Decision Server Rules V7.5 > Configuring Decision Server > Configuring Rule Execution Server > Configuring Rule Execution Server on! WebSphere Application Server for Linux on System z > Troubleshooting > Activating the XU log in WebSphere Application Server
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Configuring Rule Execution Server > Changing the default behavior of the execution stack > Changing the trace level
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Configuring Rule Execution Server > Finding the cause of an improper Rule Execution Server configuration
A Decision Server Rules topic in the Information Center contains an invalid statement for an exception handler. In the following topic for Decision Server Rules, the second paragraph ("The exception handler is also available...") is no longer valid.

The last paragraph after the lines of code should read as follows:
"The execution of a RetePlus engine or task continues if you use an exception handler. However, for other algorithms and the ruleflow, the execution stops, and might call the ruleflow exception handler."

The topic with the invalid statement:
  • Decision Server Rules V7.5 > Developing rule projects in Rule Designer > Executing business rules > Executing rules using the rule engine > Executing a ruleset using a native rule engine > Writing a ruleset execution method > Setting an exception handler

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Operational Decision Manager
General

Software version:

7.5.0.2

Operating system(s):

AIX, HP-UX, IBM i, Linux, Platform Independent, Solaris, Windows, z/OS

Software edition:

Enterprise, Standard

Reference #:

1591052

Modified date:

2012-09-28

Translate my page

Machine Translation

Content navigation