This chapter describes the steps involved in the installation of Oracle RTD, the creation of the Oracle RTD database, and the (optional) population of database tables that provide the data source referenced by the Inline Services released with Oracle RTD.
The Real-Time Decision Server must be installed on the computer where your chosen application server is resident.This chapter contains the following topics:
Section 2.2, "Creating and Initializing the Oracle RTD Database"
Section 2.3, "Populating the CrossSell Example Data (Optional)"
Section 2.4, "Populating the DC_Demo Example Data (Optional)"
Real-Time Decision Server can run on either Windows or UNIX. The Oracle RTD client tools, such as Decision Studio, Load Generator, and SDDBTool, can only run on Windows.
This section contains the following topics:
Section 2.1.1, "Installing Oracle RTD on a Single Windows Computer"
Section 2.1.2, "Installing Real-Time Decision Server on UNIX"
To install all Oracle RTD components on a single Windows computer, follow these steps:
Unzip the appropriate Oracle RTD archive file into the directory where you want to install the Oracle RTD files. Be sure to choose the correct archive file for your operating system and application server type. For example, the file format for Windows and WebLogic is rtd-weblogic-3.2.0.0.0.<build_number>.zip.
After you extract the files, a directory called OracleBI\RTD is created that contains all the Oracle RTD files. This directory is your RTD_HOME.
If you are using WebLogic, the .ear file for the Oracle RTD application must be expanded before it can be deployed on the WebLogic application server. To do this, follow these steps:
Go to RTD_HOME\package and create a directory called expanded to hold the contents of the RTD.ear file.
Use WinZip to extract the RTD_HOME\package\RTD.ear file into the RTD_HOME\package\expanded directory.
To install Real-Time Decision Server on a UNIX computer, and install the Oracle RTD client tools on a Windows computer, follow these steps:
To install Real-Time Decision Server on UNIX, use cpio to extract the appropriate archive file into the directory on the UNIX computer where you want to install the Real-Time Decision Server files. Be sure to choose the correct archive file for your operating system and application server type. For example, the file format for Windows and WebLogic is rtd-weblogic-3.2.0.0.0.<build_number>.cpio.
After you extract the files, a directory called OracleBI/RTD is created that contains all the Real-Time Decision Server files. This directory is your RTD_HOME on the UNIX computer.
If you are using WebLogic, the .ear file for the Oracle RTD application must be expanded before it can be deployed on the WebLogic application server. To do this, follow these steps:
Go to RTD_HOME/package and create a directory called expanded to hold the contents of the RTD.ear file. Note that the expanded folder should not contain the actual RTD.ear file, just its contents.
Use the jar utility to extract the RTD_HOME/package/RTD.ear file into the RTD_HOME/package/expanded directory.
To install the Oracle RTD client tools on Windows, unzip the appropriate Oracle RTD archive file into the directory where you want to install the Oracle RTD client tools. Be sure to choose the correct archive file for your operating system and application server type.
After you extract the files, a directory called OracleBI\RTD is created that contains all the Oracle RTD files. This directory is your RTD_HOME on the Windows computer.
In this document, RTD_HOME refers to the directory where the Oracle RTD files were installed. Because a directory structure is created when you extract the Oracle RTD files, the last part of the path will always be OracleBI/RTD. For example, if you extracted the Oracle RTD files to C:\ on Windows, the RTD_HOME is C:\OracleBI\RTD.
Some Oracle RTD management tasks, such as viewing Oracle RTD logs, require you to locate the RTD_RUNTIME_HOME. The location of RTD_RUNTIME_HOME depends on the application server you are using:
If you are using WebSphere, RTD_RUNTIME_HOME is WEBSPHERE_HOME/AppServer/profiles/profile_name/installedApps/cell_name/OracleRTD.ear.
If you are using WebLogic, RTD_RUNTIME_HOME is the directory where the expanded RTD.ear folder is deployed. For example, MW_HOME/user_projects/domains/domain_name/servers/server_name/stage/OracleRTD/.
After you have installed the Oracle RTD files, you must create and initialize the Oracle RTD Database. Oracle RTD requires two database users: an administrative user, and a run-time user. The administrative user needs to be able to create tables and stored procedures, and is only used when the database is being initialized during initial Oracle RTD configuration. The administrative user is never used during Oracle RTD run time. The run-time database user is used by Oracle RTD during run time to access information in the database.
There are two ways to initialize the Oracle RTD Database. You can either run SDDBTool, an Oracle RTD Windows client application, or you can run command line scripts provided by Oracle RTD.
This section contains the following topics:
Section 2.2.2, "Initializing the Oracle RTD Database Using SDDBTool"
Section 2.2.3, "Initializing the Oracle RTD Database Using Command Line Scripts"
For your Oracle RTD Database, you must provide the net service name and a valid user name and password. Refer to your Oracle Database documentation for information about how to set up net services.
On your Oracle RTD database, as the database type is Oracle, the administration user and the run-time user must be the same user. This user needs to have the database roles Connect and Resource. The Resource role can be revoked after the database has been initialized. If you do revoke the Resource role, set the quota for the tablespace of the run-time user to an appropriate level, or to unlimited, depending on your database policies.
You must install Oracle Administrator Client on the computer where you plan to run SDDBTool. See Section 2.2.2, "Initializing the Oracle RTD Database Using SDDBTool" for more information about SDDBTool.
You can initialize the Oracle RTD Database using SDDBTool, an Oracle RTD Windows client application. Before using SDDBTool to initialize the database, perform the following steps:
Ensure that Real-Time Decision Server is not running
Perform the instructions in RTD_HOME\lib\jdbc\readme.txt to install ojdbc6.jar into RTD_HOME\lib\jdbc\.
To initialize the Oracle RTD Database using SDDBTool:
Ensure that your database server is running.
Edit the file RTD_HOME\scripts\sql\Oracle\SDTablespaceMap.txt on the computer where you installed the Oracle RTD client tools. This file allows you to control the allocation of Real-Time Decision Server tables to your Oracle tablespaces. Read the instructions in the file for more information. After you edit the file, save and close the file.
Open SDDBTool by running RTD_HOME\scripts\SDDBTool.cmd on the computer where you installed the Oracle RTD client tools. Then, choose your database type.
Enter your database settings, as follows:
Database Host
Database Port
Database Name
Database Runtime User
Database Administrative User
Database Administrative User Password
Note:
The database administrative user you provide must have rights to create tables and stored procedures on the database. The run-time user is used to access system data at run time.
As the database type is Oracle, the Database Runtime User and the Database Administrative User are the same user.
Click Next.
If your database is a RAC database, select the "RAC database" option.
To enable throughput improvements on Learning Server processing, and if your database supports partitioning, select the ”Enable partitioning” option.
Select Initialize or Upgrade. Initialize creates the data and data source needed to run Oracle RTD. Upgrade will upgrade from a previous version to the current version.
If you do not plan to use the example CrossSell Inline Service, and you are using Oracle Database for your Oracle RTD Database, you can revoke the Resource role from the database user after you complete database initialization. See Section 2.3, "Populating the CrossSell Example Data (Optional)" for more information about the example CrossSell Inline Service.
You can initialize the Oracle RTD Database using command line scripts. Before using the scripts to initialize the database, make sure that Real-Time Decision Server is not running.
Under the directory RTD_HOME\scripts\sql, there is a directory, OracleStatic.
This directory contains a readme.txt file, which contains instructions on how to use the other files provided in the directory.
Follow the instructions in the readme.txt file.
Note:
The OracleStatic directory does not contain an initialize.sql file. The OracleStatic readme.txt file contains instructions on how to generate the sql to initialize the database from the initalize.template file.
If you do not plan to use the example CrossSell Inline Service, and you are using Oracle Database for your Oracle RTD Database, you can revoke the Resource role from the database user after you complete database initialization. See Section 2.3, "Populating the CrossSell Example Data (Optional)" for more information about the example CrossSell Inline Service.
An example Inline Service, called CrossSell, is included with Oracle RTD. To use this sample inline service, you must create and populate three tables, CrossSellCustomers, CrossSellResponses, and CrossSellBestOffer in the Oracle RTD Database. To do this, run the script InitAppDB on the Windows computer where you installed the Oracle RTD client tools.
InitAppDB is located with the example Inline Service. Using a command prompt, run the following script:
RTD_HOME\examples\CrossSell\etc\data\Oracle\initappdb.cmd
This script takes the following parameters:
InitAppDB RTD_HOME db_host db_port db_name db_runtime_user db_admin_user db_admin_password
Table 2-1 describes the parameters for the InitAppDB script.
Table 2-1 Parameters for InitAppDB Script
| Parameter | Description |
|---|---|
|
|
The full path of the directory where the Oracle RTD files are installed. |
|
|
The name of the computer hosting the database server. |
|
|
The database port number. |
|
|
The database name. |
|
|
The user name of the run-time user for the system. |
|
|
The name of a user that has rights to create tables and stored procedures on the database. |
|
|
The password of the administrative user. |
Footnote 1 For Oracle Database, the db_runtime_user and db_admin_user are the same user.
For your Oracle RTD Database, you can revoke the Resource role from the database user after you run the InitAppDB script.
Another example Inline Service, called DC_Demo, is included with Oracle RTD, to demonstrate dynamic choices and external rules. To use this sample inline service, you must first create and populate a sample database table WebOffers.
To do this, run the script InitAppDB on the Windows computer where you installed the Oracle RTD client tools.
InitAppDB is located with the example Inline Service. Using a command prompt, run the following script:
RTD_HOME\examples\DC_Demo\etc\data\Oracle\initappdb.cmd
This script takes the following parameters:
InitAppDB RTD_HOME db_host db_port db_name db_runtime_user db_admin_user db_admin_password
See Table 2-1 for the parameters for the InitAppDB script.
If you want to use SSL for client connections to Oracle RTD (recommended), and if you want to use the Oracle RTD keystore and truststore, you must first change the passwords for the keystore and truststore. To do this, follow these steps:
Run the following keytool command to change the keystore password:
JAVA_HOME/bin/keytool –storepasswd -new new_password –keystore RTD_HOME/etc/ssl/sdserver.keystore
Make sure to replace RTD_HOME with the actual Oracle RTD installation path. For new_password, provide the new password you want to use for the Oracle RTD keystore.
When the script prompts for the existing keystore password, enter tc-ssl.
Note:
If you cut and paste the keytool command syntax from this document, the hyphen character (-) may be copied as a long hyphen rather than a short hyphen. If you receive an error, try re-typing the hyphen characters in the command.
Run the following keytool command to change the truststore password:
JAVA_HOME/bin/keytool –storepasswd –new new_password –keystore RTD_HOME/etc/ssl/sdtrust.store
Make sure to replace RTD_HOME with the actual Oracle RTD installation path. For new_password, provide the new password you want to use for the Oracle RTD truststore.
When the script prompts for the existing truststore password, enter tc-ssl.
Run the following keytool command to change the server private key password:
JAVA_HOME/bin/keytool -keypasswd -alias tc-ssl -keypass tc-ssl -new new_password -keystore RTD_HOME/etc/ssl/sdserver.keystore
Make sure to replace RTD_HOME with the actual Oracle RTD installation path. For new_password, provide the password you want to use for the server private key.
When the script prompts for the keystore password, enter the password you provided for the keystore in Step 1.
For greater security, when setting up SSL, you should disable the regular HTTP port to ensure that all client connections are routed through the SSL port.
Note:
Before you disable the regular HTTP port, make sure that SSL is working and that you can connect to Oracle RTD using the HTTPS protocol, as in https://server:ssl_port/ui/.
When Oracle RTD is deployed on an application server, you may need to perform the following additional steps when setting up an SSL-only configuration:
Run the following keytool command to import the Oracle RTD certificate into the cacerts for your application server:
keytool -import -file RTD_HOME/etc/ssl/sdserver.cer -keystore cacerts
The file keytool.exe is located in the standard jdk/bin directory for the JDK used by the application server.
When prompted, enter the keystore password for the application server's cacerts file.
The default location of cacerts is in the standard jdk/jre/lib/security directory for the JDK used by the application server.
When prompted to trust the certificate, enter yes.
This procedure is useful for test environments. For production systems, you should use your own certificate rather than the test certificate that ships with Oracle RTD.