Skip Headers
Oracle® On Track Communication Installation Guide
Release 1 (1.0)

Part Number E20956-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Preparing for Installation

This chapter provides the steps to prepare for the installation of Oracle On Track. Ensure that your system environment meets the general installation requirements before installing Oracle On Track.

The following sections describe the installation prerequisites:

System Requirements

Before performing any installation, you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing. The system requirements for running the installation program are listed in Table 2-1.

Table 2-1 System Requirements

Category Requirement

Platform configuration

A supported configuration of hardware, operating system, JDK, and database specific to the product you are installing.

For information about other prerequisites and recommendations, see the Certifications tab at

http://support.oracle.com

Character Set AL32UTF8

The database must be in AL32UTF8 set.

Color bit depth display and size

For Graphical User Interface (GUI) mode installation, 8-bit color depth (256 colors) is required.

For console-mode and silent-mode installation, there is no color bit depth requirement.

JDK

The Oracle WebLogic Server installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with file names ending in .bin). For other UNIX platforms, the installation program does not install a JDK. File names for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition. It is important that you use JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.

Oracle Outside In

Oracle Outside In requires access to True Type fonts that match the fonts in uploaded documents, in order to generate thumbnail and page images. If you don't have appropriate fonts, then characters appear as asterisks (*). As part of install setup, an administrator should make sure the system has appropriate fonts installed, and then set the font path from the Oracle On Track Administrator Console.

Oracle Outside In do not recursively descend the font directory to look for its fonts. So if you have your fonts in /usr/share/fonts/ja/TrueType and /usr/share/fonts/zh_TW/TrueType and /usr/share/fonts/liberation, then your font directory should be set to /usr/share/fonts/ja/TrueType:/usr/share/fonts/zh_TW/TrueType:/usr/share/fonts/liberation.

Typically for SLES 11, run the following command:

FONTS:/usr/share/fonts/Type1

For Solaris:

FONTS:/usr/openwin/lib/X11/fonts/TrueType

For Red Hat Enterprise Linux 5

FONTS :/usr/share/fonts/liberation

SuSE 11

lSuSE 11 32 bit requires ibstdc++33 package version 3.3.3-7.1. SuSE 11 64 bit requires libstdc++33 and libstdc++33-32bit versions 3.3.3-7.1.


SSL Configuration

Secure Sockets Layer (SSL) secures communication by providing message encryption, integrity, and authentication.

When a client initiates an SSL session, the server typically sends its certificate to the client. The client verifies that the server is authentic by validating the certificate chain in the server certificate. The server certificate is guaranteed by the certificate authority (CA) who signed the server certificate.

Even though a valid certificate is always preferred, a test or self-signed certificate can be used when the user approves the hosting site. The user is warned if the site's certificate is not valid before the approval.

For non-SSL configured servers, the user is able to approve for the current session but is not be allowed to permanently store the trust relationship. In this way, the security is not compromised as DNS spoofing or cache poisoning can be used to turn any malicious site into approved but unprotected site.

Installation Steps

The installation of Oracle On Track consists of the following steps:

Installing Oracle Database

The configuration of Oracle On Track requires the availability of a supported database. The database must be up and a database instance must be running. It does not have to be on the same machine where you are installing Oracle On TRack.

Oracle On Track requires the availability of Oracle Database Enterprise Edition with Oracle Text and Secure Files.

For the latest information about supported databases, see the Certification Tab at

http://support.oracle.com

The database must also be compatible with RCU, which creates the schemas for the Oracle On Track.

Note:

RCU is available only for a Linux or Windows operating system. You can use either the Linux-based RCU or Windows-based RCU to create schemas in any supported database.

For more information about Oracle Database, see the Oracle Database Documentation page on Oracle Technology Network at

http://www.oracle.com/technetwork/database/enterprise-edition/documentation/database-093888.html

Installing Oracle Fusion Middleware and Oracle WebLogic Server

Oracle On Track requires an Oracle Fusion Middleware home with Oracle WebLogic Server on your system. Oracle On Track supports Oracle Web Logic Server 10.3.3 and higher versions.

A Middleware home is a container for the Oracle WebLogic Server home, and, optionally, one Oracle Common home and one or more Oracle homes, with a directory structure as follows:

/middleware_home
     coherence_3.6
     jdk160_21
     jrockit_160_20_1.1.0-2119
     logs
     modules
     wlserver_10.3
     oracle_common
     utils
     ECM_Oracle_ONTRACK1
     user_projects

The default Oracle Middleware home is /Oracle/Middleware on Linux and UNIX-based operating system or c:\Oracle\Middleware on a Windows operating system. MW_HOME represents the location of a Middleware home in path names. More information on the Oracle Web Logic Server is available at

http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html

For more information about the structure and contents of a Middleware home, see Oracle Fusion Middleware Administrator's Guide.

Choosing a Product Installation Directory

The product installation directory, where you install Oracle On Track, contains all the software components that you choose to install on your computer, including program files and examples.

For example, the default installation directory for Oracle WebLogic Server is $MW_HOME\wlserver<version>.

The installation program installs the software components in a product installation directory represented by the MW_HOME variable (the default is Oracle\Middleware).

Installing Oracle On Track

You can run the installation program in the following modes:

  • Graphical Mode: Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems. For graphical installation procedures, see Installing in Graphical Mode.

  • Silent Mode: Silent-mode installation is a non-interactive method of installing your software. You use .rsp response file to specify the installation options. You can run silent-mode installation from either a script or from the command line. Silent-mode installation allows you to define the installation configuration only once, and then use that configuration to duplicate the installation on many machines. For more information about silent mode installation, see Installing in Silent Mode.

Installing Oracle Repository Creation Utility

You need to install and run the Oracle Repository Creation Utility (RCU) to create a database schema for each Oracle On Track application that you plan to configure.

Starting RCU

RCU is available in your shiphome as rcuontrack_home.zip for Linux and rcuontracknt_home.zip for Windows. Unzip the file and extract the contents to a directory of your choice. Start RCU from the bin directory as follows:

On Linux operating systems

./rcu

On Windows operating systems

rcu.bat

Note:

UNIX-based operating systems do not support RCU.

Creating Schemas

After starting RCU, follow the instructions in Table 2-2 to create schemas.

Table 2-2 How to Create Schemas

No. RCU Screen Action

1

Welcome Screen

None

2

Create Repository Screen

Select Create.

3

Database Connection Details Screen

Specify the connection details for your database.

4

Select Components Screen (for Create Operation)

You can either select an existing prefix from the list or create a new prefix.

If you are creating a prefix, then specify a schema prefix. Select the following components:

  • Oracle AS Repository Components, AS Common Schemas, Metadata Services

  • Oracle On Track, On Track Schema

You must remember the prefix and schema names for the components you are installing. Oracle recommends that you write these values down.

5

Schema Passwords Screen

Specify the passwords for your schema owners.

You must remember the passwords you enter on this screen; you require this information during the configuration phase of Oracle On Track installation. Oracle recommends that you write these values down.

6

Map Tablespaces Screen

Configure the desired tablespace mapping for the schemas you want to create.

7

Summary Screen

Review the information on this screen and click Create to begin schema creation.

8

Completion Summary Screen (for Create Operation)

Oracle recommends that you note the location of the log files. Click Close to dismiss the screen.


For information about installing and running RCU, see Oracle Fusion Middleware Repository Creation Utility User's Guide.

Creating or Extending a Domain

You must create an Oracle WebLogic Server domain if it does not already exist. If you already have a domain, you must extend the domain before it can run the Oracle On Track application. For more information on this, see Creating or Extending a Domain.

Temporary Disk Space Requirements

The installation program uses a temporary directory into which it extracts the files that are needed to install the software on the target system.

Depending on the platform that you are using, the requirement for temporary disk space may vary from 50 to 100 MB. The files in the temporary directory require approximately 2.5 times the space that is ultimately required for the installation.

During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program and a non-compressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory after the installation process.