Oracle Database Companion CD Installation Guide 10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit)
10g Release 2 (10.2)
B14325-03

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documentation

- Conventions

Support for Windows Server 2008 and Windows Server 2008 R2

- Managing User Accounts with User Account Control on Windows Server 2008 and Windows Server 2008 R2

1 Oracle Database Companion CD Installation Overview

- 1.1 Overview of the Installation Process

- 1.2 Products Available in the Oracle HTML DB Installation Type

- 1.2.1 Oracle HTML DB

- 1.2.2 Oracle HTTP Server

- 1.3 Products Available in the Oracle Database 10g Products Installation Type

- 1.3.1 Oracle JDBC Development Drivers

- 1.3.2 Oracle SQLJ

- 1.3.3 Oracle Database Examples

- 1.3.3.1 Required Products

- 1.3.4 Oracle Text Supplied Knowledge Bases

- 1.3.5 Oracle Workflow Server

- 1.3.6 Oracle Ultra Search

- 1.3.7 Natively Compiled Java Libraries

- 1.3.8 JPublisher

- 1.4 Products Available in the Oracle Database 10g Companion Products Installation Type

- 1.4.1 Oracle Workflow Middle Tier Components

- 1.4.2 Oracle HTTP Server

2 Oracle Database Companion CD Requirements

- 2.1 Requirements for Oracle HTML DB Products

- 2.1.1 Oracle HTML DB Requirements

- 2.1.1.1 Requirements Overview

- 2.1.1.2 Disk Space Requirements

- 2.1.1.3 Browser Requirements

- 2.1.1.4 Oracle Database Requirement

- 2.1.1.5 Oracle HTTP Server Requirement

- 2.1.1.6 Oracle XML DB Requirement

- 2.1.1.7 Oracle Text Requirement

- 2.2 Requirements for Oracle Database 10g Products

- 2.2.1 Requirements Overview

- 2.2.2 Disk Space Requirements

- 2.2.3 Oracle Database Requirement

- 2.2.4 Oracle Workflow Server Browser Requirements

- 2.2.5 Oracle Workflow Server Product Requirements

- 2.3 Requirements for Oracle Database 10g Companion Products

- 2.3.1 Requirements Overview

- 2.3.2 Disk Space Requirements

- 2.3.3 Browser Requirements

- 2.3.4 Oracle Workflow Server Requirement

- 2.3.5 Oracle HTTP Server Requirement

- 2.3.5.1 Using the Oracle HTTP Server Provided with the Companion Products

- 2.3.5.2 Using an Existing Oracle HTTP Server Installation

- 2.4 Hardware and Software Certifications

- 2.4.1 Windows Telnet Services Support

- 2.4.2 Windows Terminal Services and Remote Desktop Support

- 2.5 Oracle Database Companion CD Network Topics

- 2.5.1 Installing Oracle Database Companion CD on DHCP Computers

- 2.5.2 Installing Oracle Database Companion CD on Computers with Multiple IP Addresses

- 2.5.3 Installing Oracle Database Companion CD on Computers with Multiple Aliases

- 2.5.4 Installing a Loopback Adapter

- 2.5.4.1 Checking if a Loopback Adapter Is Installed on Your Computer

- 2.5.4.2 Installing a Loopback Adapter on Windows Server 2003 or Windows XP

- 2.5.4.3 Installing a Loopback Adapter on Windows Server 2008 and Windows Server 2008 R2

- 2.5.4.4 Removing a Loopback Adapter

3 Installing the Oracle Database Companion CD Software

- 3.1 General Steps for Installing Companion CD Products

- 3.2 Accessing the Installation Software

- 3.2.1 Copying Oracle Database Software to Hard Disk

- 3.2.2 Installing from a Remote DVD Drive

- 3.2.2.1 On the Remote Computer, Share the DVD Drive

- 3.2.2.2 On the Local Computer, Map the DVD Drive

- 3.2.3 Installing on Remote Computers Through Remote Access Software

- 3.2.3.1 Installing on Remote Computers from a Hard Drive

- 3.2.3.2 Installing on Remote Computers from a Remote DVD Drive

- 3.3 Installing Oracle HTML DB and Oracle HTTP Server

- 3.3.1 Recommended Preinstallation Task for Oracle HTML DB

- 3.3.2 Oracle Home Location for Oracle HTML DB and Oracle HTTP Server

- 3.3.3 Procedure for Installing Oracle HTML DB and Oracle HTTP Server

- 3.4 Installing Oracle Database 10g Products

- 3.4.1 Oracle Home Location for the Oracle Database 10g Products

- 3.4.1.1 Identifying the Oracle home Directory Location

- 3.4.2 Procedure for Installing Oracle Database 10g Products

- 3.4.3 Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation

- 3.5 Installing Oracle Database 10g Companion Products

- 3.5.1 Oracle Home Location for Oracle Database 10g Companion Products

- 3.5.2 Procedure for Installing Oracle Database 10g Companion CD Products

- 3.6 Removing the Oracle Database Companion CD Software

- 3.6.1 Removing Oracle HTML DB from Oracle Database

- 3.6.2 Removing Oracle Workflow

- 3.6.3 Removing Oracle Database Products and Oracle Database Companion CD Products

4 Oracle Database Companion CD Postinstallation Tasks

- 4.1 Installing the Latest Patch Set Release

- 4.2 Postinstallation Tasks for Oracle HTTP Server

- 4.2.1 Backing Up the Files

- 4.2.2 Migrating from a Previous Release of Oracle HTTP Server

- 4.2.3 Migrating the httpd.conf Configuration File from an Earlier Oracle HTTP Server

- 4.2.3.1 Step1: Copying and Opening the httpd.conf File

- 4.2.3.2 Step 2: Making Global Changes

- 4.2.3.3 Step 3: Modifying the List of LoadModule Directives

- 4.2.3.4 Step 4: Removing Directives and Sections for Unsupported Features

- 4.2.3.5 Step 5: Modifying Port Numbers

- 4.2.3.6 Step 6: Modifying Existing Sections and Directives

- 4.2.3.7 Step 7: Adding New Sections and Directives

- 4.2.3.8 Step 8: Migrating Your Server Certificate and Private Key

- 4.2.3.9 Step 9: Modifying the Secure Socket Layer Sections and Directives

- 4.2.3.10 Step 10: Copying or Moving the Required Files to New Directories

- 4.2.4 Migrating Database Access Descriptors Used by mod_plsql

- 4.2.5 Enabling the High Availability Features of Oracle HTTP Server

- 4.3 Postinstallation Tasks for Oracle HTML DB

- 4.3.1 Restarting Processes

- 4.3.2 Configuring Oracle HTTP Server for an Oracle HTML DB Upgrade

- 4.3.2.1 Oracle HTTP Server Release 9.0.3

- 4.3.2.2 Oracle HTTP Server 10g Release 1

- 4.3.3 Obfuscating PlsqlDatabasePassword Parameter

- 4.3.3.1 Obfuscating Passwords in a New Oracle HTML DB Installation

- 4.3.3.2 Obfuscating Passwords if Upgrading Oracle HTML DB

- 4.3.4 Installing and Configuring Oracle HTML DB on a Remote Oracle Database

- 4.3.4.1 Requirements for Running htmldbca

- 4.3.4.2 Syntax for htmldbca

- 4.3.4.3 Running htmldbca

- 4.4 Postinstallation Tasks for Oracle Workflow Server

- 4.4.1 Checking Initialization Parameter Values

- 4.4.2 Compiling Invalid Objects

- 4.4.3 Configuring Oracle Workflow HTML Help

- 4.4.4 Completing Additional Set-up Tasks

5 Getting Started with the Oracle Database Companion CD Products

- 5.1 Checking the Installation Contents

- 5.2 Getting Started with Oracle HTTP Server

- 5.2.1 Starting, Stopping, or Restarting Oracle HTTP Server

- 5.2.2 Logging into Oracle HTTP Server

- 5.3 Getting Started with Oracle HTML DB

- 5.3.1 Logging into Oracle HTML DB

- 5.3.2 Set-up Tasks for Oracle HTML DB Administrators

- 5.4 Getting Started with Oracle Workflow

- 5.4.1 Logging into the Oracle Workflow Home Page

- 5.4.2 Logging into Oracle Workflow Manager

- 5.4.3 Set-up Tasks for Oracle Workflow Administrators

- 5.5 Getting Started with Oracle Ultra Search

A Installing Oracle Database Companion CD Using Response Files

- A.1 How Response Files Work

- A.1.1 Reasons for Using Silent Mode or Noninteractive Mode

- A.1.2 General Procedure for Using Response Files

- A.2 Preparing a Response File

- A.2.1 Editing a Response File Template

- A.2.2 Recording a Response File

- A.3 Running Oracle Universal Installer Using the Response File

- A.4 Running Oracle Workflow Configuration Assistant in Noninteractive Mode

B Configuring Oracle Database Companion CD Globalization Support

- B.1 Installing and Using Oracle Components in Different Languages

- B.1.1 Installing Oracle HTML DB in Other Languages

- B.1.2 Installing Oracle Workflow in Other Languages

- B.1.3 Running Oracle Universal Installer in Different Languages

- B.1.4 Using Oracle Components in Different Languages

- B.2 Configuring Locale and Character Sets with the NLS_LANG Parameter

C Managing Oracle Companion CD Port Numbers

- C.1 About Managing Ports

- C.2 Viewing Port Numbers and Access URLS

- C.3 Port Numbers and Protocols of Oracle Components

- C.4 Changing the Oracle HTTP Server Port

- C.5 Changing the Oracle Workflow Container Ports

- C.6 Changing the Oracle Ultra Search Ports

D Troubleshooting the Oracle Database Companion CD Installation

- D.1 Verifying Requirements

- D.2 Reviewing a Log of an Installation Session

- D.2.1 Reviewing the Log of an Oracle Companion CD Installation Session

- D.2.2 Reviewing the Log of an Oracle HTML DB Installation Session

- D.3 Cleaning Up After a Failed Installation

- D.3.1 Cleaning Up After a Failed Oracle Companion CD Installation

- D.3.2 Cleaning Up After a Failed Oracle HTML DB Installation

- D.3.2.1 Cleaning Up After a Failed Upgrade Installation

- D.3.2.2 Cleaning Up After a Failed New Installation

- D.4 Silent or Noninteractive Installation Response File Error Handling

- D.5 Images Displaying Incorrectly in Oracle HTML DB

- D.6 Oracle HTML DB Online Help Not Working

Index

Oracle® Database

Companion CD Installation Guide

10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit)

B14325-03

March 2011

Oracle Database Companion CD Installation Guide 10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit)

B14325-03

Copyright © 2006, 2011, Oracle and/or its affiliates. All rights reserved.

Primary Author: Richa Agarwala

Contributing Author: Reema Khosla, Patricia Huey

Contributors:  Punsri Abeywickrema, Eric Belden, Phil Choi, Toby Close, Sudip Datta, Jim Emmond, David Friedman, Alex Keh, Mark Kennedy, Peter LaQuerre, Rich Long, Anu Natarajan, Mark MacDonald, Matt McKerley, Mohamed Nosseir, Bharat Paliwal, Sham Rao Pavan, Hanlin Qian, Christian Shay, Helen Slattery, Debbie Steiner, Linus Tanaka, Ravi Thammaiah, Sujatha Tolstoy

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. 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, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This document describes the features of Oracle Database for Microsoft Windows Itanium (64-Bit) software installed on the following operating systems:

- Windows Server 2003 Datacenter Edition for 64-Bit Itanium 2 Systems

- Windows Server 2003 Enterprise Edition for 64-Bit Itanium 2 Systems

- Windows Server 2008 for Itanium-Based Systems

- Windows Server 2008 R2 for Itanium-Based Systems

This Preface contains these topics:

- Audience

- Documentation Accessibility

- Related Documentation

- Conventions

Audience

Oracle Database Companion CD Installation Guide for Microsoft Windows Itanium (64-Bit) is intended for anyone responsible for installing the following products available on the Oracle Database Companion CD for Microsoft Windows Itanium (64-Bit):

- Oracle Workflow server and Oracle Workflow middle tier components

- Oracle HTML DB

- Oracle HTTP Server

- Oracle JDBC Development Drivers

- Oracle SQLJ

- Oracle Database Examples

- JPublisher

- Natively Compiled Java Libraries

- Oracle Text Supplied Knowledge Bases

- Oracle Ultra Search

To use this manual, you must have administrative privileges on the computer where you installed your Oracle Database and familiarity with object-relational database management concepts.

See Also:

Oracle Database Companion CD Quick Installation Guide for Microsoft Windows Itanium (64-Bit) to perform a quick installation using the default settings

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. 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 http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

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.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documentation

For more information, see these Oracle resources:

- Oracle Database Release Notes for Microsoft Windows Itanium (64-Bit)

- Oracle Database Installation Guide for Microsoft Windows Itanium (64-Bit)

- Oracle Database Client Installation Guide for Microsoft Windows Itanium (64-Bit)

- Oracle Database Concepts

For information about Oracle error messages, see Oracle Database Error Messages. Oracle error message documentation is available only in HTML. If you only have access to the Oracle Database 10g release 2 (10.2) Online Documentation Library, you can browse the error messages by range. Once you find the specific range, use your browser's "find in page" feature to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.

Many of the examples in this book use the sample schemas, which are installed by default when you select the Basic Installation option with an Oracle Database installation. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.

To download free release notes, installation documentation, white papers, or other collateral, visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://www.oracle.com/technology/membership/index.html

If you have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://www.oracle.com/technetwork/indexes/documentation/index.html

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Support for Windows Server 2008 and Windows Server 2008 R2

Oracle Database is supported on Windows Server 2008 and Windows Server 2008 R2 with the 10.2.0.5 release. Use the Oracle Database 10g Release 2 (10.2.0.5.0) for Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 media available in the 10.2.0.5 media pack and the Oracle Technology Network site. Do not install Oracle Database on Windows Server 2008 or Windows Server 2008 R2 using the media for Oracle Database 10g Release 2 (10.2) for Microsoft Windows.

Managing User Accounts with User Account Control on Windows Server 2008 and Windows Server 2008 R2

To ensure that only trusted applications run on your computer, Windows Server 2008 and Windows Server 2008 R2 provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.

You must have Administrator privileges to run some Oracle tools, such as Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly start these tasks with Windows Administrator privileges. Refer to "Starting Database Tools" in Oracle Database Platform Guide for Microsoft Windows Itanium (64-Bit) for more information.

To Run a Windows Shortcut with Windows Administrator Privileges:

1. Click the Start menu button.

2. Navigate to Programs, then to Oracle - HOME_NAME.

3. Right-click the name of the command or application you want to run, then select Run as administrator.

To Start a Command Prompt Window with Windows Administrator Privileges:

1. On your desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the desktop.

2. Right-click the icon for the newly created shortcut, and specify "Run as administrator."

When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.

1 Oracle Database Companion CD Installation Overview

This chapter provides an overview of the products available on the Oracle Database Companion CD and describes issues to consider before you install the products:

- Overview of the Installation Process

- Products Available in the Oracle HTML DB Installation Type

- Products Available in the Oracle Database 10g Products Installation Type

- Products Available in the Oracle Database 10g Companion Products Installation Type

1.1 Overview of the Installation Process

The installation process consists of six steps:

1. Read the release notes: Read the Oracle Database 10g release 2 (10.2) release notes before you begin the installation. The release notes are available with the platform-specific documentation. The latest version of the release notes is available on Oracle Technology Network at:
http://www.oracle.com/technetwork/indexes/documentation/index.html

2. Plan the installation: This chapter describes the products in the installation types and provides information that you must understand before installing the software.
You also may want to refer to Appendix A, "Frequently Asked Questions about Installation," in Oracle Database Installation Guide. This appendix advises on the best way to install Oracle products depending on your site's requirements.

3. Verify system requirements: Chapter 2 describes the minimum requirements that your system must meet before you install the software.

4. Install the software: Use the following sections to install the Oracle Database Companion CD products:

- Chapter 3 describes how to use Oracle Universal Installer to install the software.

- Appendix A describes how to perform the installation using silent or noninteractive mode using response files. It also explains how to run Oracle Workflow Configuration Assistant in noninteractive mode.

- "Installing and Using Oracle Components in Different Languages" describes how to install and use Oracle Database Companion CD components in different languages.

- Appendix D provides installation troubleshooting advice.

5. Complete postinstallation tasks: Chapter 4 describes recommended and required postinstallation tasks.

6. Get started using the Companion CD products: Use the following sections to get started using Oracle Database Companion CD products:

- Chapter 5 describes where to go after you have installed the Oracle Database Companion CD products and performed any necessary postinstallation steps: how to check the contents of the installation and how to start and log in to the products you have installed.

- "Configuring Locale and Character Sets with the NLS_LANG Parameter" explains how to configure the Oracle Database Companion CD locale and character sets.

- Appendix C describes how to check and modify port numbers.

1.2 Products Available in the Oracle HTML DB Installation Type

The following products are available in the Oracle HTML DB installation type:

- Oracle HTML DB

- Oracle HTTP Server

Note:

The Summary window of Oracle Universal Installer provides a detailed list of the products available with the Oracle HTML DB installation type.

1.2.1 Oracle HTML DB

Oracle HTML DB is a tool for rapid development and deployment of Web applications on an Oracle database. It provides developers with the productivity of a desktop database, but with the security, reliability, and performance of the Oracle database. With little programming or scripting and only a Web browser, you can build reporting and data entry applications either on existing tables or views or by importing data from spreadsheets.

1.2.2 Oracle HTTP Server

Oracle HTTP Server is a Web server that is based on Apache Standalone version 10.2.0.0. Use the Oracle HTML DB installation type to install Oracle HTTP Server in a new Oracle home. (If you are installing Oracle Workflow middle tier components, Oracle HTTP Server is available with Oracle Database 10g Companion Products.) This standalone release of Oracle HTTP Server provides the following features:

- A robust and reliable Web server that you can use to serve Web pages

- Support for Perl and Fast CGI scripts using mod_perl and mod_fastcgi

- Support for PL/SQL applications using mod_plsql

- High-availability, with the use of Oracle Process Manager and Notification server (OPMN)
OPMN monitors Oracle HTTP Server processes and restarts them if they fail.

- Support for secure transactions using secure socket layer (SSL)

- Single sign-on capabilities using mod_osso
To enable single sign-on, you must use Oracle HTTP Server with Oracle Internet Directory and Single Sign-On Server, both of which are available with Oracle Application Server 10g.

- Many standard Apache modules, in addition to modules provided by Oracle

See Also:

Oracle Application Server Installation Guide for more information about Oracle Internet Directory and Single Sign-On Server

1.3 Products Available in the Oracle Database 10g Products Installation Type

The following products are available with the Oracle Database 10g Products installation type:

- Oracle JDBC Development Drivers

- Oracle SQLJ

- Oracle Database Examples

- Oracle Text Supplied Knowledge Bases

- Oracle Workflow Server

- Oracle Ultra Search

- Natively Compiled Java Libraries

- JPublisher

Note:

- The Summary window of Oracle Universal Installer provides a detailed list of the products available with the Oracle Database 10g Products installation type.

- Legato Single Server Version (LSSV) is no longer supported on Oracle Database. Oracle Database Recovery Manager (RMAN), which is a backup and recovery tool integrated into Oracle Database. Oracle Database Backup and Recovery Basics covers RMAN in more detail.

1.3.1 Oracle JDBC Development Drivers

Oracle provides a set of JDBC drivers that you can use for debugging your code and other deployment scenarios. These drivers can access Oracle Database release 8.1.7 or later.

See Also:

- Oracle Technology Network (http://www.oracle.com/technetwork/index.html) for more information about Oracle JDBC Drivers and Oracle Call Interface

- Oracle Call Interface Programmer's Guide

1.3.2 Oracle SQLJ

Oracle SQLJ enables applications programmers to embed SQL operations in Java code in a way that is compatible with the Java design philosophy. A SQLJ program is a Java program containing embedded SQL statements. Oracle SQLJ offers extensions to support dynamic SQL operations—those that are not predefined, where the operations themselves can change in real-time. It is also possible to use dynamic SQL operations through JDBC code or PL/SQL code within a SQLJ application. Typical applications contain much more static SQL than dynamic SQL. SQLJ has both a translator and a run-time component and is smoothly integrated into your development environment.

1.3.3 Oracle Database Examples

Oracle Database Examples include a variety of examples and product demonstrations that you can use to learn about the products, options, and features of Oracle Database. Many of these examples are designed to work with the Sample Schemas which you can optionally install in any Oracle database. Many of the documents in the Oracle Online Documentation Library use the example programs and scripts provided with the Oracle Database Examples.

1.3.3.1 Required Products

Before you can use the Oracle Database Examples, you must install the Sample Schemas into an Oracle database. When you install Oracle Database, or use Database Configuration Assistant (DBCA) to create a database, you can choose to include the Sample Schemas when you create the database. You can also manually install the Sample Schemas into an existing database.

See Also:

Oracle Database Sample Schemas for information about manually installing the Sample Schemas into an existing database

1.3.4 Oracle Text Supplied Knowledge Bases

The Oracle Database 10g Products installation type installs two Oracle Text knowledge bases, English and French. You can extend the supplied knowledge bases depending on your requirements. Alternatively, you can create your own knowledge bases, in languages other than English and French.

See Also:

Oracle Text Reference for more information about creating and extending knowledge bases

1.3.5 Oracle Workflow Server

Oracle Workflow provides a complete workflow management system that supports business process-based integration. Its technology enables modeling, automation, and continuous improvement of business processes, routing information of any type according to user–defined business rules. The Oracle Workflow installation includes Oracle Workflow server and Oracle Workflow Manager on the Oracle Database Products installation type and the Oracle Workflow middle tier components on the Companion Products installation type.

In this release, starting the Oracle Application Server Containers for J2EE (OC4J) instances for Oracle Workflow Manager has been simplified to running two scripts.

Note:

Do not install Oracle Workflow server in an Oracle E-Business Suite database. If you want to use the version of Oracle Workflow available with Oracle Database 10g, or any Oracle Database components that depend on this version of Oracle Workflow, you must install the Oracle Workflow server into a database that is not used for an Oracle E-Business Suite instance.
For an Oracle E-Business Suite database, you can continue to use the version of the Oracle Workflow server embedded in Oracle E-Business Suite instead.

See Also:

Oracle Workflow Client Installation Guide on Oracle Technology Network (OTN) for information about installing Oracle Workflow Client:
http://www.oracle.com/technetwork/indexes/documentation/index.html

Oracle Workflow Client is available from Oracle Technology Network:

http://www.oracle.com/technetwork/middleware/ias/overview/index.html

Other Installation Types that Install Oracle Workflow

Oracle Workflow is also installed by some installation types of the following products:

- Oracle Application Server 10g

- Oracle Content Management SDK 10g

If you installed either of these products, you might have installed Oracle Workflow. In this case, you must install Oracle Workflow again.

1.3.6 Oracle Ultra Search

You can use Oracle Ultra Search to build different kinds of search applications. It lets you index and search Web sites, database tables, files, mailing lists, Oracle Application Server Portals, and user-defined data sources.

1.3.7 Natively Compiled Java Libraries

The Oracle Database 10g Products installation type installs JAccelerator and Oracle interMedia Image Accelerator which contains the natively compiled Java libraries (NCOMPs) for Oracle JVM and Oracle interMedia. These libraries are required to improve the performance of these products on your platform.

1.3.8 JPublisher

JPublisher is a Java utility that generates Java classes to represent the following user-defined database entities in a Java program:

- SQL object types

- Object reference types (REF types)

- SQL collection types (VARRAY types or nested table types)

- PL/SQL packages

- Server-side Java classes

- SQL queries and DML statements

You can use JPublisher to specify and customize the mapping of SQL object types, object reference types, and collection types (VARRAYs or nested tables) to Java classes in a strongly typed paradigm.

JPublisher also can generate classes for PL/SQL packages. These classes have wrapper methods to invoke the stored procedures in the PL/SQL packages.

In addition, JPublisher simplifies access to PL/SQL-only types from Java. You can employ predefined or user-defined mappings between PL/SQL and SQL types, and use PL/SQL conversion functions between such types. With such type correspondences in place, JPublisher can automatically generate the required Java and PL/SQL code.

In a similar way that SQL or PL/SQL entities publish to Java, you can publish server-side Java classes to client-side Java classes. Doing this enables applications to make direct calls to Java classes in the database.

JPublisher lets you expose generated Java classes as Web services, for example. You can publish either SQL or PL/SQL entities or server-side Java entities.

JPublisher uses SQLJ code in most Java classes that it generates, so it includes Oracle SQLJ Translator and Oracle SQLJ Runtime. Oracle SQLJ is a standard way to embed SQL statements in Java programs.

Oracle SQLJ Translator

Because JPublisher uses SQLJ code in its generated classes, it automatically invokes the Oracle SQLJ translator during the code generation process, as necessary. The translator converts embedded SQL statements into JDBC calls.

Oracle SQLJ Runtime

Oracle SQLJ Runtime is used during program execution to execute most classes that were generated by JPublisher. SQLJ Runtime is a thin layer of pure Java code that runs above the JDBC driver. It acts as an intermediary that reads information about SQL operations and passing instructions along to the JDBC driver.

See Also:

Oracle Database JPublisher User's Guide

1.4 Products Available in the Oracle Database 10g Companion Products Installation Type

The following products are available with the Oracle Database 10g Companion Products installation type:

- Oracle Workflow Middle Tier Components

- Oracle HTTP Server

Note:

The Summary window of Oracle Universal Installer provides a detailed list of the products available with the Oracle Database 10g Companion Products installation type.

1.4.1 Oracle Workflow Middle Tier Components

Oracle Workflow middle tier components enable the Oracle Workflow user interface Web pages, including the Database Access Descriptor (DAD) and virtual directory mappings for Oracle Workflow. Before you can use Oracle Workflow server, you must install Oracle Workflow middle tier components. The Oracle Workflow middle tier components are associated with one Oracle database, the database for which Oracle Workflow server is installed.

Use the Oracle Database 10g Companion Products installation type to install the Oracle Workflow middle tier components after you install Oracle Workflow server.

1.4.2 Oracle HTTP Server

"Oracle HTTP Server" describes Oracle HTTP Server in detail.

2 Oracle Database Companion CD Requirements

This chapter describes the requirements for installing the Oracle Database 10g Companion CD products:

- Requirements for Oracle HTML DB Products

- Requirements for Oracle Database 10g Products

- Requirements for Oracle Database 10g Companion Products

- Hardware and Software Certifications

- Oracle Database Companion CD Network Topics

2.1 Requirements for Oracle HTML DB Products

This section covers the following topics:

- Oracle HTML DB Requirements

- Oracle HTTP Server Requirement

2.1.1 Oracle HTML DB Requirements

This section covers the following topics:

- Requirements Overview

- Disk Space Requirements

- Browser Requirements

- Oracle Database Requirement

- Oracle HTTP Server Requirement

- Oracle XML DB Requirement

- Oracle Text Requirement

2.1.1.1 Requirements Overview

Table 2-1 summarizes the requirements for each Oracle HTML DB installation option. For details on each requirement, refer to the remaining topics in this section.

Table 2-1 Oracle HTML DB Requirements

Installation Option

Required Disk Space

Required Browsers

Required Products

Oracle HTML DB Only (in Oracle HTTP Server home)

Total disk space: 682.13 MB

Details: "Disk Space Requirements"

Details: "Browser Requirements"

Details:

- "Oracle Database Requirement"

- "Oracle HTTP Server Requirement"

- "Oracle XML DB Requirement"

- "Oracle Text Requirement"

Oracle HTML DB and Oracle HTTP Server

Total disk space: 1.03 GB

Details: "Disk Space Requirements"

Same as Oracle HTML DB Only installation

Details:

- "Oracle Database Requirement"

- "Oracle XML DB Requirement"

- "Oracle Text Requirement"

2.1.1.2 Disk Space Requirements

The following disk space sizes apply to Oracle HTML DB and Oracle HTTP Server only. They do not include the sizes in an existing Oracle Database installation.

Disk space requirements for Oracle HTML DB only:

- TEMP space: 110 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 0.13 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 342 MB

- SYSTEM_DRIVE:\ORACLE_BASE\oradata directory: 230 MB (datafiles)

- Total: 682.13 MB

Disk space requirements for Oracle HTML DB and Oracle HTTP Server:

- TEMP space: 110 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 1.12 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 715 MB

- SYSTEM_DRIVE:\ORACLE_BASE\oradata directory: 230 MB (datafiles)

- Total: 1.03 GB

2.1.1.3 Browser Requirements

To view or develop Oracle HTML DB applications, Web browsers must support JavaScript and the HTML 4.0 and CSS 1.0 standards. The following Web browsers are supported:

- Netscape Navigator 7.2

- Netscape Navigator 8.1

- Internet Explorer 6.0 SP2

- Internet Explorer 7.0

- Mozilla 1.7

- Firefox 1.0.4

- Firefox 1.5

- Firefox 2.0

- Safari 1.2

See Note 412431.1 on My Oracle Support (formerly OracleMetaLink) for the latest certification.

2.1.1.4 Oracle Database Requirement

Oracle HTML DB requires an Oracle database that is release 9.2.0.3 or higher. You must install Oracle HTML DB into an Oracle home that contains Oracle HTTP Server. This Oracle home can be on a different physical server from the Oracle Database home, if Oracle HTML DB can access this database with Oracle*Net.

For example, if Oracle Database has been installed in OraDB10g_home1, when you run Oracle Universal Installer to install Oracle HTML DB and are prompted for an Oracle database, you can specify the Oracle Database in that home, but you must install Oracle HTML DB into its own home that contains Oracle HTTP Server, for example, OraDB10g_home2.

2.1.1.5 Oracle HTTP Server Requirement

Oracle HTML DB must have access to Oracle HTTP Server and mod_plsql to run. The Oracle HTML DB installation option that you choose determines the available versions of Oracle HTTP Server that meet this requirement:

- Oracle HTML DB Only: If you plan to select the Oracle HTML DB Only installation option, you must install it into an existing Oracle HTTP Server home. Oracle9i release 2 (9.2) or higher meets this requirement.
Oracle HTTP Server has the following minimum operating system requirements:

- Windows Server 2003 Datacenter Edition for 64-bit Itanium 2 Systems

- Windows Server 2003 Enterprise Edition for 64-bit Itanium 2 Systems

Note:

Windows Multilingual User Interface Pack is supported on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

If the system does not meet these requirements, select the Oracle HTML DB and Oracle HTTP Server installation option instead of Oracle HTML DB Only.

- Oracle HTML DB and Oracle HTTP Server: If you plan to install the version of Oracle HTTP Server that is included in the Oracle Database 10g Companion Products release, see "Using the Oracle HTTP Server Provided with the Companion Products" for its requirements.

2.1.1.6 Oracle XML DB Requirement

Oracle XML DB first must be installed in the Oracle database to use Oracle HTML DB. If you are using a preconfigured database created either during an installation or by Database Configuration Assistant (DBCA), Oracle XML DB is installed and configured.

See Also:

Oracle XML DB Developer's Guide for more information about manually adding Oracle XML DB to an existing database

2.1.1.7 Oracle Text Requirement

Oracle Text must be installed so that you can use the searchable online help in Oracle HTML DB. By default, Oracle Text is installed as part of Oracle Database.

In addition, ensure that the default language preferences for Oracle Text have been installed. To install the Oracle Text default language, log in to the Oracle database where you plan to install Oracle HTML DB and run the appropriate drdeflang.sql script, which by default is located in ORACLE_BASE\ORACLE_HOME\ctx\admin\defaults. For example, to run the language preferences script for US English, drdefus.sql:

c:\> sqlplus sys/SYS_password as sysdba
SQL> @c:\oracle\product\10.2.0\db_1\ctx\admin\defaults\drdefus.sql

See Also :

Oracle Text Application Developer's Guide for more information about Oracle Text

2.2 Requirements for Oracle Database 10g Products

This section covers the following topics:

- Requirements Overview

- Disk Space Requirements

- Oracle Database Requirement

- Oracle Workflow Server Browser Requirements

- Oracle Workflow Server Product Requirements

See Also:

"Products Available in the Oracle Database 10g Products Installation Type"

2.2.1 Requirements Overview

Table 2-2 summarizes the requirements for an Oracle Database 10g Products installation. For details on each requirement, refer to the remaining topics in this section.

Table 2-2 Oracle Database 10g Products Requirements

Required Disk Space

Required Browsers

Required Products

Total: 920.2 MB

Details: "Disk Space Requirements"

Oracle Workflow server needs the following browsers:

Details: "Oracle Workflow Server Browser Requirements"

Oracle Workflow server requires the following products, in addition to Oracle Database:

- Unzip utility

- JDK 1.4

- Outbound SMTP mail server (optional)

- Inbound IMAP mail server (optional)

Details:

- "Oracle Workflow Server Product Requirements"

- "Oracle Database Requirement"

2.2.2 Disk Space Requirements

The following disk space sizes reflect the sizes required by Oracle Database 10g Products only. They do not include the sizes in an existing Oracle Database installation.

- TEMP space: 100 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 100 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 650 MB

- SYSTEM_DRIVE:\ORACLE_BASE\oradata: 40 MB

- Total: 850 MB

2.2.3 Oracle Database Requirement

Your system must have access to Oracle Database release 2 (10.2) before you can install the Oracle Database 10g Products installation type.

See Also:

Oracle Database Installation Guide for Microsoft Windows Itanium (64-Bit)

2.2.4 Oracle Workflow Server Browser Requirements

Oracle Workflow server requires a Web browser that supports frames, JavaScript, Java Development Kit (JDK) Version 1.4, and AWT. The following Web browsers are supported:

- Netscape Navigator 7.2

- Netscape Navigator 8.1

- Internet Explorer 6.0 SP2

- Internet Explorer 7.0

- Mozilla 1.7

- Firefox 1.0.4

- Firefox 1.5

- Firefox 2.0

- Safari 1.2

2.2.5 Oracle Workflow Server Product Requirements

In addition to Oracle Database, Oracle Workflow server needs the following products to run:

- An unzip utility, such as WINZIP from NicoMak, 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, to send and receive e-mail notifications using an Oracle Workflow notification mailer.

2.3 Requirements for Oracle Database 10g Companion Products

This section covers the following topics:

- Requirements Overview

- Disk Space Requirements

- Browser Requirements

- Oracle Workflow Server Requirement

- Oracle HTTP Server Requirement

See Also:

"Products Available in the Oracle Database 10g Companion Products Installation Type"

2.3.1 Requirements Overview

Table 2-3 summarizes the requirements for each Oracle Database 10g Companion Products installation option. For details on each requirement, refer to the remaining topics in this section.

Table 2-3 Oracle Database 10g Companion Products Requirements

Installation Option

Required Disk Space

Required Browsers

Required Products

Oracle Workflow middle tier components (in Oracle HTTP Server home)

Total: 111.15 MB

Details: "Disk Space Requirements"

Details: "Browser Requirements"

Oracle Database

Oracle Workflow Server

Details: "Oracle Workflow Server Requirement"

Oracle Workflow middle tier components and Oracle HTTP Server

Total: 481.11 MB

Details: "Disk Space Requirements"

Details: "Browser Requirements"

Oracle Database

Oracle Workflow Server

Details: "Oracle Workflow Server Requirement"

Oracle HTTP Server only

Total: 463.1 MB

Details: "Disk Space Requirements"

Details: "Browser Requirements"

Oracle Database

Details:

- "Oracle Database Requirement"

- "Oracle HTTP Server Requirement"

2.3.2 Disk Space Requirements

The following disk space sizes reflect the sizes required by the Oracle Database 10g Companion Products only. They do not include the sizes in an existing Oracle Database installation.

Disk space requirements for Oracle Workflow middle tier components only:

- TEMP space: 90 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 0.15 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 21 MB

- Total: 111.15 MB

Disk space requirements for Oracle Workflow middle tier components and Oracle HTTP Server:

- TEMP space: 90 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 1.11 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 390 MB

- Total: 481.11 MB

Disk space requirements for Oracle HTTP Server only:

- TEMP space: 90 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 1.1 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 372 MB

- Total: 463.1 MB

2.3.3 Browser Requirements

The Oracle Database 10g Companion Products require a Web browser that supports frames, JavaScript, Java Development Kit (JDK) Version 1.4, and AWT. The following Web browsers are supported:

- Netscape Navigator 7.2

- Netscape Navigator 8.1

- Internet Explorer 6.0 SP2

- Internet Explorer 7.0

- Mozilla 1.7

- Firefox 1.0.4

- Firefox 1.5

- Firefox 2.0

- Safari 1.2

2.3.4 Oracle Workflow Server Requirement

If Oracle Workflow server is not installed, follow the instructions in this guide for installing Oracle Database 10g products. After you install Oracle Workflow server, you must configure it using Oracle Workflow Configuration Assistant.

Oracle Workflow server must be installed in an Oracle Database 10g Oracle home. You can use the Oracle Universal Installer to check the contents of an Oracle home.

See Also:

"Identifying the Oracle home Directory Location" for how to find the contents of the Oracle home

2.3.5 Oracle HTTP Server Requirement

The Oracle Workflow middle tier components need access to Oracle HTTP Server to run. You can install the version of Oracle HTTP Server that is available with the Oracle Database 10g Companion Products. Alternatively, you can use an existing Oracle HTTP Server installation.

- Using the Oracle HTTP Server Provided with the Companion Products

- Using an Existing Oracle HTTP Server Installation

2.3.5.1 Using the Oracle HTTP Server Provided with the Companion Products

If you plan to use the version of Oracle HTTP Server available with Oracle Database 10g Companion Products, you can install this version of Oracle HTTP Server, along with the Companion Products, into their own Oracle HTTP Server home. If you plan to choose this option, ensure that you have the following requirements in place:

- Requirements Overview

- Disk Space Requirements

- Operating System and Service Pack Requirements

- Oracle Database Requirement

Requirements Overview

Table 2-4 summarizes the requirements for an Oracle HTTP Server installation. For details on each requirement, refer to the remaining topics in this section.

Table 2-4 Oracle HTTP Server Requirements

Required Disk Space

Required Operating System and Service Pack

Required Products

Total: 486.2 MB

Details: "Disk Space Requirements"

Details: "Operating System and Service Pack Requirements"

Oracle Database

Details: "Oracle Database Requirement"

Disk Space Requirements

The disk space requirements for Oracle HTTP Server are as follows:

- TEMP space: 100 MB

- SYSTEM_DRIVE:\Program Files\Oracle directory: 1.2 MB

- SYSTEM_DRIVE:\ORACLE_BASE\ORACLE_HOME directory: 385 MB

- Total: 486.2 MB

Operating System and Service Pack Requirements

Oracle HTTP Server has the following minimum operating system requirements:

- Windows Server 2003 Datacenter Edition for 64-bit Itanium 2 Systems

- Windows Server 2003 Enterprise Edition for 64-bit Itanium 2 Systems

- Windows Server 2008 for Itanium-Based Systems

- Windows Server 2008 R2 for Itanium-Based Systems

Note:

Windows Multilingual User Interface Pack is supported on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

Oracle Database Requirement

Oracle HTTP Server must have access to Oracle9i release 9.2.0.3 or higher run. Oracle Database can be on a separate system from Oracle HTTP Server, if it is accessible by Oracle*Net. However, Oracle HTTP Server must be in its own home.

For example, if Oracle Database has been installed in OraDB10g_home1, when you run Oracle Universal Installer to install Oracle HTTP Server, you can specify the Oracle Database in that home, but you must install Oracle HTTP Server into its own home, for example, OraDB10g_home2, along with the Oracle Database 10g Companion Products.

2.3.5.2 Using an Existing Oracle HTTP Server Installation

If you plan to install the Oracle Database 10g Companion Products into an existing Oracle HTTP Server home, ensure that this version of Oracle HTTP Server has mod_plsql. Oracle 9i Release 2 (9.2) or higher meets this requirement.

2.4 Hardware and Software Certifications

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support (formerly OracleMetaLink) Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support (formerly OracleMetaLink) Web site is available at the following URL:

https://support.oracle.com

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in, click the Certifications tab at the top of the page. Other options include Dashboards, Knowledge, Service Requests, Patches & Updates, Community, Systems, On Demand, and More.

The following sections list the following certification information:

- Windows Telnet Services Support

- Windows Terminal Services and Remote Desktop Support

2.4.1 Windows Telnet Services Support

Windows Server 2003 includes a Telnet Service that allows remote users to log on to the operating system and run console programs using the command line. Oracle supports the use of command line utilities using this feature, but does not support the database GUI tools such as Oracle Universal Installer, Database Configuration Assistant, and Oracle Net Configuration Assistant.

Note:

Ensure that the Telnet service is started on the Windows Services utility.

2.4.2 Windows Terminal Services and Remote Desktop Support

Oracle supports Terminal Services on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. Oracle does not support the installation of Oracle components from a remote Terminal Services Client on to a 64-bit Windows server that is running a Terminal Server service. Start all configuration tools from the Terminal Server console (using mstsc/console) and not from the Terminal Services Client.

You can have multiple Remote Desktop sessions on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. You can configure Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 to use Terminal Services in Remote Desktop for Administration Mode or Terminal Server Mode.

See Also:

- The Microsoft Web site for more information about terminal services:
http://www.microsoft.com/en/us/default.aspx

- The My Oracle Support (formerly OracleMetaLink) Web site for the latest Terminal Server certification information:
https://support.oracle.com

2.5 Oracle Database Companion CD Network Topics

Typically, the computer on which you want to install the Oracle Database Companion CD products is connected to the network, has local storage to contain this installation, has a display monitor, and has a DVD drive.

This section describes how to install the Oracle Database Companion CD products on computers that do not meet the typical scenario. It covers the following cases:

- Installing Oracle Database Companion CD on DHCP Computers

- Installing Oracle Database Companion CD on Computers with Multiple IP Addresses

- Installing Oracle Database Companion CD on Computers with Multiple Aliases

- Installing a Loopback Adapter

2.5.1 Installing Oracle Database Companion CD on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing allows a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.

In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign that computer a unique IP address. However, before installing the Oracle Database Companion CD products onto a computer that uses the DHCP protocol, you must install a loopback adapter to assign a local IP address to that computer.

See also:

"Checking if a Loopback Adapter Is Installed on Your Computer"

2.5.2 Installing Oracle Database Companion CD on Computers with Multiple IP Addresses

You can install Oracle Database Companion CD on a computer that has multiple IP addresses, also known as a multihomed computer. Typically, a multihomed computer has multiple network cards. Each IP address is associated with a host name; additionally, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the host name by using the first name in the hosts file, typically located in SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

Clients must be able to access the computer using this host name (or using aliases for this host name). To check, ping the host name from the client computer using the short name (host name only) and the full name (host name and domain name). Both must work.

Setting the ORACLE_HOSTNAME Environment Variable

To set the ORACLE_HOSTNAME environment variable:

1. Display System in the Windows Control Panel.

2. In the System Properties dialog box, click Advanced.

3. In the Advanced tab, click Environment Variables.

4. In the Environment Variables dialog box, under System Variables, click New.

5. In the New System Variable dialog box, enter the following information:

- Variable name: ORACLE_HOSTNAME

- Variable value: The host name of the computer.

6. Click OK, then in the Environment Variables dialog box, click OK.

7. Click OK in the Environment Variables dialog box, then in the System Properties dialog box, click OK.

2.5.3 Installing Oracle Database Companion CD on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose host name has to be used.

2.5.4 Installing a Loopback Adapter

When you install a loopback adapter, the loopback adapter assigns a local IP address for your computer. After you install a loopback adapter on your computer, you have at least two network adapters on your computer: your own network adapter and the loopback adapter. The Oracle Database Companion CD products must have Windows using the loopback adapter as the primary adapter.

The primary adapter is determined by the order in which you installed the adapters: it is the last adapter installed. If you install additional network adapters after you install the loopback adapter, you must uninstall the loopback adapter and reinstall it.

A loopback adapter is required if you are installing on a DHCP computer.

See Also:

"Installing Oracle Database Companion CD on DHCP Computers"

This section covers the following topics:

- Checking if a Loopback Adapter Is Installed on Your Computer

- Installing a Loopback Adapter on Windows Server 2003 or Windows XP

- Installing a Loopback Adapter on Windows Server 2008 and Windows Server 2008 R2

- Removing a Loopback Adapter

2.5.4.1 Checking if a Loopback Adapter Is Installed on Your Computer

To check if a loopback adapter is installed on your computer, run the ipconfig /all command:

SYSTEM_DRIVE:\> ipconfig /all

If there is a loopback adapter installed, you would see a section that lists the values for the loopback adapter. For example:

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.25.129
Subnet Mask . . . . . . . . . . . : 255.255.0.0

2.5.4.2 Installing a Loopback Adapter on Windows Server 2003 or Windows XP

To install a loopback adapter on Windows Server 2003 or Windows XP:

1. Open the Windows Control Panel.

2. Double-click Add Hardware to start the Add Hardware wizard.

3. In the Welcome window, click Next.

4. In the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.

5. In the The following hardware is already installed on your computer window, in the list of installed hardware, select Add a new hardware device, and click Next.

6. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

7. From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.

8. In the Select Network Adapter window, make the following selections:

- Manufacturer: Select Microsoft.

- Network Adapter: Select Microsoft Loopback Adapter.

9. Click Next.

10. In the The wizard is ready to install your hardware window, click Next.

11. In the Completing the Add Hardware Wizard window, click Finish.

12. If you are using Windows Server 2003, restart your computer.

13. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections control panel.

14. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

15. On the General tab, select Internet Protocol (TCP/IP), and click Properties.

16. In the Properties dialog box, click Use the following IP address and do the following:

1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

- 192.168.x.x (x is any value between 0 and 255)

- 10.10.10.10

2. Subnet mask: Enter 255.255.255.0.

3. Record the values you entered, which is required later in this procedure.

4. Leave all other fields empty.

5. Click OK.

17. Click OK.

18. Close Network Connections.

19. Restart the computer.

20. Add a line to the SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc\hosts file with the following format, after the localhost line:

IP_address   host_name.domain_name   host_name

where:

- IP_address is the non-routable IP address you entered in step 16.

- host_name is the name of the computer.

- domainname is the name of the domain.

For example:

10.10.10.10   mycomputer.mydomain.com   mycomputer

21. Check the network configuration:

1. Open System in the Control Panel, and select the Computer Name tab. In Full computer name, make sure you see the host name and the domain name, for example, sales.us.mycompany.com.

2. Click Change. In Computer name, you should see the host name, and in Full computer name, you should see the host name and domain name. Using the previous example, the host name would be sales and the domain would be us.mycompany.com.

3. Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.mycompany.com.

2.5.4.3 Installing a Loopback Adapter on Windows Server 2008 and Windows Server 2008 R2

To install a loopback adapter on Windows Server 2008 or Windows Server 2008 R2:

1. Open the Windows Control Panel.

2. Double-click Add Hardware to start the Add Hardware wizard.

3. In the Welcome window, click Next.

4. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from the list, and click Next.

5. From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.

6. In the Select Network Adapter window, make the following selections:

- Manufacturer: Select Microsoft.

- Network Adapter: Select Microsoft Loopback Adapter.

7. Click Next.

8. In the The wizard is ready to install your hardware window, click Next.

9. In the Completing the Add Hardware Wizard window, click Finish.

10. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections control panel.

11. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

12. On the General tab, select Internet Protocol (TCP/IP), and click Properties.

13. In the Properties dialog box, click Use the following IP address and do the following:

1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

- 192.168.x.x (x is any value between 0 and 255)

- 10.10.10.10

2. Subnet mask: Enter 255.255.255.0.

3. Record the values you entered, which is required later in this procedure.

4. Leave all other fields empty.

5. Click OK.

14. Click OK.

15. Close Network Connections.

16. Restart the computer.

17. Add a line to the SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc\hosts file with the following format, after the localhost line:

IP_address   host_name.domain_name   host_name

where:

- IP_address is the non-routable IP address you entered in step 13.

- host_name is the name of the computer.

- domain_name is the name of the domain.

For example:

10.10.10.10   mycomputer.mydomain.com   mycomputer

18. Check the network configuration:

1. Open System in the Control Panel, and select the Computer Name tab. In Full computer name, make sure you see the host name and the domain name, for example, sales.us.mycompany.com.

2. Click Change. In Computer name, you should see the host name, and in Full computer name, you should see the host name and domain name. Using the previous example, the host name would be sales and the domain would be us.mycompany.com.

3. Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.mycompany.com.

2.5.4.4 Removing a Loopback Adapter

To remove a loopback adapter:

1. Display System in the Windows Control Panel.

2. In the Hardware tab, click Device Manager.

3. In the Device Manager window, expand Network adapters. You should see Microsoft Loopback Adapter.

4. Right-click Microsoft Loopback Adapter and select Uninstall.

5. Click OK.

3 Installing the Oracle Database Companion CD Software

This chapter covers the following topics:

- General Steps for Installing Companion CD Products

- Accessing the Installation Software

- Installing Oracle HTML DB and Oracle HTTP Server

- Installing Oracle Database 10g Products

- Installing Oracle Database 10g Companion Products

- Removing the Oracle Database Companion CD Software

3.1 General Steps for Installing Companion CD Products

After completing the tasks in Chapter 1 and Chapter 2, follow these general steps to install the Companion CD products:

1. Consider the following issues:

- Installing in interactive mode or in silent or noninteractive mode: The instructions in this chapter are written for interactive installations. If you prefer to perform the installation in silent mode noninteractive mode using response files—for example, if your site requires multiple installations—read Appendix A, "Installing Oracle Database Companion CD Using Response Files" for more information.

- Installing in a Different Language: See "Installing and Using Oracle Components in Different Languages" for language considerations.

2. Use the procedures under "Accessing the Installation Software" if you install the software from a hard drive or install remotely.

3. Follow the steps in these sections to complete the installation, depending on the products you want to install:

- "Installing Oracle HTML DB and Oracle HTTP Server"
You must install Oracle HTML DB in an Oracle HTTP Server home. If a current Oracle HTTP Server has not been installed yet, the installation process enables you to install both of these products.

- "Installing Oracle Database 10g Products"
If you plan to use Oracle Workflow server, which is included in the Oracle Database 10g products, you must complete the steps under "Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" before installing the Oracle Workflow middle tier components. The Oracle Workflow middle tier components are available with the Oracle Database 10g Companion Products.

- "Installing Oracle Database 10g Companion Products"
This section explains how to install Oracle Workflow middle tier components.

3.2 Accessing the Installation Software

The Oracle Database software is available on DVD. Do not use Oracle Universal Installer from an earlier release to install components from this release.

If you install the Oracle Database Companion CD products using any of the following scenarios, follow the procedures in this section before continuing to the installation instructions.

- Copying Oracle Database Software to Hard Disk

- Installing from a Remote DVD Drive

- Installing on Remote Computers Through Remote Access Software

3.2.1 Copying Oracle Database Software to Hard Disk

Instead of installing from the Oracle Database Companion CD products DVD, you can copy the contents of the DVD to a hard drive and install from there. This might be easier if you plan to install many instances of the Oracle Database Companion CD products on your network, or if the computers where you want to install the products do not have DVD drives.

To copy the contents of the installation media to a hard disk:

1. Create a directory on your hard drive. For example:

c:\install\companion

2. Copy the contents of the installation media to the directory that you just created.

3. After you have copied all of the required installation files, you can install the Oracle Database Companion CD products.

3.2.2 Installing from a Remote DVD Drive

If the computer where you want to install the Oracle Database Companion CD products does not have a DVD drive, you can perform the installation from a remote DVD drive. Check the following points:

- On the Remote Computer, Share the DVD Drive

- On the Local Computer, Map the DVD Drive

3.2.2.1 On the Remote Computer, Share the DVD Drive

The remote DVD drive must allow shared access. To set this up, perform these steps on the remote computer that has the DVD drive:

1. Log in to the remote computer as an Administrator user.

2. Start Windows Explorer.

3. Right-click the DVD drive letter and choose Sharing (or Sharing and Security).

4. Click the Sharing tab and do the following:

1. Select Share this folder.

2. In Share name, give it a share name such as dvd. Use this name when you map the DVD drive on the local computer. Under "On the Local Computer, Map the DVD Drive" see Step d under Step 1.

3. Click Permissions. You need at least "read" permission for the user who accesses it to install Oracle Database.

4. Click OK when you are finished.

5. Insert the Oracle Database installation media into the DVD drive.

3.2.2.2 On the Local Computer, Map the DVD Drive

Perform these steps on the local computer to map a remote DVD drive and to run Oracle Universal Installer from the mapped drive:

1. Map the remote DVD drive.

1. Start Windows Explorer on the local computer.

2. From the Tools menu, select Map Network Drive to display the Map Network Drive dialog.

3. Select a drive letter to use for the remote DVD drive.

4. In Folder, enter the location of the remote DVD drive using the following format:

\\remote_hostname\share_name

where:

- remote_hostname is the name of the remote computer with the DVD drive.

- share_name is the share name that you entered in Step 4 of the previous procedure. For example

\\computer2\dvd

5. If you connect to the remote computer as a different user, Click different user name, and enter the username.

6. Click Finish.

2. Run Oracle Universal Installer from the mapped DVD drive.

3.2.3 Installing on Remote Computers Through Remote Access Software

To install and run the Oracle Database Companion CD products on a remote computer (that is, the remote computer has the hard drive and runs these components), and you do not have physical access to the computer, you still can perform the installation on the remote computer if it is running remote access software such as VNC or Symantec pcAnywhere. You also need the remote access software running on your local computer.

You can install the Oracle Database Companion CD products on the remote computer in one of two ways:

- If you have copied the contents of the Oracle Database Companion CD products DVD to a hard drive, you can install from the hard drive.

- You can insert the DVD into a drive on your local computer, and install from the DVD.

3.2.3.1 Installing on Remote Computers from a Hard Drive

If you have copied the contents of the Oracle Database Companion CD products DVD to a hard drive, you can install from the hard drive.

The steps that you must complete are:

1. Ensure that the remote access software is installed and running on the remote and local computers.

2. Share the hard drive that contains the Oracle Database Companion CD products DVD.

3. On the remote computer, map a drive letter to the shared hard drive. You would use the remote access software to do this on the remote computer.

4. Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared hard drive.

3.2.3.2 Installing on Remote Computers from a Remote DVD Drive

You can insert the DVD into a drive on your local computer, and install from the DVD. This is similar to the scenario described in "Installing from a Remote DVD Drive".

The steps that you must complete are:

1. Ensure that the remote access software is installed and running on the remote and local computers.

2. On the local computer, share the DVD drive.
On the remote computer, map a drive letter to the shared DVD drive. You would use the remote access software to do this on the remote computer.

These steps are described in "Installing on Remote Computers from a Remote DVD Drive".

3. Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared DVD drive.

3.3 Installing Oracle HTML DB and Oracle HTTP Server

This section covers the following topics:

- Recommended Preinstallation Task for Oracle HTML DB

- Oracle Home Location for Oracle HTML DB and Oracle HTTP Server

- Procedure for Installing Oracle HTML DB and Oracle HTTP Server

3.3.1 Recommended Preinstallation Task for Oracle HTML DB

Before you install Oracle HTML DB, back up the Oracle database in that you plan to use for the installation. You can use Oracle Database Recovery Manager, which is included the Oracle Database installation, to perform the backup.

See Also:

Oracle Database Backup and Recovery Basics

3.3.2 Oracle Home Location for Oracle HTML DB and Oracle HTTP Server

When you install the Oracle HTML DB installation type, you can install either Oracle HTML DB or Oracle HTTP Server, or both Oracle HTML DB and Oracle HTTP Server.

Oracle home locations for these two products are as follows:

- Oracle HTML DB: You must install Oracle HTML DB into an Oracle home that contains Oracle HTTP Server. In a new installation, install Oracle HTML DB into the same home as Oracle HTTP Server. If Oracle HTTP Server is installed, you can install Oracle HTML DB into the Oracle home where Oracle HTTP Server is installed.

- Oracle HTTP Server: You must install Oracle HTTP Server in a new Oracle home. You can install Oracle HTTP Server on the same system, if each installation uses a separate Oracle home directory.

3.3.3 Procedure for Installing Oracle HTML DB and Oracle HTTP Server

This section explains how to install Oracle HTML DB using either of the following scenarios:

- Installing both a new Oracle HTML DB and Oracle HTTP Server: Oracle Universal Installer creates an Oracle HTTP Server home in which to install Oracle HTML DB.

- Installing Oracle HTML DB into an existing Oracle HTTP Server home: You can either install a new Oracle HTML DB or upgrade an existing HTML DB into an existing Oracle HTTP Server home.

To install Oracle HTML DB and Oracle HTTP Server:

1. Log on as a member of the Administrators group to the computer on which to install Oracle components.
If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

2. Ensure that the Oracle database that you plan to use for Oracle HTML DB is accessible and running.
You can use the Windows Services utility, located either in the Windows Control Panel or from the Administrative Tools menu (under Start and then Programs), to check that the Oracle database service is running. In the Services listing, names of Oracle databases are preceded with OracleService. Right-click the name of the database service you want and from the drop-down menu, choose Start.

3. Delete the ORACLE_HOME environment variable (from the System Control Panel) if it exists.
Refer to your Microsoft online help for more information about deleting environment variables.

Note:

The ORACLE_HOME environment variable is automatically set in the registry. Manually setting this variable prevents installation.

4. Insert the Oracle Database installation media and navigate to the companion directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
Use the same installation media to install Oracle Database on all supported Windows platforms.

5. Double-click setup.exe to start Oracle Universal Installer.

6. In the Welcome window click Next.

7. In the Select a Product to Install window, choose Oracle HTML DB and click Next.

8. In the Select Installation Type window, select a following choice 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 into a new Oracle home.

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

9. In the Specify Home Details window, enter the following:

- Name: If you chose Oracle HTML DB and Oracle HTTP Server in the previous step, enter a new Oracle home. If you chose Oracle HTML DB only, select the name of the existing Oracle HTTP Server home that Oracle HTML DB uses.

- Path: Enter the directory location for the Oracle home that you specified under Name. Do not enter a directory path that has spaces. After you enter a correct directory path, Oracle Universal Installer creates a new directory for you.

See also:

"Identifying the Oracle home Directory Location" for information on finding the Oracle home. Select each home and search for Apache Standalone. Oracle HTTP Server is listed as Apache Standalone in the Specify Home Details window.

10. Click Next.

11. In the Available Product Components window, select the additional components you would like to have installed as part of Oracle HTML DB, and then click Next.

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

13. Click Next.

14. In the Specify HTML DB Database Details window, enter the information required to configure Oracle HTML DB.

- Hostname
Specify the host name of the system where the database is installed. If the host name is the local host, enter the name of the computer (for example, myserver.us.mycompany.com), 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 current port number for your Oracle Database installation, check its tnsnames.ora file, which by default is located in ORACLE_BASE\ORACLE_HOME\network\admin.

- Database Service Name
Specify the database service name for the database where you want to install the Oracle HTML DB database objects, for example, sales. (You can find the database service names in the tnsnames.ora file.) 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 an Oracle database. The database that you choose must be a release 9.2.0.3 or later database. If you plan to use the 10g release of Oracle HTTP Server, Oracle Universal Installer automatically creates a database access descriptor (DAD) in the mod_plsql configuration file and directory aliases in the Oracle HTTP Server configuration file httpd.conf, based on the information you enter during installation. However, if you plan to use a release 9i Release 2 of Oracle HTTP Server, you must create these settings manually by using procedure described in the postinstallation steps in Chapter 4.

- TABLESPACE Name
Enter the name of the tablespace where 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 to use for the Oracle HTML DB schemas (users). These schemas 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.

15. Click Next.

16. In the Summary window, check the list of products that has to be installed, and click Install.

17. When the installation completes, click Exit and then click Yes to exit from Oracle Universal Installer.

18. Optionally, delete the OraInstalldate_time directory to remove the temporary files that were created during the installation process. The OraInstalldate_time directory holds about 45 MB of files. This directory is created in the location set by the TEMP environment variable setting.
Restarting your computer also removes the OraInstalldate_time directory.

See Also:

- Chapter 4, "Oracle Database Companion CD Postinstallation Tasks" for information on tasks that you must complete after you have installed the Oracle HTML DB and Oracle HTTP Server

- "Installing and Configuring Oracle HTML DB on a Remote Oracle Database" to install additional Oracle HTML DB instances in a remote Oracle database

3.4 Installing Oracle Database 10g Products

This section covers the following topics:

- Oracle Home Location for the Oracle Database 10g Products

- Procedure for Installing Oracle Database 10g Products

- Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation

3.4.1 Oracle Home Location for the Oracle Database 10g Products

You must install Oracle Database 10g Products in an existing Oracle Database 10g release 2 (10.2) Oracle home. These products are:

- Oracle JDBC Development Drivers

- Oracle SQLJ

- Database Examples

- Oracle Text Knowledge Base

- JAccelerator (NCOMP)

- Intermedia Image Accelerator

- Oracle Workflow

3.4.1.1 Identifying the Oracle home Directory Location

Before you install Oracle Database 10g Products into an existing Oracle home, you must identify the location of this Oracle home. If you do not know the path of the Oracle home directory, you can check it using Oracle Universal Installer.

To check the path of the Oracle home directory:

1. From the Start menu, choose Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer.

2. When the Welcome window appears, click Installed Products.
The Inventory window appears, listing all of the Oracle homes on the system and the products installed in each Oracle home.

3. In the Inventory window, expand each Oracle home and locate Oracle Database 10.2.0.1.0.

4. Click Close and then Cancel to exit Oracle Universal Installer.

5. Have the Oracle home name available when you begin installing Oracle Database 10g Products, described next.

3.4.2 Procedure for Installing Oracle Database 10g Products

In brief, you first run Oracle Universal Installer to install the Oracle Database 10g Products. Afterwards, you configure Oracle Workflow server before you install the Oracle Workflow middle tier components.

To install Oracle Database 10g Products:

1. Log on as a member of the Administrators group to the computer on which to install Oracle components.
If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

2. Ensure that the Oracle database that you plan to use for Oracle Workflow is accessible and running.
You can use the Windows Services utility, located either in the Windows Control Panel or from the Administrative Tools menu (under Start and then Programs), to check that Oracle Database is running. Names of Oracle databases are preceded with OracleService. Right-click the name of the service and from the menu, choose Start.

3. Delete the ORACLE_HOME environment variable (from the System Control Panel) if it exists.
Refer to your Microsoft online help for more information about deleting environment variables.

Note:

The ORACLE_HOME environment variable is automatically set in the registry. Manually setting this variable prevents installation.

4. Insert the Oracle Database installation media and navigate to the companion directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
Use the same installation media to install Oracle Database on all supported Windows platforms.

5. Double-click setup.exe to start Oracle Universal Installer.

6. In the Welcome window click Next.

7. In the Select a Product to Install window, choose Oracle Database 10g Products and click Next.

8. In the Specify Home Details window, do the following:

1. Name: Verify that the Oracle home specified is the Oracle Database Oracle home. (The default Oracle home is offered.)

2. Path: Enter the directory location of the Oracle Database Oracle home where you want to install the Oracle home files. (The directory of the default Oracle home is offered.) Do not enter a directory path that has spaces. After you enter a correct directory path, Oracle Universal Installer creates a new directory for you.

See also:

"Identifying the Oracle home Directory Location" for information on finding the correct Oracle home

9. Click Next.

10. In the Product-specific Prerequisite Checks window, check for and correct any errors that may have occurred when Oracle Universal Installer checked your system.

11. Click Next.

12. In the Summary window, check the list of products has to be installed, and click Install.

13. When the installation completes, click Exit and then click Yes to exit from Oracle Universal Installer.

14. Optionally, delete the OraInstalldate_time directory to remove the temporary files that were created during the installation process. The OraInstalldate_time directory holds about 45 MB of files. This directory is created in the location set by the TEMP environment variable setting.
Restarting your computer also removes the OraInstalldate_time directory.

15. Restart Oracle HTTP Server. For example:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server

See Also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

3.4.3 Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation

After you have installed Oracle Workflow server, you must configure it before you install the Oracle Workflow middle tier components. You use Oracle Workflow Configuration Assistant to configure Oracle Workflow. The following steps explain how to run Oracle Workflow Configuration Assistant by using its graphic user interface.

See Also:

"Running Oracle Workflow Configuration Assistant in Noninteractive Mode" for information on running Oracle Workflow Configuration Assistant in noninteractive mode.

To prepare Oracle Workflow server for the Oracle Workflow middle tier components:

1. Ensure that the Oracle database that you plan to use for Oracle Workflow is accessible and running.
You can use the Windows Services utility, located either in the Windows Control Panel or from the Administrative Tools menu (under Start and then Programs), to check that Oracle Database is running. Names of Oracle databases are preceded with OracleService. Right-click the name of the service and from the menu, choose Start.

2. From the Start menu, choose Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools, then Workflow Configuration Assistant.

3. In the Welcome to Oracle Workflow Configuration Assistant window, enter the following information:

- Install Option - Select either Server Only or Add Language.
If you choose the Server Only option, Workflow Configuration Assistant installs Oracle Workflow into the Oracle database.

Note:

To upgrade to Oracle Workflow release 2.6.4, ensure that the existing Oracle Workflow server is release 2.6.2 or higher.

If you chose the Add Language installation option, select the language abbreviation for the language to add. You must install Oracle Workflow before you can add a language.

See Also:

Oracle Database Globalization Support Guide for a list of language abbreviations used by Oracle database

- Workflow Account - Enter the name to use for the Oracle Workflow database account or accept the default name, typically owf_mgr.
The default tablespace for this account is USERS and the temporary tablespace is TEMP. You can change the tablespace if necessary.

Note:

If you are upgrading an existing installation of Oracle Workflow, enter the name and password for the existing Oracle Workflow database account.

- Workflow Password - Enter a password for the Oracle Workflow account.

- SYS Password - Enter the password for the SYS account of the Oracle Database installation on the system. The password is mandatory for Oracle Workflow Server installations but not if you are adding a language.

- TNS Connect Descriptor - The database connect string in TNS format:

(DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST =
host_name)(PORT = port_number))) (CONNECT_DATA = (SERVICE_NAME =
database_service_name)))

The connect string is stored in the tnsnames.ora file, which in a default installation is located in ORACLE_BASE\ORACLE_HOME\network\admin. An easy way to find the connect string in a single-line format is to run the tnsping command at a command prompt, output the results into a text file, and then copy and paste the connect string into the TNS Connect Descriptor box. For example, to get the connect string for a server named mau, you could enter:

c:\> tnsping mau > tns.txt

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

Note:

If you are upgrading an existing Oracle Workflow installation in which you implemented Oracle Internet Directory integration, 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 click OK. After the installation, you can update these values if necessary in the Global Workflow preferences Web page.

See Also:

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

- LDAP Host Name - Enter the host on which the Lightweight Directory Access Protocol (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 username used to connect to the LDAP server. This username 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.

- Changelog DN - Enter the LDAP node where change log files are located. For example:

cn=changelog

- 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, see Oracle Workflow Administrator's Guide.

5. If you do not want to integrate with Oracle Internet Directory, leave the Enter LDAP Parameters check box blank.

6. To enter configuration parameters for the seeded Java-based notification mailer service component Workflow Notification Mailer, select the Enter Mailer Parameters check box and then select Get Mailer Values to display the Workflow Mailer Parameters. Enter values for the following parameters and then click OK.

- Inbound EMail Account: Server Name:

- Server Name - Enter the name of the inbound IMAP mail server.

- Username - Enter the username of the mail account where the notification mailer receives e-mail messages.

- Password - Enter the password of the mail account specified in the Username parameter.

- Outbound EMmail Account - Enter the name of the outbound SMTP mail server.

- 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.

- 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:

- HTML Agent - The HTML Agent is 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 installed Oracle HTTP Server, 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 complete the Oracle HTTP Server and Oracle Workflow installations.

See Also:

"Setting Up Oracle Workflow" in Oracle Workflow Administrator's Guide

- 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 update the notification mailer configuration values if necessary 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:

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

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

8. Choose Submit to begin the configuration or choose Quit to exit Workflow Configuration Assistant without performing the configuration.

9. When the configuration is complete, a confirmation window appears. Click OK.
You can check the status of the configuration by reviewing the ORACLE_BASE\ORACLE_HOME\wf\install\workflow.log file.

If you want to add additional languages to Oracle Workflow, rerun Oracle Workflow Configuration Assistant with the Add Language install option.

Do not rerun Oracle Workflow Configuration Assistant with the Server Only install option to add additional Oracle Workflow schemas, because only one Oracle Workflow schema is allowed in each Oracle home. If you attempt it, the configuration assistant succeeds, but you may encounter errors later on in the Oracle Workflow middle tier services.

If you re-create the Oracle Workflow schema, first drop the existing schema and uninstall Oracle Workflow. Then follow the instructions in this chapter to reinstall Oracle Workflow and create a new Oracle Workflow schema using the Oracle Workflow Configuration Assistant.

See Also:

Chapter 4, "Oracle Database Companion CD Postinstallation Tasks" for tasks that you must complete after you have installed Oracle Workflow server

3.5 Installing Oracle Database 10g Companion Products

This section covers the following topics:

- Oracle Home Location for Oracle Database 10g Companion Products

- Procedure for Installing Oracle Database 10g Companion CD Products

3.5.1 Oracle Home Location for Oracle Database 10g Companion Products

When you install Oracle Database 10g Companion Products, you can install either Oracle HTTP Server, Oracle Workflow middle tier components, or both Oracle HTTP Server and Oracle Workflow middle tier components.

Oracle home locations for these two products are as follows:

- Oracle Workflow middle tier components: You must install Oracle Workflow middle tier components into a new Oracle home. In a new installation, install Oracle Workflow middle tier components into the same home as Oracle HTTP Server. If Oracle HTTP Server is installed, you can install Oracle Workflow middle tier components into the Oracle home where Oracle HTTP Server is installed.

- Oracle HTTP Server: You must install Oracle HTTP Server in a new Oracle home. You can install Oracle HTTP Server on the same system, if each installation uses a separate Oracle home directory.

3.5.2 Procedure for Installing Oracle Database 10g Companion CD Products

To install Oracle Database 10g Companion CD Products:

1. Ensure that you have first installed Oracle Workflow server from the Oracle Database 10g Products installation type and run Workflow Configuration Assistant to configure Oracle Workflow.

2. Log on as a member of the Administrators group to the computer on which to install Oracle components.
If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

3. Delete the ORACLE_HOME environment variable if it exists. Refer to your Microsoft online help for more information about deleting environment variables.

Note:

The ORACLE_HOME environment variable is automatically set in the registry. Manually setting this variable prevents installation

4. Insert the Oracle Database installation media and navigate to the companion directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
Use the same installation media to install Oracle Database on all supported Windows platforms.

5. Double-click setup.exe to start Oracle Universal Installer.

6. In the Welcome window click Next.

7. In the Select a Product to Install window, choose Oracle Database 10g Companion Products and click Next.

8. In the Specify Home Details window, do the following:

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

2. Path: Enter the directory location for the Oracle home. If the directory does not exist, then Oracle Universal Installer creates it for you. Do not enter a directory path that has spaces. After you enter a correct directory path, Oracle Universal Installer creates a new directory for you.

See Also:

"Identifying the Oracle home Directory Location" for information on finding the correct Oracle home.

9. Click Next.

10. In the Available Product Components window, select from the following products and then click Next:

- Apache Standalone (this option installs Oracle HTTP Server)

- Oracle Workflow Middle Tier

Note:

If you are installing Oracle Workflow middle tier in a new Oracle home, you must choose Oracle HTTP Server.

11. In the Product-specific Prerequisite Checks window, 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 into an existing Oracle HTTP Server home, you may manually verify the prerequisite check to confirm the selected Oracle home.

12. Click Next.

13. In the Oracle Workflow Middle Tier Configuration window, specify the configuration settings needed for the Oracle Workflow middle tier.
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. The Oracle Universal Installer completes these tasks for you using the information that you specify in this step.

Enter the following information:

- Workflow Schema
Specify the user name (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 where the database is installed. If the host name is the local host, enter the name of the computer, for example, myserver.us.mycompany.com, 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. You can find this information in the Oracle database's tnsnames.ora file. In a default installation, this file is located in ORACLE_BASE\ORACLE_HOME\network\admin.

- Oracle SID
Specify the database instance identifier (SID) for the database where you installed the Oracle Workflow server database objects.

14. In the Oracle Workflow Middle Tier Configuration window, enter a password for the Oracle Workflow schema you created in the previous step, and then click Next.

15. In the Oracle Apache Installation window, enter the following information required to configure Oracle Workflow middle tier and click Next.

- Enter Password
Specify the password for the Workflow user (typically OWF_MGR) that you specified on the previous window. This password is used for the mod_plsql database access descriptor.

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

16. In the Summary window, check the list of products that are installed, and click Install.

17. In the End of Installation window, make a note of the URLs that Oracle HTTP Server uses.

Note:

These URLs are also listed in the ORACLE_BASE\ORACLE_HOME\Apache\Apache\setupinfo.txt file.

18. Click Exit and click Yes to exit from the Oracle Universal Installer.

19. Optionally, delete the OraInstalldate_time directory to remove the temporary files that were created during the installation process. The OraInstalldate_time directory holds about 45 MB of files. This directory is created in the location set by the TEMP environment variable setting.
Restarting your computer also removes the OraInstalldate_time directory.

20. Restart Oracle HTTP Server. For example:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server

See Also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

See Also:

Chapter 4, "Oracle Database Companion CD Postinstallation Tasks" for information on tasks that you must complete after you have installed Oracle HTTP Server

3.6 Removing the Oracle Database Companion CD Software

This section covers the following topics:

- Removing Oracle HTML DB from Oracle Database

- Removing Oracle Workflow

- Removing Oracle Database Products and Oracle Database Companion CD Products

3.6.1 Removing Oracle HTML DB from Oracle Database

After you have successfully deinstalled Oracle HTML DB using the Oracle Universal Installer, you can remove Oracle HTML DB from the database. Be aware that following these instructions renders inoperable any previous version of HTML DB you may have installed on your system.

1. Connect to the database as a privileged user, such as SYS or SYSTEM, for example:

c:\> sqlplus sys/SYS_password as sysdba

2. Execute the following commands:

SQL> ALTER SESSION SET current_schema = FLOWS_010600;
SQL> EXEC wwv_flow_upgrade.drop_public_synonyms;
SQL> ALTER SESSION SET current_schema = SYSTEM;
SQL> DROP USER FLOWS_010600 CASCADE;
SQL> DROP USER flows_files CASCADE;
SQL> DROP USER htmldb_public_user CASCADE;

3.6.2 Removing Oracle Workflow

To remove Oracle Workflow:

1. Use Oracle Universal Installer to uninstall Oracle Workflow server or the Oracle Workflow middle tier components.

See Also:

"Removing Oracle Database Products and Oracle Database Companion CD Products"

2. Drop the Oracle Workflow schema from the database.
Log in to the database as the SYS user:

c:\> sqlplus sys/SYS_password as sysdba

Enter the following DROP USER command. For example, if the Oracle Workflow schema is named owf_mgr, you would enter:

SQL> drop user owf_mgr cascade

3.6.3 Removing Oracle Database Products and Oracle Database Companion CD Products

The following steps describe how to use Oracle Universal Installer to remove Oracle software:

Note:

Always use Oracle Universal Installer to remove Oracle software. Do not delete any Oracle home directories without first using Oracle Universal Installer to remove the software.

Stop the Oracle HTTP Server and Oracle Process Manager and Notification services.

See also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

1. From the Start menu, select Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer.

2. When the Welcome window appears, click Deinstall Products.
The Inventory window appears, listing all of the Oracle homes on the system and the products installed in each Oracle home.

3. In the Inventory window, select the Oracle home and the Oracle products to remove.

4. To delete specific products, select them in the tree window.

5. Click Remove.
A confirmation window appears asking you to confirm to deinstall the products and their dependent components.

6. Click Yes.
A progress indicator appears as the software is removed.

4 Oracle Database Companion CD Postinstallation Tasks

This chapter describes the following tasks that you must complete after you install the software:

- Installing the Latest Patch Set Release

- Postinstallation Tasks for Oracle HTTP Server

- Postinstallation Tasks for Oracle HTML DB

- Postinstallation Tasks for Oracle Workflow Server

Note:

On Windows Server 2008, and Windows Server 2008 R2, utilities such as Oracle Universal Installer, and Oracle Process Management Notification (OPMN) require Administrator privileges.

4.1 Installing the Latest Patch Set Release

Oracle recommends installing the latest patch set release after you have successfully installed the Oracle Companion CD components. Doing so ensures that you have the latest update of Oracle Database Companion CD.

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in to My Oracle Support (formerly OracleMetaLink), select Patches from the left-hand column.

To find and download patches:

1. Go to the My Oracle Support (formerly OracleMetaLink) Web site at

https://support.oracle.com

2. Log in to My Oracle Support (formerly OracleMetaLink).

Note:

If you are not an My Oracle Support (formerly OracleMetaLink) registered user, then click Register and follow the registration instructions.

3. Click Patches & Updates on the main My Oracle Support (formerly OracleMetaLink) page.

4. In the Patch Search section, specify the Patch Name, Number, or Sun CR ID, then click Search.

- If you select the Patch Name or Number option, you can specify the exact patch names or numbers.
If you select Sun CR ID option instead, specify the exact change request.

- If you choose the Platform option, you have the option of selecting a maximum of 5 platforms from the list.
If you choose Language option instead, you have the option of selecting one or more languages from the list.

You can also search by Product, Release, and Platform using the Product or Family (Advanced Search) link.

5. Select the patch to download. Patch sets for Oracle databases are identified as x.x.x.x.x PATCH SET FOR ORACLE DATABASE SERVER.

6. Review the README file before proceeding with the download.
Each patch has a README file with installation requirements and instructions. Some patches install with Oracle Universal Installer; others require special procedures. Oracle recommends that you always read the README file before proceeding.

7. Download and install the patch.

4.2 Postinstallation Tasks for Oracle HTTP Server

If you installed Oracle HTTP Server, complete the tasks described in the following sections.

This section contains these topics:

- Backing Up the Files

- Migrating from a Previous Release of Oracle HTTP Server

- Migrating the httpd.conf Configuration File from an Earlier Oracle HTTP Server

- Migrating Database Access Descriptors Used by mod_plsql

- Enabling the High Availability Features of Oracle HTTP Server

4.2.1 Backing Up the Files

Oracle recommends that you back up the Oracle HTTP Server configuration and log files. The configuration and log files are located in the following locations:

ORACLE_BASE\ORACLE_HOME\opmn\conf
ORACLE_BASE\ORACLE_HOME\opmn\logs
ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf
ORACLE_BASE\ORACLE_HOME\Apache\Apache\logs
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf

Oracle recommends that you back up the entire Oracle home directory before applying a patch.

4.2.2 Migrating from a Previous Release of Oracle HTTP Server

If you are using a version of Oracle HTTP Server that was installed with a previous release of Oracle Database on this system, you can migrate the configuration of that HTTP server to the current release.

There are two parts to the migration process:

- Migrating the httpd.conf Configuration File from an Earlier Oracle HTTP Server

- Migrating Database Access Descriptors Used by mod_plsql

4.2.3 Migrating the httpd.conf Configuration File from an Earlier Oracle HTTP Server

To migrate the configuration of an earlier release of Oracle HTTP Server to the current release, you must copy and modify the httpd.conf file used by that release.

The following sections describe how to complete this task:

- Step1: Copying and Opening the httpd.conf File

- Step 2: Making Global Changes

- Step 3: Modifying the List of LoadModule Directives

- Step 4: Removing Directives and Sections for Unsupported Features

- Step 5: Modifying Port Numbers

- Step 6: Modifying Existing Sections and Directives

- Step 7: Adding New Sections and Directives

- Step 8: Migrating Your Server Certificate and Private Key

- Step 9: Modifying the Secure Socket Layer Sections and Directives

- Step 10: Copying or Moving the Required Files to New Directories

4.2.3.1 Step1: Copying and Opening the httpd.conf File

Copy the Oracle HTTP Server configuration httpd.conf file used by the previous release to the current release configuration file directory.

To copy and open the http.conf file:

1. Change directory to the configuration file directory for the current release of Oracle HTTP Server:

c:\> cd ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf

2. Back up the httpd.conf file:

c:\> copy httpd.conf httpd.conf.orig

3. Back up the configuration file directory for the current release of Oracle HTTP Server:

c:\> copy ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf ORACLE_BASE\ORACLE_HOME

4. Change directory to the configuration file directory:

c:\> cd ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf

5. Copy the httpd.conf file used by the previous release to the current directory, for example:

c:\> copy \OLD_ORACLE_HOME\Apache\Apache\conf\httpd.conf

6. Open the httpd.conf file in any text editor.

4.2.3.2 Step 2: Making Global Changes

To make the following global changes to the httpd.conf file:

1. Search for all occurrences of the old Oracle home directory path and replace them with the current Oracle home directory path.

2. Change all occurrences of mod_ssl.c to mod_ossl.c.

Note:

Oracle recommends that you change the SSL related directives in the httpd.conf file, even if SSL is not used.

4.2.3.3 Step 3: Modifying the List of LoadModule Directives

To modify the list of LoadModule directives:

1. Remove the following directives:

LoadModule oprocmgr_module    libexec\liboprocmgr.so
LoadModule rewrite_module     libexec\mod_rewrite.so

Note:

You must add a LoadModule directive for the mod_rewrite module later in the file.

2. Add the following directive, which loads the onsint module, immediately before the <IfDefine SSL> section:

LoadModule onsint_module      libexec\mod_onsint.so

3. In the LoadModule directive in the <IfDefine SSL> section, change ssl_module to ossl_module and change mod_ssl.so to mod_ossl.so, as follows:

LoadModule ossl_module      libexec\mod_ossl.so

4.2.3.4 Step 4: Removing Directives and Sections for Unsupported Features

To remove all directives and sections for unsupported features:

1. Remove the following directives from the <IfModule mod_alias.c> section:

Alias /jservdocs/ "\ORACLE_BASE\ORACLE_HOME\Apache\Jserv\docs\"
Alias /soapdocs/ "\ORACLE_BASE\ORACLE_HOME\soap\"

2. Remove the following directive from the <IfModule mod_fastcgi> section:

FastCGIServer fcgi-bin/echo -initial-env ORACLE_HOME \
-initial-env NLS_LANG

3. Remove the following include directive:

include "/ORACLE_BASE/ORACLE_HOME/Apache/Jserv/etc/jserv.conf"

4. Remove the <IfModule mod_oprocmgr.c> section.

4.2.3.5 Step 5: Modifying Port Numbers

The httpd.conf file is used by previous releases of Oracle HTTP Server that were installed with Oracle HTTP Server or Oracle Database. This file specifies different ports for non-SSL (HTTP) requests depending on whether you started an SSL-enabled server. These ports are shown as port1 and port2 in the following example:

Port port1
Listen port1

<IfModule mod_ossl.c>
Port port2
Listen port2
Listen SSL_port
</IfModule>

To modify the port numbers:

1. If you did not use SSL, remove the following directives:

Port port2
Listen port2

Oracle HTTP Server listens for HTTP requests on port port1.

2. If you used only the ports defined for SSL, change the directives as shown in the following example:

Port port2
Listen port2

<IfModule mod_ossl.c>
Listen SSL_port
</IfModule>

Oracle HTTP Server listens for HTTP requests on port port2 and for HTTPS requests on port SSL_port.

3. If you intend to continue using the previous version of Oracle HTTP Server concurrently with this release, change the ports specified by the Port and Listen directives to unused ports.

4. If you changed SSL_port in the previous step, complete the following steps:

1. Locate the <VirtualHost _default_:SSL_port> directive and ensure that the value of SSL_port matches the value specified by the Listen directive in the <IfModule mod_ossl.c> section.

2. In the <VirtualHost _default_:SSL_port> section, ensure that the port number specified by the Port directive equals SSL_port.

4.2.3.6 Step 6: Modifying Existing Sections and Directives

To modify the following sections and directives in httpd.conf:

1. In the default directory section, <Directory />, add the MultiViews option to the Options directive. For example:

<Directory />
Options FollowSymLinks MultiViews
AllowOverride None
</Directory>

2. In the <IfModule mod_alias.c> section, create a new <IfModule mod_perl.c> section and move the Alias directive that defines the /perl/ alias into this section. For example:

<IfModule mod_alias.c>
...
<IfModule mod_perl.c>
Alias /perl/ "\ORACLE_BASE\ORACLE_HOME\Apache\Apache\cgi-bin\"
</IfModule>
...
</IfModule>

3. Modify the <IfModule mod_dms.c> section as shown in the following example, substituting the appropriate values for the hostname and domain variables:

<IfModule mod_dms.c>
<Location /dms0>
SetHandler dms-handler
Order deny,allow
Deny from all
Allow from localhost hostname.domain hostname
</Location>
</IfModule>

4. In the directive that sets the PERL5LIB environment variable, edit the Perl directory location and version, as shown in the following example:

SetEnv PERL5LIB "\ORACLE_BASE\ORACLE_HOME\perl\5.6.1\lib:\ORACLE_BASE\ORACLE_HOME\perl\site\5.6.1\lib"

Enter this setting on one line.

4.2.3.7 Step 7: Adding New Sections and Directives

To add the following new sections and directives to the http.conf file:

1. Add the following section to protect the WEB-INF directories:

#Protect WEB-INF directory

<DirectoryMatch /WEB-INF/>
Order deny,allow
Deny from all
</DirectoryMatch>

2. Add the following lines before the line that includes the oracle_apache.conf file:

# Include the configuration files needed for mod_oc4j
include "\ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\mod_oc4j.conf"

# Loading mod_rewrite module here as it loads before mod_oc4j
LoadModule rewrite_module     modules/ApacheModuleRewrite.dll

4.2.3.8 Step 8: Migrating Your Server Certificate and Private Key

If you use SSL and have an existing server certificate and private key, you must migrate them to the format required by mod_ossl before using them with this release of Oracle HTTP Server.

To migrate an existing server certificate and private key:

1. Enter a command using the following syntax in a separate terminal window:

\ORACLE_BASE\ORACLE_HOME\Apache\Apache\bin\ssl2ossl -cert cert_file \
-key key_file \
{[ -chain chain_file] |
[ -cafile CA_file] |
[ -capath CA_path] }\
-wallet wallet_path \
[ -certpass key_file_pwd]
[ -wltpass wallet_pwd] \
[ -ssowallet yes] \
[ -validate yes]

The following table lists the recommended value for each option available with the ssl2ossl command:

Note:

You must specify at least one option: -chain, -cafile, or -capath.

Option

Recommended Value

-cert

Use the value specified by the SSLCertificateFile directive in the httpd.conf file for the previous release.

-key

Use the value specified by the SSLCertificateKeyFile directive in the httpd.conf file for the previous release.

-chain

Use the value specified by the SSLCertificateChainFile directive in the httpd.conf file for the previous release, if that directive is not preceded by the comment character (#).
Note: If the SSLCertificateChainFile directive is not specified or is preceded by a comment character, do not specify the -chain option.

-cafile

Use the value specified by the SSLCACertificateFile directive in the httpd.conf file for the previous release.
Note: If the SSLCACertificateFile directive is not specified or is preceded by a comment character, do not specify the -cafile option.

-capath

Use the value specified by the SSLCACertificatePath directive in the httpd.conf file for the previous release.
Note: If the SSLCACertificatePath directive is not specified or is preceded by a comment character, do not specify the -capath option.

-wallet

Specify the path to the directory in which you want to create the wallet. The default value is:

\ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\ssl.wlt\default

-certpass

Specify the password for your private key file, if it is encrypted.

-wltpass

Specify a password for your new wallet.
If you do not specify this option, the ssl2ossl utility prompts you to enter and verify the wallet password.

-ssowallet

Specify the value yes to create a wallet that is compatible with Oracle Single Sign-On.

-validate

Specify the value yes to verify that the wallet to be converted successfully. If you specify this option with the value yes, the wallet is not created.

2. Optionally, enter a command similar to the following to generate an encrypted version of the wallet password you specified in the ssl2ossl command:

ORACLE_BASE\ORACLE_HOME\Apache\Apache\bin\iasobf -p wallet_pwd

Note:

If you specify the -ssowallet option in the ssl2ossl command, you do not complete this step. Otherwise, because the password must be specified in the httpd.conf file, Oracle recommends that you encrypt it.

The output from this command is the encrypted version of the password specified by the -p option. In the following section, you must specify this value for the SSLWalletPassword directive.

4.2.3.9 Step 9: Modifying the Secure Socket Layer Sections and Directives

Note:

Oracle recommends that you change the Secure Socket Layer (SSL) related sections and directives in the httpd.conf file, even if SSL is currently not used.

Make the following changes to the directives contained in the <IfModule mod_ossl.c> sections:

1. Change the setting for the SSLSessionCache directive as follows:

SSLSessionCache shmcb:/ORACLE_BASE/ORACLE_HOME/Apache/Apache/logs/ssl_scache(512000)

2. Change the setting for the SSLCipherSuite directive as follows:

SSLCipherSuite SSL_RSA_WITH_RC4_128_MD5:SSL_RSA_WITH_RC4_128_SHA:SSL_RSA_WITH_3DES_EDE_CBC_SHA:SSL_RSA_WITH_DES_CBC_SHA:SSL_RSA_EXPORT_WITH_RC4_40_MD5:SSL_RSA_EXPORT_WITH_DES40_CBC_SHA

3. Remove the following directives and their associated comments:

SSLRandomSeed
SSLCertificateFile
SSLCertificateKeyFile
SSLCertificateChainFile
SSLCACertificateFile
SSLCACertificatePath
SSLVerifyDepth

4. In the <VirtualHost _default_:SSL_port> section, add the following lines:

#   Server Wallet:
#   The server wallet contains the server's certificate, private key
#   and trusted certificates. Set SSLWallet at the wallet directory
#   using the syntax:  file:<path-to-wallet-directory>
SSLWallet file:\ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\ssl.wlt\default

#   Server Wallet Password:
#   Both clear text wallet password and obfuscated password are allowed
#   here. An obfuscated one is recommended.
#   Examples:
#   SSLWalletPassword <clear_pass>
#   SSLWalletPassword <obfuscated_pass>
#SSLWalletPassword ...

5. If you migrated a server certificate and private key, complete the following steps:

1. Change the value specified by the SSLWallet directive to specify the wallet path, if it is different from the default value.

2. If you did not create a wallet that is compatible with Oracle Single Sign-On (using the -ssowallet yes option in the previous section), remove the comment from the SSLWalletPassword directive and specify the clear-text or encrypted wallet password as its value.

4.2.3.10 Step 10: Copying or Moving the Required Files to New Directories

Copy (or move) any scripts for files from the document root and script directories to the equivalent directories for the new release.

You must copy or move only files that are located in subdirectories of the previous release Oracle home directory. Alias directories in other locations continue to be accessible, because the permissions on these directories and their contents enables the server to read them. If you changed the User or Group directive, you must change these permissions.

Copy the following files, as appropriate

- Files and subdirectories in directories specified by a DocumentRoot or Alias directive

- CGI, Perl, and FastCGI programs and scripts and their associated files in directories specified by a ScriptAlias directive

4.2.4 Migrating Database Access Descriptors Used by mod_plsql

If you used mod_plsql to access a database with the previous release of Oracle HTTP Server, you must migrate the database access descriptors (DADs) to the format required by mod_plsql in the current release. You can use the dadTool.pl Perl script to complete this migration.

To run the dadTool.pl script:

1. Set the ORACLE_HOME environment variable to specify the path to the Oracle home directory for the current release and set the PATH environment variable to include the directory containing the perl executable and the location of the dadTool.pl script.
For example:

c:\> set PATH=%ORACLE_BASE%\%ORACLE_HOME%\Apache\modplsql\conf;
%ORACLE_BASE%\%ORACLE_HOME%\perl\5.6.1\bin\MSWin32-x86;%PATH%

Enter this setting on one line.

2. If ORACLE_BASE\ORACLE_HOME\bin is not in your PATH, include it in the PATH statement.
For example:

c:\> set PATH=c:oracle\product\10.1.0\Db_1\bin;%PATH%

3. Change directory to the mod_plsql configuration directory for the current release of Oracle HTTP Server:

c:\> cd ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf

4. Copy the DAD configuration file (wdbsvr.app) used by the previous release to this directory:

c:\> copy OLD_ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app

5. Enter the following command to run the dadTool script:

c:\> perl dadTool.pl -m

The dadTool script reads the DAD information from the wdbsvr.app file and creates new equivalent DADs in the dads.conf file.

4.2.5 Enabling the High Availability Features of Oracle HTTP Server

If you want to enable the high-availability features of Oracle HTTP Server, you must use Oracle Process Manager and Notification server (OPMN) with Oracle HTTP Server. To use OPMN, you must first start the OPMN service. To start the OPMN service and the Oracle HTTP Server processes, enter the following command:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startall

Note:

The apachectl script is not supported for starting and stopping Oracle HTTP Server in this release.

When the OPMN service is running, you can start, stop, or restart Oracle HTTP Server.

See Also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

To stop the OPMN service and the Oracle HTTP Server processes, enter the following command:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopall

4.3 Postinstallation Tasks for Oracle HTML DB

If you installed Oracle HTML DB, complete the following tasks:

- Restarting Processes

- Configuring Oracle HTTP Server for an Oracle HTML DB Upgrade

- Obfuscating PlsqlDatabasePassword Parameter

- Installing and Configuring Oracle HTML DB on a Remote Oracle Database

4.3.1 Restarting Processes

Restart the processes that you stopped before you began the installation, such as listener and other processes. In addition, restart Oracle HTTP Server.

See Also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

4.3.2 Configuring Oracle HTTP Server for an Oracle HTML DB Upgrade

If you are upgrading Oracle HTML DB from release 1 (10.1) and the password you provided during your initial installation differs from the one you specified during this installation, you must modify the file that contains the Database Access Descriptors (DADs). The following sections describe the parameter you must modify depending upon the type of Oracle HTTP Server in your environment.

Topics in this section include:

- Oracle HTTP Server Release 9.0.3

- Oracle HTTP Server 10g Release 1

Note:

Only perform the tasks that follow if the password you provided during your initial installation differs from the one you specified during the installation.

4.3.2.1 Oracle HTTP Server Release 9.0.3

If you are upgrading Oracle HTML DB and run the version of Oracle HTTP Server included with Oracle Database release 9.2.0.x, you must modify the parameter password in the wdbsvr.app file.

To modify the parameter password in the wdbsvr.app file:

1. Use a text editor and open the wdbsvr.app file.

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app

2. Find the DAD settings for Oracle HTML DB by searching for the following:

DAD_htmldb

3. Edit value next to the parameter password to match the password you provided during the installation.

4. Save your changes.

5. Stop and restart Oracle HTTP Server:

- Stop Oracle HTTP Server: From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.

- Restart Oracle HTTP Server: From the Start menu, select Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.

See Also:

Oracle HTTP Server Administration Guide

4.3.2.2 Oracle HTTP Server 10g Release 1

If you are upgrading Oracle HTML DB and run Oracle HTTP Server 10g release 1, you must modify the parameter PlsqlDatabasePassword in the marvel.conf file.

To modify the parameter PlsqlDatabasePassword in the marvel.conf file:

1. Use a text editor and open the marvel.conf file:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\marvel.conf

2. Find the DAD settings for Oracle HTML DB by searching for the following:

/pls/htmldb

3. Modify the value of the parameter PlsqlDatabasePassword to match the password you provided during installation.

4. Save your changes.

5. Stop and restart Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server

See Also:

"Obfuscating PlsqlDatabasePassword Parameter" and Oracle HTTP Server Administration Guide

4.3.3 Obfuscating PlsqlDatabasePassword Parameter

The PlsqlDatabasePassword parameter specifies the password for logging in to the database. You can use the dadTool.pl script to obfuscate passwords in the dads.conf file.

You can find the dadTool.pl script in the following directory:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf

4.3.3.1 Obfuscating Passwords in a New Oracle HTML DB Installation

In a new Oracle HTML DB installation, the PlsqlDatabasePassword parameter is found in the dads.conf file. To obfuscate passwords in a new installation, run the dadTool.pl utility by following the instructions in the dadTool.README file.

4.3.3.2 Obfuscating Passwords if Upgrading Oracle HTML DB

If you have upgraded from a previous release of Oracle HTML DB, the DAD information is in the file marvel.conf. Before you can run the dadTool.pl script, you must copy the DAD entry from the marvel.conf file to the dads.conf file.

To obfuscate passwords when upgrading:

1. Use a text editor and copy the entry for /pls/htmldb from the marvel.conf file into the dads.conf file, located in:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.conf

2. Run dadTool.pl by following the instructions in the dadTool.README file.

3. Copy the entry for /pls/htmldb from the dads.conf file back into marvel.conf.

4. Remove the entry for /pls/htmldb from the dads.conf file.

4.3.4 Installing and Configuring Oracle HTML DB on a Remote Oracle Database

You can use the htmldbca command-line tool to perform the following activities:

- Install and configure Oracle HTML DB onto a remote Oracle database.

- Upgrade an existing Oracle HTML DB in a remote Oracle database.

- Add languages to an existing Oracle HTML DB in a remote Oracle database.

4.3.4.1 Requirements for Running htmldbca

To use htmldbca, you must have the following requirements in place:

- A local Oracle Database Companion CD installation that has HTML DB installed. The htmldbca executable is in the bin directory in the same Oracle home as Oracle HTML DB.

- A remote Oracle database. This database can be on the same computer as the Oracle HTML DB home or on an Oracle database installation on a remote computer. You must have a valid connection to this remote Oracle database installation.

- Connection privileges to the remote Oracle database. You should be able to connect as SYS using the SYSDBA privilege. htmldbca prompts you for the password for user SYS.

See Also:

Oracle Database Net Services Administrator's Guide for information on connecting to another Oracle database

4.3.4.2 Syntax for htmldbca

The syntax for htmldbca is as follows:

htmldbca [options]

where options are:

- -oracle_home string: Enter the location of the Oracle home where Oracle HTML DB is installed. If you do not specify this Oracle home, htmldbca tries to use the ORACLE_HOME environment variable setting. If ORACLE_HOME is not set or is unusable, and if you do not specify the oracle_home option, htmldbca prompts for the Oracle home. Required. For example:

htmldbca -oracle_home c:\oracle\product\10.2.0\db_2

- -db_host string: Host name of the remote Oracle Database. Required, but if you do not specify it, htmldbca prompts for it. For example:

htmldbca -db_host shobeen

- -db_servicename string: Oracle Database service name. Required, but if you do not specify it, htmldbca prompts for it. For example:

htmldbca -db_servicename welcome

- sys_password | -sys_obfuscatedPassword string: Remote password or obfuscated password for SYS. Required, but if you do not specify either of these parameters, htmldbca prompts for the sys_password. In that case, sys_obfuscatedPassword becomes optional. For example:

htmldbca -sys_password welcome

- -htmldb_password | -htmldb_obfuscatedPassword string: Oracle HTML DB password | obfuscated password. Password or obfuscated password for Oracle HTML DB. Required, and if you do not specify either of these passwords, htmldbca prompts for the htmldb_password. (If you are upgrading from an earlier version of Oracle HTML DB, enter the password you had created for that version of the HTMLDB_PUBLIC_USER schema.) For example:

htmldbca -htmldb_password htmldb_welcome

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.

If you want to obfuscate the password after installation, see "Obfuscating Passwords in a New Oracle HTML DB Installation" for more information.

- -ts_htmldb string: Specifies the name of the HTML DB tablespace to be created for the remote HTML DB. Required, but if you do not specify it, htmldbca prompts for it. For example:

htmldbca -ts_htmldb sysaux

- -ts_files string: Oracle HTML DB Files tablespace. By default, htmldbca uses the ts_htmldb value. Optional, but if you enter an invalid value, htmldbca prompts for a valid one. For example:

htmldbca -ts_files sysaux

- -ts_temp string: Oracle HTML DB Temporary tablespace. The default value is set to use temp tablespace. Optional, but if you enter an invalid value, htmldbca prompts for a valid one.

- -load_lang string [,string[,string[...]]]: Specifies one or more additional languages to install. Optional, but if you enter an invalid value, htmldbca prompts for a valid response. (In this case, you can only enter one language.) If you do not enter a value, English is selected. For example:

htmldbca -load_lang de, fr, it

Language choices are as follows:

- de: German

- en: English, which is the default. If the English version of Oracle HTML DB is installed in the remote Oracle database, htmldbca displays a notification message and exits.

- es: Spanish

- fr: French

- it: Italian

- ja: Japanese

- ko: Korean

- pt-br: Brazilian Portuguese

- zh-cn: PRC Chinese

- zh-tw: Taiwan Chinese

Oracle Database Globalization Support Guide provides information about language support for Oracle Database.

- -DAD_name string: Creates a new Database Access Descriptor Name for Oracle HTML DB. The default value is htmldb. htmldbca updates the ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\marvel.conf file with the new DAD value. Optional, but if you enter an duplicate value, htmldbca prompts for a valid one. In order for the changes to take effect, you must restart Oracle HTTP Server, in which case you can use the -restart parameter, described in the next section. For example:

htmldbca -DAD_name my_htmldb -restart

Alternatively, after you run htmldbca, you can enter the following command at a command prompt to restart Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server

Afterward, users can access this instance by entering a URL using the following syntax:

http://host:port/pls/DAD_name

For example:

http://mycompany:7778/pls/my_html

- -restart: Restarts Oracle HTTP Server after the configuration completes. Optional and is not prompted. For example:

htmldbca -restart

- -interactive on|off: Turns interactive mode on or off. When interactive mode is on, htmldbca prompts for missing or incorrect parameter values. When off, no prompts appear; hence, you must specify all the required prompt values at the command line when you run htmldbca. By default, htmldbca runs in interactive mode. Optional and is not prompted. For example:

htmldbca -interactive off

- -help: Displays brief usage description for htmldbca. Optional and is not prompted. For example:

htmldbca -help

4.3.4.3 Running htmldbca

To run htmldbca, open a Windows command prompt and either run htmldba by itself or run it using any combination of the options described in the previous section. For example:

c:\> htmldbca

Unless the -interactive mode is set to off, htmldbca prompts you for any required information that you do not specify in the command line.

4.4 Postinstallation Tasks for Oracle Workflow Server

This section contains these topics:

- Checking Initialization Parameter Values

- Compiling Invalid Objects

- Configuring Oracle Workflow HTML Help

- Completing Additional Set-up Tasks

4.4.1 Checking Initialization Parameter Values

Verify that the initialization parameters listed in the following table are set to the values shown or higher, and if necessary, change those values:

Note:

If a current value is higher than the required value, do not change the current value.

Parameter

Required Value

AQ_TM_PROCESSES

Greater than 1

JOB_QUEUE_PROCESSES

10 or greater

To check the values of these initialization parameters and change them if necessary:

1. Log in to the database as the SYS user:

c:\> sqlplus sys/SYS_password as sysdba

2. To determine the current value for all initialization parameters, enter the following command:

SQL> SHOW PARAMETER parameter_name

3. To alter the value of an initialization parameter, enter a command similar to the following:

SQL> ALTER SYSTEM SET parameter_name=value

4. If the database is not using a server parameter file, edit the value specified for the parameter in the initialization parameter file (initsid.ora).

4.4.2 Compiling Invalid Objects

Log into the Oracle database and run the utlrp.sql script to compile any invalid objects in the SYS schema. For example:

c:\> sqlplus sys/SYS_password as sysdba
SQL> @C:\oracle\product\10.2.0\db_1\rdbms\admin\utlrp.sql

4.4.3 Configuring Oracle Workflow HTML Help

Oracle Workflow provides access to context-sensitive HTML help from the Help button on each of its Web pages. Before you can view the Oracle Workflow HTML help, you must extract the doc directory tree from the ORACLE_BASE\ORACLE_HOME\wf\wfdoc.zip file to your file system.

To extract the wfdoc.zip file:

1. Use an unzip utility to extract the doc directory tree from the zip file within the Workflow directory in your middle-tier Oracle home.
This extraction requires at least 5 MB of free disk space. After extracting the doc directory tree, you can optionally remove the wfdoc.zip zip file.

2. Click the Help button on any Oracle Workflow Web page to access the HTML help.
You also can access any HTML help file directly by appending its virtual path to your Web listener base URL. The path for the contents page of the Oracle Workflow help is:

http://hostname:portID/OA_DOC/lang/wf/toc.htm

3. Optionally, if you add custom help, you can replace the placeholder file in the ORACLE_BASE\ORACLE_HOME\wf\doc\lang\wfcust directory, wfcust.htm, with your own help material.
The HTML file that is the main entry point for your custom help must be named wfcust.htm and must contain an anchor named contents. Your custom help is accessible through the Custom Help link on the contents page of the Oracle Workflow help, or you can access your custom help directly through the following path:

http://hostname:portID/OA_DOC/lang/wfcust/wfcust.htm

4.4.4 Completing Additional Set-up Tasks

After you complete the Oracle Workflow server and middle tier installation process, you must perform some additional steps to set up Oracle Workflow for your site.

See Also:

"Setting Up Oracle Workflow" in Oracle Workflow Administrator's Guide for instructions on completing these tasks

5 Getting Started with the Oracle Database Companion CD Products

This chapter describes where to go now that you have installed the Oracle Database Companion CD products:

- Checking the Installation Contents

- Getting Started with Oracle HTTP Server

- Getting Started with Oracle HTML DB

- Getting Started with Oracle Workflow

- Getting Started with Oracle Ultra Search

Note:

On Windows Server 2008 and Windows Server 2008 R2, utilities such as Oracle Universal Installer and Oracle Process Management Notification (OPMN) utility require Administrator privileges.

5.1 Checking the Installation Contents

You can check the installation contents of your Oracle software by using Oracle Universal Installer:

1. From the Start menu, choose Programs, then Oracle - HOME_NAME, Oracle Installation Products, then Universal Installer.
You can access Oracle Universal Installer from any Oracle home.

2. When the Welcome window appears, click Installed Products.
The Inventory window appears, listing all of the Oracle homes on the system and the products installed in each Oracle home. To check the paths of the products, click the Environment tab.

5.2 Getting Started with Oracle HTTP Server

This section covers the following topics:

- Starting, Stopping, or Restarting Oracle HTTP Server

- Logging into Oracle HTTP Server

5.2.1 Starting, Stopping, or Restarting Oracle HTTP Server

To start, stop, or restart Oracle HTTP Server:

1. From the Start menu, choose Programs, then Oracle - HOME_NAME, then Oracle HTTP Server.

2. Select the appropriate option:

- Start HTTP Server

- Stop HTTP Server

Alternatively, you can open a command prompt and run the following commands:

- To start Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server

- To restart Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server

- To stop Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server

5.2.2 Logging into Oracle HTTP Server

To log in to Oracle HTTP Server, in a browser, enter a URL using the following syntax:

http://server:port/

where:

- server is the computer where you have installed Oracle HTTP Server, for example, mycomputer.us.mycompany.com.

- port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from the httpd.conf file, located in ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf, by searching for Port.
You can also find the port number in the portlist.ini file, located in ORACLE_BASE\ORACLE_HOME\install. However, be aware that if you change a port number, it is not updated in the portlist.ini file, so you can only rely on this file immediately after installation.

After you have logged in, you can find Oracle HTTP Server product demonstrations and a listing of new features for this release. This link also provides access to the Oracle Technology Network.

5.3 Getting Started with Oracle HTML DB

This section covers the following topics:

- Logging into Oracle HTML DB

- Set-up Tasks for Oracle HTML DB Administrators

5.3.1 Logging into Oracle HTML DB

You open the Oracle HTML DB home page in a Web browser. To view or develop Oracle HTML DB applications, the Web browser must support JavaScript and the HTML 4.0 and CSS 1.0 standards.

See Also:

"Browser Requirements" for supported Web browsers

To log in to Oracle HTML DB Administration Services:

1. In a Web browser, navigate to the Oracle HTML DB Administration Services application:

http://hostname:port/pls/database_access_descriptor/htmldb_admin

where:

- hostname is the name of the computer where Oracle HTTP Server is installed.

- port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from the httpd.conf file, located in ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf, by searching for Port.
You can also find the port number in the portlist.ini file, located in ORACLE_BASE\ORACLE_HOME\install. However, be aware that if you change a port number, it is not updated in the portlist.ini file, so you can only rely on this file immediately after installation.

- database_access_descriptor is the database access descriptor (DAD) defined in the mod_plsql configuration file. The default value is htmldb.

See Also:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.readme for more information about how database access descriptors work

For example:

http://myserver.us.mycompany.com:7777/pls/htmldb/htmldb_admin

The Login page appears.

2. In Username, enter admin.

3. In Password, enter the Oracle HTML DB administrator account password you specified when you installed Oracle HTML DB.

4. Click Login.
The Oracle HTML DB Administration Services page appears.

5.3.2 Set-up Tasks for Oracle HTML DB Administrators

If you are an Oracle HTML DB administrator, you must:

- Log in to Oracle HTML DB Administration Services. Oracle HTML DB Administration Services is a separate application for managing an entire Oracle HTML DB instance.

- Specify a provisioning mode. In Oracle HTML DB Administration Services you must determine how the process of creating (or provisioning) a workspace works in your development environment.

- Create a Workspace. A workspace is a shared work area within the Oracle HTML DB development environment that has a unique ID and name. An Oracle HTML DB administrator can create a workspace manually or have users submit requests.

- Log in to a Workspace. Once you have created workspace in Oracle HTML DB Administration Services, you can return to the Oracle HTML DB Login page and log in to that workspace.

See Also:

Oracle HTML DB User's Guide for more information about using, developing applications with, and administering Oracle HTML DB

5.4 Getting Started with Oracle Workflow

This section covers the following topics:

- Logging into the Oracle Workflow Home Page

- Logging into Oracle Workflow Manager

- Set-up Tasks for Oracle Workflow Administrators

5.4.1 Logging into the Oracle Workflow Home Page

You open the Oracle Workflow home page in a Web browser. You must be a valid user in the Workflow directory service. Depending on the settings you selected during the installation and configuration, the directory service is based on either Oracle Internet Directory or on the native database users.

See Also:

"Oracle Workflow Server Browser Requirements" for list of supported Web browsers

To access the Oracle Workflow home page, connect as a valid Oracle Workflow user to the following URL:

http://hostname:port/pls/wf/wfa_html.home

See Also:

ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\deploy_db_wf.ini if you are not sure which server and port number to use

5.4.2 Logging into Oracle Workflow Manager

The Oracle Workflow server installation includes the Oracle Workflow Manager component of Oracle Enterprise Manager. This component provides administrative and management tools for Oracle Workflow. When you install Oracle Workflow into your Oracle Database home, Oracle Workflow Configuration Assistant configures Oracle Workflow Manager. It creates two Oracle Application Server Containers for Java 2 Enterprise Edition (OC4J) instances:

- OC4J_Workflow_Component_Container: Workflow Configuration Assistant deploys two applications within this instance. One application runs the agent listener service components and the other runs notification mailer service components.

- OC4J_Workflow_Management_Container: Workflow Configuration Assistant deploys one application within this instance to implement the Oracle Workflow Manager user interface.

Starting, Stopping, or Restarting the OC4J Instances

To start these instances, run the following scripts:

ORACLE_BASE\ORACLE_HOME\wf\admin\wfmgrstart.bat
ORACLE_BASE\ORACLE_HOME\wf\admin\wfsvcstart.bat

You can stop and restart the OC4J instances in which Oracle Workflow Manager is deployed. To stop the instances, run the following scripts:

ORACLE_BASE\ORACLE_HOME\wf\admin\wfmgrstop.bat
ORACLE_BASE\ORACLE_HOME\wf\admin\wfsvcstop.bat

Accessing the Oracle Workflow Manager User Instance

To access the Oracle Workflow Manager user interface:

1. Log in to Oracle Enterprise Manager Database Control:

http://server:port/em

For example:

http://myserver.mycompany:5500/em

2. In the Home page, navigate to the Related Links section.

3. In the Related Links section, select Workflow Manager.

4. Log in using your Oracle Workflow Manager database username (typically owf_mgr) and password.

See Also:

- Oracle Workflow Administrator's Guide

- Oracle Workflow Developer's Guide

- Oracle Workflow User's Guide

- Oracle Workflow API Reference

5.4.3 Set-up Tasks for Oracle Workflow Administrators

If you are an Oracle Workflow administrator, complete the tasks described in the "Setting Up Oracle Workflow" chapter of the Oracle Workflow Administrator's Guide.

See Also:

Oracle Workflow Administrator's Guide

5.5 Getting Started with Oracle Ultra Search

After you install Oracle Ultra Search, Oracle Universal Installer creates the following Oracle Ultra Search-specific administrative accounts:

- WK_TEST: The default Ultra Search instance schema.

- WKPROXY: The Ultra Search proxy user.

- WKSYS: Used for storing Ultra Search system dictionaries and PL/SQL packages.

See Also:

Oracle Ultra Search Administrator's Guide

A Installing Oracle Database Companion CD Using Response Files

This appendix covers the following topics:

- How Response Files Work

- Preparing a Response File

- Running Oracle Universal Installer Using the Response File

- Running Oracle Workflow Configuration Assistant in Noninteractive Mode

A.1 How Response Files Work

You can automate the installation and configuration of Oracle software, either fully or partially, by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values in the response file to provide answers to some or all of the Oracle Universal Installer prompts.

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run Oracle Universal Installer at a command prompt using either of the following modes:

- Silent mode: Oracle Universal Installer does not display any screens. Instead it displays progress information in the command window where you started it. To use silent mode, you run setup.exe with the -silent parameter and include a response file, which contains responses to the Oracle Universal Installer prompts.

- Noninteractive (or suppressed) mode: Oracle Universal Installer only displays screens for which you did not supply information in the response file. You can use variables in the response file or command-line prompts to suppress other Oracle Universal Installer screens, such as Welcome and Summary, that do not prompt for information. To use noninteractive mode, run setup.exe without the -silent parameter, but include the response file or any other parameters that apply.

You define the settings for a silent or noninteractive installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home name, you would supply the appropriate value for the ORACLE_HOME_NAME variable, as in the following example:

ORACLE_HOME_NAME="OraDBHome1

Another way of specifying the response file's variable settings is to pass them as command line arguments when you run Oracle Universal Installer. For example:

SYSTEM_DRIVE:\setup.exe_location> setup -silent "ORACLE_HOME_NAME=OraDBHome1" ...

This method is particularly useful if you do not want to embed sensitive information, such as passwords, in the response file. For example:

SYSTEM_DRIVE:\setup.exe_location> setup -silent "s_sysPwdFresh=binks342" ...

Ensure that you enclose the variable and its setting in quotes.

See Also:

Oracle Universal Installer and OPatch User's Guide for more information about response file formats.

A.1.1 Reasons for Using Silent Mode or Noninteractive Mode

Table A-1 describes several reasons why you might want to run Oracle Universal Installer in silent mode or noninteractive mode.

Table A-1 Reasons for Using Silent Mode or Noninteractive Mode

Mode

Uses

Silent

Use silent mode to:

- Complete an unattended installation

- Complete several similar installations on multiple systems without user interaction

Oracle Universal Installer displays progress information in the window that you used to start it, but it does not display the Oracle Universal Installer screens.

Noninteractive

Use noninteractive mode to complete similar Oracle software installations on multiple system, providing default answers to some, but not all, of Oracle Universal Installer prompts.

If you do not specify information required for a particular Installer screen in the response file, Oracle Universal Installer displays that screen. It suppresses screens for which you have provided all of the required information.

A.1.2 General Procedure for Using Response Files

You follow these general steps to install the Oracle Database Companion CD products using response files:

1. Customize or create a response file for the installation settings that you need.
You can create the response file by using one of the following methods:

- Modify one of the sample response files that is provided with the installation.

- Run Oracle Universal Installer at a command prompt using record mode.

"Preparing a Response File" explains how to customize or create the response file.

2. Run Oracle Universal Installer from a command prompt, specifying the response file, using either silent or noninteractive mode.

Note:

Windows Server 2008 and Windows Server 2008 R2 require Administrator privileges at the command prompt.

"Running Oracle Universal Installer Using the Response File" explains how to run Oracle Universal Installer with a response file.

A.2 Preparing a Response File

This section describes the methods that you can use to prepare a response file for use during silent-mode or noninteractive-mode installations:

- Editing a Response File Template

- Recording a Response File

A.2.1 Editing a Response File Template

Oracle provides response file templates for each product and installation type, and for each configuration tool. These files are located in the companion\response directory on the Oracle Database installation media.

Creating a response file using a response file template is most useful for the Enterprise Edition or Standard Edition installation types.

Table A-2 lists the available sample response files:

Table A-2 Response Files

Response File Name

This File Silently Runs The...

companionCD.db.rsp

Oracle Database Products installation type

companionCD.midtier.rsp

Oracle Database Companion CD installation type

htmldb.HTMLDBONLY

Oracle HTML DB-only installation of Oracle HTML DB installation type

htmldb.HTMLDBwithOHS.rsp

Oracle HTML DB and Oracle HTTP Server installation of Oracle HTML DB installation type

To copy and modify a response file:

1. Copy the appropriate response files from the companion\Response directory on the Oracle Database media to your hard drive.

2. Modify the response files with a text file editor.
In addition to editing settings specific to the Oracle Database Companion CD products installation, check that the FROM_LOCATION path is correct and points to the products.xml file in the stage directory in the installation media. You may want to set this variable to point to an absolute path, for example:

FROM_LOCATION="\\myserver\companion\stage\products.xml"

Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "How Response Files Work" explains this method.

See Also:

Oracle Universal Installer and OPatch User's Guide for detailed information on creating response files. In an installed Oracle Database, select Start, then Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer Concepts Guide. It appears in HTML format.

3. Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section.

A.2.2 Recording a Response File

You can create a response file by running Oracle Universal Installer in interactive mode using record mode. This method is most useful for custom or software-only installations.

Recording the response file generates the response file immediately after you complete the Summary window, so you must install the Oracle Database Companion CD products to create the response file. After you create the response file in this manner, you can customize it to meet your needs.

If you want to use record mode during a noninteractive mode installation, Oracle Universal Installer records the variable values that were specified in the original source response file into the new response file.

Note:

You cannot use record mode to create a response file based on the Basic installation type.

To record a response file:

1. Ensure that the computer on which you are creating the response file has met the requirements in Chapter 2.

2. At the command prompt, use the cd command to change to the directory that contains the Oracle Universal Installer setup.exe executable.

Note:

Windows Server 2008 and Windows Server 2008 R2 require Administrative privileges at the command prompt.

On the installation DVD, setup.exe is located in the db directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.

3. Enter the following command:

SYSTEM_DRIVE:\setup.exe_location> setup -record -destinationFile response_file_name

Replace response_file_name with the complete path name for the new response file. On Windows Server 2008 and Windows Server 2008 R2, you must open the command prompt with Administrator privileges. For example:

SYSTEM_DRIVE:\setup.exe_location> setup -record -destinationFile c:\response_files\install_oracle10_2.rsp

4. After Oracle Universal Installer starts, enter the installation settings, which is recorded in the response file.

5. When the Summary window appears, do any one:

- Click Install to create the response file and continue with the installation.

- Click Cancel if you only want to create the response file but not continue with the installation. The installation stops, and the settings you have entered is also recorded in the response file.

Afterwards, Oracle Universal Installer saves your new response file using the path and file name you specified on the command line.

6. Edit the new response file to have any environment-specific changes for the computer to run it.
In addition to editing settings specific to the Oracle Database Companion CD products installation, check that the FROM_LOCATION path is correct and points to the products.xml file in the stage directory in the installation media. You may want to set this variable to point to an absolute path, for example:

FROM_LOCATION="\\myserver\companion\response\stage\products.xml"

Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "How Response Files Work" explains this method.

7. Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section, next.

A.3 Running Oracle Universal Installer Using the Response File

At this stage, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. On Windows Server 2008 and Windows Server 2008 R2, you must open the command prompt with Administrator privileges. The Oracle Universal Installer executable, setup.exe, provides several options. For help information about the full set of these options, run setup.exe with the -help option, for example:

SYSTEM_DRIVE:\setup.exe_location> setup -help

A new command window appears, with the "Preparing to launch..." message. In a moment, the help information appears in that window.

To run Oracle Universal Installer and specify a response file:

1. Place the response file on the computer where you want to install the Oracle Database Companion CD products.

2. At a command prompt, run Oracle Universal Installer with the appropriate response file. On Windows Server 2008 and Windows Server 2008 R2, you must open the command prompt with Administrator privileges. For example:

SYSTEM_DRIVE:\setup.exe_location> setup [-silent] "variable=setting" [-nowelcome] [-noconfig] [-nowait] -responseFile filename

where:

- filename: Identifies the full path of the response file.

- -silent: Runs Oracle Universal Installer in silent mode and suppresses the Welcome window. When you use -silent, then the -nowelcome option is not necessary.

- "variable=setting" refers to a variable within the response file that you may prefer to run at the command line rather than set in the response file. Enclose the variable and its setting in quotes.

- -nowelcome: Suppresses the Welcome window that appears during installation.

- -noconfig: Suppresses running the configuration assistants during installation, performing a software-only installation instead.

- -nowait: Closes the console window when the silent installation completes.

See Also:

- "Installing Oracle Products" in Oracle Universal Installer and OPatch User's Guide for more information about installing using response files

- "Deinstalling Products" in Oracle Universal Installer and OPatch User's Guide for more information about deinstalling using response files

A.4 Running Oracle Workflow Configuration Assistant in Noninteractive Mode

You can run Workflow Configuration Assistant in noninteractive mode by entering your configuration parameter settings directly in the Workflow Configuration Assistant wfinstall.bat script. You must specify all required and conditionally required parameters for the features to use.

To run Oracle Workflow Configuration Assistant in noninteractive mode:

1. Go to the ORACLE_BASE\ORACLE_HOME\wf\install directory, which is the default location of the wfinstall.bat script.

2. Open the wfinstall.bat script in a text editor and locate a line similar to the following:

. . . repository.jar" WorkflowCA /wfdir workflow_directory /orahome oracle_home

For example:

. . . repository.jar" WorkflowCA /wfdir /d1/iasinstall/m21pw1/wf
/orahome /d1/iasinstall/m21pw1

3. Edit the script to append your additional parameters after the /wfdir, /orahome, and /ospath parameters. Enter the parameters all on the same line; otherwise, the script does not runs correctly.

. . . repository.jar" WorkflowCA /wfdir workflow_directory /orahome
oracle_home /wfacct workflow_schema /instype installation_type
/tnsconndesc connection_string

where:

- /wfdir: The Oracle Workflow directory within your Oracle home directory. The default directory is ORACLE_BASE\ORACLE_HOME\wf.

- /orahome: Your Oracle home directory location, for example, C:\oracle\product\10.2\Db_1.

- /wintz: The time zone you are using, for example, "Pacific Daylight Time". (Enclose the time zone in quotes.)

- /systemroot: The location of the system root files for your operating system, for example, C:\WINDOWS.

- /wfacct: Workflow Account.

- /instype: Specify one of the following installation options:

- server - Configures Workflow Server only; available in both GUI mode and command-line mode

- add_language - Sets the language or languages used; available in both GUI mode and command-line mode

- /tnsconndesc: Connection string to the Oracle database

Note:

If a parameter can be entered in both user interface mode and noninteractive mode, this section lists the name of the corresponding field in the Oracle Workflow Configuration Assistant window alongside the noninteractive mode parameter name.

4. If you specified add_language for the /instype parameter, enter the /nlsopt parameter with the languages you want to add.
Enclose the languages in quotes. For example, to specify Arabic, German, and Danish, enter the following value:

"ar d dk"

To use all available languages, set nlsop to all. Oracle Workflow server supports all languages that Oracle Database supports.

See Also:

"Locale Data" in Oracle Database Globalization Support Guide for a list of standard language abbreviations.

5. If you specified server for the /instype parameter, enter the following parameters to integrate Oracle Internet Directory as your Oracle Workflow directory service:

- /ldaphost - LDAP host name

- /ldapport - LDAP Non-SSL port

- /ldapuser - LDAP admin username

- /ldaplogbase - Changelog DN

- /ldapuserbase - User base (for example, /ldapuserbase cn=Users,dc=us,dc=oracle,dc=com)

In these cases, Oracle Workflow Configuration Assistant configures your Oracle Internet Directory integration using the existing LDAP parameters defined in your database. However, if you specify new LDAP parameters here, the Oracle Workflow Configuration Assistant updates your settings.

6. If you specified server or all for the /instype parameter, enter these parameters to use Oracle Workflow Notification Mailer:

- /mailserver - Inbound e-mail account: server name

- /mailuser - Inbound e-mail account: username

- /mailhost - Outbound e-mail account: server name

- /htmlagent - Mail generation: HTML agent

- /mailreply - Message generation: reply-to address

- /processfolder - E-mail processing: name of processed folder

- /discardfolder - E-mail processing: name of discard folder

7. If you specified server for the /instype parameter, and to change the tablespace assigned to the Oracle Workflow database account, set the /tablespace parameter to a valid existing tablespace name.

8. To control how Oracle Workflow Configuration Assistant writes log information, set these parameters:

- /debug - Specify true if you want Oracle Workflow Configuration Assistant to write debug information to the workflow.log file. By default, Oracle Workflow does not log this information.

- /logdir - Specify the path to the directory where you want Oracle Workflow Configuration Assistant to write the workflow.log file, or specify nolog if you do not want to create a log file. By default, the log file is written to the ORACLE_BASE\ORACLE_HOME\wf\install directory.

9. Save your changes and exit the wfinstall.bat script.

To run the wfinstall.bat script, enter the following command:

ORACLE_BASE\ORACLE_HOME\wf\install\wfinstall.bat

If the wfinstall.bat script includes the minimum parameters, all entered as a single line of text in the file, it performs the configuration in noninteractive mode, without displaying the Oracle Workflow Assistant window. However, as a security precaution, the script may prompt you to enter the following passwords at run-time, depending on the installation options that your site uses:

- The password for your Oracle Workflow database account

- Your SYS password

- The password for the LDAP user account, if you enter LDAP parameters

- The password for the notification mailer e-mail account, if you enter mailer parameters

B Configuring Oracle Database Companion CD Globalization Support

This appendix describes the following Globalization Support topics:

- Installing and Using Oracle Components in Different Languages

- Configuring Locale and Character Sets with the NLS_LANG Parameter

B.1 Installing and Using Oracle Components in Different Languages

This section describes the following features:

- Installing Oracle HTML DB in Other Languages

- Installing Oracle Workflow in Other Languages

- Running Oracle Universal Installer in Different Languages

- Using Oracle Components in Different Languages

B.1.1 Installing Oracle HTML DB in Other Languages

The Oracle HTML DB interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle HTML DB can be installed with one or more of these translated versions. At run-time, each user's Web browser language settings determine the specific language version.

The translated version of Oracle HTML DB should be loaded into a database that has a character set that can support the specific language. If you attempt to install a translated version of Oracle HTML DB into a database that does support the character encoding of the language, the installation may fail or the translated Oracle HTML DB instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle HTML DB.

You can manually install translated versions of Oracle HTML DB using SQL*Plus. The installation files are encoded in UTF8.

Note:

Regardless of the target database character set, to install a translated version of Oracle HTML DB you must set the character set value of the NLS_LANG environment variable to AL32UTF8 before starting SQL*Plus.

Caution:

AL32UTF8 is the Oracle Database character set that is appropriate for XMLType data. It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters.
Do not confuse Oracle Database database character set UTF8 (no hyphen) with database character set AL32UTF8 or with character encoding UTF-8. Database character set UTF8 has been superseded by AL32UTF8. Do not use UTF8 for XML data. UTF8 supports only Unicode version 3.1 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.

Using database character set UTF8 for XML data could potentially cause a irrecoverable error or affect security negatively. If a character that is not supported by the database character set appears in an input-document element name, a replacement character (usually "?") is substituted for it. This terminates parsing and raise an exception.

The following examples illustrates valid NLS_LANG settings for loading Oracle HTML DB translations:

American_America.AL32UTF8
Japanese_Japan.AL32UTF8

To install a translated version of Oracle HTML DB:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

c:\> set NLS_LANG=American_America.AL32UTF8

2. Start SQL*Plus and connect to the target database as SYS:

c:\> sqlplus sys/SYS_password as sysdba

3. Execute the following statement:

SQL> ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;

4. Execute the appropriate language specific script. For example:

SQL> @c:\oracle\product\10.2.0\db_1\htmldb\builder\de\load_de.sql

The installation scripts are located in subdirectories identified by a language code in the unzipped distribution /htmldb/builder. For example, the German version is located in /htmldb/builder/de and the Japanese version is located in /htmldb/builder/ja. Within each of these directories, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

See Also:

"Installing and Configuring Oracle HTML DB on a Remote Oracle Database" if you add languages to an existing Oracle HTML DB on a remote Oracle database

B.1.2 Installing Oracle Workflow in Other Languages

Use the Add Language option in Oracle Workflow Configuration Assistant to install Oracle Workflow in another language.

See Also:

"Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" for instructions on starting Oracle Workflow Configuration Assistant

B.1.3 Running Oracle Universal Installer in Different Languages

Oracle Universal Installer runs by default in the selected language of your operating system. You can run Oracle Universal Installer in the following additional languages:

- Brazilian Portuguese

- German

- Japanese

- Simplified Chinese

- Traditional Chinese

- French

- Italian

- Korean

- Spanish

To run Oracle Universal Installer in a different language:

1. Change the language in which your operating system is running. For example, on Windows Server 2003:

1. From the Start menu, select Control Panel, then Regional and Language Options.

2. From the drop-down list, select a language from the preceding table list and choose OK.

2. Run Oracle Universal Installer by following the instructions in the Oracle Database Installation Guide for Microsoft Windows Itanium (64-Bit).

Note:

The selected language is assigned to the NLS_LANG registry parameter.

B.1.4 Using Oracle Components in Different Languages

You can select other languages in which to use Oracle components (such as Oracle Net Configuration Assistant, and Database Configuration Assistant). Note that this does not change the language in which Oracle Universal Installer is run. For the Oracle component to run in the selected language, it must be the same as the language set for your operating system. You can change your operating system language in the Regional Settings window from the Control Panel.

To use components in different languages:

1. Start Oracle Universal Installer:

- From the installation media: From the installation media, navigate to the companion directory and double-click setup.exe.

- From an installed Oracle Database Companion CD: From the Start menu, select Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer.

2. From the Select Installation Type window, select the Product Languages button.
The Language Selection window appears.

3. Select a language in which to use Oracle components from the Available Languages field.

4. Use the > arrow to move the language to the Selected Languages field and click OK.

5. Select appropriate products for installation and click Next.
After installation is complete, the dialog box wording, messages, and online help for the installed components display in the language you selected.

B.2 Configuring Locale and Character Sets with the NLS_LANG Parameter

Oracle provides Globalization Support that enables users to interact with a database in their preferred locale and character set settings. The NLS_LANG parameter specifies locale behavior for Oracle software. It sets the language and territory used by the client application and the database. It also sets the character set for entering and displaying data by a client program, such as SQL*Plus.

The NLS_LANG parameter is stored in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID\NLS_LANG subkey, where ID is the unique number identifying the Oracle home. This parameter uses the following format:

NLS_LANG = LANGUAGE_TERRITORY.CHARACTER_SET

where:

Parameter

Description

LANGUAGE

Specifies the language and conventions for displaying messages, day name, and month name.

TERRITORY

Specifies the territory and conventions for calculating week and day numbers.

CHARACTER_SET

Specifies the encoding of the database client, which is the character set for data entered or displayed by a client program.

The following table lists some values for the NLS_LANG parameter:

Operating System Locale

NLS_LANG Values

French (France)

FRENCH_FRANCE.WE8ISO8859P15
FRENCH_FRANCE.WE8ISO8859P1

FRENCH_FRANCE.WE8MSWIN1252

FRENCH_FRANCE.AL32UTF8

Japanese (Japan)

JAPANESE_JAPAN.JA16EUC
JAPANESE_JAPAN.JA16SJIS

JAPANESE_JAPAN.AL32UTF8

See Also:

- Oracle Database Installation Guide for Microsoft Windows for more information about how NLS_LANG works in a Windows installation of Oracle Database

- Oracle Database Platform Guide for Microsoft Windows for more information about the subkey locations for multiple Oracle homes

- Oracle Database Globalization Support Guide for information about the NLS_LANG parameter and Globalization Support initialization parameters

- The operating system documentation on how to determine the operating system locale environment setting

C Managing Oracle Companion CD Port Numbers

This appendix lists the default port numbers and describes how to change the assigned port after installation:

- About Managing Ports

- Viewing Port Numbers and Access URLS

- Port Numbers and Protocols of Oracle Components

- Changing the Oracle HTTP Server Port

- Changing the Oracle Workflow Container Ports

- Changing the Oracle Ultra Search Ports

C.1 About Managing Ports

During installation, Oracle Universal Installer assigns port numbers to components from a set of default port numbers. Many Oracle Database components and services use ports. As an administrator, it is important to know the port numbers used by these services, and to ensure that the same port number is not used by two services on your host.

Most port numbers are assigned during installation. Every component and service has an allotted port range, which is the set of port numbers Oracle Database attempts to use when assigning a port. Oracle Database starts with the lowest number in the range and performs the following checks:

- Is the port used by another Oracle Database installation on the host?
The installation may be up or down at the time; Oracle Database can still detect if the port is used.

- Is the port used by a process that is currently running?
This could be any process on the host, even a non-Oracle Database process.

If the answer to any of the preceding questions is yes, Oracle Database moves to the next highest port in the allotted port range and continues checking until it finds a free port.

C.2 Viewing Port Numbers and Access URLS

In most cases, the Oracle Database component's port number is listed in the tool used to configure the port. In addition, ports for some Oracle Database applications are listed in the portlist.ini file. This file is located in ORACLE_BASE\ORACLE_HOME\install.

If you change a port number, it is not updated in the portlist.ini file, so you can only rely on this file immediately after installation. To find or change a port number, use the methods described in this appendix.

C.3 Port Numbers and Protocols of Oracle Components

The following table lists the port numbers and protocols used by components that are configured during the installation. By default, the first port in the range is assigned to the component, if it is available.

Table C-1 Ports Used in Oracle Components

Component and Description

Default Port Number

Port Range

Protocol

Oracle HTTP Server

Allows Oracle applications, such as Oracle HTML DB, to communicate to the Web server through this port. It is configured during installation. "Changing the Oracle HTTP Server Port" explains how to modify this port.

7777

7777–7877

HTTP

Oracle Workflow Component Container

HTTP port for Oracle Workflow. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6010

6010–6020

TCP/HTTP

Oracle Workflow Component Container

JMS port for Oracle Workflow. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6030

6030–6040

TCP

Oracle Workflow Component Container

RMI port for Oracle Workflow. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6110

6050–6060

TCP

Oracle Workflow Management Container

HTTP port for Oracle Workflow Management. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6070

6070-6080

TCP/HTTP

Oracle Workflow Management Container

JMS port for Oracle Workflow Management. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6090

6090–6100

TCP

Oracle Workflow Management Container

RMI port for Oracle Workflow Management. It is configured automatically during installation. "Changing the Oracle Workflow Container Ports" explains how to change its ports.

6110

6110–6120

TCP

Oracle Ultra Search

HTTP port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5620

5620–5639

TCP/HTTP

Oracle Ultra Search

RMI port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5640

5640–5659

TCP

Oracle Ultra Search

JMS port for Oracle Ultra Search. Its port number is assigned automatically when you install Oracle Ultra Search, by using the Custom installation type. "Changing the Oracle Ultra Search Ports" explains how to change its port number.

5660

5660–5679

TCP

C.4 Changing the Oracle HTTP Server Port

To change the Oracle HTTP Server port:

1. In the Oracle HTTP Server home, modify the following settings in the ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf file:

Port port
Listen listener

2. Restart Oracle HTTP Server:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server

See Also:

"Starting, Stopping, or Restarting Oracle HTTP Server"

C.5 Changing the Oracle Workflow Container Ports

The following sections explain how to change the HTTP, RMI, and JMS ports for the Oracle Workflow Component Containers and Management Containers.

Changing the HTTP Port

To change the HTTP port, edit the following files:

- Oracle Workflow Component Container: ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Component_Container\config\http-web-site.xml
Modify the port attribute of the web-site element:

<web-site port="6001" ...>

- Oracle Workflow Management Container: ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Management_Container\config\http-web-site.xml
Modify the port attribute of the web-site element:

<web-site port="6061" ...>

Changing the RMI Port

To change the RMI port for Oracle Workflow Component Container, modify the port attribute of the rmi-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Component_Container\config\rmi.xml file:

<rmi-server port="6041">

For Oracle Workflow Management Container, modify the port attribute of the rmi-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Management_Container\config\rmi.xml file:

<rmi-server port="6101">

Changing the JMS Port

To change the JMS port for Oracle Workflow Componet Container, modify the port attribute of the jms-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Management_Container\config\jms.xml file:

<jms-server port="6021">

For Oracle Workflow Management Container, modify the port attribute of the jms-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_Workflow_Management_Container\config\jms.xml file:

<jms-server port="6080">

C.6 Changing the Oracle Ultra Search Ports

The following sections describe how to change the Oracle Ultra Search ports.

Changing the HTTP Port

To change the HTTP port, modify the port attribute of the web-site element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_SEARCH\config\http-web-site.xml file:

<web-site port="5620"...>

Changing the RMI Port

To change the RMI port, modify the port attribute of the rmi-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_SEARCH\config\rmi.xml file:

<rmi-server port="5640"...>

Changing the JMS Port

To change the JMS port, modify the port attribute of the jms-server element in the ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_SEARCH\config\jms.xml file:

<jms-server port="5660"...>

D Troubleshooting the Oracle Database Companion CD Installation

This appendix contains the following information on troubleshooting:

- Verifying Requirements

- Reviewing a Log of an Installation Session

- Cleaning Up After a Failed Installation

- Silent or Noninteractive Installation Response File Error Handling

- Images Displaying Incorrectly in Oracle HTML DB

- Oracle HTML DB Online Help Not Working

D.1 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

- Check Chapter 2, "Oracle Database Companion CD Requirements" to ensure that the system meets the requirements and that you have completed all of the preinstallation tasks.

- Read the release notes for the product on your platform before installing it. The release notes are available on the Oracle Database installation media. You can find the latest version of the release notes on the Oracle Technology Network Web site:

http://www.oracle.com/technetwork/index.html

D.2 Reviewing a Log of an Installation Session

This section covers the following topics:

- Reviewing the Log of an Oracle Companion CD Installation Session

- Reviewing the Log of an Oracle HTML DB Installation Session

D.2.1 Reviewing the Log of an Oracle Companion CD Installation Session

Oracle Universal Installer creates the DRIVE_LETTER:\ORACLE_BASE\ORACLE_HOME\Inventory\logs directory the first time it runs to record an inventory of products that it installs on your system and other installation information.

The log file is named installActionsdate_time.log, where date_time is the date and time of the installation. For example, installActions2004-055-14_09-00-56-am.log.

You can also view a list of installed components by clicking Installed Products on any window of Oracle Universal Installer.

Note:

Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.
The installActionsdate_time.log file contains a log of actions executed during the installation process. This file also records any link errors during installation. Do not delete or alter the installActionsdate_time.log file.

D.2.2 Reviewing the Log of an Oracle HTML DB Installation Session

After you install Oracle HTML DB, Oracle Universal Installer creates a log file in the htmldb directory using the naming convention installYYYY-MM-DD_HH24-MI-SS.log. In a successful installation, the log file contains the following text:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

If the log file contains a few errors, it does not necessarily mean that your installation failed. Acceptable errors are noted as such in the log file.

D.3 Cleaning Up After a Failed Installation

Stop the Oracle HTTP Server.

Proceed to the following sections to complete the process:

- Cleaning Up After a Failed Oracle Companion CD Installation

- Cleaning Up After a Failed Oracle HTML DB Installation

D.3.1 Cleaning Up After a Failed Oracle Companion CD Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Perform the following steps to remove the files:

1. Stop the Oracle HTTP Server.

2. Insert Oracle Database installation media and navigate to the companion directory. Alternatively, navigate to the directory where you downloaded or copied the installation files. Then double-click setup.exe to start Oracle Universal Installer.

3. Click Deinstall Products on the Welcome window or Installed Products available on any Oracle Universal Installer window. The Inventory window appears, listing installed products.

4. Select the products to remove and click Remove.

Note:

If you have multiple installation on the system, products installed in other Oracle homes appear in the Inventory window. If you select products from other Oracle homes, they are deinstalled.

5. If you installed Oracle HTTP Server, manually remove the Oracle HTTP Server Oracle home directory used in the failed installation.

6. If you installed Oracle HTML DB, follow the steps in the next section.

D.3.2 Cleaning Up After a Failed Oracle HTML DB Installation

In a successful Oracle HTML DB installation, the following banner displays after the installation:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

However, if the installation fails, in addition to using Oracle Universal Installer to remove the Oracle HTML DB components, you must drop either one or two database schemas depending upon the installation type before retrying the installation.

See Also:

"Cleaning Up After a Failed Oracle Companion CD Installation"

D.3.2.1 Cleaning Up After a Failed Upgrade Installation

In the case of a failed upgrade installation, you should first revert Oracle HTML DB to release 1.5 and then remove the schemas associated with release 1.6.

To revert Oracle HTML DB to release 1.5:

1. If you altered your images directory, you must point the text alias /i/ back to images directory for release 1.5.

2. Execute the following command in SQL*Plus:

1. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM, for example:

c:\> sqlplus sys/SYS_password as sysdba

2. Execute the following:

SQL> ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;
SQL> exec FLOWS_010600.wwv_flow_upgrade.switch_schemas
('FLOWS_010600','FLOWS_010600');

To remove the release 1.6 schema:

1. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

2. Execute the following commands:

DROP user FLOWS_010600 CASCADE;

D.3.2.2 Cleaning Up After a Failed New Installation

To remove schemas after a failed new installation:

1. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

2. Execute the following commands:

drop user FLOWS_010600 cascade;
drop user FLOWS_FILES cascade;

D.4 Silent or Noninteractive Installation Response File Error Handling

To determine whether a silent or nonintereactive installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in the DRIVE_LETTER:\Program Files\Oracle\Inventory\logs directory.

A silent installation fails if:

- You do not specify a response file.

- You specify an incorrect or incomplete response file.
For example, a common problem is that while all the product-specific data is filled out correctly, the staging area location may be incorrect. If this is the case, check the FROM_LOCATION variable and ensure that it points to the products.xml file in the installation media. In the installation media, this products.xml is in companion\stage.

- Oracle Universal Installer encounters an error, such as insufficient disk space.

Oracle Universal Installer or a configuration assistant validates the response file at run-time. If the validation fails, the installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.

See Also:

"Reviewing a Log of an Installation Session" for information on interactive installation log files

D.5 Images Displaying Incorrectly in Oracle HTML DB

If the images in Oracle HTML DB do not display correctly, Oracle HTML DB may be having a problem locating the directory where these images are stored. The directory location for the images is stored in an alias in the marvel.conf file. To address this problem:

1. Open the marvel.conf file, located in ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf, in a text editor.

2. Look for an alias to the images directory, which appears similar to the following:

Alias /i/ C:/oracle/product/10.2.0/db_HTMLDB/htmldb/images

3. Check for the following problems:

- If the /i/ alias appears, rename the first instance of /i/ to a different alias name. Alternatively, copy the images from the ORACLE_BASE\ORACLE_HOME\htmldb\images directory to the directory defined by the first /i/ alias.

- If the /i/ alias points to an incorrect directory, correct the directory path.

D.6 Oracle HTML DB Online Help Not Working

If users are accessing Oracle HTML DB through a Virtual Host, the online help does not works. Consider the following example:

- The host name of the Oracle HTTP Server where the Oracle HTML DB DAD resides is internal.server.com and the port is 7777.

- Users access Oracle HTML DB through a Virtual Host. In their Web browsers, users see external.server.com and the port 80.

In this example, Oracle HTML DB online help does not works if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle HTML DB Database Access Descriptor (DAD) to override the CGI environment variables SERVER_NAME and SERVER_PORT:

PlsqlCGIEnvironmentList SERVER_NAME=external.server.com
PlsqlCGIEnvironmentList SERVER_PORT=80

See Also:

Oracle Application Server 10g mod_plsql User's Guide for information on overriding the CGI environment variables

Index

A  B  C  D  E  F  H  I  J  L  M  N  O  P  Q  R  S  T  U  W  X

A

accounts

WK_TEST, 5.5

WKPROXY, 5.5

WKSYS, 5.5

adapters, loopback. See loopback adapters, network adapters

Administrators group

requirements for Oracle Database Companion Product installations in new home, 3.5.2

requirements for Oracle Database Products installations, 3.4.2

requirements for Oracle HTML DB installations in existing HTTP Server home, 3.3.3

AL32UTF8 character set

upgrade considerations, B.1.1

aliases, multiple on computers, 2.5.3

Apache HTTP Server, 1.2.2

apachectl script, 4.2.5

Automatic Storage Management (ASM)

silent or noninteractive mode installations, A.1.2

B

Backup Domain Controller (BDC), 3.4.2

backups of database

Oracle Database Recovery Manager, 1.3

Basic installation method

silent or noninteractive installations, A.2.2

C

certification, hardware and software, 2.4

CGI environment variables, D.6

companionCD.db.rsp response file, A.2.1

companionCD.midtier.rsp response file, A.2.1

components

using in different languages, B.1.4

computers with multiple aliases, 2.5.3

configuration assistants

suppressing during silent or noninteractive installation, A.3

copying DVD to hard drive, 3.2.1

D

dadTool.pl utility, 4.3.3

database access descriptors

accessing internal.server.com, D.6

creating during Oracle HTML DB installation, 3.3.3

migrating, 4.2.4

Database Configuration Assistant (DBCA)

suppressing during silent or noninteractive installation, A.3

database requirement

Oracle Database 10g Products, 2.2.3

Oracle HTML DB, 2.1.1.4

databases

recovery with Oracle Backup and Recovery, 1.3

deinstalling

Oracle HTML DB from Oracle Database, 3.6.1

Oracle software, 3.6

DHCP computers, installing on, 2.5.1

disk space requirements

Oracle Database 10g Products, 2.2.2

Oracle HTML DB, 2.1.1.2

Oracle HTTP Server, 2.3.5.1

documentation

installing, 3.4

on administration and tuning, Preface

on migrating and upgrading from previous release, Preface

related, Preface

DVD

copying to hard drive, 3.2.1

drive, installing from, 3.2.2

E

environment variables

CGI, overriding, D.6

ORACLE_HOME

deleting for Companion CD installation, 3.3.3

deleting for Oracle Products installation, 3.4.2

migrating previous HTTP Server, 4.2.4

ORACLE_HOSTNAME, 2.5.2

PATH, 4.2.4

PERL5LIB, 4.2.3.6

SERVER_NAME (CGI), D.6

SERVER_PORT (CGI), D.6

errors

noninteractive installation, D.4

silent mode, D.4

existing Oracle home

Oracle Workflow requirements, 2.3.4

F

files, Oracle Universal Installer log files, D.2.1

H

hardware requirements

Oracle HTML DB, 2.1.1.2

hostname, setting before installation, 2.5.2

hosts file

editing for multihomed computers, 2.5.2

location, 2.5.2

HTML DB. See Oracle HTML DB

htmldbca utility, 4.3.4

htmldb.HTMLDBONLY.rsp response file, A.2.1

htmldb.HTMLDBwithOHS.rsp response file, A.2.1

HTTP Server. See Oracle HTTP Server

httpd.conf file, migrating, 4.2.3

I

images, Oracle HTML DB, D.5

installation

about, 3.1

computer aliases, multiple, 2.5.3

DVD drive, 3.2.2

general steps, 3.1

log file (noninteractive install), D.4

multiple, 3.1

noninteractive mode error handling, D.4

quick installation, Preface

remote installation with remote access software, 3.2.3

remote installation, DVD drive, 3.2.2.1

response files, D.4

silent mode error handling, D.4

suppressing screens, A.3

installation types

Oracle Database 10g Products, 1.3

Oracle Database Companion 10g Companion Products, 1.4

Oracle HTML DB, 1.2

installing

failures

Companion CD, D.3.1

Oracle HTML DB, D.3.2

on Backup Domain Controller (BDC), 3.4.2

on Primary Domain Controller (PDC), 3.4.2

Oracle Database 10g Companion Products in new Oracle home, 3.5

Oracle Database 10g Products, 3.4

Oracle HTML DB in existing Oracle HTTP Server home, 3.3

Oracle Internet Directory, Preface

software, 3

installing from hard drive, 3.2.1

Intermedia Image Accelerator

installing, 3.4.1

Inventory directory, D.2.1

IP addresses, multiple, 2.5.2

J

JAccelerator, 1.3.7

JAccelerator (NCOMP)

installing, 3.4.1

JPublisher

about, 1.3.8

installing, 3.4

Oracle SQLJ Runtime, 1.3.8

Oracle SQLJ Translator, 1.3.8

L

languages

adding to additional Oracle HTML DB in remote database, 4.3.4

installing Oracle components in different languages, B.1.3

installing Oracle HTML DB in another language, B.1.1

installing Oracle Workflow in another language, B.1.2

using Oracle components in different languages, B.1.4

Legato Single Server Version (LSSV), 1.3

LoadModule directives, 4.2.3.3

log files

Companion CD, D.2.1

noninteractive, D.4

Oracle HTML DB, D.2.2

Oracle Universal Installer, D.2.1

loopback adapters

about, 2.5.4

checking if installed, 2.5.4.1

computers with multiple aliases, 2.5.3

installing, 2.5.4

installing on Windows 2003, 2.5.4.2, 2.5.4.2

installing on Windows XP, 2.5.4.2

removing, 2.5.4.4, 2.5.4.4

when required, 2.5.4

See also network adapters, primary network adapters

M

migrating

from previous Oracle HTTP Server, 4.2.2

httpd.conf file, 4.2.3

mod_plsql, migrating database access descriptors, 4.2.4

multihomed computers, installing on, 2.5.2

multiple aliases, computers with, 2.5.3

My Oracle Support

certification information, 2.4

My Oracle Support (formerly Oracle MetaLink) Web site, 2.4

N

Natively Compiled Java Libraries

about, 1.3.7

installing, 3.4

natively compiled Java libraries (NCOMPs), 1.3.7

NCOMPs. See natively compiled Java libraries

Net Configuration Assistant (NetCA)

suppressing during silent or noninteractive installation, A.3

network adapters

computers with multiple aliases, 2.5.3

how primary adapter is determined, 2.5.4

primary, on computers with multiple aliases, 2.5.3

See also loopback adapters, primary network adapters

network cards, multiple, 2.5.2

network topics, 2.5

about, 2.5

computers with multiple aliases, 2.5.3

DHCP computers, 2.5.1

installing from hard drive, 3.2.1

loopback adapters, 2.5.4

multiple network cards, 2.5.2

new installation

obfuscating password, 4.3.3.1

new Oracle home, 3.5

installing HTTP Server, 3.5

installing Oracle HTML DB, 3.5, 3.5

new Oracle home, Oracle HTTP Server requirements, 3.3.2, 3.5.1

NLS_LANG parameter

about, B.2

noninteractive installation

errors, D.4

noninteractive mode

about, A.1

error handling, D.4

reasons for using, A.1.1

See also response files, silent mode, A.1

noninteractive Oracle Workflow configuration, A.4

O

obfuscating password for Oracle HTML DB, 4.3.3

OC4J_Workflow_Component_Container, 5.4.2

OC4J_Workflow_Management_Container, 5.4.2

OPMN. See Oracle Process Manager and Notification server

Oracle Application Server OC4J containers

OC4J_Workflow_Component_Container, 5.4.2

OC4J_Workflow_Management_Container, 5.4.2

Oracle Database

accessing previous release of HTTP Server, 4.2.4

removing Oracle HTML DB, 3.6.1

Oracle Database 10g Companion Products, 1.4

about, 1.4

installing in new Oracle home, 3.5

products available on, 1.4

removing, 3.6.3

requirements, 2.3

Oracle Database 10g Products

about, 1.3

database requirement, 2.2.3

disk space requirements, 2.2.2

installation location, 3.4.1

installation type components, 1.3

installing, 3.4

JPublisher, 1.3.8

Natively Compiled Java Libraries, 1.3.7

Oracle Database Examples, 1.3.3

Oracle home directory, identifying, 3.4.1.1

Oracle home location, 3.4.1

Oracle Text

Supplied Knowledge Bases, 1.3.4

Oracle Ultra Search, 1.3.6

products available on, 1.3

removing, 3.6.3

requirements, 2.2

Oracle Database Companion 10g Products

installation location, 3.5.1

Oracle home location, 3.5.1

Oracle Database Companion CD

hardware certification, 2.4

installation overview, 1

installing software, 3

software certification, 2.4

troubleshooting, D

Oracle Database Examples

about, 1.3.3

installing, 3.4, 3.4.1

required products, 1.3.3.1

Sample Schemas, 1.3.3.1

Oracle Database Recovery Manager (RMAN)

about, 1.3

Oracle Enterprise Manager

Oracle Workflow Manager component, 5.4.2

Oracle Enterprise Manager Database Control

logging into Oracle Workflow Manager, 5.4.2

Oracle home directory

identifying, 3.4.1.1

multiple homes, 2.5.2

Oracle hostname, setting before installation, 2.5.2

Oracle HTML DB

about, 1.2.1

about installing, 1.4

administrative set-up tasks, 5.3.2

alias for HTML DB image directory, D.5

cleaning up after failed installation, D.3.2

database requirement, 2.1.1.4

disk space requirements, 2.1.1.2

htmldbca utility, 4.3.4

installation location, 3.3.2

installing and configuring on remote database, 4.3.4

installing in another language, B.1.1

installing in existing Oracle HTTP Server home, 3.3

installing in new Oracle home, 3.5

language addition to existing Oracle HTML DB in remote database, 4.3.4

logging into, 5.3.1

online help not working, D.6

Oracle home location, 3.3.2

Oracle HTTP Server, 1.2.2

Oracle HTTP Server requirement, 2.1.1.5

Oracle Text requirement, 2.1.1.7

patch downloads, 4.1

ports. See Oracle HTTP Server ports

postinstallation tasks, 4.3

preinstallation tasks, 3.3.1

removing, 3.6.3

removing from Oracle Database, 3.6.1

requirements, 2.1, 2.1.1

upgrading existing Oracle HTML DB on remote database, 4.3.4

XML DB requirement, 2.1.1.6

Oracle HTML DB images not displaying correctly, D.5

Oracle HTML DB installation type

products available on, 1.2

Oracle HTTP Server

about, 1.2.2, 1.2.2

about installing, 1.4

Apache HTTP Server version used, 1.2.2

backing up files, 4.2.1

disk space requirements, 2.3.5.1

enabling single sign-on, 1.2.2

installation location, 3.3.2

installing in new Oracle home, 3.5, 3.5.1

LoadModule directives, 4.2.3.3

migrating from a previous release, 4.2.2

migrating server certificate and private key, 4.2.3.8

modifying port numbers in httpd.conf file, 4.2.3.5

Oracle home location, 3.3.2

Oracle Process Manager and Notification server, 4.2.5

patch downloads, 4.1, 4.1

port

changing, C.4

ranges and protocol, C.3

postinstallation tasks, 4.2

release 9.0.3

configuring (upgrade), 4.3.2.1

removing, 3.6.3

removing configuration info for unsupported features, 4.2.3.4

requirements in a new Oracle home, 3.3.2, 3.5.1

starting, 5.2.1

stopping, 5.2.1

version required, 2.1.1.5

where to install, 3.3.2, 3.5.1

Oracle interMedia Image Accelerator, 1.3.7

Oracle Internet Directory

integrated with Oracle Workflow, 3.4.3

synchronizing Oracle Workflow directory service, 3.4.3

Oracle inventory log files, D.2.1

Oracle JDBC Development Drivers

about, 1.3.1

installing, 3.4.1

Oracle JVM, 1.3.7

Oracle MetaLink Web site

patches, 4.1

Oracle Process Manager and Notification server (OPMN), 4.2.5

Oracle SQLJ

about, 1.3.2

installing, 3.4.1

Oracle SQLJ Runtime, 1.3.8

Oracle SQLJ Translator, 1.3.8

Oracle Text

default language scripts, 2.1.1.7

requirement for Oracle HTML DB, 2.1.1.7

Supplied Knowledge Bases

about, 1.3.4

Oracle Text Supplied Knowledge Bases

installing, 3.4, 3.4.1

Oracle Ultra Search

about, 1.3.6

default schema, 5.5

getting started, 5.5

ports

changing, C.6

ranges and protocol, C.3

Oracle Universal Installer, 3

inventory, D.2.1

log files, D.2.1

removing software, 3.6

running components in different languages, B.1.4

running in different languages, B.1.3

version of to use, 3.2

Oracle Workflow

administrative set-up tasks, 5.4.3

directory service, 3.4.3

disk space requirements, 2.3.2

getting started, 5.4

HTML Help configuration, 4.4.3

installation alternatives, 1.3.5

invalid objects compilation, 4.4.2

logging into home page, 5.4.1

logging into Oracle Workflow Manager, 5.4.2

OC4J_Workflow_Component_Container, 5.4.2

OC4J_Workflow_Management_Container, 5.4.2

Oracle Internet Directory integration, 3.4.3

Oracle Workflow Client, 1.3.5

patch downloads, 4.1

ports

changing, C.5

ranges and protocol, C.3

postinstallation tasks, 4.4

additional set-up tasks, 4.4.4

compiling invalid objects, 4.4.2

configuring Oracle Workflow HTML Help, 4.4.3

verifying requirements, 4.4.1

removing, 3.6.2, 3.6.3

tablespaces, changing, 3.4.3

verifying the server installation, 2.3.4

See also Oracle Workflow Client, Oracle Workflow Manager, Oracle Workflow middle tier components, Oracle Workflow server, Oracle Workflow Configuration Assistant

Oracle Workflow Client, 1.3.5

Oracle Workflow Configuration Assistant

running in GUI mode, 3.4.3

running in noninteractive mode, A.4

Oracle Workflow installing in another language, B.1.2

Oracle Workflow Manager

logging in, 5.4.2

Oracle Enterprise Manager, 5.4.2

Oracle Workflow middle tier components

about, 1.4.1

installing, 3.5.1

requirements, 2.3.4

See also Oracle Workflow

Oracle Workflow server

about, 1.3.5

configuring, 3.4.3

installing, 3.4.1

See also Oracle Workflow

ORACLE_HOME environment variable

deleting for Companion CD installation, 3.3.3

deleting for Oracle Products installation, 3.4.2

migrating previous HTTP Server, 4.2.4

ORACLE_HOSTNAME environment variable

about, 2.5.2

computers with multiple aliases, 2.5.3

multihomed computers, 2.5.2

setting before installation, 2.5.2

P

password

obfuscating for Oracle HTML DB, 4.3.3

passwords

specifying for response files, A.1

See alsosecurity

patches

downloading for HTML DB, 4.1

downloading for Oracle Companion CD, 4.1

downloading for Oracle Workflow, 4.1

PATH environment variable, 4.2.4

PERL5LIB environment variable, 4.2.3.6

portlist.ini file, C.2

ports

access URLs, C.2

configured for applications, C.2

default ranges, C

Oracle HTTP Server

changing, C.4

ranges and protocol, C.3

Oracle Ultra Search, changing, C.6

Oracle Ultra Search, ranges and protocol, C.3

Oracle Workflow

changing, C.5

ranges and protocol, C.3

postinstallation tasks

Oracle HTML DB, 4.3

Oracle HTTP Server, 4.2

Oracle Workflow, 4.4

Primary Domain Controller (PDC), 3.4.2

primary network adapters

how determined, 2.5.4

See also loopback adapters, network adapters

Q

quick installation, Preface

R

readme.txt file, C.2

record mode, A.2.2

recovery of databases

Oracle Backup and Recovery, 1.3

related documentation, Preface

release notes, 1.1

remote access software, 3.2.3

remote installations, 3.2.3

remote installations, DVD drive, 3.2.2.1

remote Oracle databases

Oracle HTML DB installations and upgrades, 4.3.4

removing

Oracle software, 3.6

response files, using, A.3

software, 3.6

requirements

Oracle Database 10g Companion Products, 2.3

Oracle Database 10g Products, 2.2

Oracle HTML DB, 2.1, 2.1.1

disk space, 2.1.1.2

Oracle HTTP Server requirement, 2.1.1.5

Oracle Text requirement, 2.1.1.7

Oracle XML requirement, 2.1.1.6

Oracle HTTP Server disk space, 2.3.5.1

Oracle HTTP Server in a new Oracle home, 3.3.2, 3.5.1

Oracle Workflow in existing Oracle home, 2.3.4

response files

about, A.1

Automatic Storage Management (ASM), A.1.2

companionCD.db.rsp, A.2.1

companionCD.midtier.rsp, A.2.1

creating

with record mode, A.2.2

with template, A.2.1

error handling, D.4

general procedure, A.1.2

htmldb.HTMLDBONLY.rsp, A.2.1

htmldb.HTMLDBwithOHS.rsp, A.2.1

passing values at command line, A.1

passwords, A.1

record mode, A.2.2

security, A.1

specifying with Oracle Universal Installer, A.3

See also silent mode, noninteractive mode, A.1

S

Sample Schemas, 1.3.3.1

Secure Sockets Layer (SSL) settings, 4.2.3.9

security

See alsopasswords

SERVER_NAME CGI environment variable, D.6

SERVER_PORT CGI environment variable, D.6

silent mode

about, A.1

error handling, D.4

reasons for using, A.1.1

See also noninteractive mode, response files, A.1

SSLCipherSuite setting, 4.2.3.9

starting Oracle HTTP Server, 5.2.1

stopping Oracle HTTP Server, 5.2.1

suppressed mode. See noninteractive mode

T

tablespaces, changing, 3.4.3

Telnet Services support, 2.4.1

Terminal Services support, 2.4.2

troubleshooting, D

cleaning up after failed Companion CD installation, D.3.1

cleaning up after failed Oracle HTML DB installation, D.3.2

HTML DB images not displaying correctly, D.5

Inventory log files, D.2.1

log files

Companion CD, D.2.1

Oracle HTML DB, D.2.2

Oracle HTML DB images, D.5

U

unsupported components

on Windows Terminal Server, 2.4.2

upgrading

AL32UTF8 character set, B.1.1

configuring Oracle HTTP Server 9.0.3, 4.3.2.1

modifying wdbsvr.app, 4.3.2.1

obfuscating password, 4.3.3.2

upgrading. See patches

usernames

WK_TEST, 5.5

WKPROXY, 5.5

WKSYS, 5.5

W

Windows Telnet Services support, 2.4.1

Windows Terminal Servers

unsupported components, 2.4.2

WK_TEST administrative username, 5.5

WKPROXY administrative username, 5.5

WKSYS administrative username, 5.5

X

XML DB requirement, Oracle HTML DB, 2.1.1.6

Copyright © 2006, 2011, Oracle and/or its affiliates. All rights reserved.