This chapter describes issues associated with Oracle Real-Time Decisions (Oracle RTD). It includes the following topics:
Section 54.2, "Oracle RTD Installation Issues and Workarounds"
Section 54.4, "Oracle RTD Configuration Issues and Workarounds"
Section 54.6, "Oracle RTD Administration Issues and Workarounds"
Section 54.7, "Oracle RTD Integration Issues and Workarounds"
Section 54.8, "Oracle RTD Decision Studio Issues and Workarounds"
Section 54.9, "Oracle RTD Decision Center Issues and Workarounds"
Section 54.10, "Oracle RTD Performance Monitoring Issues and Workarounds"
Section 54.11, "Oracle RTD Externalized Objects Management Issues and Workarounds"
Section 54.12, "Oracle RTD Localization Issues and Workarounds"
Section 54.14, "Oracle RTD Third-Party Software Information"
This section describes general issues and workarounds related to Oracle RTD. It includes the following topics:
Section 54.1.3, "DC_Demo Deployment Helper Possible Errors When Changing Rule Scope"
Section 54.1.4, "DC_Demo Deployment Helper Name Change for SQL Server WebOffers Table"
Section 54.1.5, "Infrequent Errors When Processing Concurrent Integration Point Requests"
Section 54.1.6, "Save Choice IDs in Inline Services Rather Than Choices"
Users accessing Decision Center through an Oracle RTD server which does not have Learning Service running will not be able to view any Decision Center reports and may see errors in the Inline Service Navigator pane.
The workaround is to enable and start the Learning Service on the Oracle RTD server.
There are cases where non-mature predictive models will return an actual likelihood rather than NaN during the early life of a model. There are also some cases where mature predictive models will return NaN as opposed to actual likelihoods when the Randomize Likelihood option is enabled for a model. These situations are transient in nature and, in the latter case, do not outweigh the benefits of the Randomize Likelihood feature.
In the DC_Demo Deployment Helper, external_rules_deployment_helper.jsp, when you switch from one rule scope to another, if the xml (Metadata View) is not cleared, then errors may appear. For example, this may occur if you switch scopes from scoring rule to filtering rule, or vice versa. The errors can be safely ignored. The workaround is to manually clear the xml before changing the rule scope.
The DC_Demo Deployment Helper accesses the WebOffers table, whose setup is a standard post-installation task. If the WebOffers table is a SQL Server table, change the name of the table in the external_rules_deployment_helper.jsp file from "WEBOFFERS" to "WebOffers".
When concurrent integration points requests are processed, the system may at times indicate warnings/errors as follows: [WARNING] [RTD-10247]..... "<attributeX_value>" is not a valid value for <type> model attribute "<EntityA.attributeY>". [ERROR] [RTD-10202]..... "<attributeX_value>" is not a valid value for <type> model attribute "<EntityA.attributeY>".For example: [WARNING] [RTD-10247]..... "Call" is not a valid value for numeric model attribute "customer.age".Models may be adversely affected when the above warnings/errors constitute a significant percentage of the total number of requests.
The Getting Started tutorial chapters within Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions and the sample Inline Services CrossSell and DC_Demo store choices in session-tied entities. It is recommended that configurations only save IDs of choices instead of the full choice objects.
Deployment states will be deprecated in a future release. Until then, do not use any deployment state other than Development.
This section describes issues and workarounds related to installing Oracle RTD. It includes the following topic:
If Oracle RTD was installed against a SQL Server database, the test table name for the JDBC data source rtd_datasource must be updated from SDSCHEMAVERSION to SDSchemaVersion.
After logging in to the WebLogic Server administration console, perform the following steps:
Select Services, then JDBC, then Data Sources.
Select rtd_datasource, then the Connection Pool tab.
Select Advanced, click Lock & Edit.
Change the Test Table Name to SDSchemaVersion.
Click Save.
Restart the managed server that Oracle RTD is running on.
There are no known issues at this time.
This section describes general issues and workarounds related to Oracle RTD configuration. It includes the following topic:
Before you run the InitAppDB command script to set up the DC_Demo example data on a DB2 database, you must first edit the file RTD_HOME\examples\DC_Demo\etc\data\DB2\WebOffers.sql (where RTD_HOME is the directory where you installed the Oracle RTD client-side tools). Specifically, add a comma at the end of the following line:
EligibilityRuleMetadata varchar(4000)
This section describes general issues and workarounds related to Oracle RTD and security. It includes the following topic:
When Webgate 10g against Oracle Access Manager (OAM) 11g is configured as the SSO provider for Oracle RTD Decision Center access, logging out of, then back into Decision Center should ask users for their user name and password credentials on the re-login. To ensure that this occurs correctly, you must configure the following Oracle RTD Decision Center resources in OAM/Webgate as public (unprotected or anonymous access): 1. Decision Center logout URI /ui/do/logout 2. Decision Center images /ui/images/*
For information on how to perform the configuration, see the topic "Managing Policies to Protect Resources and Enable SSO" in Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager at the location:
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15478/app_domn.htm#CHEIDJAF
This section describes issues and workarounds related to Oracle RTD Administration. It includes the following topic:
To restart the Oracle RTD application, restart the managed server that Oracle RTD is running on.
This section describes issues and workarounds related to Oracle RTD integration. It includes the following topic:
When setting up the Java Smart Client example, depending on the properties file you are using, you must make some changes to the run configuration in Decision Studio before you run the example.
Note:
<RTD_HOME> refers to the directory where you installed the client-side files, for example, C:\RTD_Tools.
The changes you must make in the Arguments tab require you to enter an explicit, full path name. Make sure that you replace <RTD_HOME> with the exact name of your client-side files installation directory.
If you are using sdclient.properties for your properties file, perform the following change:
In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:
-u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\sdclient.properties"
If you are using sdjrfclient.properties for your properties file, perform the following changes:
In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:
-u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\sdjrfclient.properties"
If you are using clientHttpEndPoints.properties for your properties file, perform the following changes:
In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:
-u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\clientHttpEndPoints.properties"
In the Classpath tab:
Remove the existing project
Add the following jar files: commons-code.jar, commons-httpclient.jar, commons-logging.jar, j2ee-client.jar, rtd-ds-client.jar (if not already present), stax-api-1.0.jar, and wstx.jsr
Add the project with defaults
This section describes issues and workarounds related to Oracle RTD Decision Studio. It includes the following topics:
Section 54.8.1, "Mapping Array Attributes in a Multi-Level Entity Hierarchy"
Section 54.8.2, "Decision Studio Help Cannot be Opened After Particular Operation Sequence"
Section 54.8.3, "Issues When Trying to Enable Caching for Some Entities"
A "parent-child" entity hierarchy is typically defined with the child entity as an attribute of the parent entity. When the child entity is an Array attribute, be careful to map the child Array attribute to its data source in the direct parent entity only. Assume, for example, a Customer with many Accounts, each of which has many Contracts. In Decision Studio, the Customer entity's Mapping tab may display the complete hierarchy as follows: - The Customer entity contains the Account entity as an Array attribute - The Account attribute contains the Contract entity as an Array attribute The Account entity's Mapping tab contains the Contract entity as an Array attribute.With this example, only map the Contract attribute in the Account entity's Mapping tab. Do not map the Contract attribute in the Customer entity's Mapping tab.
After first importing, and then deploying, an Inline Service, an attempt to open Decision Studio Help using the path Help > Help Contents will result in an error, and the Help window will not be displayed. The workaround is to close and reopen Decision Studio.
There are known issues, which may result in compilation and runtime errors, with enabling entity caching where a number of design factors coincide:
You have a multi-level entity hierarchy, and a child entity is an array attribute of a parent entity
The data source for the child entity has no Input column defined
You want to enable caching on the child entity
If possible, simplify the structure of the child entity, specifically the attributes that are mapped to the sources. If this is not possible, contact Oracle Support with details of your particular design configuration.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle RTD performance monitoring. It includes the following topic:
The instructions to access performance count information, by opening the ds_perf.xls file, and following the directions that appear in the top cell, do not format the output correctly. As a workaround, create a new spreadsheet in Microsoft Excel, and import the ds_perf.csv data through the Text Import Wizard (Data > Import External Data > Import Data, then select the default options).
See also Section 54.13.1.1, "CSV File Contents" and Section 54.13.1.2, "XLS File Contents."
There are no known issues at this time.
There are no known issues at this time.
This section describes errata in Oracle RTD documentation and help systems. It includes the following topic:
This section describes documentation errata in the Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions. It includes the following topics:
In Section 11.3, "CSV File Contents", the following field names should be removed:
Max Allowable Running Requests
Request Queue Capacity
Peak Queue Length
Max Queue Length
Requests Waiting (Queue Length)
Requests When Queue Full, Total
Requests Queued, Total
In the same section, the following field name and description should be added:
Requests Finished
The total number of Inline Service requests that have been finished.
In Section 11.4, "XLS File Contents", the information about the column Utilization (%) should be removed, as this column is no longer generated.
See also Section 54.10.1, "Access Performance Counts Directly from ds_perf.csv."
This section describes errata in the Oracle RTD help systems. It includes the following topic:
An attempt to access the manual Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions from within Decision Studio using the path Help > Help Contents > Oracle RTD Decision Studio > Decision Studio Reference > User Manuals > Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions will result in a different Oracle Fusion Middleware manual appearing. The workaround is to access the correct manual from http://download.oracle.com/docs/cd/E14571_01/bi.1111/e16630.pdf.
This section provides third-party software information. It includes the following topic:
The third-party package Displaytag can be downloaded from http://displaytag.sourceforge.net.