Known limitations in WebSphere Operational Decision Management V7.5

Technote (FAQ)


Question

What are the known limitations in WebSphere Operational Decision Management V7.5? 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.
The Italian verbalizer does not compute the following articles properly, causing the rules containing these articles to fail to parse:
  • "di + la" should be "della"
  • "di + le" should be "delle"
  • "di + i" should be "dei"
  • "di + il" should be "del"
  • "di + lo" should be '"dello"
  • "di + gli" should be "degli"
Change the rules so that they use the correct grammatical forms of the articles.
The Rule Execution Server component of Decision Server is not installed in the launch configuration panels of the Decision Vadidation Service (DVS) Archive and the DVS Excel File. With DVS Archive and DVS Excel File launch configurations, Rule Execution Server must be installed on the computer using Rule Designer to performer local and remote DVS testing.
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 IRL generated for BOM domains has been changed to take into account the type of the collection in the BOM. This change might have a limited impact on the behavior of rules. In V7.5, the BOM Integer domain is cast to an Integer in IRL. In the last version of the product, V7.1, BOM members with an Integer domain generated a Double type in IRL.
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.
No error message is displayed when synchronization fails between Rule Designer and a Decision Center of a different locale.
WebSphere Application Server 7 cannot use the Monitored Transparent Decision Service (MTDS) generated with Rule Designer. The generated URL triggers the following error:
Error 404: javax.servlet.UnavailableException: SRVE0201E?: Servlet [pretradecheckswdsruleapp.
PretradecheckswdsRunnerImpl]: not a servlet class
Artifacts published from Rule Designer must have the same locale as the target Decision Center. Artifacts of a different locale are ignored, and a message on the failed synchronization is entered in the log.
To resolve the problem, change the generated build.xml by adding the UseWFSEP61ScanPolicy property to manifest in the create.war target (see Manifest Code Example below).

Event Designer

Event Designer
Limitation Comment or workaround
In the FTP Event Connector editor, clearing the Directory is relative to login directory check box results in a malformed directory path. Instead of /%2F, it is incorrectly prepended with %2F/. After clearing the box, manually change %2F/ to /%2F in the directory path.
After a project from WebSphere Business Events V7.0 is imported into WebSphere Operational Decision Management V7.5, the Problems View displays errors. Refer to the following technote for a solution:
Errors are displayed in the Problems View
Prior to V7.5, execution of a rule with a filter would result in a single entry. With V7.5, there are now two entries. In previous releases, a typical rule (NEW RULE) could be written as IF MYFILTER THEN ACTION1, and the filter MYFILTER might be written as THE FIELD1 OF INTERMEDIATEOBJECTA IS 1. Execution of this rule and filter would result in a single entry in the HISTORY_FILTER table for MYFILTER.

With V7.5, there are now two entries: one for the filter MYFILTER, and a second for the rule NEW RULE.
In V7.5, conditional logic can be embedded within a rule. For example, take the rule IF THE FIELD1 OF BUSINESSOBJECTA IS 1 THEN ACTION1. If this rule has the name NEW RULE, an entry called NEW RULE is recorded in history (in the HISTORY_FILTER table) and the Event Tester.

The introduction of the filter history entry corresponding to the rule could cause confusion, but this is correct and expected behavior.

For more information, see the following technote:
In the History_Filter table, and the events tester, an entry for a rule will appear in addition to any filters

Rule Execution Server

Rule Execution Server
Limitation Comment or workaround
The ra.xml deployment descriptor includes a new property: XOM_PERSISTENCE_LAZYLOAD. Set the value of XOM_PERSISTENCE_LAZYLOAD to true to switch to a lazy loading mode for the Managed XOM resources. In lazy loading mode, resources are loaded only when needed. They are unloaded if the system runs low on memory, and reloaded only if the required class cannot be found in the already loaded classes.
The ressetup Ant task is adjusted accordingly.

This option is available only for database access. Some JDBC drivers might not accept this option because it breaks the classic transactional contract.

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 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.
Cannot deploy an event project with rtsUser rights if the "Create a baseline for this deployment" option is selected.

This is visible in tutorial Managing event rules > Tutorials > Managing releases.

Deploy with rtsConfigManager rights instead. For the tutorial, sign in as 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.

Decision Center for z/OS

Decision Center for z/OS
Limitation Comment or workaround
WebSphere Application Server OEM Edition prevents the installation of user-written web applications. Users cannot customize and deploy web applications or use Decision Validation Services. When you run Decision Center for z/OS inside WebSphere Application Server OEM Edition, you cannot do the following operations:
  • Customize Decision Center and Rule Solutions for Office.
  • Repackage the SSP to make the XOM accessible, or package the run time to test it.
  • Repackage the SSP or Decision Center archives to customize tests and simulations.
The Decision and Events widgets do not run in Decision Center for z/OS. The widgets cannot be installed on z/OS, and there is no facility to install them on WebSphere Application Server via Business Space. Use Decision Center on the distributed platform to perform Business Space operations.

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 Server Events

Decision Server Events
Limitation Comment or workaround
With Websphere Fix Pack Versions 15, 17 and 19, and WebSphere MQ Version V7.0.1.4 and V7.0.1.5, the message listener receives the first message published on its topic or queue, but it does not receive any subsequent messages. Only stand-alone JMS applications are affected. Refer to this technote for more information:
- IC76544: WebSphere MQ V7 JMS non-durable subscriber is only able to receive one message
Decision Server Events tries to make database assets. You can set a property to stop Decision Server Events from attempting to create database assets. All you require are the "standard" client rights (select, insert, update, and delete) for the various assets.

See this technote for more information:
Disabling Database creation or validation at Decision Server Events startup

Decision Server for z/OS

Decision Server for z/OS
Limitation Comment or workaround
When you run Rule Execution Server on WebSphere Application Server OEM Edition, you can only call rules that use Hosted Transparent Decision Services. WebSphere Application Server OEM Edition prevents the installation of user-written web applications.
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.

COBOL Management

COBOL Management
Limitation Comment or workaround
The COBOL Management features are not available for 64-bit systems. The installer for Windows includes a 32-bit Java SDK, which is compatible with the provided 32-bit Eclipse. To use Rule Designer in 64-bit, you must have a 64-bit Java SDK and a 64-bit Eclipse. However, the COBOL Management features are not available in 64-bit.

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
LaunchPad uses Installation Manager, a 32-bit executable that is dynamically linked to 32-bit libraries. These libraries might not exist on some 64-bit systems. Install 32-bit libraries prior before you use LaunchPad or Installation Manager. Click here for more information.
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.
Error when you navigate to Typical installation from the LaunchPad:
0x80041013 (“Provider not found”) or 0x80041014 (“Component failed to initialize")
This error can happen in 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 this Windows documentation:
I’m getting an 0x80041013 ("Provider not found") or an 0x80041014 ("Component failed to initialize") error
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 cannot run a typical installation if you copy the installation DVDs to different directories. To perform a typical installation, copy the contents of both disks to the same directory on your computer.

For more information, see this technote:
Installing WebSphere Operational Decision Management using DVDs
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 this 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 LaunchPad or Installation Manager, do not enter a space in the user ID or password.
If you chose to extend an existing Eclipse, the start and stop sample server shortcuts and script might not work. You might have to reset JAVA_HOME. 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
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.

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.

The 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.
Sample: Rule Engine for .NET does not execute. The scripts for the sample do not contain the correct paths. This problem has been fixed for the next release, V7.5.0.1.

Documentation

Documentation
Limitation Comment or workaround
Incorrect: "You can use the Array Type option only on ruleset parameters based on a Java XOM. You cannot use it on ruleset parameters based on an XML XOM." In fact, Rule Execution Server rule sessions and Hosted Transparent Decision Services (HTDS) do not support array types on ruleset parameters from XML XOM. However, if you want to use the Array Type option for engine execution only, you can add the Dcom.ibm.rules.
studio.ignoreXmlXomArrayParameterFilter argument to the VM command line to enable the option in Rule Designer.
Product information center reference:
  • Decision Server Rules V7.5 > Reference > Rule Designer reference > Rule Designer user interface > Dialogs > Rule Project Properties dialog > Ruleset Parameters
Wrong reference to Installation Settings wizard. In the following topics in the product information center, Installation Manager should be Installation Settings wizard:
  • Decision Center V7.5 > Decision Center for business users > Managing business rules > Configure: Manage your project configuration > Administering the console > Running the Decision Center Installation Settings Wizard > Configuring the database
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Rule Execution Server basics > Rule Execution Server persistence layer
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Rule Execution Server console online help > Introducing the Rule Execution Server console > Platform limitations
  • Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server > Rule Execution Server basics > Decision Warehouse
Rule Execution Server message pool.freeConnectionTimeout has been replaced with pool.waitTimeout. The Execution Unit (XU) message can be found in the product information center:
  • Decision Server Rules V7.5 > Reference > Rule Execution Server reference > Messages Rule Execution Server Messages
The parameters -DtargetEar and -DsourceEar are misassociated with repackage-war. The parameters -DtargetEar and -DsourceEar are used with repackage-ear.
The parameters -DtargetWar and -DsourceWar are used with repackage-war.
Product information center reference:
  • Decision Center V7.5 > Deploying and configuring Decision Center > Deploying and configuring Decision Center on WebSphere Application Server V7.0 > Completing the configuration using Ant tasks > Repackaging the Decision Center archive
Sample documentation mistakenly lists Tomcat among server names. Tomcat does not support Enterprise Java Beans.
Product information center reference:
  • Decision Server Rules V7.5 > Samples > Rule Execution Server samples > Sample: Java EE rule session
In the section "Configuring for a CICS JVMServer," this statement is wrong:
"If JVMPROFILEDIR already points to a profile directory that contains a profile, you must merge the profiles."
You do not have to merge the profile files. The JVMServer picks the correct profile, as specified in the resource definition, from the JVMPROFILEDIR.
Missing from documentation: The Jobstep codes for zRule Execution Server (zRES) do not contain 1020. Jobstep code RC 1020 is returned when the HBRINSTPATH property does not point to a valid WebSphere Operational Decision Management for z/OS installation path. Jobstep code 1020 is missing for zRES.
Throughout the product documentation the sample batch application is referred to as ++HBRWORKDS++.SHBRJCL(HBRMINB). The Sample can actually be found at ++HBRWORKDS++.SHBRJCL(HBRMINIB).
The documentation lists JCL variables that are no longer required. The JCL variables ++RESWASINSTANCE++, ++RTSWASINSTANCE++ and ++DVSWASINSTANCE++ are no longer required.
The jdkLoggingEnabled property is set to false by default. For WAS, the default value is true, and for the other application servers, the default value is false.
Product information center reference:
  • 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 > Enabling JDK logging > Setting the XU configuration property
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
Two tasks are out of sequence in a tutorial on configuring the Decision Center console on WebSphere Application Server for Linux on System z. The user should do the "Changing the class loading sequence" task before the "Verifying the deployment of the Decision Center console" task in the following tutorial step:
  • Decision Center V7.5 > Configuring Decision Center > Configuring the Decision Center console on WebSphere Application Server for Linux on System z > Step 7: Deploying the Decision Center EAR on WebSphere Application Server
Section on loading a module is missing from a topic on configuring z/OS. Information on loading a product module is missing from the following section in the documentation:
  • Decision Server for z/OS V7.5 > Configuring Decision Server for z/OS > Configuring your system for usage data collection > Configuring COBOL generated rule subprograms to collect data > Configuring z/OS
Use either of the following procedures to add a definition to the parmlib member PROGxx, where BRCF7100 is the COBOL load module that interacts with SMF:

To load the program dynamically:
1. Issue the following z/OS command:
SETPROG LPA,ADD,MODNAME=(BRCF7100),DSNAME=++HBRHLQ++.SHBRAUTH
Where ++HBRHLQ++ is your user-defined high-level qualifier.
2. Optional: Check that the program has been loaded into the LPA, using the following z/OS system command:
D PROG,LPA,MODNAME=BRCF7100

To load the program permanently:
1. Add the following definition to the parmlib member PROGxx:
LPA ADD MODNAME(BRCF7100) DSNAME(++HBRHLQ++.SHBRAUTH)
Where ++HBRHLQ++ is your user-defined high level qualifier.
2. Optional: Check that the program has been loaded into LPA.
Table gives incorrect configuration for HBRCONSOLECOMPORT. HBRCONSOLECOMPORT should be set to the same port number of the first server hosting the zRES console.
Product information center reference:
Decision Server for z/OS V7.5 > Configuring Decision Server for z/OS > Configuring zRule Execution Server for z/OS > Configuring topologies for production
Incomplete instructions for configuring Decision Center for z/OS.
Product information center reference:
  • Decision Center for z/OS V7.5 > Configuring Decision Center for z/OS > Performing the initial configuration
The effect is minimal if you use the manual configuration instructions. However, you must create the database before you run the wsadmin script. If you want to run the wsadmin script, perform the following step:
  • Decision Center for z/OS V7.5 > Configuring Decision Center for z/OS > Configuring the Decision Center console on WebSphere Application Server for z/OS with DB2 > Step 2: Creating the Decision Center DB2 database
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-java.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
The start menu shortcut to open the Getting Started with events PDF (Start > All Programs > IBM WebSphere Operational Decision Management V7.5 > WebSphere Decision Server > Getting Started with events) opens the Getting Started with business rules PDF. To open the Getting Started with events PDF, open the WebSphere Operational Decision Management information center and click Getting started with event rules on the welcome page, or open from the table of contents: Decision Server Events V7.5 > Getting started with event rules.
You might need to do an extra step to use the scripts to create Rule Execution Server database tables in DB2. 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.
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
The following Decision Server Events topic contains a results image that does not correctly show the error that the user sees in the workspace:
Task 1: Create an event project
For an accurate image, see the following topic for WODM V8.0:
Task 1: Create an event project
The WODM information center does not explain how to turn on event action recording in Decison Server Events. To enable action recording, create the property as.director.bet.install in the Decision Server Events environment and set the property value to true. Restart the event runtime after the change. For more information on configuring properties for Decision Server Events, see Setting properties.
The WODM Information Center provides an incorrect example for the Location JNDI bindings setting in the topic DSEREventOutput node. The correct default URL for the Location JNDI bindings property is corbaloc://localhost:2809.

The following description corrects the information for the URL:

"The connection uses a CORBA-object URL. You can modify the default host name (localhost) and the port number (2809). When integrating WebSphere Message Broker with a clustered Decision Server Events environment, enter the host and port number of each of the clustered Decision Server Events servers separated with a comma, for example, corbaloc::localhost:9809,:localhost:9810."

Related information

WebSphere Operational Decision Management Support
Passport Advantage Online Support
WebSphere Operational Decision Management Home Page
IBM User Communities
Product Information Center
Product Download Document
Product System Requirements
WebSphere Operational Decision Management Technotes

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Operational Decision Manager

Software version:

7.5

Operating system(s):

Platform Independent

Reference #:

1516969

Modified date:

2012-09-28

Translate my page

Machine Translation

Content navigation