Known limitations in WebSphere Operational Decision Management V8.0.0.1

Technote (FAQ)


What are the known limitations in WebSphere Operational Decision Management (WODM) V8.0.0.1? 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 3 Oct. 2014.


Rule Designer

Rule Designer
Limitation Comment or workaround
If you use Internet Explorer 11, a security update from Microsoft can make Eclipse crash when you use the internal web browser. Use an external web browser.
Google Chrome does not display the Rule Project Statistics Report. Launch Google Chrome with the flag "allow-file-access-from-files."
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
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
When using a stored procedure within the JDBC event connector, all of the rows returned by the stored procedure may be processed and put onto the event destination in one unit of work. If a large result set is returned, this could cause performance degradation or issues with full destinations. Ensure that the number of rows returned by a stored procedure is appropriate for the resources of the system.

Rule Execution Server

Rule Execution Server
Limitation Comment or workaround
In WebSphere Application Server, the default value of the jdkLoggingEnabled XU property is set to true. You must set the jdkLoggingEnabled XU property to false to be able to follow the steps in the documentation accurately.
After following the optional configuration steps in Configure the WebSphere Optimized Local Adapters (WOLA) to allow CICS to execute rules using WOLA, you are unable to connect to the RES in zWAS, and you get the following message: GBRZC9000E RC=3018. The error occurs when CICS checks for a valid HBRSSIDLIST run-time variable, which is not required with this configuration. The problem is fixed in the next product release (V8.0.0.2). For V8.0.0.1, use the following workaround:

Pass the necessary run-time variable to the server by adding the SHBRPARM(HBRCICSZ) data set member to the HBRENVPR DD statement in the JCL of the CICS region, as shown in the following statement:

Adding HBRCICSZ to //HBRENVPR resolves the problem because you are now specifying a HBRSSIDLIST run-time variable. The value of HBRSSIDLIST is not important, so the recommended setting is HBRSSIDLIST=WOLA.

zRule Execution Server

zRule Execution Server
Limitation Comment or workaround
When starting instances of zRule Execution Server that share the same work path (for example, a single JCL job or a script), one or more of the instances might fail to start, and an XML error message like the following one might open:

ilog.rules.res.util.IlrRemoteException: The document is not XML valid.

Do not start the instances together. Introduce a short wait before each succeeding start.

This problem is fixed in Operational Decision Manager V8.0.1.

Decision Center

Decision Center
Limitation Comment or workaround
The decision table editor in the Business console does not support the following features:
  • Hierarchical overlap and symmetry checks.
  • Hidden and locked columns.
  • Display of row and cell comments.
  • Specific formatting for a cell, including tooltip, font, and color.
  • Moving a row in manual row ordering mode.
  • Supports only predefined patterns when specifying a value format.
No workaround.
If you customize Decision Center by completing AJAX calls to a custom servlet, you may end up with an error 400 (Bad request). For example, it may be the case if you create a new custom value editor. This error is due to the introduction of a mechanism to prevent CSRF attacks. CSRF attacks allow an attacker to perform an action on behalf of an authenticated user. To prevent this kind of attack, a request must have a parameter containing a user-specific token. This token is checked by the server to make sure the request was actually sent by the authenticated user and not by another person.
The token is generated using the class with the SHA-1 algorithm and we assume an attacker is not able to generate a valid token.
As a developer, you need to make sure each request you send to the server contains the user-specific token. To help you, Decision Center javascript API provides you with the following functions:
function addParameterWithAccessToken(/* String / url)
This function adds a user-specific token to a given url. It is likely to be called with URLs used in an AJAX GET request.
function addAccessToken(/ Object */ obj)
This function adds a user-specific token to a given object. It is likely to be called with objects used in an AJAX POST request.
url: 'dummy url',
content: addAccessToken({param1:
val1, param2: val2}),
load: function(result) {
// do something
function getAccessToken()
This function returns an object with the name and the value of the user-specific token.
name: '__dcsid',
value: 'xxxxxxxx'
Note the user-specific token is stored as an attribute of the HTTP session and is bound the name '__dcsid'.
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.

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.

With a rule project that uses an XML-based Business Object Model and includes an unbounded list of elements as part of the ruleset parameter objects, you might encounter issues when you run Decision Validation Services (DVS) test suites on a WebLogic application server. You might receive an exception such as ilog.rules.dvs.common.output.IlrScenarioDataException with a cause: Argument is not an array. Use the following solution:
  1. Copy the original jrules-res-xu-WL10.rar and jrules-ssp-WL10.ear files to a new location.
  2. Modify jrules-res-xu-WL10.rar/META-INF/ra.xml to replace xuName=default with xuName=ssp in the plug-in configuration property.
  3. Modify jrules-res-xu-WL10.rar/META-INF/weblogic-ra.xml
    by replacing eis/XUResourceAdapter with eis/XUResourceAdapter_SSP; jrules_xu.log with jrules_xu_ssp.log; and
    eis/XUConnectionFactory with eis/XUConnectionFactory_SSP.
  4. Package the modified jrules-res-xu-WL10.rar into the jrules-ssp-WL10.ear.
  5. Modify jrules-ssp-WL10.ear/META-INF/application.xml by adding the declaration jrules-res-xu-WL10.rar.
  6. Add a file, jrules-ssp-WL10.ear/META-INF/weblogic-application.xml, with the following content:
    <weblogic-application xmlns:xsi=""
    xsi:schemaLocation="" xmlns="">
  7. Modify jrules-ssp-WL10.ear/jrules-ssp-server.war/WEB-INF/weblogic.xml changing the XU reference jndi-name element as follows:
  8. Deploy the modified SSP application through the Weblogic console as usual.

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.

Pattern for PureApplication System

Pattern for PureApplication System
Limitation Comment or workaround
There is only one catalog server in the deployment manager node. This can cause Events to fail. There should be at least three catalog servers in the cluster because they start in pairs within a catalog server domain. The catalog servers should be deployed to the node agents, not to the cluster member where the event runtime is running.
See the following topics in the WebSphere eXtreme Scale information center:
When ODM Pattern V8.0 was released, its documentation noted that IBM PureApplication System V1.0.0.1 was the supported deployment platform. In addition to PureApplication System V1.0.0.1, ODM Pattern Version 8.0 now also supports IBM Workload Deployer V3.1.0.6 as a stand-alone appliance.
The SSP design in WebSphere Operational Decision Management V8.0.0.1 supports multiple execution threads, but it runs on a single server. Because large simulations can take a very long time to execute, simulation results are returned asynchronously. As a consequence, if you use a web server (with the WebSphere Application Server plug-in) or a server proxy in a clustered environment, the requests for results might be routed to the wrong cluster member. To overcome this limitation, you can address a specific cluster member for simulations and tests.

In testing and simulation environments (typically not production environments) and where the Rule Execution Server console is not deployed to the same cluster as the SSP (as is the case with the ODM Pattern V8.0), you must also set the LOCAL_DEPLOYMENT_ONLY parameter to true in the SSP web.xml, and the SSP application must be redeployed. In addition, the Rule Execution Server MBean descriptors must be deployed to each Decision Server cluster member, the deployment manager, and the Rule Execution Server console in the manner described in Deploying the Rule Execution Server MBean descriptors.

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 (BOM to XOM).


Limitation Comment or workaround
When installing the execution unit (XU) RAR for the Oracle WebLogic Servers, you might get the following warning:
<Warning> <WorkManager> <BEA-002919> <Unable to find a Work Manager with name jrules-res-xu-WL12.rar. Dispatch policy jrules-res-xu-WL12.rar will map to the default Work Manager for the application jrules-res-xu-WL12.rar>
You can safely ignore the warning. If the work manager settings are not appropriate, you can create a work manager with the reported name and the appropriate settings.
The following service repositories are not connected: websphere/bpm/repositories/server/ wodm/8.0.0/updates/ websphere/bpm/repositories/server/ wodm/8.0.0/extensions/ This warning does not prevent the user from upgrading their WebSphere Operational Decision Manager version to the version offering

In the Installation Manager Preferences; uncheck "Check available service repositories"
Rational Software Architect does not work when you upgrade your WebSphere Operational Decision Management from version to version in the package groups of the following products: IBM Integration Designer, Rational Application Developer, Rational Developer for z (RDz). Use the embedded Eclipse
When you crate a Java Project for Rules, the project is created with 2 libraries: JRE System and IBM WebSphere Operation Decision Manager Rule Engine. However, the Rule Engine library is created with an error, missing the jdom1.1.2.jar Copy jdom1.1.2.jar from C:\Program Files\IBM\WODM80\executionserver\lib or C:\Program Files\IBM\WODM8001\executionserver\lib to \studio\lib directory

Installation of Pattern for PureApplication System

Installation of Pattern for PureApplication System
Limitation Comment or workaround
To extract the ODM Pattern V8.0 installation files, you must use a compression utility that supports the GNU tar format. IBM provides ODM Pattern V8.0 as a compressed package. Because the package exceeds 8 GB, it uses the GNU tar compression format.

Rate this page:

(0 users)Average rating

Document information

More support for:

IBM Operational Decision Manager

Software version:

Operating system(s):

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

Software edition:

Enterprise, Standard

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation