Known Limitations in WebSphere Operational Decision Management V8.0

Technote (FAQ)


Question

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

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
No error message is displayed when synchronization fails between Rule Designer and a Decision Center of a different locale. Artifacts published from Rule Designer must have the same locale as the target Decision Center. Otherwise, the Decision Center ignores artifacts of a different locale, and enters a message on the failed synchronization in the log.
On the 64-bit Windows 7, you might encounter an error when exiting Eclipse. Switching workspaces might also fail and generate an error. When this happens, Rule Designer closes and an error message opens. The problem stems from an Eclipse bug. See the technote
Restart workbench crashes on Windows 7
Accessibility limitation in Ruleflow editor: There is no keyboard equivalent for creating nodes or links. You must use the graphical tools.
When 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.
Renaming an artifact closes the editor of the artifact. Right-clicking an artifact in Rule Explorer and clicking Refactor > Rename also closes the artifact editor. You must reopen the editor after renaming the artifact.
When you use the local help system in Eclipse, the back arrow button in the Help view does not work. Use the Show in Contents button to navigate through the documentation.
If some of the ruleset parameters of your rule project involve non-instantiable classes, you cannot generate Excel scenario file templates out of the box. For a possible workaround, see the technote BOM class inheritance and Excel scenarion files.
Inconsistent return value of 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 is because sequential mode and Fastpath mode both perform a deep compilation of the rules. In these circumstances the condition part and the action part of a rule cannot be distinguished anymore at runtime. Any exception thrown from a rule executed in sequential mode or in Fastpath mode is already wrapped in an IlrUserRuntimeException but the isInConditions() and the isInActions() methods of this exception class always returns false.
When you create a Java Project for Rules, you make two libraries for the project: JRE System and IBM WODM Rule Engine. However, creating the Rule Engine library produces an error, missing 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.
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
While searching with the Eclipse-based help, you might receive the following warning: Some network help is not available. Ignore the warning. The network help link should work correctly if an Internet connection is available. The warning is from a redundant invalid link installed with the Event Designer plug-in.
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
There is no "hot" deployment for using a monitored transparent decision service (MTDS) with the JBoss 6.1.0 application server. When redeploying the web service to the JBoss 6.1.0 application server, you have to stop and restart the server for the service to be successfully deployed.
If you configure zRES on CICS with DB2 persistence, and then deploy a new version of a ruleset, zRES does not pick up the new version immediately. In this configuration, zRES cannot support hot deployment. The RES Console also displays errors for the CICS JVMServer XU. This issue has been fixed for the V8.0.0.1 patch release.
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 runtime variable, which is not required with this configuration. The problem is fixed in the next product release (V8.0.0.1). For V8.0, use the following workaround:

Pass the necessary runtime 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:


//HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.
<HBRSSID_NAME>.SHBRPARM(HBRCICSZ
)


Adding HBRCICSZ to //HBRENVPR resolves the problem because you are now specifying a HBRSSIDLIST runtime 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 Server

Decision Server
Limitation Comment or workaround
Running the HBRDSWAS job to configure Decision Server on WebSphere Application Server for z/OS might not add the jrules-mbean-descriptors.jar file to the server classpath. This can prevent the correct deployment of rulesets to Decision Server. After running the HBRDSWAS job, perform Step 8: Deploying the Rule Execution Server MBean descriptors.

Decision Center

Decision Center
Limitation Comment or workaround
When running the HBRDCCDB job to create the Decision Center database on DB2, the return code is 4, instead of the expected 0, when the job has finished successfully. Check the job output to make sure the only issues are SQLWARNING ON CREATE COMMAND for the following views (Note: <SCHEMA> is the name of the DB2 schema holding the referenced views in your database):
<SCHEMA>.ABSTRACTQUERYDTLS
<SCHEMA>.BOMDTLS
<SCHEMA>.BOM2XOMMAPPINGDTLS
<SCHEMA>.EVENTDTLS
<SCHEMA>.RULEARTIFACTAGGRGTD
<SCHEMA>.RULEARTIFACTDTLS
<SCHEMA>.RULEFLOWAGGRGTD
<SCHEMA>.RULEFLOWDTLS
<SCHEMA>.RULEPACKAGEDTLS
<SCHEMA>.SCENARIOSUITEAGGRGTD
<SCHEMA>.SCENARIOSUITEDTLS
<SCHEMA>.TEMPLATEAGGRGTD
<SCHEMA>.TEMPLATEDTLS
<SCHEMA>.VARIABLESETAGGRGTD
<SCHEMA>.VARIABLESETDTLS
<SCHEMA>.VOCABULARYDTLS
<SCHEMA>.CHANGEVIEW
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.

Decision Validation Services

Decision Validation Services
Limitation Comment or workaround
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="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
    http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
    <classloader-structure>
    <module-ref>
    <module-uri>jrules-ssp-server.war</module-uri>
    </module-ref>
    <module-ref>
    <module-uri>jrules-res-xu-WL10.rar</module-uri>
    </module-ref>
    </classloader-structure>
    </weblogic-application>
  7. Modify jrules-ssp-WL10.ear/jrules-ssp-server.war/WEB-INF/weblogic.xml changing the XU reference jndi-name element as follows:
    <resource-description>
    <res-ref-name>eis/XUConnectionFactory</res-ref-name>
    <jndi-name>eis/XUConnectionFactory_SSP</jndi-name>
    </resource-description>
  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.

Installation

Installation
Limitation Comment or workaround
Error when running the launchpad: Installation Manager already exists. If you already have Installation Manager 1.5.0 or 1.5.1 installed, you must update it to Version 1.5.2 or later to run the installer for WebSphere Application Server, Business Space, and WebSphere Operational Decision Management.
Error when navigating to the Typical installation from the launchpad:
0x80041013 (“Provider not found”) or 0x80041014 (“Component failed to initialize").
This type of error can happen in the launchpad when you click the link to the Typical installation on the Welcome page or the side navigation panel. This error indicates a problem with your Windows Management Instrumentation (WMI) configuration. To troubleshoot the problem, see the Microsoft publication I’m getting an 0x80041013 (“Provider not found”) or an 0x80041014 (“Component failed to initialize) error.
WebSphere Application Server fails to install if your hostname contains the underscore (_) character. Use a hostname with no underscore character.
See the technote Portal installation fails when hostname contains underscore "_".
Icons for folders in the Linux shortcut menu are not consistent with the icons of the applications that you use. No solution.
The launchpad uses an Installation Manager that is a 32-bit application dynamically linked to 32-bit libraries that might not exist on some 64-bit systems such as Red Hat Enterprise Linux (RHEL) 6.0 and 6.1. If you are using one of these systems, you must install 32-bit libraries prior to using the launchpad or the Installation Manager. See the technote Unable to install Installation Manager on RHEL 6.0/6.1 (64-bit).
On Windows, you might get an error like the following one when using the Stand-alone Server installation option in the launchpad:

augmentProfileWithBspaceNotDerbyEmbedded:
[standalone.echo] May 16, 2012 12:07:38 PM com.ibm.wodm.Log info
[standalone.echo] INFO: GBRPS0007I?: This is expected to take a while
[standalone.echo] GBRPS0007I?: This is expected to take a while
[exec] The following validation errors were present with the command line arguments:
[exec] configureBSpace: The following path in the profile exceeds the Microsoft Windows file path limitation of 260 bytes:
[exec] C:\tmp_folder\WODM80_launchpad\WAS\

AppServer\profiles\standalone8000DNS
/installedApps/soprules04Node05Cell
/BSpaceHelp_soprules04Node05_standal
one.ear/BSpaceHelp.war/WEB-INF/eclip
se/plugins/webapp/web-archive/org.ec
lipse.help.infocenter-feature/build.

properties[260 bytes]
[exec] To avoid this error, you can create a profile with a shorter path, or choose a shorter cellName, nodeName or serverName.

BUILD FAILED

You have given a directory path that is too long. To avoid this problem, define a path in the launchpad for the WODM installation directory that does not exceed 33 characters. For example, C:\Program Files\IBM\WODM80. This path is valid because it contains 28 characters.
The Test Connection button in the Launchpad does not operate with the Derby database when you follow the Standalone Server path. This is a known minor defect.
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.
With WODM for z/OS, when you import a copybook with DBCS characters, and the DBCS data item uses a redefined clause, and the length of the data name is longer than 10 DBCS characters, the COBOL importer reports an exception, and does not import the DBCS copybook. The problem is with the RAD components. The RAD 8402 release will provide an official fix in Q4 2012. Until then, customers who encounter the problem must request a hot fix at Support Level 2. The RAD team has delivered a hot fix on the Win 32 platform.
Running Launchpad on Windows 7 can result in installation errors and "Build Failed" messages even when logged in with administrator privileges. Righ-click Launchpad and select Run as administrator when installing on Windows 7.

Samples

Samples
Limitation Comment or workaround
Sample Server (startserver.sh) fails to launch on Ubuntu 10.04 and 11.10. Do the following actions:
- Make sure Korn Shell (ksh) is installed.
- Redirect the link /bin/sh from dash to bash.
You might get an authentication error if you run several applications at the same time on the Sample Server. If you log out of one session, another session might display a message like this one: SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user: { } Clear your browser history. For more information, see the technote PM47514: SESN0008E error when user logs out.
When you start the Sample Server on HP UX for the first time, the server might appear to hang at the following point:


init.sample.server:
augmentSamplesProfileIfNeeded:
checkIfWBEisInstalled:
checkToAugmentWithWBE:
augmentWithWBEIfNeeded:
[samples.echo] May 10, 2012 10:31:35 AM com.ibm.rules.sampleserver.Log info
[samples.echo] INFO: GBRPS0007I: This is expected to take a while
[samples.echo] GBRPS0007I: This is expected to take a while
checkIfTesterWidgetIsInstalled:
augmentWithWBEWithTesterWidget:


The log file wsadminListener.out in the profile directory contains this message:
Permanent generation is full...
increase MaxPermSize (current capacity is set to: 134217728 bytes

In the script bin/launchWsadminListener.sh, change the property
PERF_JVM_OPTIONS to add -XX:MaxPermSize=128m.

Documentation

Documentation
Limitation Comment or workaround
The documentation does not provide the correct location for the preference properties for the Solr search engine. The preferences.properties for Solr should be in decisioncenter.war under WEB-INF/classes/com/ibm/rules/decisioncenter/web/search/preferences.properties.
The URL for accessing Business Space with a web browser is incorrect in the WODM Information Center. Use this URL: http://hostname:port/mum/resources/bootstrap/login.jsp.
The Information Center does not provide enough information to migrate WODM for z/OS V7.5 to V8.0. For additional information, see the technote WebSphere Operational Decision Management for z/OS: Migrating from V7.5 to V8.0.
z/OS does not support clustering. Steps 4-8 in the topic Installing on a managed node on z/OS are not applicable.
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 V8.1 > Decision Server Rules > Running 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
The Scenario Service Provider (SSP) archive must be on the same host and port as the Rule Execution Server console. The documentation does not clearly state where to place the archive. Unless the IlrSSPResolver API is used, the SSP archive and Rule Execution Server console must use the same host and port. See Step 2: Deploying the Decision Validation Services archive.
The documentation refers to jrules-res-session-<appserver>.jar under the directories <InstallDir>/executionserver/applicationservers/<appserver>. This .jar cannot be found for the WAS 7 or 8 application server directories. The correct paths for the rule session .jar files are
<InstallDir>/executionserver/lib/jrules-res-session-java.jar
and
<InstallDir>/executionserver/applicationservers/<appserver>/jrules-res-session-ejb3-<appserver>.jar,
and not
<InstallDir>/executionserver/applicationservers/<appserver>/jrules-res-session-<appserver>.jar.
The documentation for choosing a XU connection factory when deploying the Rule Execution Server console on WAS and other application servers provides an incorrect configuration order. You must deploy the MBeans descriptors and XU RAR file before you deploy the management EAR file.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Operational Decision Manager

Software version:

8.0

Operating system(s):

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

Software edition:

Enterprise, Standard

Reference #:

1588177

Modified date:

2012-09-28

Translate my page

Machine Translation

Content navigation