Oracle Ultra Search Online Documentation
Release 9.2


Home	Book List	Contents	Master Index	Feedback

Installing the Ultra Search Server Component on an Existing Database

	Related Topics
About the Ultra Search Administration Tool Installing Ultra Search Server Component Installing the Ultra Search Middle Tier Component on Web Server Hosts Installing the Ultra Search Server Tier Component on Remote Crawler Hosts

Ultra Search can be installed on an Oracle database that is currently in use.

Database Requirements

The Java development kit (JDK) must be version 1.2.207 or higher.
Oracle database must be version 8.1.7 or higher.
The initialization file must have JOB_QUEUE_PROCESSES set to greater than two.
Oracle Context must be installed in the database.
Note: To run the crawler, Ultra Search requires a Java 1.2 compliant runtime environment (JDK) to be installed on the database machine. For version 8.1.7, the path to this JDK must be specified. For version 9i or higher, JDK 1.2.2 07 should already be installed with the Oracle HTTP server.

Installation

Installing Ultra Search on an existing database includes transferring files, creating Ultra Search super user wksys, loading Ultra Search PL/SQL database packages, and associating Oracle9i Application Server (9iAS) with Ultra Search. Unlike the infrastructure database installation, Ultra Search packages are loaded from the middle tier installation. By choosing to install Oracle Portal to your database, Oracle Portal Configuration Assistant (OPCA) loads the Ultra Search packages onto the database host you choose. You then manually transfer necessary files to the database tier's file system.
For more information on Oracle Portal and how to use OPCA, see http://portalstudio.oracle.com/.

1. Create user wksys, load Ultra Search PL/SQL packages, and associate Ultra Search with 9iAS

Ultra Search PL/SQL database packages are loaded during the middle tier (9iAS) installation. During this installation, after the Oracle Universal Installer copies the necessary files to the middle tier host, Oracle Portal Configuration Assistant (OPCA) associates Ultra Search with 9iAS. After specifying the database tier host, Oracle SID, and port, Ultra Search packages area loaded by OPCA to the database on the database tier host.
If OPCA detects that the Ultra Search super user wksys already exists, then it asks the user to choose from the following three options:

Continue: This drops the existing wksys user, creates a new wksys user, and reloads the Ultra Search packages. All data collected by Ultra Search is deleted.

Migrate: This asks the user to follow the instructions on the Ultra Search migration document here for manual migration.

Abort: This stops OPCA from loading Ultra Search PL/SQL database packages into the existing database.

Note: The default password for wksys is wksys. You should immediately change the password to avoid any security issues.
OPCA then configures 9iAS to work with Ultra Search. Configuration involves the following files: mod_oc4j.conf, server.xml, and ultrasearch.properties. For more details, see Installing the Ultra Search Middle Tier Component.

2. Transfer files and configure the database.
Ultra Search requires that certain files exist on the database tier's file system. Because the database tier might exist in a physically unreachable place, and because neither the Oracle Universal Installer nor OPCA have access to the remote database tier's file system, you must manually copy the necessary files. In the ORACLE_HOME/ultrasearch/setup/ directory, there are several files including setupDB.jar, setupDB.bat,setupDB.csh, and setupDB.sh. Copy these files to the ORACLE_HOME of your remote database tier.
3. Set the files to the correct location by running the following scripts for your operating system.
For Windows NT:

Edit setupDB.bat using any text editor. After the line "set ORACLE_HOME=" put the directory name where you installed the Oracle database. If you are using Oracle 8.1.7, then download and install the latest JDK, and put the directory name where you installed the JDK after "set JDK_HOME=". If you are using Oracle 9i or higher, you do not need to change anything.

Save the change and run setupDB.bat by double clicking setupDB.bat or by running setupDB in the command prompt.

For Solaris:

Run setupDB.sh under the Bourne shell prompt. The system sets the current directory as ORACLE_HOME and asks for the path to your JDK_HOME. If the default path to the jar executable or Java executable is not correct, then the system asks for the path to JDK. If you do not have JDK installed, then download the latest JDK and run setupDB.sh again. Note: To run this script, the executable bit of setupDB.sh should be turned on.


Home	Book List	Contents	Master Index	Feedback