News
Abstract
This page lists the known limitations in the different release versions of Operational Decision Manager 8.11. The list also provides workarounds for most of the issues.
Content
Table of contents
|
|||
General
Limitation | Comment or workaround | Version |
---|---|---|
Some features that use IBM WebSphere Application Server Liberty server do not work with the latest Semeru Java. | If you upgrade to Semeru Java 8.0.332.0 (OpenJDK 8u332-b09 - OpenJ9 0.32.0) or later, you should also update IBM WebSphere Application Server Liberty to 22.0.0.3. If you do not update Liberty, you can lose some functionality. For example, the Decision Server sample server might not start, and you see the following message in the log: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found | 8.11.0 |
Using Java from JDK 8.0.6.25 on Windows might trigger an IBMJCEPLUS exception. | Use one of following workarounds:
|
8.11.0 |
When you use JDK 8.0.4.5, there can be long GC pause times that are caused by the unloading of classes by the JVM. This action can disrupt service.
|
Upgrade your JDK to the latest recommended version (see Detailed system requirements). | 8.11.0 |
Limitation | Comment or workaround | Version |
---|---|---|
WebSphere Application Server 9 gets IllegalHttpBodyException. | See Deploying the Rule Execution Server management EAR. Apply steps 3 and 4 to HTTP inbound channel (HTTP 2) and HTTP inbound channel (HTTP 4). | All |
Spring Framework has a potential remote code execution issue when used for Java deserialization of untrusted data (CVE-2016-1000027). | There is no fix for the CVE-2016-1000027 vulnerability. Pivotal Spring Framework through 5.3.16 has a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue might occur, and authentication might be required. The vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data. | All |
Users of Semeru JDK on macOS machines cannot use the Norwegian locale (no_No). They get an exception when loading a project. | To work in Norwegian on Operational Decision Manager components, use a different operating system. | 8.11.0.1 |
After installing Rule Designer from Eclipse with Install New Software, the Rule perspective does not open. The perspective is the main interface for Rule Designer. |
Eclipse installs a version of the org.eclipse.draw2d plug-in that is incompatible with Java 8. The plug-in prevents the Rule perspective from starting. In Eclipse, disable the Latest Eclipse Release setting before installing Rule Designer:
|
8.11.0 |
Spring 5.3 has introduced an incompatibility with old versions of JBoss. An open source framework, Spring is used in the foundation of IBM Operational Decision Manager Decision Center in the Business console and the REST API. |
To resolve the problem, see
Spring incompatibility with old versions of JBoss affects
|
8.11.0 |
In Configuring on a clustered environment, the instructions show an incorrect attribute for increasing the heap sizing on Linux. |
Instead of -Xms256M, the documentation should show -Xmx256M. | 8.11.0 |
Rule Designer
Limitation | Comment or workaround | Version |
---|---|---|
Rule Designer runs slowly or stops responding when a help view is open. |
Try the following workarounds:
|
8.11.0 |
The sample in Automated decision service deployment sample setup and details does not work as described. | You need to modify two files to run the tasks successfully:
|
8.11.0 |
The BOMs do not support Java 8 java.time types. | Don't use Java 8 java.time types in BOMs. | 8.11.0 |
You cannot test decision operations in the Rule Designer that is available in the Eclipse Marketplace. | The testing feature is available in the Rule Designer that is packaged in the Decision Server repository that is available through IBM Passport Advantage Online. | 8.11.0 |
While you are editing decision tables in Rule Designer on macOS, the Eclipse window stops responding, and the Eclipse process must be closed. The same behavior is observed for the following deprecated features: decision trees, rule template, and decision table template. |
Avoid editing ruleflows, decision tables, and decision trees or templates in Rule Designer on macOS. Use the editors in Decision Center, or use Rule Designer on a different operating system, for example, Windows or Linux.
For decision tables, try disabling the Swing editors in Rule Designer:
|
8.11.0 |
If you use Rule Designer in macOS, and you deselect Embedded Swing editors as shown in the previous workaround, Eclipse stops responding if you open a ruleflow, and you must close the Eclipse process. | Avoid editing ruleflows, decision tables, and decision trees or templates in Rule Designer on macOS. Use the editors in Decision Center, or use Rule Designer on a different operating system, for example, Windows or Linux. | 8.11.0 |
When you import a rule project into Rule Designer on macOS, you might not be able to expand the folders in the project. |
When you import a rule project:
|
8.11.0 |
When you use the Samples Console, you cannot see the commands in the Samples Commands tab. | You cannot see the commands when an Ant window is open. Restart Eclipse to display the commands. | 8.11.0 |
The name property cannot be empty when you publish a project from Rule Designer to Decision Center. | Make sure that all the rules and packages are in the rule folder, and there is no .rulepackage file directly in the rule folder or anywhere else in the rule project. | 8.11.0 |
When you run automated builds in headless mode from the Windows command line, you get an error message if no argument is specified. For languages that use extended character sets, the error message is displayed incorrectly. |
To avoid this issue:
|
8.11.0 |
While the ilog.rules.brl types that represent a complete date without a time (SimpleDate and UniversalDate) can be used as is for comparisons, the other types for partial dates might require changes to obtain the wanted comparison behavior. For example, if you use ilog.rules.brl.Month and data for month/day/year, a comparison of months might fail as whole dates, and not partial dates, are compared. |
To prevent this problem:
|
8.11.0 |
Decision Center
Limitation | Comment or workaround | Version |
---|---|---|
Vulnerability scanners show Content Security Policy (CSP) as a vulnerability.
|
The HTTP Content Security Policy (CSP) response header allows website administrators to control resources that the user agent is allowed to load for a given page. The script source policy for Operational Decision Manager requires the use of directives that might be detected by some vulnerability scanners as vulnerable: script-src: unsafe-inline unsafe-eval. Those directives are needed by Decision Center to work properly and you must keep them. | All |
In the Business Console, the same user cannot open several windows in the same browser. | None | 8.11.0 |
Running decision model RuleApps does not generate all the execution trace information:
|
Some trace information is not available when trace is enabled for a ruleset that is generated by using a decision model. | 8.11.0 |
The Import Excel File command in the decision table editor in the Business console imports any formula that is contained in an Excel file, instead of just the results of the formula. | To import a copy of an Excel file with the formulas replaced by their results:
|
8.11.0 |
The search feature does not take into account technical rules or functions. | Users can find technical rules and functions by using the query feature. | 8.11.0 |
In OpenID Connect, when you run a request that needs authentication from the decisioncenter-API Swagger URL, the basic authentication connection setting is displayed, instead of the OAUTH/OpenID connection panel. | N.A. | 8.11.0 |
Snapshot comparison does not work when decision service dependencies are updated after snapshot creation. | Snapshots made after a dependency update can be compared. | 8.11.0 |
You might encounter improper functioning of the search in the Business console or log entries related to org.apache.solr that are caused by upgrades to the embedded Apache Solr search engine.
|
Re-index the search:
Solr indexes are then automatically regenerated. You can locate the Solr index directory by running the diagnostic in the Business console.
|
8.11.0 |
Spring Boot has a feature that automatically detects any logging framework that is available. It is based on the presence of classes listed in org.springframework.boot.logging.LoggingSystem.SYSTEMS - either Logback, Log4j or JUL). Spring Boot configures the feature from either an application-provided logging configuration file or Spring Boot’s own default configuration file, which is packaged in Spring Boot. This can cause issues when Spring Boot bypasses the application server logging configuration. In this case, the application server configuration file is not taken into account and all the defined filters are ignored. |
To configure logging with a platform logging configuration file, you must disable the Spring Boot override mechanism. To do so, set a JVM property to configure the Spring Boot logging behavior with the following property and value:
-Dorg.springframework.boot.logging.LoggingSystem=none
|
8.11.0 |
On Weblogic 12.2.1.0, decisioncenter.war, deicisioncenter-api.war, decisionmodel.war, org.springframework.beans.factory.BeanDefinitionStoreException: IOException |
The problem is an issue with WebLogic Server 12.2.1.0.0, and is fixed in WebLogic Server 12.2.1.3.0.
Options:
|
8.11.0 |
The Decision Center ear cannot start on WAS 8.5.5, using the bundled JDK (IBM JDK 8.0.5.6). This is caused by the following issue: http://www.ibm.com/support/docview.wss?uid=swg1IJ03716 | Upgrade the IBM SDK version bundled in WAS8.5.5 to IBM SDK 8.0.5.10 or earlier. | 8.11.0 |
When you start the Decision Center enterprise archive on WLP18.0.0.2, you might get the following harmless warnings:
|
Filter out the warnings by changing the log level to ERROR for the package name com.ibm.wsspi.injectionengine. | 8.11.0 |
You cannot put more than 256 input nodes in a decision model. | Using more than 256 input nodes makes the Validate and Deploy features fail. | 8.11.0 |
In decision modeling, when you choose the Hebrew or Islamic calendar in your preferences, you still get dates in the Gregorian calendar. | You can only edit a date using the Gregorian calendar in a decision model in Decision Center. Even when the user profile is set to the Islamic or Hebrew calendar, the dates are still in Gregorian. | 8.11.0 |
Rule Execution Server
Limitation | Comment or workaround | Version |
---|---|---|
If you create a profile with the profile management tool in WebSphere Application Server 9.x, the profile augmentation of Decision Server fails because the server.xml file cannot be found. | The profile template does not support the profile management tool. Follow the instructions in the topic Configuring components on a stand-alone profile. | 8.11.0 |
With versions of WebSphere Application Server before 9.0.5.3, a defect (PH14966) prevents the Rule Execution Server console from starting. |
Change the name of the library
<WAS_HOME>/plugins/com.ibm.ws.prereq.jsfportlet.jar
to <WAS_HOME>/plugins/com.ibm.ws.prereq.jsfportlet.jar.bk.
|
8.11.0 |
The contextual help in the Rule Execution Server console might not work in your installation, especially if you use the IBM WebSphere Liberty server. |
If you get errors for SSL handshakes in the Rule Execution Server console logs, note the name of the host that is related to the errors, and then add the certification chain for this host to your JVM trust store. Usually, the host name is www.ibm.com, but it can be different.
Follow these steps to add the certification chain to WebSphere Liberty:
|
8.11.0 |
If you use a Swagger API to run rules that have a parameter named response or request, the run stops and you get a bad request error:
statusCode=400, responseMessage=Bad Request,
responseBody=sun.net.www.protocol.http.HttpURLConnection$HttpInputStream@7c8dbe70, responseHeaders=CaseInsensitiveMultivaluedMap [map=[null=HTTP/1.1 400 Ba
|
Do not use response or request in parameter names for Swagger calls. | 8.11.0 |
In Hosted transparent decision services, one of the URLs inverts the RuleApp and the ruleset. |
The following URL is incorrect:
It must be:
|
8.11.0 |
Since the update of the Myfaces third-party library, warnings are issued to the RES console log when users browse the web application, for example:
|
Set the logging trace org.apache.myfaces.shared.renderkit.html.* to error to hide the warning messages in the log
For liberty/WAS: Use the trace specification org.apache.myfaces.shared.renderkit.html.*=error
For Tomcat: add org.apache.myfaces.shared.renderkit.html.*.level = SEVERE
to the logging.properties file . |
8.11.0 |
In the decision engine, a ruleset with ruleflows that contain tasks and packages with UTF-8 characters in their names might break at runtime when you run IBM JDK 8.0.6.5 or 8.0.6.6. | Avoid updating your runtime servers to IBM JDK 8.0.6.0. IBM JDK is looking for a solution. If upgrading the JDK is required, modify the names in the ruleflow to use ASCII characters. | 8.11.0 |
JBoss EAP 7.1.x before 7.1.3 prevents HTDS from running correctly. |
Update to JBoss 7.1.3. Alternatively, you can update the commons-logging-jboss-logmanager Wildfly module to version 1.0.3.Final in $WILDFLY_HOME/modules/system/layers/base/org/jboss/logmanager/commons/logging/main directory.
Compile the commons-logging-jboss-logmanager-1.0.3.Final.jar by using the repository https://github.com/jboss-logging/commons-logging-jboss-logmanager/tree/1.0.3.Final. Change the module.xml file to take the new JAR. |
8.11.0 |
While running a test, you get the following exception error: Caused by: com.ibm.db2.jcc.am.SqlDataException: VALUE <Lob-Value> IS TOO LONG. SQLCODE=-433, SQLSTATE=22001, DRIVER=3.72.45
|
You might need to modify the size of the tables that are used by Decision Runner. In the table EXECUTIONINSTANCEDATA, increase the column parameters to a BLOB of 2GB.
On DB2:
ALTER EXECUTIONINSTANCEDATA ALTER parameter SET BLOB(2G)
|
8.11.0 |
zRule Execution Server for z/OS
Limitation | Comment or workaround | Version |
---|---|---|
CICS 5.5 upwards: Configuration of the automatic HBRC on startup requires updating. |
Add a member DFHPLTHB to one of the datasets in the z/OS PARMLIB concatenation, and put this code in it: DFHPLT TYPE=INITIAL,SUFFIX=HB |
All |
The topic Configuring SSL (TLS) for a zRule Execution Server for z/OS® using RACF shows the wrong sslProtocol: SSL_TLS. |
The correct sslProtocol is SSL_TLSv2:
|
8.11.0 |
In the topic Configuring the Liberty server angel process, the following start command is incorrect: START HBRZANGL | The command should be as follows: START HBRZANGL,NAME='HBRZANGL' | 8.11.0 |
In the Rule Execution Server console, you can display the execution statistics of a ruleset. These statistics include Last execution date. Session caching on z/OS results in Last execution date showing In Progress, even after rule execution completes.
|
If you need to use the Last execution date value, you must start zRule Execution Server for z/OS with the -DHBRNOSESSIONCACHE=true setting. | 8.11.0 |
Operational Decision Manager on Certified Kubernetes
Limitation | Comment or workaround | Version |
---|---|---|
If you use an ibm-odm-dev Helm chart earlier than version 21.2.0, you will encounter an error when installing an instance of Operational Decision Manager for Developers.
|
IBM is moving product images from Docker, docker.io/ibmcom, to the IBM Container Registry, icr.io. You can now obtain the IBM Operational Decision Manager for Developers image without authentication by using this IBM-controlled source.
Move from Docker to the IBM Container Registry by setting the image.repository parameter to icr.io/odm-k8s when you install an instance of Operational Decision Manager for Developers.
|
8.11.0 |
Was this topic helpful?
Document Information
Modified date:
22 September 2023
UID
ibm16494491