5
Installing OP

Before installing Oracle9iAS Personalization (OP), install Oracle9i database and Oracle9iAS (Chapter 3) and Oracle Workflow 2.6.1 (Chapter 4).

Then, follow the steps described in this chapter to install OP.

The installation of OP is divided into two top-level steps, as follows:

The first step of the installation is generally performed by the database administrator on the back-end Oracle9i database. This part entails creating database accounts and schemas, loading stored procedures into the database, and installing necessary software and libraries. The components that are installed in the first step are the Mining Object Repository (MOR), Mining Table Repository (MTR), and Recommendation Engine (RE). Each of these three components requires separate schemas and tablespaces; for the MOR there is also a temporary tablespace dedicated to running data mining model builds.
The second step of the installation is generally performed by the application server administrator on the system where the Oracle9i Application Server is installed. This step installs the Java libraries for runtime support of the Recommendation Engine API and the Recommendation Engine Batch API, along with REAPI demo. (The REAPI demo is a servlet that works with the demo movie data that can optionally be loaded into the MTR. The servlet can be used to verify that all the OP components are configured and working.)

Note that each step has manual steps that you must perform after the OUI installation completes.

Installing OP Components

OP is installed on two different systems.

The following components, referred to as the "OP Application Server components," are installed on the system where Oracle9iAS is installed:

Recommendation Engine API
Recommendation Engine Batch API
redemo servlet

All other OP components, referred to as the "OP database components" (including the Administrative UI and OP documentation), are installed on the system where Oracle9i is installed.

Installing OP Database Components

Follow these steps to install the OP database components:

Log in to your Oracle DBA's operating system account on the system where Oracle9i is installed.
If any OP components are already installed on this system, deinstall them (see "Deinstalling OP", below).
In a shell, issue the following command to start Oracle Universal Installer (OUI):
```
<cdrom>/Disk1/runInstaller
```
where <cdrom> points to the directory where your cd is mounted. Be sure your DISPLAY environment variable is set appropriately.
Welcome: The Welcome screen appears. Click Next.
File Locations: Displays source and destination. Confirm that the correct source and destination paths are specified. The destination should be the Oracle Home directory. Then click Next.
Available Products: Select Oracle9iAS Personalization Database Components. Click Next.
Installation Types: Complete or Custom. Choose Custom only if you want to install certain components, for example, if you want to install everything except the MTR on one system and then install the MTR on a different system. Click Next.
Available Product Components: This page lists the components; check the ones you want to install. If you are doing a complete installation, everything is checked by default. Click Next.
Database Information: Provide the following information for your Oracle database, as established while installing the database. The fields may be filled in with default values. Confirm that these values are appropriate for your database or enter new values.
- ORACLE_SID:
- TNSName:
- INET Hostname: This is the hostname or IP address of the system containing the database.
- Port:
Click Next.
DB System Account Information: Provide the following and then click Next:
- DBA Name: system (This is the default; provide a user name for a user with DBA privileges.)
- DBA Password: manager (This is the default; provide a password for a user with DBA privileges.)
- Workflow Admin Name: owf_mgr (This is the default; provide the Workflow administrator name created during Workflow installation.)
- Workflow Admin Password: owf_mgr (This is the default; provide the Workflow administrator password created during Workflow installation.)
- OPWFBase Password: The OPWFBase user is created during MOR configuration. Create the OPWFBase password here.
- SYS Password: Enter the password for SYS user (provided after database installation).
OP Tablespace Data File Directory: Specify the path and directory for OP tablespace data files. The default path is displayed as:
```
$ORACLE_HOME/oradata/<ORACLE_SID>
```
By clicking the Browse button, you can browse and assign another path for data file directory. If you accept the default path, confirm that this path exists. If it does not exist, OUI prints a message saying that the path does not exist, and your installation will fail. Click Next.
MOR Configuration Information: Provide the following and then click Next:
- MOR User Name: OPMOR (default)
- MOR Password: MORPW (default; change this password here)
- MOR Tablespace Name: OPMOR (default)
- MOR Data File Size: 512M (default)
  
  Important: Sizes must be specified in megabytes. If, for example, you want 1 gigabyte, you must convert it to megabytes and enter 1024M. (For 2 gigabytes, however, you cannot specify 2048M, because 2047M is Oracle's limit.)
- MOR Temp Tablespace Name: OPMOR_TEMP_TS (default)
- MOR Temp Data File Size: 1024M (default)
RE Configuration Information: Provide the following and then click Next.
- RE User Name: RE (default)
- RE Password: REPW (default; change this password here)
- RE Tablespace Name: RE (default)
- RE Data File Size: 512M (default)
MTR Configuration Information: Provide the following and then click Next:
- MTR User Name: DEMO_MTR (default)
- MTR User Password: MTRPW (default; change this password here)
- MTR Tablespace Name: DEMO_MTR (default)
- MTR Data File Size: 512M (default)
Populated MTR Schema: Choose whether you want to install an MTR schema populated with demo data. The default selection is Yes, which results in an MTR schema populated with the demo data. Select No if you want to use your own data (you will get the same schema structure, but without data). (See Chapter 8 and Chapter 9.) Click Next.
Summary: Lists elements to be installed. Click Install.
Install: OUI starts installing. (If this is the first installation of OP, you will see several messages such as "RE doesn't exist" -- this is normal. OP creates all necessary files and tables.)
Configuration Tools: There is a tool for each component being configured; use the vertical scroll bar on the right to see the names of all the tools:
- RE Create Wizard: Once this tool completes successfully, it creates an RE user and RE schema on the specified database.
- MTRDemo Create Wizard: When it completes successfully, it creates an MTR user and MTR schema populated with demo data on the specified database.
- MOR Create Wizard: When it completes successfully, it creates an MOR user and an MOR schema and OPWFBASE user and OPWFBASE schema on the specified database.
End of Installation: Click Exit.
You may have to stop and restart the database, especially if you are reinstalling OP.

Note:
Whenever you stop and restart the database, you should check to see if Listener is still running. If Listener is not running, you should restart it.

Installing OP Application Server Components

Follow these steps to install the OP Application Server components:

Log in to your Oracle DBA's operating system account on the system where Oracle9iAS is installed.
If any OP components are already installed on this system, deinstall them (see "Deinstalling OP", below).
In a shell, issue the following command to start Oracle Universal Installer (OUI):
```
<cdrom>/Disk1/runInstaller
```
where <cdrom> points to the directory where your cd is mounted. Be sure your DISPLAY environment variable is set appropriately.
Welcome: The Welcome screen appears. Click Next.
File Locations: Displays source and destination. Confirm that the correct source and destination paths are specified. The destination should be the Oracle Home directory. Then click Next.
Available Products: Select Oracle9iAS Personalization iAS Components. Click Next.
Installation Types: Complete or Custom. We recommend that you select Complete. Click Next.
Available Product Components: This page lists the components; check the ones you want to install. REAPI Demo Test Servlet should be checked. If you are doing a complete installation, everything is checked by default. Click Next.
Summary: Lists elements to be installed. Click Install.
Install: OUI starts installing. OP creates all necessary files and tables.
End of Installation: Click Exit.

Manual Steps

After completing an OP installation and configuration that includes an MOR, there are a few things you need to do manually on both systems where you've installed OP.

Manual Steps for Oracle9i System

Perform the following steps on the system where Oracle9i is installed.

Update jserv.conf file: Go to

$ORACLE_HOME/Apache/Jserv/etc/

and append the file

$ORACLE_HOME/dmt/conf/jservConf.add

to jserv.conf file.

Update jserv.properties: Append the file
```
$ORACLE_HOME/dmt/conf/jservProperties.add
```
to jserv.properties file.
In thejserv.properties file, update the DISPLAY parameter to point to the display at the host that is running X Windows by replacing the name of the X Windows server host name in wrapper.env=DISPLAY=<hostname>:0.0

Verify that there is only one entry configuring wrapper.env=DISPLAY=<hostname>. If you have more than one entry, comment the others out.

The system that is running the Xdisplay must allow the use of its display by the java awt toolkit with the command

xhost + <system_where_Jserv_runs>

Note: You need X Windows to render images related to the OP Administrative UI. Ideally, X Windows runs on the machine on which you have installed OP. If this is inconvenient or impractical, X Windows must run on a machine that is connected to the machine on which you installed OP.
Stop and restart the database.

Note:
Whenever you stop and restart the database, you should check to see if Listener is still running. If Listener is not running, you should restart it.
Log in as root and restart the Oracle HTTP Server server with these commands:
- Stop Oracle HTTP Server:
```
$ORACLE_HOME/Apache/Apache/bin/apachectl stop
```
- Wait 15 seconds.
- Start Oracle HTTP Server in ssl mode:
```
$ORACLE_HOME/Apache/Apache/bin/apachectl startssl
```
  If the command succeeds, you see the following line:
```
./apachectl start ssl:http started
```
- Exit root.
To start Oracle Workflow engine, as Oracle DBA, use the following command:
```
/usr/bin/csh $ORACLE_HOME/dmt/install/WF/opwfengine.csh start <MOR_schema>
```
You will be prompted to enter the following:
- Workflow user name (default was owf_mgr; use the user name you provided in step 10 earlier in this chapter)
- Workflow password (default was owf_mgr; use the password you provided in step 10 earlier in this chapter)
- Database TNS name

Manual Steps for Oracle9iAS System

Perform the following steps on the system where Oracle9iAS is installed.

Log in to your Oracle DBA's operating system account on the system where Oracle9iAS is installed.
Update jserv.conf file on the system where Oracle9iAS is installed: Go to
```
$ORACLE_HOME/Apache/Jserv/etc/
```
and append the file
```
$ORACLE_HOME/dmt/conf/oprocmgr/reapiJservConf.add
```
to jserv.conf file.
Log in as root and restart the Oracle HTTP Server with these commands:
- Stop Oracle HTTP Server:
```
$ORACLE_HOME/Apache/Apache/bin/apachectl stop
```
- Wait 15 seconds.
- Start Oracle HTTP Server in ssl mode:
```
$ORACLE_HOME/Apache/Apache/bin/apachectl startssl
```
  If the command succeeds, you see the following:
```
./apachectl start ssl:http started
```
- Exit root.

Test the OP Installation

To confirm that OP is properly installed, do the following:

Verify that you can run the OP Administrative UI by pointing your browser to the URL http://<hostname>/OP/Admin, where <hostname> is the name of the server on which Oracle9i is installed.
Verify that you can run the REAPI demo and use it to get a recommendation, as described in Getting Started withOracle9iAS Personalization. To start REAPI demo, point your browser to the URL http://<hostname>/redemo, where <hostname> is the name of the server on which Oracle9iAS is installed.

Deinstalling OP

If there is a copy of OP installed on either of your systems, deinstall it from both systems before installing a new version.

Deinstalling Oracle9i OP Components

Follow these steps to deinstall the OP components that are installed on the system where Oracle9i is installed:

Stop Oracle Workflow with the command

/usr/bin/csh $ORACLE_HOME/dmt/install/WF/opwfengine.csh stop  <MOR_schema>

Make sure no OP users are connected to the database. To find out whether there are any OP user sessions, connect to the database as SYSTEM user and execute the following SQL statement:
```
SQL> select username from v$session where status='ACTIVE' or status= 
'INACTIVE';
```
and close the connections or kill the existing sessions for OP users.
All OP processes are now stopped or removed, and you are ready to deinstall OP. Log in to your Oracle DBA system account.
Set the DISPLAY environment variable if necessary.
Run the following command to start Oracle Universal Installer:
```
<cdrom>/Disk1/runInstaller
```
Welcome: Click Deinstall Products.
Inventory: This window displays the installed products in the available Oracle home.
Select Oracle9iAS Personalization Database Components 9.0.0.1.0, and click Remove. A confirmation window appears; click Yes.
Remove: The Remove window appears; it displays a progress bar.
You may want to remove data files corresponding to MOR and RE tablespaces for the deinstalled OP. MTR schema and associated data files that are not removed when you deinstall. If you want to install an MTR with the same user name, the current MTR will be dropped and replaced with the new one.
Remove the $ORACLE_HOME/dmt directory.

Deinstalling Oracle9iAS OP Components