4 Configuration Issues

This chapter provides release notes related to Oracle RTD configuration. It contains the following topics:

• Section 4.1, "Oracle RTD Application Must be Deployed Within its Own Managed Server Instance"

• Section 4.2, "Known Issue with Oracle JDBC Driver Packaged with Oracle RTD 3.0"

• Section 4.3, "Decision Service Only Accepts Requests from the Local Host by Default"

• Section 4.4, "Communication Between Multiple Real-Time Decision Servers Is Restricted by Default"

• Section 4.5, "Import Database Table Box Returns All Tables from All Catalogs for an Oracle BI EE Data Source"

• Section 4.6, "Issue with Some Versions of Sun Java 1.5 on OC4J"

4.1 Oracle RTD Application Must be Deployed Within its Own Managed Server Instance

This issue applies to Version 3.0 and Version 3.0.0.1.

Other applications may be rendered inoperable if they are deployed within the same java virtual machine as Oracle RTD. If other applications share a JVM with Oracle RTD, you may encounter initialization errors upon application server start-up. In order to work around this issue, deploy Oracle RTD within its own managed server instance.

4.2 Known Issue with Oracle JDBC Driver Packaged with Oracle RTD 3.0

This issue applies to Version 3.0 and Version 3.0.0.1.

There is a known issue with the version of the Oracle JDBC driver shipped with Oracle RTD 3.0. This may occur while running the Oracle RTD batch facility or in Oracle RTD's runtime causing unexpected results and ArrayIndexOutOfBoundsExceptions being logged in the Oracle RTD server log file.

To address this issue, the Oracle 10.2.0.4 driver ojdbc14.jar shipped with Oracle RTD, and located in RTD_HOME/lib/jdbc, should be replaced with the Oracle DB 10.2.0.5 jdbc driver.

4.3 Decision Service Only Accepts Requests from the Local Host by Default

This issue applies to Version 3.0 and Version 3.0.0.1.

The Decision Service by default will only accept (integration point) requests from the computer that hosts the Decision Service.

For production environments where Real-Time Decision Server is installed on a separate host, administrators can set up a list of trusted hosts from which the Decision Service can receive requests.

Note:

Remote Decision Center access (browser access) is not affected by this feature.

To specify a list of trusted hosts for Decision Service requests:

1. If you are using OC4J or WebLogic, open JConsole by running JAVA_HOME/bin/jconsole.exe. If you are using WebSphere, run the batch script you created during JConsole configuration. See Installation and Administration of Oracle RTD for more information about accessing JConsole.

2. Click the Remote tab. Then, enter the appropriate port number (typically 12345) and the administrator credentials you created during installation and click Connect.

3. Click the MBean tab, then go to the OracleRTD > SDClusterPropertyManager > Cluster MBean and ensure the RestrictDSClients attribute is set to true. This attribute ensures that the Decision Service only accepts requests from its own host, or from the list of hosts identified in the TrustedDSClients attribute. If RestrictDSClients is set to false, any machine can send Decision Service requests to the RTD server.

4. In the OracleRTD > SDClusterPropertyManager > Cluster MBean, update the TrustedDSClients attribute to include a semicolon-separated list of IP addresses of the hosts from which you want Decision Service to accept requests. You must specify IP addresses; do not specify host names.

4.4 Communication Between Multiple Real-Time Decision Servers Is Restricted by Default

This issue applies to Version 3.0 and Version 3.0.0.1.

Multiple Real-Time Decision Servers cannot communicate with each other by default.

For production environments where multiple Real-Time Decision Servers are installed, administrators can set up a list of trusted cluster hosts so that the Real-Time Decision Servers can communicate with each other.

To specify a list of trusted cluster hosts for Real-Time Decision Server internal communication:

1. If you are using OC4J or WebLogic, open JConsole by running JAVA_HOME/bin/jconsole.exe. If you are using WebSphere, run the batch script you created during JConsole configuration. See Installation and Administration of Oracle RTD for more information about accessing JConsole.

2. Click the Remote tab. Then, enter the appropriate port number (typically 12345) and the administrator credentials you created during installation and click Connect.

3. Click the MBean tab, then go to the OracleRTD > SDClusterPropertyManager > Cluster MBean and ensure the RestrictClusterMembers attribute is set to true. This attribute ensures that the Real-Time Decision Servers can only communicate with the hosts listed in the TrustedClusterMembers attribute.

4. In the OracleRTD > SDClusterPropertyManager > Cluster MBean, set the SDGroupName attribute to some non-blank value.

5. In the OracleRTD > SDClusterPropertyManager > Cluster MBean, update the TrustedClusterMembers attribute to include a semicolon-separated list of IP addresses of the hosts where the Real-Time Decision Servers are installed. You must specify IP addresses; do not specify host names.

4.5 Import Database Table Box Returns All Tables from All Catalogs for an Oracle BI EE Data Source

This issue applies to Version 3.0 and Version 3.0.0.1.

When you enter the URL for an Oracle BI EE data source, you can specify a value for the parameter catalog. The intention of the catalog parameter is to enable you to view and select from just the tables in a particular catalog.

The error is that all tables in all catalogs appear in the Import Database Table window, even when you specify a value for the catalog parameter. This situation is undesirable because different catalogs may have tables of the same name.

In the process of creating a data source in Oracle RTD Decision Studio, if you select an incorrect table name, you can either delete the Inline Service data source, or manually alter the column names of the Inline Service data source, by checking table and column names in the Oracle BI EE Administration Tool or Oracle BI Answers.

4.6 Issue with Some Versions of Sun Java 1.5 on OC4J

This issue applies to Version 3.0 and Version 3.0.0.1.

When using SUN Java 1.5.0_17+ on OC4J, OC4J may fail to start unless the following jvm option is added to the OC4J command script (oc4j or oc4j.cmd):

-XX:CompileCommand=exclude,com/evermind/server/http/EvermindHttpServletRequest,init

For example, if using oc4j.cmd, add the following line after the line marked by ":oc4j":

set JVMARGS=%JVMARGS% -XX:CompileCommand=exclude,com/evermind/server/http/EvermindHttpServletRequest,init