1 Reviewing Information About This Guide

This guide describes the installation procedure for the following installation types:

Oracle HTML DB Installation Type

This installation type includes the following products:

Oracle HTTP Server

Oracle HTML DB

Oracle Database 10g Products Installation Type

This installation type includes the following products:

Oracle JDBC Development Drivers

Oracle SQLJ

Oracle Database Examples

Oracle Text Supplied Knowledge Bases

Oracle Workflow Server

Oracle Ultra Search

JPublisher

Oracle Database 10g Companion Products Installation Type

This installation type includes the following products:

Oracle Workflow middle-tier components

Oracle HTTP Server

Note:

In this guide, the term Companion CD products has been used to refer to the products available on the Oracle Database Companion CD installation media. In contrast, the term Oracle Database 10gCompanion Products has been used to refer to the products available in the Oracle Database 10g Companion Products installation type.

The formal name of the operating system, Solaris Operating System (SPARC 64-Bit), has been shortened to Solaris in this guide.

Information Not Provided in this Guide

This guide does not provide information about the following:

Detailed instructions for verifying that the installation requirements are met

Postinstallation tasks to be performed before using the Companion CD products

Instructions for using the Companion CD products

Where to Get Additional Installation Information

For more information about installing Oracle Database 10g Companion CD products, including information about the tasks not described in this guide, refer to Oracle Database Companion CD Installation Guide for Solaris Operating System (SPARC 64-Bit).

This guide is available on the installation media. To access it, use a Web browser to open the welcome.htm file, which is in the companion directory on the installation media. On the Welcome page, select the Documentation tab.

2 Requirements for Installing Companion CD Products

The following sections describe the requirements for installing Companion CD products:

2.2 General Requirements for Installing Oracle Software

The following are the general requirements for installing Oracle software:

Logging in to the system as the root user

Unless you intend to complete a silent installation, you must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.

Setting up the required operating system group

You must create the Oracle Inventory group the first time you install Oracle software on the system, if it does not already exist. This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system. Typically, the name chosen for this group is oinstall.

Setting up the required Oracle software owner user

The Oracle software owner user owns all of the software installed during a given installation. This user must have the Oracle Inventory group as its primary group. You must create an Oracle software owner user if any of the following conditions is true:

An Oracle software owner user does not exist. This condition may be true if this is the first installation of Oracle software on the system.

An Oracle software owner user exists, but you want to use a different operating system user.

If the Oracle software owner user exists, but its primary group is not the Oracle Inventory group, then you should modify it.

Note:

In this document, the Oracle software owner user is referred to as oracle.

Setting up the Oracle base directory

The Oracle base directory acts as a top-level directory for Oracle software installations. The Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:

/mount_point/app/oracle_sw_owner

In this example:

mount_point is the full path of the mount point directory for the file system that will contain the Oracle software

oracle_sw_owner is a directory that is given the same name as the name of the operating system user that you intend to use to perform the installation

Setting up the Oracle Inventory directory

The first time you install Oracle software on a computer, Oracle Universal Installer prompts you to specify the path to the Oracle Inventory directory. For all subsequent installations of Oracle software, the same Oracle Inventory directory is used.

Setting up the Oracle home

You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. Every time you run Oracle Universal Installer, it prompts you to specify the path and a name for this directory.

Configuring the oracle user's environment

To configure the oracle user's environment, you must:

Set the default file mode creation mask (umask) to 022 in the shell startup file.

Set the DISPLAY environment variable.

Ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set.

2.3.1 Oracle Database Requirement

Oracle HTTP Server must have access to an Oracle9i Database release 9.2.0.3 or later instance in order to run. Oracle Database can be on a separate system from Oracle HTTP Server, as long as it is accessible by using Oracle*Net. However, Oracle HTTP Server must be in its own home.

2.3.2 Hardware Requirements

The system must meet the following hardware requirements:

256 MB of physical RAM

512 MB of swap space

125 MB of free disk space in the /tmp directory

530 MB of disk space for the software files

To ensure that the system meets these requirements:

To determine the physical RAM size, enter the following command:

# /usr/sbin/prtconf | grep "Memory size"

If the size of the physical RAM installed on the system is less than the required size, then you must install more memory before continuing.

To determine the size of the configured swap space, enter the following command:

# /usr/sbin/swap -s

If necessary, refer to your operating system documentation for information about how to configure additional swap space.

To determine the amount of free disk space on the system, enter the following command:

# df -k

To determine if the system architecture can run the software, enter the following command:

# /bin/isainfo -kv

The expected output of this command is the processor type. Verify that the processor architecture matches the requirement for the current release.

Note:

If you do not see the expected output, then you cannot install the software on this system.

2.3.3 Software Requirements

The system must meet the software requirements described in the following table.

The operating system version must be Solaris 8 Update 7 or later, Solaris 9 update 6 or later, and Solaris 10.

There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, determine whether a more recent version is installed before installing the version listed.

For all installations on Solaris 8, all of the patches included in the J2SE Patch Cluster for Solaris 8 are required:

If you want to install Oracle HTML DB from the Oracle HTML DB installation type, then you must ensure that the system meets the following requirements:

Oracle Database requirement

Oracle HTML DB requires a release 9.2.0.3 or later release of Oracle Database. You must install Oracle HTML DB in an Oracle home that contains Oracle HTTP Server. This Oracle home can be on a different physical server from the Oracle Database home, as long as Oracle HTML DB can access this database by using Oracle*Net.

Disk space requirements

Verify that the file system that contains the Oracle home contains at least 355 MB of free disk space.

To check that the Oracle home has enough space, enter the following command:

# df -k/httpserver_oracle_home_path

Oracle HTTP Server requirement

Oracle HTML DB must have access to Oracle HTTP Server and mod_plsql in order to run.

Oracle XML DB requirement

Oracle XML DB must be installed in the database that you want to use.

Oracle Text requirement

Oracle Text must be installed so that you can use the searchable online Help in Oracle HTML DB.

Browser requirements

To view or develop Oracle HTML DB applications, the Web browser you use must support JavaScript and the HTML 4.0 and CSS 1.0 standards.

2.5 Requirements for Installing Oracle Database 10g Products

If you want to install Oracle Database 10g products, then you must ensure that the system meets the following requirements:

Oracle Database requirement

Before you install products from the Oracle Database 10g Products installation type, ensure that your system has access to an Oracle Database 10g release 2 (10.2) Oracle home.

Disk space requirements

Verify that the file system that contains the Oracle home has at least 1194 MB of free disk space.

Oracle Workflow Server requirements

Requirements for Oracle Workflow Server are as follows:

A Web browser that supports frames, JavaScript, Java Development Kit (JDK) version 1.3.1, and AWT, such as Netscape Communicator version 4.76 or a later 4.7x version, or Microsoft Internet Explorer version 5.0x or 5.5x

An unzip utility to extract the Workflow HTML Help from the wfdoc.zip file

Java Development Kit (JDK) version 1.4, to run the Oracle Workflow Java Function Activity Agent and the Workflow XML Loader

An outbound SMTP mail server and an inbound IMAP mail server, if you want to send and receive e-mail notifications using an Oracle Workflow notification mailer

If you want to install Oracle Database 10g Companion Products, then you must ensure that the system meets the following requirements:

Oracle Workflow Server requirements

Before you install Oracle Workflow middle-tier components, you must verify that Oracle Workflow Server is installed in an Oracle Database 10g Oracle home.

Oracle HTTP Server requirements

Oracle Workflow middle-tier components need access to Oracle HTTP Server in order to run. You can install Oracle Workflow middle-tier components with Oracle HTTP Server in a new Oracle home.

Disk space requirements

The disk space requirements for the Oracle Database 10g Companion Products are shown in the following table.

Products for Installation

Disk Space Required (MB)

Oracle HTTP Server

2300

Oracle HTTP Server and Oracle Workflow

2400

3 Beginning the Procedure to Install Companion CD Products

This section provides screen-wise instructions for beginning the installation of each of the 3 installation types. Most of the Oracle Universal Installer screens are the same for all 3 installation types. However, before you install Oracle Workflow middle-tier components, you must first install and prepare Oracle Workflow Server.

After you install Oracle Workflow Server, you must configure it before you install the Oracle Workflow middle-tier components. You can use Oracle Workflow Configuration Assistant to configure Oracle Workflow. The following steps explain how to run Oracle Workflow Configuration Assistant by using its graphical user interface (GUI):

The connection string is stored in the tnsnames.ora file, which by default is located in the $ORACLE_HOME/network/admin directory.

If you want to integrate Oracle Internet Directory as the directory repository for Oracle Workflow, then select Enter LDAP Parameters and select Get LDAP Values.

Note:

If you are upgrading an existing Oracle Workflow installation in which you have already implemented Oracle Internet Directory integration, then you must reenter the Lightweight Directory Access Protocol (LDAP) values here to preserve the Oracle Internet Directory integration during the upgrade.

Enter the following LDAP server information for the LDAP directory to which you want to connect, and then click OK.

Note:

If required, after the installation, you can update these values on the Global Workflow preferences Web page.

Refer to the "Setting Up Oracle Workflow" section in Oracle Workflow Administrator's Guide for more information.

LDAP Host Name: Enter the name of the host on which the LDAP directory is installed.

LDAP Non-SSL Port: Enter the port number that the host uses. This port must not be a Secure Sockets Layer (SSL) port.

LDAP Admin Username: Enter the user name used to connect to the LDAP server. This user name must have write privileges and is required to bind to the LDAP directory. For example:

cn=orcladmin

LDAP Admin Password: Enter the Oracle Internet Directory password for the LDAP user account. LDAP password values are masked as asterisks (*) in the display and are stored in encrypted form.

User Base: Enter the LDAP node under which user records can be found. For example:

cn=Base, cn=OracleSchemaVersion

Note:

After setting up integration with Oracle Internet Directory during installation, you must use the WF_LDAP APIs to synchronize the Oracle Workflow directory service with Oracle Internet Directory. For instructions, refer to Oracle Workflow Administrator's Guide.

Email Processing: Processed Folder: Enter the name of the mail folder in the inbound e-mail account where the notification mailer places successfully processed notification messages.

Email Processing: Discard Folder: Enter the name of the mail folder in the inbound e-mail account where the notification mailer places incoming messages that are not recognized as notification messages.

Message Generation: HTML Agent: Enter the base URL that identifies the Web agent defined for Oracle Workflow in Oracle HTTP Server. The notification mailer uses this URL to support e-mail notifications with HTML attachments. By default, this parameter is set to the following placeholder value:

http://localhost.com/pls/wf

If you have already installed Oracle HTTP Server, then replace localhost.com with the server and TCP/IP port number on which the Web listener accepts requests. Otherwise, leave this parameter set to the placeholder value. In this case, you must set this parameter in the notification mailer configuration wizard in Oracle Workflow Manager after you install Oracle HTTP Server and Oracle Workflow.

Message Generation: Reply-To Address: Enter the address of the e-mail account that receives incoming messages, to which notification responses should be sent.

After the initial installation, you can, if required, update the notification mailer configuration values in the Oracle Workflow Manager. You can also update the HTML agent value for Oracle Workflow in the Global Workflow preferences Web page.

See Also:

The "Setting Up Oracle Workflow" section in Oracle Workflow Administrator's Guide and Oracle Workflow Manager online Help for more information

To change the tablespace assigned to the Oracle Workflow database account, first select Change Tablespace and then select an existing tablespace from the list of values.

Select Submit to begin the configuration, or select Quit to exit Oracle Workflow Configuration Assistant without performing the configuration.

When the configuration is complete, a confirmation window appears. Click OK.

You can check the status of the configuration by reviewing the $ORACLE_HOME/wf/install/workflow.log file.

Refer to the following section for instructions about beginning the installation of Oracle Workflow middle-tier components.

Beginning the Installation

To begin installing Companion CD products:

If you are installing from the installation media, then mount the disc if it is not already mounted.

If required, log in as the Oracle software owner user (oracle) and set the DISPLAY environment variable.

If you are going to install Oracle HTML DB, then verify that the Oracle Database that you plan to use for Oracle HTML DB is accessible and running.

To start Oracle Universal Installer, enter the following commands:

$ cd /tmp
$ /directory_path/runInstaller

In the preceding command, directory_path is the path of the companion directory on the installation media or the hard drive.

On the Welcome screen, click Next.

If this is the first installation of Oracle products on this system, then Oracle Universal Installer displays the Specify Inventory Directory and Credentials screen. Specify the following information, and then click Next:

Enter the full path of the inventory directory

Verify that the path is similar to the following, where oracle_base is the full path of the Oracle base directory:

oracle_base/oraInventory

Specify operating system group name

Verify that the group specified is the Oracle Inventory group, oinstall.

The following section provides instructions specific to each installation type.

4 Specifying Product-Specific Information During the Installation

To continue with the installation procedure, refer to one of the following sections:

This section explains how to install Oracle HTML DB by using one of the following options:

Installing Oracle HTML DB with Oracle HTTP Server: If you select this option, then Oracle HTML DB is installed with Oracle HTTP Server in a new Oracle home.

Installing or upgrading Oracle HTML DB in an existing Oracle HTTP Server home: If you select this option, then depending on the preinstallation conditions, either Oracle HTML DB is installed or the existing Oracle HTML DB installation is upgraded.

To continue with the procedure for installing Oracle HTML DB products:

On the Select a Product to Install screen, select Oracle HTML DB and then click Next.

On the Select Installation Type screen, select one of the following and then click Next.

Oracle HTML DB and Oracle HTTP Server: Select this option to install a new Oracle HTML DB and Oracle HTTP Server in a new Oracle home.

Oracle HTML DB only: Select this option to install a new Oracle HTML DB in an existing Oracle HTTP Server home, or to upgrade an existing Oracle HTML DB installation.

On the Specify Home Details screen, enter the following:

Name: If you select Oracle HTML DB and Oracle HTTP Server in the previous step, then specify the name for a new Oracle home. If you select Oracle HTML DB only, then select the name of the existing Oracle HTTP Server home. If you select Oracle HTML DB only and if there is an existing Oracle HTML DB installation, then specify the name of the Oracle home of this existing installation.

Path: Enter the directory location for the Oracle home that you specified under Name. If the directory does not exist, then Oracle Universal Installer creates it for you.

Click Next.

On the Product-specific Prerequisite Checks screen, check for and correct any errors that may have occurred while Oracle Universal Installer was checking your system. Click Next.

When you click Next, a warning message may be displayed. If there is an existing Oracle HTML DB installation, then this message informs you that the database access descriptors (DADs) associated with this installation have insufficient or incorrect values for some of the required directives. This makes them unsuitable for upgrade. If you want to upgrade Oracle HTML DB under these conditions, then you must first fix the problem. If you want to install Oracle HTML DB, then continue with this installation session.

Specify the host name of the system on which the database is installed. If the host name is the local host, then enter the name of the computer, not localhost.

Port

Specify the TCP/IP port number for the Oracle Net listener on the database system. The default port number is 1521. To find the default port number for your Oracle Database installation, check its tnsnames.ora file, which by default is located in the $ORACLE_HOME/network/admin directory.

Database Service Name

Specify the database service name for the database in which you want to install the Oracle HTML DB database objects, for example, sales. Alternatively, you can enter the domain name, which is usually the same as the global database name, for example, sales.us.mycompany.com.

To configure Oracle HTML DB, you must install the Oracle HTML DB database objects in a release 9.2.0.3 or later release of Oracle Database. If you plan to use the 10g release of Oracle HTTP Server, then based on the information that you specify during installation, Oracle Universal Installer automatically creates a database access descriptor (DAD) in the mod_plsql configuration file and directory aliases in httpd.conf, the Oracle HTTP Server configuration file.

Tablespace Name

Enter the name of the tablespace in which you want to load the Oracle HTML DB database objects, or accept the default (SYSAUX).

SYS Password

Specify the password for the SYS user in the database.

HTML DB Password

Specify the password that you want to use for the Oracle HTML DB schemas (users), which are created in the database during the installation.

After the installation, you can use this password to connect to Oracle HTML DB as the administrative user. The password that you specify is also used for the HTMLDB_PUBLIC_USER schema, which is used by mod_plsql to connect to the database, and for the FLOWS_010600 and FLOWS_FILES schemas.

Confirm HTML DB Password

Enter the password again to verify that you have specified it correctly.

Upgrading an existing Oracle HTML DB installation

On the Specify HTML DB Upgrade Information screen, select the Oracle HTML DB installation that you want to upgrade from the list of available DADs.

When you specify the Oracle HTML DB installation that you want to upgrade, the host name, port, and database service name values are automatically displayed in their respective fields. You cannot change these values. The remaining fields are the same as those displayed on the Specify HTML DB Database Details screen.

To continue with the procedure for installing Oracle Database 10g Products:

On the Select a Product to Install screen, select Oracle Database 10gProducts and then click Next.

On the Specify Home Details screen, enter the following:

Name: In this field, the default Oracle home is displayed. Verify that the Oracle home specified is the Oracle Database Oracle home.

Path: In this field, the directory of the default Oracle home is displayed. Enter the directory location of the Oracle Database Oracle home in which you want to install the Oracle home files. If the directory does not exist, then Oracle Universal Installer creates it for you.

On the Product-specific Prerequisite Checks screen, check for and correct any errors that may have occurred while Oracle Universal Installer was checking your system.

To continue with the procedure for installing Oracle Database 10g Companion products:

On the Select a Product to Install screen, select Oracle Database 10gCompanion Products and then click Next.

On the Specify Home Details screen, enter the following:

Name: Enter a name for the Oracle home. You can install the Oracle Database 10g Companion Products in a new Oracle home. Alternatively, you can install Oracle Workflow middle tier only in an existing Oracle HTTP Server Oracle home. You cannot install the Oracle Database 10g Companion Products in an existing Oracle Database home.

Path: Enter the directory location for the Oracle home. If the directory does not exist, then Oracle Universal Installer creates it for you.

On the Product-specific Prerequisite Checks screen, check for and correct any errors that may have occurred while Oracle Universal Installer was checking your system.

If you are installing Oracle Workflow middle tier only in an existing Oracle HTTP Server Oracle home, then you may need to manually verify that the selected Oracle home exists. Then, click Next.

To configure the Oracle Workflow middle tier, you must create a database access descriptor (DAD) in the mod_plsql configuration files and directory aliases in the Oracle HTTP Server configuration file. Oracle Universal Installer completes these tasks for you using the information that you specify. Enter the following information:

Workflow Schema

Specify the user (schema) name that you used when installing the Oracle Workflow Server database objects in the database. The default user name is owf_mgr.

DB Hostname

Specify the host name of the system on which the database is installed. If the host name is the local host, then enter the name of the computer, not localhost.

Port Number

Specify the TCP/IP port number for the Oracle Net listener on the database system. The default port number is 1521.

Oracle SID

Specify the database instance identifier (SID) for the database on which you installed the Oracle Workflow Server database objects.

On the Oracle Workflow Middle Tier Configuration screen, enter a password for the Oracle Workflow schema that you created in the previous step, and then click Next.

On the Oracle Apache Installation screen, enter the following information and then click Next.

Enter Password

Specify the password for the Workflow user (typically, owf_mgr) that you specified on the previous screen. This password is used for the mod_plsql DAD.

Confirm Password

Enter the password again to verify that you have specified it correctly.

7 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Scripting on this page enhances content navigation, but does not change the content in any way.