43 Oracle Real-Time Decisions

43.1.1 Oracle RTD Server Used for Decision Center Reports Must Have Learning Service Running

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.

43.1.2 Transient Likelihood Problems

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.

43.1.3 DC_Demo Deployment Helper Possible Errors When Changing Rule Scope

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.

43.1.4 DC_Demo Deployment Helper Name Change for SQL Server WebOffers Table

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".

43.1.5 Infrequent Errors When Processing Concurrent Integration Point Requests

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.

43.1.6 Save Choice IDs in Inline Services Rather Than Choices

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.

43.1.7 Use Development Deployment State Only

Deployment states will be deprecated in a future release. Until then, do not use any deployment state other than Development.

43.1.8 Ignore Exception Message While Runnning Oracle RTD Job

On scaling out the domain with Oracle RTD component to a different computer that has Oracle WLS and Oracle BI installed, managed server gets created. But on starting the managed server it shows the following stack in Oracle BI server:

<Sep 26, 2010 11:32:57 PM PDT> <Error> <oracle.rtd.logger> <RTD-10336>
<Exception was thrown while executing RTD job
com.sigmadynamics.exception.SDRuntimeException: Unable to resolve 'RTDCF'.
Resolved ''
        at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNod
e.java:1139)
        at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) 
        at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
        at
weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) 
        at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)

You can ignore these exception messages as it is just a stack trace appearing in log files with no functional impact.

43.1.9 Model Snapshot Values for Correlation and Predictiveness Incorrect for Completed Time Windows

Model snapshot values for correlation (table RTDCorrelation) and predictiveness (table RTDPredictiveness) are incorrect for completed time windows for model instances marked with state = c.

43.1.10 Error Deploying Inline Services from Command Line if Inline Service Uses Certain Functions

An Inline Service that uses one or more of the built-in functions Days Since Last Event, Days Since Last Event on Channel, Number of Recent Events, or Number of Recent Events on Channel cannot be deployed using the command-line deployer.

The workaround is as follows:

1. Navigate to the unzipped RTDdeploytool folder, for example, C:\<myDir>\OracleBI\RTDdeploytool.

2. Copy the includes folder from RTD_HOME\eclipse\plugins\com.sigmadynamics.studio_11.1.1.5.0 (for example, C:\OracleBI\RTD\eclipse\plugins\com.sigmadynamics.studio_11.1.1.5.0\includes) into the unzipped RTDdeploytool folder.

43.1.11 Model Corruption Occurs When the Aggregate Number of Choice Events Exceeds Maximum Range

Model corruption occurs when the aggregate number of choice events recorded for a model exceeds the "int" java class maximum value: 2,147,483,647. Upon learning server restart, the corrupt model will be detected but not loaded into memory, and a new empty model will be created. This new model learns on new data until the next learning server restart when the existing corrupt model will be detected again.

43.2.1 Update Test Table Name for SQL Server Data Source rtd_datasource

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:

1. Select Services, then JDBC, then Data Sources.

2. Select rtd_datasource, then the Connection Pool tab.

3. Select Advanced, click Lock & Edit.

4. Change the Test Table Name to SDSchemaVersion.

5. Click Save.

6. Restart the managed server that Oracle RTD is running on.

43.4.1 Edit DB2 Setup Script for DC_Demo

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)

43.5.1 Decision Center Logout Not Redirected Correctly for Oracle Access Manager (OAM) 11g Form-Based Authentication

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

43.6.1 Restarting Oracle RTD Deployment Causes Unexpected Behaviors

If you restart Oracle RTD by restarting the WebLogic Oracle RTD deployment instead of restarting the WebLogic server itself, this could lead to unexpected behaviors that affect model updates and the saving of updated Oracle RTD MBean settings. The workaround is to restart the WebLogic server that Oracle RTD has been deployed into.

43.6.2 Oracle RTD JDBC Data Source Disruptions Cause Unexpected Behaviors

If an Oracle RTD JDBC data source is disrupted as a result of network or database outage, or if an Oracle RTD data source is suspended and resumed in WebLogic, unexpected behaviors may occur, including models that are no longer updated. The workaround is to restart the WebLogic server that Oracle RTD has been deployed into.

43.7.1 Java Smart Client Run Configuration Changes Required for Different Properties Files

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.

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, and rtd-ds-client.jar (if not already present).

  • Add the project with defaults

43.8.1 Mapping Array Attributes in a Multi-Level Entity Hierarchy

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.

43.8.2 Decision Studio Help Cannot be Opened After Particular Operation Sequence

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.

43.8.3 Issues When Trying to Enable Caching for Some Entities

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.

43.10.1 Access Performance Counts Directly from ds_perf.csv

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 43.13.2.1, "External Rules Development Helper Mismatch between Code and Manual Description" and Section 43.13.1.2, "XLS File Contents."

43.13.1 Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions

This section describes documentation errata in the Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions. It includes the following topics:

• Section 43.13.1.1, "CSV File Contents"

• Section 43.13.1.2, "XLS File Contents"

43.13.2 Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions

This section describes documentation errata in the Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions. It includes the following topic:

• Section 43.13.2.1, "External Rules Development Helper Mismatch between Code and Manual Description"

43.14.1 Displaytag Download Location

The third-party package Displaytag can be downloaded from http://displaytag.sourceforge.net.