3 Installation Notes

This chapter presents information that will be helpful to anyone installing Oracle Application Server Personalization (OracleAS Personalization).

The installation of OracleAS Personalization is integrated with Oracle Application Server standards.

The installation is done in two parts. The first part is done by an Oracle Application Server administrator and the second part is done by the database administrator.

3.1 Part 1 Installation

Note the following:

Before installing OracleAS Personalization, install the Oracle Application Server Infrastructure database.
To install OracleAS Personalization, you must select Business Intelligence and Forms as the type of installation.

The first part of the installation happens automatically as part of installing Oracle Application Server Business Intelligence on your system, which copies the software onto the Oracle Application Server ORACLE_HOME/mp directory and configures the OracleAS Personalization Admin UI servlet in Oracle Application Server Containers for J2EE (OC4J).

When the Oracle Application Server installation completes, the OracleAS Personalization Admin UI will be available at this location:

https://<hostname>:<SSLPORT>/OP/Admin

(You will find the actual names in $ORACLE_Home/ Apache/Apache/setupinfo.txt. Two paths are shown; use the https: path.)

When the Oracle Application Server installation completes, you will be able to view the OracleAS Personalization login screen, but you cannot log in until you have completed the second part of the installation. (If you try to log in before completing the second part, login fails with "Authentication Errors" because the MOR schema required for authentication is not available.

3.2 Part 2 Installation

In the second part of the installation, your DBA configures the required schemas in the Oracle database and Oracle Application Server Containers for J2EE (OC4J) is reloaded to read the new configuration settings. See the Oracle Application Server Containers for J2EE User's Guide for information on reloading OC4J.

The schemas are configured using the OracleAS Personalization Schema Creation Wizard, which is a Java application that creates these schemas over the network to your Oracle database.

3.2.1 Before Running the OracleAS Personalization Schema Creation Wizard

The database administrator will need to allow remote SYS access for the duration of the schema creation process.

Documentation on updating the database init.ora parameters can be found in the Database Administrator Authentication section of the Database Administrator's Guide (http://download.oracle.com/otndoc/oracle9i/901_doc/server.901/a90117/dba.htm#10431). <<<find the lastest equivalent link>>>

Remote SYS access can be tested using the following command on the system where you installed Oracle Application Server Business Intelligence:

sqlplus "SYS/<password@GlobalDatabaseName> AS SYSDBA"

where password is the SYS password on the remote database and GlobalDatabaseName is the database alias in the tnsnames.ora file.

The DBA will need to collect the following information for the Mining Object Repository (MOR), the Recommendation Engine Repository (RE), and the Mining Table Repository (MTR) before starting the Java application to configure the required database schemas.

(Note the following: When you specify the data file names for the tablespaces, the names must be the fully qualified names for the data files on the local file system where the Oracle database is running. You must replace the <full path> prompt with the directory name for the data file.)

MOR (Mining Object Repository)

SYS password for the database
JDBC connect information
- Host
- Port
- SID
Schema name for the MOR (default: OPMOR)
Password for the MOR
Fully qualified file name of the tablespace data file for the MOR
Fully qualified file name of the tempspace data file for the MOR
Email address for replies from notification messages

RE (Recommendation Engine Repository)

SYS password for the database
JDBC connect information
1. Host
2. Port
3. SID
Schema Name for the RE (default: RE)
Password for the RE
Fully qualified file name of the tablespace data file for the RE

MTR (Mining Table Repository)

SYS password for the database
JDBC connect information
- Host
- Port
- SID
Schema name for the MTR (default: MTR); importing the movie data forces the name DEMO_MTR
Password for the MTR
Fully qualified file name of the tablespace data file for the MTR

3.2.2 Running the OracleAS Personalization Creation Wizard

After collecting the required information, log in to the Oracle Application Server system where you installed Oracle Application Server Business Intelligence and run the following command:

(UNIX)
prompt> $ORACLE_HOME/mp/admin/opconfig.sh

(Windows)
prompt> cd %ORACLE_HOME%\mp\admin
prompt> opconfig.bat

3.2.3 After Running OracleAS Personalization Schema Creation Wizard

Once the schemas have been successfully created, remote SYS access can be safely disabled. However, if there is a need to configure more REs, remote SYS will need to be reestablished.

Use the Oracle Enterprise Manager 10g to restart OC4J, Business Intelligence, and Forms. The OracleAS Personalization Admin UI will not allow you to log in until you have restarted OC4J.

3.3 Data Collection Form

This section displays the data that will be collected while you are running the OracleAS Personalization Schema Creation Wizard.

Table 3-1 Data to Be Collected for the MOR

Item	Collected Data	Default
SYS password	******	change_on_install
JDBC connect info	Host Port SID	None None None
Schema name		OPMOR
Password		MORPW
Fully qualified file names of the schema tablespace data file
Fully qualified file names of the schema tempspace data file
Email address for replies from notification messages		Your.Email@domain.com

Table 3-2 Data to Be Collected for the RE

Item	Collected Data	Default
SYS password	******	change_on_install
JDBC connect info	Host Port SID	None
Schema name for the RE		RE
Password for the RE		REPW
Fully qualified file name of the schema tablespace data time		None

Table 3-3 Data to Be Collected for the MTR

Item	Collected Data	Default
SYS password	******	change_on_install
JDBC connect info	Host Port SID	None
Schema name for the MTR; importing the movie data forces the name DEMO_MTR		DEMO_MTR or MTR
Password for the MTR		MTRPW
Fully qualified file name of the schema tablespace data file		None