3
Installation Notes

This chapter presents information that will be helpful to anyone installing Oracle9iAS Personalization.

Background

The installation of Oracle9iAS Personalization has been redesigned to integrate into the new Oracle9iAS standards.

The installation is done in two parts. The first part is done by an Oracle9i Application Server administrator; the second part is to be done by the database administrator.

Part 1 Installation

The first part happens automatically as part of the installation of iAS2 Business Intelligence or Unified Messaging on your system, which copies the software onto Oracle9iAS ORACLE_HOME/dmt directory and configures the OP Admin UI servlet in OC4J. The Admin UI will be available at https://localhost:4443/OP/Admin once the iAS installation completes. You will be able to view the login screen, but login will fail with "Authentication Errors" until the required database schemas are configured by your DBA in the second part of the installation.

Note the following:

• Before installing OP, you must first install the Oracle9iAS Infrastructure database. If you are installing the Oracle9iAS Infrastructure database, you can check the default values during the installation.

• To install Oracle Personalization, you must select Business Inteligence and Forms as the type of iAS installion.

Part 2 Installation

The second part of the installation configures the required schemas in the Oracle9i database. The schemas are configured using the Oracle Personalization Configuration Wizard -- a Java application -- that creates these schemas over the network to your Oracle9i database.

Before Running the Personalization Schema Creation Wizard

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

Documentation on how to update the database init.ora parameters can be found in the Database Administrator Authentication section of the Oracle9i Database Administrator's Guide, Release 1 (9.0.1), part number A90117-01 (http://download.oracle.com/otndoc/oracle9i/901_doc/server.901/a90117/dba.htm#10431).

Remote SYS access can be tested using the following command on the system where you installed iAS 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 determine the following 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 Oracle9i database is running. You must replace the <full path> prompt with the directory name for the data file.

MOR (Mining Object Repository)

1. SYS password for the database

2. JDBC connect information
   1. Host

   2. Port

   3. SID

3. Schema name for the MOR (default: OPMOR)

4. Password for the MOR

5. Fully qualified file name of the tablespace data file for the MOR

6. Fully qualified file name of the tempspace data file for the MOR

7. Email address for replies from notification messages

RE (Recommendation Engine)

1. SYS password for the database

2. JDBC connect information
   1. Host

   2. Port

   3. SID

3. Schema Name for the RE (default: RE)

4. Password for the RE

5. Fully qualified file name of the tablespace data file for the RE

MTR (Mining Table Repository)

1. SYS password for the database

2. JDBC connect information
   1. Host

   2. Port

   3. SID

3. Schema name for the MTR (default: MTR); importing the movie data forces the name DEMO_MTR

4. Password for the MTR

5. Fully qualified file name of the tablespace data file for the MTR

Running the Personalization Configuration Wizard

After collecting the required information, log in to the iAS system where you installed the Oracle9iAS Business Intelligence as the oracle account and run the following command:

     (UNIX) $ORACLE_HOME/dmt/admin/opconfig.sh

(Windows) %ORACLE_HOME%/dmt/admin/opconfig.bat

After Running the Wizard

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

Data Collection Form

MOR

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

RE

	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 file		None

MTR

	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