Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Oracle Solaris Part Number E14772-32 |
|
|
PDF · Mobi · ePub |
This chapter describes issues associated with Oracle Real-Time Decisions (Oracle RTD). It includes the following topics:
Section 43.2, "Oracle RTD Installation Issues and Workarounds"
Section 43.4, "Oracle RTD Configuration Issues and Workarounds"
Section 43.6, "Oracle RTD Administration Issues and Workarounds"
Section 43.7, "Oracle RTD Integration Issues and Workarounds"
Section 43.8, "Oracle RTD Decision Studio Issues and Workarounds"
Section 43.9, "Oracle RTD Decision Center Issues and Workarounds"
Section 43.10, "Oracle RTD Performance Monitoring Issues and Workarounds"
Section 43.11, "Oracle RTD Externalized Objects Management Issues and Workarounds"
Section 43.12, "Oracle RTD Localization Issues and Workarounds"
Section 43.14, "Oracle RTD Third-Party Software Information"
Depending on your Oracle Fusion Middleware implementation, some information in other chapters of this document might also be relevant, including:
Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control"
Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment"
This section describes general issues and workarounds related to Oracle RTD. It includes the following topics:
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.
Deployment states will be deprecated in a future release. Until then, do not use any deployment state other than Development.
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:
Navigate to the unzipped RTDdeploytool folder, for example, C:\<myDir>\OracleBI\RTDdeploytool.
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.
It is a standard requirement for Inline Service names and batch names to be unique within a cluster.
After an Inline Service is copied within a cluster, batch names registered in the Inline Service can be changed manually to achieve uniqueness. This manual step is not required if the batch registration code in the Inline Service automatically generates the batch name from the new Inline Service name, as in the following generic examples:
batchAgent.registerBatch(
batchAgent.getInlineService().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);
or
batchAgent.registerBatch(
Application.getApp().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);
Note that all programs that may call the batch need to be made aware of the new batch name.
There are no known issues at this time.
There are no known issues at this time.
There are no known issues at this time.
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
There are no known issues at this time.
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, and rtd-ds-client.jar (if not already present).
Add the project with defaults
This section describes issues and workarounds related to Oracle RTD Decision Studio. It includes the following topics:
Section 43.8.1, "Mapping Array Attributes in a Multi-Level Entity Hierarchy"
Section 43.8.2, "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.
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.
Deploying an Inline Service to a cluster with the "Terminate active sessions" option selected will terminate sessions on only the Decision Server that receives the Inline Service deployment request.
There are no known issues at this time.
There are no known issues at this time.
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:
There are no known documentation errata at this time in the Oracle Fusion Middleware Administrator'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"
Section 43.13.2.2, "Save Choice IDs in Inline Services Rather Than Choices"
The External Rules Development Helper, currently released with the DC_Demo Inline Service, does not function as described in Section 17.2.8, "Setting Up the External Interface and Embedded Rule Editor" and Section 17.3, "Example of End to End Development Using Dynamic Choices and External Rules."
The Getting Started tutorial chapters within Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions store choices in session-tied entities. It is recommended that configurations only save IDs of choices instead of the full choice objects.
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
.