There are currently “two” Versions, or Installers available for RTD, 11g and 3.2. While the 11g labelled Version is bundled with the Oracle BI Suite and actually is the 3.2 version, it is not recommended to use this Installer:
After trying to use 11g labelled RTD from the Oracle BI Suite 11g installer, I experienced a variety of errors and Issues when trying to start & run RTD.
After visiting the website again, I discovered a mild warning (recommendation from Oracle) “Oracle Real-Time Decisons 3.2 is the recommended release for both Platform and Applications.” on the RTD download page:
This recommendation can be emphasized! Do not use the 11g installer of RTD to avoid a series of errors with the 11g labelled version and use the 3.2 version instead. The upper link for 3.x version should be used to get to the 3.2 Installer of RTD:
Once a new version of RTD is released (post 3.2) the Issues with the bundled version might not exist with the 11g version of RTD.
The RTD tool: load generator can be used to train models with historical data to have an converged model before go-live. Otherwise the models will start by using random recommendations until a pattern is discovered.
The load generator is located in the following location:
The loadgen.cmd also calls the SetSDParams.cmd file. The file SetSDParams.cmd can be edited to with a line:
SET JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_80
to reference the correct JAVA_HOME location as shown below:
Once the load generator starts, the following configurations need to be done:
- specify path to load generator xml file (containing the training data)
- specify connection details to RTD server
to specify the path click “file open” and select the xml file:
Once the xml file is open in the load generator the connection properties need to be set using the http configuration file:
The configuration file should look similar to:
The load generator script can be started by pressing the play button and the tool will create requests using the supplied xml historical learning data:
When now accessing the RTD Decision Center, the models are already trained with the supplied data:
e.g. individuals who are best-fit for the product “Credit Protection”.
when connecting from RTD Studio to a RTD server to test integration points the following error message is displayed “A Decision Service request was received from untrusted host”:
Thus, the machine that run’s RTD Studio must be added to the list of trusted hosts via Jconsole:
select the server with the higher process id:
connect unsecure (depends on configuration):
add host to list of trusted Clients:
successfully connect from RTD Studio to RTD server: