Question & Answer
Question
What are the known limitations in the releases of WebSphere Operational Decision Management 8.0? This page lists limitations and workarounds for the product. If your component is not listed, no limitations have been reported for it. Updated 5 July 2017.
Rule Designer
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| When editing an Excel scenario file in Rule Designer, the Excel save button does not work. | Use the save button in the Rule Designer toolbar. | 8.0, 8.0.0.1, 8.0.1, 8.0.1.1, 8.0.1.2 |
| The JAR file already present in the SSP is used instead of the class of the Managed XOM even if you select Use XOM deployed to Rule Execution Server for a remote DVS execution from Rule Designer. | You have to remove the XOM from the SSP WAR packaging to avoid class confusion (same package and same name). | 8.0.1 |
| In Rule Designer, migration errors on B2X files are reported twice. | The BuildServices.migrateB2X() method reports the errors twice in the provided ErrorContext. | 8.0.1 |
| When the DE builder in Rule Designer calls BuildServices.setPriority() to migrate the priority values of rules that use a constant such as high, a false migration warning is reported: "The IRL keyword 'bind' is deprecated; use 'explicit typing' instead." | This is probably due to the recent deprecation of bind, which is still used in IRL constructed by BuildServices.migrateValueWParam InPackage(). | 8.0.1 |
| In complex operations where the order of parameters infers on the type, the BigDecimal cast fails. | Verbalize a casting method through B2X. | 8.0, 8.0.0.1 |
| 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. | 8.0 |
| 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. | 8.0, 8.0.0.1 |
| 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. See IBM Rational Application Developer terminates abruptly after starting, or does not start at all. | 8.0, 8.0.0.1 |
| 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] See Q: Why do I get "SWTException: Unable to load graphics library" using GC? | 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. | 8.0 |
| 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. | 8.0 |
| 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. | 8.0 |
| 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 BOM class inheritance and Excel scenario files. | 8.0 |
| 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. | 8.0 |
| 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. | 8.0 |
| 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. | 8.0 |
| Accessibility limitation in Ruleflow editor: There is no keyboard equivalent for creating nodes or links. | You must use the graphical tools. | 8.0 |
| 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. | 8.0-8.0.1.2 |
| Google Chrome does not display the Rule Project Statistics Report. | Launch Google Chrome with the flag "allow-file-access-from-files." | 8.0.1-8.0.1.2 |
| 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. | 8.0 |
| 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 Restart workbench crashes on Windows 7 | 8.0 |
Event Designer
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| 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. | 8.0 |
| 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. | 8.0, 8.0.0.1 |
| Importing an Events project as an existing project into the Event Designer workspace without selecting Copy projects into workspace might result in duplicate or empty asset folders. | Refresh the project.:
| 8.0.0.1 |
| When you use the CSIO_ENTRY table to run an Events test, you might receive the following error message: DSNT408I SQLCODE = -540, ERROR: THE DEFINITION OF TABLE MQMPERF.CSIO_ENTRY IS INCOMPLETE BECAUSE IT LACKS A PRIMARY INDEX OR A REQUIRED UNIQUE INDEX | Redefine csio_pkey_idx key with the following code:
CREATE UNIQUE INDEX csio_pkey_idx on csio_entry (streamid, workflowid, repclassguid, repclassinstanceguid) USING STOGROUP EVSSTG1 DEFINE NO BUFFERPOOL BP2; | 8.0.0.1 |
| If there are chart assets already in the Events runtime and you try to deploy a project from Event Designer that invalidates the chart assets, for example, the charts do not reference assets in the new project, the deployment fails and an error message is displayed. | Use the chart manager widget to modify or delete the chart assets. | 8.0.0.1 |
| The command Compare Context Definition Assets does not show useful information. | No workaround provided for V8.0.1. | 8.0.1 |
Rule Execution Server
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| 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. | 8.0.0.1 |
| There is no "hot" deployment for using a monitored transparent decision service (MTDS) with the JBoss 6.1.0 application server. | 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. | 8.0 |
| 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. | 8.0 |
| After following the optional configuration steps 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:
| 8.0, 8.0.0.1 |
| The Rule Execution Server console log might list the following error message: GBRXC0102E?: File logger initialization failed. Standard output used. Verify the log4j configuration file. Which is associated with the following error message in the servant region's SYSPRINT log: log4j:ERROR setFile(null,true) call failed. | You can ignore this error message. The logger uses standard output by default, and all log messages are located in the SYSPRINT job output elements of the server region. | 8.0.0.1 |
| When running Rule Execution Server on a CICS V5.1 JVM Server, each time a client requires rules to be fetched from DB2, the following message is issued to the MSGLOG:
A transaction dump was taken for dumpcode: AD3F, Dumpid: 20/0001 | Rule Execution Server is unaffected. However, the DB2 connection is being cleaned up on the wrong TCB, so this ABEND is issued from the DB2 termination thread.
Apply the CICS fix for APAR PM80314. You can also find a link to the APAR on the following web page: Fix list for CICS Transaction Server for z/OS 5.1. | 8.0.0.1 |
zRule Execution Server
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| 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. | 8.0, 8.0.0.1 |
| Starting zRule Execution Server can produce an RC1003 message. | The HBRSSID assigned to a zRule Execution Server must be unique across an LPAR and a Sysplex, otherwise startup returns an RC1003 message. | 8.0.1 |
| 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. | 8.0.1-8.0.1.1 |
Decision Validation Services
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| When executing a simulation on a WebSphere Application Server-clustered Rule Execution Server (RES) and Scenario Service Provider (SSP) with a load balancer between the nodes, you get the following error message with no stack trace: Cannot execute the scenario suite ... The operation was aborted by the user. | In Teamserver, set the RES to target one particular node of the cluster. | 8.0 |
| 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. | 8.0.0.1-8.0.1.2 |
| 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:
| 8.0, 8.0.1.1 |
| The DocumentBuilder API in the Oracle JDK, including versions 6u43 and 7u17, does not correctly handle some XML 1.1 documents. See JDK-8012541: Some XML 1.1 documents are not correctly handled by the DocumentBuilder API. | Instead of the Oracle JDK, use the IBM JDK or a recent version of Apache Xerces in the SSP. For Apache Xerces, make sure that its classes are used instead of the JDK classes for XML parsing. | 8.0.1-8.0.1.1 |
Decision Center
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| The search index in the Business console might not always be in sync with the content of the Decision Center repository. This typically happens after a reinstallation of ODM, a migration, or a server crash. Possible symptoms:
| If you have installed Decision Center with a remote SOLR server, you need to delete the SOLR indexes that correspond to Decision Center. If you rely on the embedded SOLR server (default behavior), you must remove the directory that contains the SOLR index. By default, this directory is computed with the following Java expression: System.getProperty("java.io.tmpdir") + "/decisioncenter-solr-dir". Depending on your application server, JVM and OS, this directory is either in a temp or tmp folder inside your application server installation directory, or in a global temporary directory. | All |
| Dynamic XOMs are not automatically taken into account during the merge process. A dynamic XOM is a property of the project information element, which is not versioned. The merge process takes into account only versioned elements such as rules and decision tables. It does not include properties in the project info information elements such as dynamic XOMs. | You must use the synchronization feature in Rule Designer to merge changes in the project information element of the target branch. | All |
| The Business console does not support decision tree rule artifacts. | No workaround. | All |
| The new decision table editor in the Decision Center Business console does not support localized cell comments and formats. When a table is edited, this information is lost and cannot be used by editors in Rule Designer and Rule Solutions for Office. | Do not switch editors if this information is important for your project. To keep this information, select Manual row ordering for the decision tables in the Decision Center Business console. | 8.0.1 |
| When you log in with the same user ID on both Decision Center Business console and Decision Center Enterprise console, you might receive the following error when you log out of one of the consoles: SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user: { }. | This issue is fixed in WebSphere Application Server 8.0.0.3 and later. To enable the fix, you need to add the following custom property to Application servers > server1 > Session management > Custom properties: InvalidateOnUnauthorizedSessionRequestException = true See Logging out results in a WebSphere Application Server error message. | 8.0.1 |
| When you have Decision Center Enterprise console and Decision Center Business console on the same application server, you might be forwarded to the wrong console when you log in to one of the consoles. | The WAS cookie WASRegURL stores a URL to redirect to after a login. After multiple logins, the URL can no longer point to the correct application because the cookie is shared across applications. This issue is fixed in WebSphere Application Server 8.0.0.4. To enable the fix, you need to set the following custom property in Security > Global Security > custom properties: com.ibm.websphere.security.setContextRootForFormLogin=true See PM58885: WASREQURL cookie might be overwritten if multiple login processes are performed. | 8.0.1 |
| When logged in to the Decision Center Enterprise or Business console with a user name of more than 50 characters, actions such as creating or updating rules, snapshots, or comments, produce a warning and fail. | This is due to an inconsistency in the database schema for storing user IDs. To work around this issue, restrict user names to 50 characters or less. | 8.0.1 |
| Entering a very long, multi-byte character string in the Decision Center Enterprise or Business console produces a server 500 error and causes the action to fail. | The database schema is configured to limit the number of bytes, whereas the string length permitted on the console is based on the number of characters. As a result, a multi-byte string that is significantly larger on the byte count causes the database update to fail. | 8.0.1 |
| In Firefox when editing a decision table column label, you cannot start editing by using a mouse click or the Home/End key. | Use the arrow keys to get out of text selection and start editing. The left arrow takes you to the end of the text, and the up arrow to the beginning. | 8.0.1 |
| 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 java.security.SecureRandom 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. Example: dojo.xhrPost({ 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. Example: { name: '__dcsid', value: 'xxxxxxxx' } Note the user-specific token is stored as an attribute of the HTTP session and is bound the name '__dcsid'. | 8.0.0.1 |
The decision table editor in the Business console does not support the following Rule Designer features:
| Features to be added in future releases. | 8.0-8.0.1.2 |
| 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 | 8.0 |
| The drop-down completion menu in the Intellirule editor might contain items from several domains in your BOM. | To resolve this problem, see Unexpected values in domain drop-down. | 8.0, 8.0.0.1 |
Rule Solutions for Office
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| In Rule Solutions for Office Excel files, you can change the formatting of decision table cells, for example, colors and fonts. However, the formatting is not synchronized with Decision Center. | If Rule Designer was used to format the decision tables, synchronizing the files with Decision Center returns the cells to the format that was defined in Rule Designer. Only use Rule Designer to format decision table cells. | 8.0-8.0.1.2 |
Pattern for PureApplication System (ODM Pattern)
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| If users deploy a virtual system pattern with IBM DB2, the pattern deployment fails. This is because the behavior of handling an empty default value in the wodm_db_hadr parameter is changed for the IBM Power hardware platform in IBM PureApplication System V1.1.0.4 or above. | Use the following workaround to change the .ovf definition:
1. Download the ODM image to a local machine into a new empty folder. 2. Run tar xvf Operational_Decision_Manager_V801_AIX_X64.ova to extract the image. 3. Run rm Operational_Decision_Manager_V801_AIX_X64.ova to delete the original image. 4. Open ODM_V801_AIX.ovf and change the following line <ovf:Property ovf:key="wodm_db_hadr" ovf:type="boolean" ovf:value="" ovf:userConfigurable="false" ovf:required="false"> to: <ovf:Property ovf:key="wodm_db_hadr" ovf:type="string" ovf:value="-" ovf:userConfigurable="false" ovf:required="false"> 5.Optional: Delete the existing ODM image that is on the rack and replace the ODM image with the new image that you downloaded. Skip this step if you plan to delete the existing ODM image later, or if you don't have an ODM image. Important: If there's an existing ODM image on the rack, also make the following change rm:name="IBM Operational Decision Manager 8.0.1 AIX 7 X64 (PowerVM?)" to: rm:name="<any name that is different than the original>", for example rm:name="Updated IBM Operational Decision Manager 8.0.1 AIX 7 X64 (PowerVM)" 6. Run tar cvf Operational_Decision_Manager_V801_AIX_X64.ova to recreate the ODM image. 7. Upload the ODM image that you recreated to the rack. | 8.0.1 |
| Users cannot use IBM DB2 HADR support because the Tivoli System Automation (TSA) license has expired in the pattern. | Use the following workaround to extend and reapply the new license, and then capture it as new image:
1. Log in to IBM PureApplication System, and click Catalog > Virtual Images. 2. Click IBM Operational Decision Manager 8.0.1 AIX 7 X64 (PowerVM), and then click Extend. 3. In the General information section, enter the name and version of the new image. In the Deployment configuration section, enter the password for the extended instance. Then, click OK to save your changes. 4. In the extended instance, log in to your virtual machine as root user. Use the password that you specified in the Deployment configuration section. 5. Enter the following command to check your license status: samlicm -s Note: The status shows Error: Product license is invalid and needs to be upgrade. 6. Upload the new license file to your virtual machine, for example, by using the scp command to upload the license file on Linux system. Then, install the license file by entering the following command: samlicm -i <your license file>. 7. Reenter the following command to check your license status: samlicm -s. 8. In the Virutal Images window, click Capture to capture the image. 9. Update virtual system patterns to use the new image that you installed. | 8.0.1 |
| With PureApplication System (Intel 1.0.0.4 and IWD 3.1.0.7), the CLI method fails to import Information Server. It blocks images, but not the pattern and script packages. See Known problems affecting InfoSphere Information Server Enterprise Hypervisor Edition V9.1. | Follow these steps: 1. Add Information Server Virtual Images to IBM Workload Deployer by using the Workload Console as described in Adding virtual images to the catalog. 2. After importing the images, remove the OVA from the content and image directory, which is located in the installer. 3. Rerun the installer script to import the pattern and script packages together. | 8.0.0.1 |
| 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: | 8.0.0.1 |
| 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. | 8.0.0.1 |
| 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. | 8.0.0.1 |
Installation
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| The location of the preferences for the Solr search engine do not work correctly. | The preferences.properties for Solr should be in decisioncenter.war under WEB-INF/classes/com/ibm/rules/decisioncenter/web/search/preferences.properties. | 8.0.0.1 |
| Operational Decision Manager (ODM) 8.0.1.x and Rational Application Developer (RAD) 8.0.4.x have compatibility issues. | Use the solution that applies to you:
| 8.0.1-8.0.1.1 |
| You cannot use the Packaging Utility user interface (UI) to copy an Installation Manager repository for ODM. The Packaging Utility UI does not support repositories that are dedicated to specific platforms. | Use the Packaging Utility command-line tool PUCL, and the option -platform os=win32. | 8.0.1 |
| The launchpad installer does not support installation from a network device. | Launchpad must be downloaded and executed locally. | 8.0.1. |
| The launchpad does not have the disks for z/OS customers to install the developer platform on Windows. | To install IBM Business Rules for z/OS for Windows for Developers or IBM Operational Decision Manager for z/OS for Windows for Developers, follow these steps with IBM Installation Manger:
1. Install IBM Installation Manager from Disk 1 by running its executable file from the Disk1\IM directory. 2. Start IBM Installation Manager and go to File > Preferences and add the following repositories:
3. Install WebSphere Application Server using IBM Installation Manager and create a default profile. 4. If you are installing IBM Decision Server, install WebSphere Extreme Scale manually using the installer located in the Disk2\WXS folder. You may notice a warning regarding the WebSphere Application Server version, which will not stop the install. 5. Finally install IBM Decision Server or IBM Decision Center using IBM Installation Manager. | 8.0.1 |
| Rational Software Architect does not work when you upgrade your WebSphere Operational Decision Management from version 8.0.0.0 to version 8.0.0.1 in the package groups of the following products: IBM Integration Designer, Rational Application Developer, Rational Developer for z (RDz). | Use the embedded Eclipse. | 8.0.0.1 |
| When you create 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 | 8.0.0.1 |
| The following service repositories are not connected: http://public.dhe.ibm.com/software/ websphere/bpm/repositories/server/ wodm/8.0.0/updates/ http://public.dhe.ibm.com/software/ websphere/bpm/repositories/server/ wodm/8.0.0/extensions/ | This warning does not prevent the user from upgrading their WebSphere Operational Decision Manager version 8.0.0.0 to the version 8.0.0.1 offering In the Installation Manager Preferences; uncheck "Check available service repositories" | 8.0.0.1 |
| 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. | 8.0-8.0.1.2 |
| 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. | 8.0 |
| 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. | 8.0 |
| WebSphere Application Server fails to install if your host name contains the underscore (_) character. | Use a host name with no underscore character. See the technote Portal installation fails when hostname contains underscore "_". | 8.0 |
| 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). | 8.0 |
| 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] | A directory path 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. | 8.0 |
| The Test Connection button in the Launchpad does not operate with the Derby database when you follow the stand-alone server path. | This is a known minor defect. | 8.0 |
| 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:
To avoid problems with the extraction of the TAR files, decompress them to the same folder at the root of your hard drive. | 8.0 |
| 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. | 8.0 |
| Running launchpad on Windows 7 can result in installation errors and "Build Failed" messages even when logged in with administrator privileges. | Right-click Launchpad and select Run as administrator when installing on Windows 7. | 8.0 |
| Icons for folders in the Linux shortcut menu are not consistent with the icons of the applications that you use. | No solution. | 8.0 |
Installation of Pattern for PureApplication System
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| 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. | 8.0.0.1 |
Samples
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| 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. | 8.0 |
| 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. | 8.0 |
| HP-UX runs out of memory while starting the sample server. | Modify the scripts WAS_HOME/bin/setupCmdLine.sh Addto the JVM_EXTRA_CMD_ARGS with the option XX:MaxPermSize=512m. | 8.0.1 |
| When you start the Sample Server on HP UX for the first time, the server might appear to hang at the following point:
| In the script bin/launchWsadminListener.sh, change the property PERF_JVM_OPTIONS to add -XX:MaxPermSize=128m. | 8.0 |
Documentation
| Limitation | Comment or workaround | Version(s) |
|---|---|---|
| In the Rule Designer tutorial "Defining a vocabulary," the code sample in Step 3c of "Task 4: Extending the Business Object Model" contains a typo: age-- | Change age-- to age = age -1 or age -=1. | All |
| The Education Assistant link on the welcome page no longer works. | Operational Decision Manager (ODM) Online Education replaces IBM Education Assistant. | All |
| The local help is not supported on 64-bit platforms. | Install a 32-bit compatible library. | 8.0.1 |
| The product information center originally showed that the Decision Center Business console was not supported on WebSphere Application Server V8.5. | The information center now shows that the Business console is supported on WAS V8.5: Configuring Operational Decision Manager on distributed platforms. | 8.0.1 |
| 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. | 8.0-8.0.1.2 |
| 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. | 8.0 |
| The Information Center does not provide enough information to migrate WODM for z/OS V7.5 to V8.0. | For additional information, see WebSphere Operational Decision Management for z/OS: Migrating from V7.5 to V8.0. | 8.0 |
| z/OS does not support clustering. | Steps 4-8 in the topic Installing on a managed node on z/OS are not applicable. | 8.0 |
| 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." See Setting an exception handler. | 8.0 |
| 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. | 8.0-8.0.1 |
| 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. | 8.0-8.0.1 |
| 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. | 8.0-8.0.1 |
[{"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF025","label":"Platform Independent"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.0.1.2;8.0.1.1;8.0.1;8.0.0.1;8.0","Edition":"Enterprise;Standard","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21689570