4 Configuration Issues

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

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

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 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. In the Remote Process section, 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 > Cluster > Decision Service 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 > Cluster > Decision Service 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.