Known limitations in WebSphere Operational Decision Management V7.5.0.1

Technote (FAQ)


Question

What are the known limitations in WebSphere Operational Decision Management V7.5.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 30 May 2014.

Answer

Rule Designer

Rule Designer
Limitation Comment or workaround
While using the Step Into feature for debugging in Rule Designer, a message might tell you that the source file cannot be found, even though the source file is available. Stop the debugger and try again.
In some installation scenarios, local contextual help in Rule Designer might not be available
(not configured).
How to manually configure local contextual help in Eclipse

If you have chosen online help :

To modify the contextual help settings:
1. Click Window > Preferences > Help > Content.
2. Select Include remote help and give it priority, and then click New.
3. Enter the values for the information center that you want to connect to. For example:
- Name: WebSphere Operational Decision Management information center
- Host: publib.boulder.ibm.com
- Path: /infocenter/dmanager/v7r5
- Select: "Use default port"
4. Click OK, and then click Apply and OK.
The contextual help now uses your new parameters.

If you have selected local help :

Important: To use the local contextual help from Rule Designer, you must start the local
instance of the information center through the Start menu shortcut or the start
scripts as described in Installing the product documentation on your computer.
The installer inserts the necessary parameters to access Remote Help in your
Rule Designer.
If you want to change the parameters to point to a different instance of the information center,
for example a shared information center server running on an internal network, you can modify
the values in Rule Designer.
To modify the contextual help settings:
1. Click Window > Preferences > Help > Content.
2. Select Include remote help and give it priority, and then click New.
3. Enter the values for the information center that you want to connect to. For example:
- Name: WebSphereOperational Decision Management information center
- Host: localhost
- Path: /help
- Use port: 3333
4. Click OK, and then click Apply and OK.
The contextual help now uses your new parameters.
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
Curly braces adjacent to Javascript fields cause the field to not be recognized. Add a space after the left curly brace ("{") and before the right curly brace ("}").
Javascript field names that start with another field name are not recognized. If your object contains the fields "purchase" and "purchase date," "purchase date" is not recognized as a field. Rename fields that contain the name of another field.
Errors are displayed in the Problems View after importing a project from WebSphere Business Events V7.0 into WebSphere Operational Decision Management V7.5. Refer to the following technote for a solutions:

Errors are displayed in the Problems View

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
The Quick Edit feature in Decision Center does not work in Firefox 5 or 6. V7.5 does not support Firefox 5 or 6. Use a supported version of Firefox.
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.

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 Server for z/OS

Decision Server for z/OS
Limitation Comment or workaround
When the HBRC CICS transaction is run with STGPROT=YES and EXECKEY(USER), you can get this message: 0C4 abend in HBRCCON at offset 0x2A9A. To solve this problem, run the transaction with either STGPROT=NO or EXECKEY(CICS) in the HBRCCON and HBRCDSCO PROGRAM definitions in the CSD.

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
Error when navigating to Typical installation from the launchpad:
0x80041013 (“Provider not found”) or 0x80041014 (“Component failed to initialize")
This error can happen in the launchpad when you click the links to Typical installation from either the Welcome page or the navigation panel. This error indicates a problem with your Windows Management Instrumentation (WMI) configuration.

To troubleshoot the problem, see the following Windows documentation:

I’m getting an 0x80041013 ("Provider not found") or an 0x80041014 ("Component failed to initialize") error

WebSphere Application Server fails to install if your host name contains an underscore ("_") character. Install the application onto a server with no underscore in its host name. See the following technote:
Portal installation fails when hostname contains underscore "_"
The Sample Server fails if you have entered a space in the user ID or password for the Sample Server profile during installation. When you install the product with the launchpad or Installation Manager, do not enter a space in the user ID or password.
If the user chooses to extend an existing Eclipse, the start and stop sample server shortcuts and script might not work Reason: JAVA_HOME is not set properly. Follow these instructions:

For Windows platforms, edit /shared/bin/startserver.bat
to indicate a valid JAVA_HOME:
set JAVA_HOME=
For example:
set JAVA_HOME="C:\Program Files\IBM\JAVA60"
Same for [InstallDirectory]/shared/bin/stopserver.bat

For UNIX platforms, edit [InstallDirectory]/shared/bin/startserver.sh to indicate a valid JAVA_HOME:
export JAVA_HOME=
For example:
export JAVA_HOME=/usr/local/softs/jdk6

Same for [InstallDirectory]/shared/bin/stopserver.sh
If you execute launchpad.exe on a Windows 64-bit operating system and run Typical Install, the launchpad installs a 64-bit WebSphere Application Server and Extreme Scale. However, it installs a 32-bit WebSphere Operational Decision Management, and the Profile Management Tool is not installed because 64-bit platforms do not support this tool. The launchpad.exe and launchpad64.exe files only define the bit size that the launchpad itself runs in. When you use Typical Install in the launchpad, the product and the prerequisites are installed silently. The launchpad installs WebSphere Application Server and eXtreme Scale in 32 or 64 bits depending on the bit size of the operating system.

To avoid this issue, use Custom Installer in the launchpad. If your operating system is running in 64-bit, Custom Installer prompts you to select a bit size (32 or 64 bits).
If you have installed WebSphere Operational Decision Management V7.5 or WebSphere Business Rules V7.5, and have configured a zRule Execution Server as a stand-alone server or in a CICS JVM Server, you must perform extra configuration steps when installing the V7.5.0.1 PTF. For both scenarios, copy ++HBRINSTPATH++/zexecutionserver/template/ config/webdefault.xml to ++HBRWORKDS++/config/webdefault.xml.

For a zRule Execution Server in a CICS JVM Server:

1) Define and install a new CICS program using the following parameters:  
DEFINE PROGRAM(HBRCJVMS)
GROUP(HBRGROUP)
LANGUAGE(ASSEMBLER)
RELOAD(NO)
EXECKEY(USER)
RESIDENT(NO)
USAGE(NORMAL)
USELPACOPY(NO)
STATUS(ENABLED)
CEDF(YES)
DATALOCATION(ANY)
CONCURRENCY(THREADSAFE)
DESCRIPTION(IBM Decision Server for zOS)

2) Generate a new JVM Profile by submitting the ++HBRWORKDS++.SHBRJCL(HBRCJVMP) JCL for CICS 4.2 or ++HBRWORKDS++.SHBRJCL(HBRCJS41) JCL for CICS 4.1, and ensure the new profile is copied to the location specified by the JVMPROFILEDIR CICS parameter.
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.

Samples

Samples
Limitation Comment or workaround
Windows 7 handles administrator rights differently from Windows XP. To run the Sample Server, you must have administrator rights. Here are three options for running the server with administrator rights:

1. Start the sample server with administrator rights. To do so, right-click the Start Sample Server shortcut, and click Run as administrator.

Note: To run the samples provided in the product, you must also start the Samples console with administrator rights (Run as administrator).

2. Install WebSphere Operational Decision Management in a directory other than Program Files (x86).

3. Give write permissions to the current user on the installation directories of WebSphere Operational Decision Management and WebSphere Application Server.
For more information on permissions, see the Windows 7 documentation.

User does not have the correct role when signing in. This is due to the Single sign-on feature for the Sample Server. If you are signed in to another application -- Decision Center, for example -- sign out before opening another application, such as Rule Execution Server.

Another option is to use the user credentials you entered during the installation of the product. You can use them to sign in to all the applications, and you must use them to sign in to Business Space, and the WebSphere Application Server and Events administrative consoles.

Documentation

Documentation
Limitation Comment or workaround
No longer correct: "If you are using Linux, you cannot use the drag-and-drop capability." The drag-and-drop capability is now available in Linux.
Product information center reference:
  • Decision Server Rules V7.5 > Getting started with business rules > Task 2: Orchestrating
The equals method is no longer mandatory for the tests on arrays or collections of complex objects.
Tests on arrays and collections of complex objects are no longer based on the equals method of the complex objects for Java XOMs.

Product information center reference:

  • Decision Server Rules V7.5 > Developing rule projects in Rule Designer > Testing and simulating rulesets > Working with Excel scenario files > Test of arrays or collections of complex objects
The new sample "Rules and Events integration" is not covered in the documentation. A technote has been created with a PDF containing instructions for the sample. See Sample: Rules and Events integration.
Decision Server Rules documentation refers to to the jrules-res-session-WAS7.jar file, which is no longer delivered with the product. The product no longer supports EJB 2.1, and no longer includes the jrules-res-session-WAS7.jar file. Instead, refer to the jrules-res-session-jar.jar file.
Product information center reference:
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Developing client applications > Creating a client for Rule Execution Server > Generating an SCA archive for Rational Application Developer
When using DB2, an extra step might be needed to use the scripts for creating Rule Execution Server database tables. BP32K is the buffer pool expected in SYSCAT.BUFFERPOOLS. If BP32K does not exist, you can use the existing buffer pool or create a new buffer pool named BP32K.

Use the following command to query SYSCAT.BUFFERPOOLS for the existing buffer pool:
Select * from SYSCAT.BUFFERPOOLS

Otherwise, use the following command to create BP32K:

CREATE BUFFERPOOL BP32K SIZE 2000 PAGESIZE 32K
Product information center reference:

  • Decision Server Rules V7.5 > Configuring Decision Server > Configuring Rule Execution Server > Configuring Rule Execution Server on JBoss 5 > Step 7: Populating a Rule Execution Server database > Populating a database by running SQL scripts
The documentation is missing a step for setting J2C security when configuring Decision Center on WebSphere Application Server. After you have created your data source and connection pool (see Step 2: Creating a data source and connection pool), you create the J2C authentication data. See the technote Creating J2C authentication data in WebSphere® Application Server for Decision Center V7.5.
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

Related information

WebSphere Operational Decision Management Support
Passport Advantage Online
WebSphere Operational Decision Managment Home Page
Product User Communities
Product Documentation - Information Center
Product Download Document
Product System Requirements
WebSphere Operational Decision Management Technotes
Fix List for WebSphere Operational Decision Management

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Operational Decision Manager

Software version:

7.5.0.1

Operating system(s):

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

Software edition:

Enterprise, Standard

Reference #:

1575190

Modified date:

2012-09-28

Translate my page

Machine Translation

Content navigation