Install PDF
Install PDF
Installation Guide
10g Release 3 (10.1.3.1.0) for Linux x86
B31013-01
October 2006
Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0) for Linux x86
B31013-01
Contributing Authors: Deborah Steiner, Rodney Ward, Beth Roeser, Kevin Hwang
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation
and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license
agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City,
CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
Contents
Preface ................................................................................................................................................................. ix
Intended Audience...................................................................................................................................... ix
Documentation Accessibility ..................................................................................................................... ix
Related Documents ..................................................................................................................................... x
Conventions ................................................................................................................................................. x
2 Requirements
2.1 Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and
Software Requirements .............................................................................................................. 2-2
2.2 System Requirements ................................................................................................................. 2-2
2.2.1 Installing from the Console or X Windows ..................................................................... 2-4
2.3 Software Requirements .............................................................................................................. 2-4
2.3.1 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems................ 2-5
2.3.2 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems................ 2-7
2.3.3 Software Requirements for SUSE Linux Enterprise Server 9 Systems ..................... 2-10
2.4 Set Shell Limits for the oracle User........................................................................................ 2-13
2.5 Ports ........................................................................................................................................... 2-14
2.5.1 Checking If a Port Is in Use ............................................................................................. 2-14
2.5.2 Using Default Port Numbers .......................................................................................... 2-14
2.5.3 Using Custom Port Numbers (the "Static Ports" Feature) .......................................... 2-15
2.5.3.1 Format of the staticports.ini File.............................................................................. 2-15
iii
2.5.3.2 Error Conditions that Will Cause the Installer to Use Default Ports Instead of
Specified Ports............................................................................................................ 2-16
2.5.3.3 Ports for Oracle HTTP Server .................................................................................. 2-17
2.5.3.3.1 staticports.ini Example ...................................................................................... 2-17
2.6 Operating System Groups ...................................................................................................... 2-18
2.6.1 Create a Group for the Inventory Directory ................................................................. 2-18
2.7 Operating System User ........................................................................................................... 2-18
2.8 Requirements for the Database .............................................................................................. 2-19
2.9 Installing Database Schemas .................................................................................................. 2-20
2.10 Environment Variables ........................................................................................................... 2-20
2.10.1 Environment Variable Tips ............................................................................................. 2-21
2.10.2 PATH, CLASSPATH, and LD_LIBRARY_PATH ........................................................ 2-21
2.10.3 DISPLAY ............................................................................................................................ 2-21
2.10.4 TNS_ADMIN..................................................................................................................... 2-22
2.10.5 TMP and TMPDIR ............................................................................................................ 2-22
2.10.6 ANT_HOME...................................................................................................................... 2-23
2.10.7 ORA_NLS .......................................................................................................................... 2-23
2.10.8 LD_BIND_NOW ............................................................................................................... 2-23
2.11 Network Topics ........................................................................................................................ 2-23
2.11.1 Installing on a DHCP Host.............................................................................................. 2-23
2.11.2 Installing on Multihomed (Multi-IP) Computers ........................................................ 2-24
2.11.3 Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard
Drive ................................................................................................................................... 2-24
2.11.4 Installing from a Remote CD-ROM or DVD-ROM Drive........................................... 2-25
2.11.5 Installing on Remote Computers.................................................................................... 2-26
2.11.6 Installing on NFS-Mounted Storage .............................................................................. 2-27
2.11.7 Running Multiple Instances from One Installation ..................................................... 2-27
2.11.8 Support for NIS and NIS+ ............................................................................................... 2-27
2.12 Prerequisite Checks Performed by the Installer .................................................................. 2-28
iv
3.10.3 Disk Space Requirements ................................................................................................... 3-6
3.10.4 Software Requirements for Unzipping Files ................................................................... 3-6
3.10.5 Extracting Software from the Zip Files............................................................................. 3-7
3.11 Setting the Mount Point for the CD-ROM or DVD-ROM ..................................................... 3-7
3.12 Starting the Oracle Universal Installer..................................................................................... 3-8
4 Basic Installation
4.1 What Components Are Installed? ............................................................................................ 4-1
4.2 Basic Installation Steps ............................................................................................................... 4-1
4.2.1 Before You Begin.................................................................................................................. 4-2
4.2.2 Installation Steps.................................................................................................................. 4-2
4.3 What Should I Do Next? ............................................................................................................ 4-5
5 Advanced Installation
5.1 What Components Are Installed? ............................................................................................ 5-1
5.1.1 J2EE Server, Web Server and SOA Suite .......................................................................... 5-1
5.1.2 J2EE Server and Web Server .............................................................................................. 5-2
5.1.3 J2EE Server............................................................................................................................ 5-2
5.1.4 Web Server............................................................................................................................ 5-2
5.2 Advanced Installation Steps...................................................................................................... 5-2
5.2.1 Before You Begin.................................................................................................................. 5-3
5.2.2 Installing J2EE Server, Web Server and SOA Suite ........................................................ 5-3
5.2.3 Installing J2EE Server and Web Server............................................................................. 5-4
5.2.4 Installing J2EE Server .......................................................................................................... 5-5
5.2.5 Installing Web Server .......................................................................................................... 5-6
5.3 Installation Screens ..................................................................................................................... 5-7
5.3.1 Oracle Application Server SOA Suite 10.1.3.1.0 Installation Screen ............................ 5-8
5.3.2 Select Installation Type Screen .......................................................................................... 5-9
5.3.3 Specify Database Connect Information Screen............................................................. 5-10
5.3.4 Specify Database Schema Passwords Screen................................................................ 5-11
5.3.5 Specify Port Configuration Options Screen .................................................................. 5-12
5.3.6 Administration Settings Screen ...................................................................................... 5-12
5.3.7 Specify Instance Name Screen ........................................................................................ 5-14
5.3.8 Cluster Topology Configuration Screen - J2EE Server, Web Server, and SOA Suite
Installation ......................................................................................................................... 5-15
5.3.9 Cluster Topology Configuration Screen - J2EE Server and Web Server
Installation ......................................................................................................................... 5-16
5.3.10 Cluster Topology Configuration Screen - J2EE Server Installation........................... 5-18
5.3.11 Cluster Topology Configuration Screen - Web Server Installation ........................... 5-19
5.3.12 Summary Screen ............................................................................................................... 5-21
5.3.13 Install Screen...................................................................................................................... 5-21
5.3.14 Configuration Assistants Screen..................................................................................... 5-22
5.3.15 End of Installation Screen ................................................................................................ 5-24
5.4 Troubleshooting Information................................................................................................. 5-24
5.5 What Should I Do Next? ......................................................................................................... 5-25
v
6 Installing in High Availability Environments
6.1 Overview of High Availability Configurations...................................................................... 6-1
6.1.1 Active-Active Topologies: OracleAS Clusters ................................................................. 6-1
6.1.2 Active-Passive Topologies: OracleAS Cold Failover Clusters ...................................... 6-2
6.1.3 OracleAS Disaster Recovery .............................................................................................. 6-3
6.1.4 Summary of Differences ..................................................................................................... 6-3
6.2 Requirements for High Availability Configurations ............................................................. 6-4
6.2.1 Check Minimum Number of Nodes ................................................................................. 6-4
6.2.2 Check That Groups Are Defined Identically on All Nodes........................................... 6-4
6.2.3 Check the Properties of the oracle User ........................................................................... 6-4
6.2.4 Check for Previous Oracle Installations on All Nodes................................................... 6-5
6.3 Creating the Active-Active Topology ...................................................................................... 6-5
6.3.1 Active-Active Topologies: Introduction ........................................................................... 6-6
6.3.2 OracleAS Clusters in Active-Active Topologies ............................................................. 6-7
6.3.3 Properties of Oracle Application Server Instances in Active-Active Topologies....... 6-8
6.3.4 Installation Steps for Active-Active Topologies.............................................................. 6-8
6.3.5 Supporting Procedures for Creating the Active-Active Topology............................ 6-12
6.3.5.1 Setting up Clusters with the Discovery Server Method ...................................... 6-13
6.3.5.2 Setting up Multicast Replication ............................................................................. 6-13
6.3.5.3 Setting up Peer-to-Peer Replication ........................................................................ 6-14
6.3.5.4 Setting up Replication to a Database ...................................................................... 6-16
6.3.5.5 Setting the Replication Policy .................................................................................. 6-16
6.3.5.6 Specifying the Number of Nodes to Replicate To ................................................ 6-18
6.4 Creating the Active-Passive Topology.................................................................................. 6-18
6.4.1 Active-Passive Topologies: Introduction ...................................................................... 6-18
6.4.2 Overview of Installation Steps for OracleAS Cold Failover Cluster......................... 6-20
6.4.3 Preinstallation Steps for OracleAS Cold Failover Cluster .......................................... 6-21
6.4.3.1 Map the Virtual Hostname and Virtual IP Address............................................. 6-21
6.4.3.2 Set Up a File System That Can Be Mounted from Both Nodes........................... 6-23
6.4.4 OracleAS Cold Failover Cluster: Details of Installation Steps ................................... 6-24
6.5 Creating an OracleAS Disaster Recovery Configuration ................................................... 6-25
6.5.1 OracleAS Disaster Recovery: Introduction ................................................................... 6-26
6.5.2 Setting up the OracleAS Disaster Recovery Environment ......................................... 6-27
6.5.2.1 Ensure Nodes Are Identical at the Operating System Level............................... 6-27
6.5.2.2 Set Up staticports.ini File.......................................................................................... 6-28
6.5.2.3 Set Up Identical Hostnames on Both Production and Standby Sites................. 6-28
6.5.2.4 If You Want to Use OracleAS Cold Failover Cluster on the Production Site
(OracleAS 10.1.2.n.n only) ........................................................................................ 6-32
6.5.3 Installing Oracle Application Server in an OracleAS Disaster Recovery
Environment ...................................................................................................................... 6-33
6.5.3.1 Installing the OracleAS Infrastructure (OracleAS Release 10.1.2.n.n Only) .... 6-34
6.5.3.2 Installing Middle Tiers (OracleAS Release 10.1.3.1.0 and 10.1.2.n.n) ................ 6-34
6.5.4 Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into
Oracle Homes .................................................................................................................... 6-35
6.5.5 Patching OracleAS Guard Release 10.1.2.n.n with Release 10.1.3.1.0 ....................... 6-36
6.5.6 What to Read Next............................................................................................................ 6-36
vi
7 Postinstallation Tasks
7.1 State of Oracle Application Server Instances After Installation........................................... 7-1
7.2 Passwords for Oracle Application Server Components........................................................ 7-1
7.3 NFS Installations ......................................................................................................................... 7-2
7.4 Configuring OracleAS Clusters ................................................................................................ 7-2
7.5 Backup and Recovery ................................................................................................................. 7-2
7.6 SSL................................................................................................................................................. 7-2
7.7 Operating System Locale and NLS_LANG Environment Variable .................................... 7-2
7.7.1 Check the Operating System Locale ................................................................................. 7-2
7.7.2 Check the NLS_LANG Setting .......................................................................................... 7-2
7.8 Proxy Settings .............................................................................................................................. 7-3
7.9 What to Do Next ......................................................................................................................... 7-3
vii
D Configuration Assistants
D.1 Troubleshooting Configuration Assistants ............................................................................ D-1
D.1.1 General Tips......................................................................................................................... D-1
D.1.2 Configuration Assistant Result Codes............................................................................. D-2
D.2 Description of Oracle Application Server Configuration Assistants ................................. D-2
E Troubleshooting
E.1 Log Files ...................................................................................................................................... E-1
E.2 General Troubleshooting Tips ................................................................................................. E-1
E.3 Installation Problems and Solutions ....................................................................................... E-2
E.3.1 Location of Log Files .......................................................................................................... E-2
E.3.2 Linking Failed, ORA Errors .............................................................................................. E-2
E.3.3 Prerequisite Checks Fail at the Start of Installation ....................................................... E-3
E.3.4 Installer Disappears After Running the Preinstallation Checks .................................. E-3
E.3.5 Unable to Clean Up a Failed Installation ........................................................................ E-3
E.3.6 User Interface Does Not Display in the Desired Language, or Does Not Display
Properly................................................................................................................................ E-3
E.3.7 Configuration Assistant Failures - General .................................................................... E-4
E.4 Need More Help?....................................................................................................................... E-4
Index
viii
Preface
The Oracle Application Server Installation Guide covers requirements, new features in the
Oracle Universal Installer, Oracle Application Server concepts that affect installation,
installation procedures, and troubleshooting tips. In addition, this guide also provides
some sample topologies for installing and running Oracle Application Server.
Intended Audience
This guide is intended for users who are comfortable running some system
administration operations, such as creating users and groups, adding users to groups,
and installing operating system patches on the computer where Oracle Application
Server is going to be installed. Users who are installing Oracle Application Server need
root access to run some scripts.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at
http://www.oracle.com/accessibility/
ix
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services
within the United States of America 24 hours a day, seven days a week. For TTY
support, call 800.446.2398.
Related Documents
For additional information, see the following manuals:
■ Oracle Application Server Administrator’s Guide
■ Oracle Application Server Concepts
■ Oracle Application Server High Availability Guide
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.
x
1
Product and Installation Overview
Table 1–1 Oracle Application Server 10g Release 3 (10.1.3.1.0) Install Types
Install Mode Available Installation Types
Basic ■ J2EE Server and SOA Suite
Advanced ■ J2EE Server, Web Server, and SOA Suite
■ J2EE Server and Web Server
■ J2EE Server
■ Web Server
The basic (one-click) installation prompts you with questions on the initial installation
screen, and then it proceeds to install the product without any further user interaction.
The default values for all the components are used.
The advanced installation provides you with a great degree of customization and
flexibility, which enables installation of additional languages, port configuration
options, and cluster configuration.
Table 1–2 summarizes the differences in the customization options between basic and
advanced installation.
10.1.2 Oracle HTTP Server: Two middle tiers, one containing 10g "Configuring Oracle
Release 2 (10.1.2) Oracle HTTP Server and OracleAS Web Cache Application Server 10.1.2
components and the second containing a 10g Release 3 (10.1.3.1.0) with Oracle Application
OC4J instance. Oracle HTTP Server and OracleAS Web Cache are Server 10.1.3" in the Oracle
installed as a part of a J2EE and Web Cache middle-tier installation. Application Server
Administrator’s Guide
10.1.4 or 10.1.2 OracleAS Infrastructure: A 10g Release 3 (10.1.3.1.0) "Configuring Instances to
middle-tier instance using a 10g (10.1.4) or 10g Release 2 (10.1.2) Use a 10.1.4 or 10.1.2 Oracle
Oracle Identity Management. This topology also supports associating Identity Management" in the
a 10g Release 3 (10.1.3.1.0) middle-tier instance with a new 10g (10.1.4) Oracle Application Server
or 10g Release 2 (10.1.2) Oracle Identity Management for the following Administrator’s Guide
scenarios:
"Moving 10.1.4 or 10.1.2
■ Moving to a new host Identity Management to a
New Host" in the Oracle
■ Creating a failover environment
Application Server
Administrator’s Guide
10.1.2 OracleAS Web Cache Instance: A single 10g Release 2 (10.1.2) "Configuring 10.1.2 OracleAS
OracleAS Web Cache acting as a reverse proxy for a 10g Release 3 Web Cache as a Reverse
(10.1.3.1.0) middle-tier. The middle tier contains an integrated OC4J Proxy" in the Oracle
instance with Oracle HTTP Server. Application Server
Administrator’s Guide
10.1.2 OracleAS Web Cache Cluster: Two or more 10g Release 2 "Configuring 10.1.2 OracleAS
(10.1.2) OracleAS Web Cache servers configured as a cluster to reverse Web Cache as a Reverse
proxy a 10g Release 3 (10.1.3.1.0) middle-tier. The middle tier contains Proxy" in the Oracle
an integrated OC4J instance with Oracle HTTP Server. Application Server
Administrator’s Guide
The remainder of this section addresses the recommended topologies for installing
Oracle HTTP Server and OC4J instances. It contains the following topics:
■ Section 1.3.1, "Installing a Standalone OC4J Instance"
■ Section 1.3.2, "Installing an Integrated Web Server and OC4J Middle Tier"
■ Section 1.3.3, "Installing a SOA Administration Instance"
■ Section 1.3.4, "Installing a J2EE Server with the SOA Suite"
■ Section 1.3.5, "Installing J2EE Server, Web Server, and the SOA Suite"
■ Section 1.3.6, "Installing J2EE Server and the SOA Suite with a Remote Oracle
HTTP Server"
■ Section 1.3.7, "Installing J2EE Server and Separate SOA Applications with a
Remote Oracle HTTP Server"
■ Section 1.3.8, "Installing Multiple SOA Middle Tiers with a Remote Oracle HTTP
Server"
Oracle_Home1
HTTP Listener
OC4J
(OC4J_Dev)
Jazn-data.xml
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform an advanced installation of J2EE Server, as described in Section 5.2.4,
"Installing J2EE Server". During the installation procedure, follow the prompts,
ensuring you perform the following:
■ On the Administration Settings screen, do not select Configure this as an
Administration OC4J instance.
■ On the Cluster Topology Configuration screen, do not select Access this OC4J
instance from a separate Oracle HTTP Server.
Oracle_Home1
AJP
OC4J
(OC4J_Dev)
Jazn-data.xml
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform an advanced installation of J2EE Server and Web Server, as described in
Section 5.2.3, "Installing J2EE Server and Web Server". During the installation
procedure, follow the prompts, ensuring you perform the following:
■ On the Administration Settings screen, do not select Configure this as an
Administration OC4J instance.
Oracle_Home1
AJP AJP
Application Java
Server Single
Control Sign-On
OC4J
(Home)
Jazn-data.xml
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform an advanced installation of J2EE Server and Web Server, as described in
Section 5.2.3, "Installing J2EE Server and Web Server". During the installation
procedure, follow the prompts, ensuring you perform the following:
■ On the Administration Settings screen, select Configure this as an Administration
OC4J instance.
Oracle_Home1
HTTP Listener
OC4J
(OC4J_SOA)
BPEL ESB OWSM
Application Server
Control
Jazn-data.xml
Oracle
Database
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform a basic installation, as described in Section 4.2, "Basic Installation Steps".
1.3.5 Installing J2EE Server, Web Server, and the SOA Suite
The J2EE Server, Web Server, and SOA Suite installation type in advanced installation
mode combines the SOA Suite, Oracle HTTP Server, and OC4J middle-tier instance in
the same Oracle home, as depicted in Figure 1–5. This topology is suitable for SOA
developers.
Figure 1–5 J2EE Server, Web Server, and the SOA Suite
Oracle_Home1
AJP AJP
OC4J OC4J
(OC4J_SOA) (Home)
Jazn-data.xml
Oracle
Database
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
Perform an advanced installation of J2EE Server, Web Server and SOA Suite, as
described in Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite". During
the installation procedure, follow the prompts, ensuring you perform the following:
■ On the Administration Settings screen, select Configure this as an Administration
OC4J instance.
■ On the Cluster Topology Configuration screen, do not select Access this OC4J
Instance from a separate Oracle HTTP Server.
1.3.6 Installing J2EE Server and the SOA Suite with a Remote Oracle HTTP Server
Figure 1–6 shows a topology in which you install Oracle HTTP Server on one
computer and OC4J and the SOA Suite on another computer. Then, you cluster the
instances using dynamic node discovery. This topology enables Oracle HTTP Server to
route requests to OC4J, and OC4J to dynamically notify Oracle HTTP Server of new
application bindings when an application is deployed. It also allows for flexibility and
growth.
Figure 1–6 Cluster with J2EE Server and the SOA Suite and a Remote Oracle HTTP
Server
Oracle_Home1
AJP AJP
Oracle_Home2
OC4J OC4J
(OC4J_SOA) (Home)
Jazn-data.xml
Oracle
Database
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
1. For the first middle tier, install a Web Server instance.
Perform an advanced installation of Web Server, as described in Section 5.2.5,
"Installing Web Server". During the installation procedure, follow the prompts,
ensuring you perform the following:
■ On the Cluster Topology Configuration screen, select Configure this Oracle
HTTP Server instance to be a part of an Oracle Application Server cluster
and specify a cluster discovery address for the cluster. The multicast address
you enter must be within the valid address range, which is 224.0.1.0 to
239.255.255.255.
Make a note of the address and port that you enter on this page; you will need
them later.
■ Make a note of the hostname and port for the Oracle HTTP Server instance;
you will need them later.
2. For the second middle tier, install a J2EE Server, Web Server and SOA Suite
instance.
Perform an advanced installation of J2EE Server, Web Server and SOA Suite, as
described in Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite".
During the installation procedure, follow the prompts, ensuring you perform the
following:
■ On the Administration Settings screen, select Configure this as an
Administration OC4J instance.
■ On the Cluster Topology Configuration screen, select Access this OC4J
Instance from a separate Oracle HTTP Server. Specify the hostname and port
for the middle tier you installed in Step 1 of this procedure.
On this same screen, select Configure this instance to be part of an Oracle
Application Server cluster topology and specify the same cluster discovery
address as you specified in Step 1 of this procedure.
3. Configure Java Single Sign-On. Perform the following steps on the second Oracle
Application Server instance you just installed (Oracle_Home2 in Figure 1–6):
a. Access the Oracle Enterprise Manager 10g Application Server Control
Console.
b. Scroll to the Administration section and click Java SSO Configuration.
The Java SSO Configuration page appears.
c. Click Participating Applications.
The applications are listed.
d. Click the check box for the following applications to be Java SSO enabled:
– orabpel (for Oracle BPEL Process Manager)
– esb-dt (for Oracle Enterprise Service Bus)
– ccore (for Oracle Web Services Manager)
– ascontrol (for Application Server Control Console)
e. Click Apply.
A confirmation message appears that the SSO configuration was completed
and will take effect after the instances are restarted.
f. Click Restart.
A confirmation message appears.
g. Click Yes.
The instance is restarted.
h. To configure JSSO for OWSM, perform the following steps:
– Navigate to ORACLE_HOME/owsm/bin.
– Edit the ORACLE_HOME/owsm/bin/install.properties file to set the
install.sso.support property to true.
– Run the following command:
prompt> wsmadmin.sh deploy password console
i. Reconfigure the owsm console application with the OID security provider as
described in "Steps to Use the Oracle Identity Management Security Provider"
and "Settings for Authentication Method with Oracle Identity Management" in
the Oracle Containers for J2EE Security Guide, Chapter 8.
1.3.7 Installing J2EE Server and Separate SOA Applications with a Remote Oracle
HTTP Server
This topology is similar to the example in the previous section, Section 1.3.6. As in the
previous section, this topology has an Oracle HTTP Server in one home and OC4J and
the SOA applications in a separate Oracle home. Unlike the previous example, the
SOA applications are separated, each with its own OC4J instance, as depicted in
Figure 1–7.
Figure 1–7 Cluster with J2EE Server and Separate SOA Applications and a Remote
Oracle HTTP Server
Oracle_Home1
AJP AJP
Oracle_Home2
Oracle
Database
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
1. For the first middle tier, install a Web Server instance.
1.3.8 Installing Multiple SOA Middle Tiers with a Remote Oracle HTTP Server
This topology builds upon the example in Section 1.3.6. It adds an additional OC4J
instance with the SOA Suite, as shown in Figure 1–8. When you install this cluster
topology, you install Oracle HTTP Server on one computer, install OC4J and SOA Suite
instances on two separate computers, and specify cluster settings. You designate one
of the OC4J instances as the Administration OC4J instance for running the Application
Server Control Console. You manage both OC4J instances from this instance of
Application Server Control Console.
Figure 1–8 Cluster with Multiple SOA Middle Tiers and a Remote Oracle HTTP Server
Oracle_Home1
AJP AJP
Oracle_Home2 Oracle_Home3
JDBC JDBC
Oracle
LDAP Database
User Repository
Requirements
The requirements are the same as those listed in Chapter 2, "Requirements".
Installation Sequence
To install this topology:
1. For the first middle tier, install a Web Server instance.
Perform an advanced installation of Web Server, as described in Section 5.2.5,
"Installing Web Server". During the installation procedure, follow the prompts,
ensuring you perform the following:
■ On the Cluster Topology Configuration screen, select Configure this Oracle
HTTP Server instance to be a part of an Oracle Application Server cluster
and specify a cluster discovery address for the cluster. The multicast address
you enter must be within the valid address range, which is 224.0.1.0 to
239.255.255.255.
Make a note of the address and port that you enter on this page; you will need
them later.
■ Make a note of the hostname and port for the Oracle HTTP Server instance;
you will need them later.
2. For the second middle tier, install a J2EE Server, Web Server and SOA Suite
instance.
Perform an advanced installation of J2EE Server, Web Server and SOA Suite, as
described in Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite".
During the installation procedure, follow the prompts, ensuring you perform the
following:
■ On the Administration Settings screen, select Configure this as an
Administration OC4J instance.
■ On the Cluster Topology Configuration screen, select Access this OC4J
Instance from a separate Oracle HTTP Server. Specify the hostname and port
for the middle tier you installed in Step 1 of this procedure.
On this same screen, select Configure this instance to be part of an Oracle
Application Server cluster topology and specify the same cluster discovery
address as you specified in Step 1 of this procedure.
3. For the third middle tier, install a J2EE Server, Web Server and SOA Suite instance.
Perform an advanced installation of J2EE Server, Web Server and SOA Suite, as
described in Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite".
During the installation procedure, follow the prompts, ensuring you perform the
following:
■ On the Administration Settings screen, do not select Configure this as an
Administration OC4J instance.
■ On the Cluster Topology Configuration screen, select Access this OC4J
Instance from a separate Oracle HTTP Server. Specify the hostname and port
for the middle tier you installed in Step 1 of this procedure.
On this same screen, select Configure this instance to be part of an Oracle
Application Server cluster topology and specify the same cluster discovery
address as you specified in Step 1 of this procedure.
4. Configure Java Single Sign-On. Perform the following steps on the second Oracle
Application Server instance you just installed (Oracle_Home2 in Figure 1–8):
a. Access the Oracle Enterprise Manager 10g Application Server Control
Console.
b. Scroll to the Administration section and click Java SSO Configuration.
The Java SSO Configuration page appears.
c. Click Participating Applications.
The applications are listed.
d. Click the check box for the following applications to be Java SSO enabled:
– orabpel (for Oracle BPEL Process Manager)
– esb-dt (for Oracle Enterprise Service Bus)
– ccore (for Oracle Web Services Manager)
– ascontrol (for Application Server Control Console)
e. Click Apply.
A confirmation message appears that the SSO configuration was completed
and will take effect after the instances are restarted.
f. Click Restart.
A confirmation message appears.
g. Click Yes.
The instance is restarted.
h. To configure JSSO for OWSM, perform the following steps:
– Navigate to ORACLE_HOME/owsm/bin.
– Edit the ORACLE_HOME/owsm/bin/install.properties file to set the
install.sso.support property to true.
– Run the following command:
prompt> wsmadmin.sh deploy password console
Before installing Oracle Application Server, ensure that your computer meets the
requirements described in this chapter.
Requirements 2-1
Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and Software Requirements
After logging into OracleMetaLink, click Certify. From the resulting Web page, you can
view the latest certifications by product, platform, and product availability.
DVD-ROM:
prompt> mount_point/application_server/runInstaller -executeSysPrereqs
The results are displayed on the screen as well as written to a log file. For more
information on the types of checks performed, see Section 2.12, "Prerequisite Checks
Performed by the Installer".
Checked by Installer: No
Processor Speed 300 MHz or faster
To determine the processor speed, run the following command:
prompt> cat /proc/cpuinfo | grep MHz
cpu MHz : 2992.553
Replace dir with the Oracle home directory or with the parent directory if the Oracle home
directory does not exist yet. For example, if you plan to install Oracle Application Server in
/opt/oracle/j2ee, you can replace dir with /opt/oracle or /opt/oracle/j2ee.
Checked by Installer: Yes
Requirements 2-3
Software Requirements
If the /tmp directory does not have enough free space, you can specify a different directory
by setting the TMP or TMPDIR environment variable. See Section 2.10.5, "TMP and
TMPDIR" for details.
Checked by Installer: Yes
Swap space 512 MB of available swap space
To determine the amount of available swap space, enter the following command:
prompt> grep SwapTotal /proc/meminfo
If necessary, see your operating system documentation for information on how to configure
additional swap space.
Checked by Installer: Yes
Monitor 256 color display
To determine your monitor’s display capabilities, run the following command:
prompt> /usr/X11R6/bin/xdpyinfo
Look for the "depths" line. You need a depth of at least 8 (bits per pixel).
Checked by Installer: Yes
Supported browsers Oracle Enterprise Manager 10g is supported on the following browsers:
■ Microsoft Internet Explorer 6.0 SP2 (supported on Microsoft Windows only)
■ Netscape 7.2
■ Mozilla 1.7. You can download Mozilla from http://www.mozilla.org.
■ Firefox 1.0.4. You can download Firefox from http://www.mozilla.org.
■ Safari 1.2, 2.0 (on Apple Macintosh computers)
For the most current list of supported browsers, check the OracleMetaLink site
(http://metalink.oracle.com).
Checked by Installer: No. However, if you access Oracle Enterprise Manager 10g using a
non-supported browser, you will get a warning message.
■ Section 2.3.2, "Software Requirements for Red Hat Enterprise Linux AS/ES 4.0
Systems"
■ Section 2.3.3, "Software Requirements for SUSE Linux Enterprise Server 9 Systems"
Oracle does not support customized kernels or modules not supported by the Linux
vendor.
You can install Oracle Application Server 10g Release 3 (10.1.3.1.0) on a Linux system
that is not on a network and you can install Oracle Application Server 10g Release 3
(10.1.3.1.0) on a Linux system that is configured to use DHCP. If you want to install
Oracle Application Server on a computer that is not on a network you must configure
the computer to use either a static IP address or a loopback IP address. Configure the
computer to resolve the hostname of the computer to either a static IP address or a
loopback IP address.
2.3.1 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems
Table 2–3 lists the software requirements for Red Hat Enterprise Linux AS/ES 3.0
systems and the procedure that follows the table describes how to ensure your system
meets these requirements and any additional requirements for installing Oracle
Application Server.
Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux
Enterprise Server 9 are certified and supported. For the most current
list of supported Linux Operating Systems, check OracleMetaLink
(http://metalink.oracle.com).
Table 2–3 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems
Item Requirement
Operating Red Hat Enterprise Linux AS/ES 3.0
System
For more information on Red Hat, see:
http://www.redhat.com
Requirements 2-5
Software Requirements
Table 2–3 (Cont.) Software Requirements for Red Hat Enterprise Linux AS/ES 3.0
Item Requirement
Software glibc-2.3.2-95.27
packages glibc-common-2.3.2-95.27
(check that these binutils-2.14.90.0.4-35
versions or compat-glibc-7.x-2.2.4.32.6
higher versions compat-libstdc++-7.3-2.96.128
are installed) compat-libstdc++-devel-7.3-2.96.128
gcc-3.2.3-42
gcc-c++-3.2.3-42
libstdc++-3.2.3-42
libstdc++-devel-3.2.3-42
openmotif21-2.1.30-8
pdksh-5.2.14-21
setarch-1.3-1
make-3.79.1-17
gnome-libs-1.4.1.2.90-34.1
sysstat-4.0.7-4.EL3.3
compat-db-4.0.14-5
Note: For Red Hat Enterprise Linux AS/ES 3.0, the equivalent version of
openmotif 2.1.30-8 is openmotif21-2.1.30-8. The
openmotif21-2.1.30-8 package can be installed from disk number 3
of the Red Hat Enterprise Linux AS/ES 3.0 distribution by entering:
$ rpm -ivh openmotif21-2.1.30-8
64-bit Red Hat Enterprise Linux AS/ES 3.0, Update 3 or higher, is certified on
Certification AMD64 and Intel EM64T. The following packages (or higher versions) are
required:
glibc-2.3.2-95.27.x86_64.rpm
glibc-3.2.3-95.27.i686.rpm (32-bit)
glibc-devel-3.2.3-95.27.x86_64.rpm
glibc-devel-3.2.3-95.27.i386.rpm (32-bit)
gcc-3.2.3-20.x86_64.rpm
libgcc-3.2.3-20.x86_64.rpm
libgcc-3.2.3-20.i386.rpm (32-bit)
setarch-1.3-1.x86_64.rpm
pdksh-5.2.14-21.x86_64.rpm
openmotif21-2.1.30-8.i386.rpm
compat-glibc-7.x-2.2.4.32.5.i386.rpm (32-bit)
compat-gcc-7.3-2.96.122.i386.rpm
sysstat-4.0.7-4.x86_64.rpm
gnome-libs-1.4.1.2.90-34.1.i386.rpm (32-bit)
compat-db-4.0.14-5.1.i386.rpm (32-bit)
To ensure that the system meets all the requirements, follow these steps:
1. Log in as the root user.
Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux
Enterprise Server 9 are certified and supported. For the most current
list of supported Linux Operating Systems, check OracleMetaLink
(http://metalink.oracle.com).
When installing a package, make sure you are using the correct architecture and
optimization rpm file. To check the architecture of an rpm file, run the following
command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
5. If the hugemem kernel is used, set the architecture using following command:
prompt> setarch i386
2.3.2 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems
Table 2–4 lists the software requirements for Red Hat Enterprise Linux AS/ES 4.0
systems and the procedure that follows the table describes how to ensure your system
meets these requirements and any additional requirements for installing Oracle
Application Server.
Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux
Enterprise Server 9 are certified and supported. For the most current
list of supported Linux Operating Systems, check OracleMetaLink
(http://metalink.oracle.com).
Requirements 2-7
Software Requirements
Table 2–4 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems
Item Requirement
Operating Red Hat Enterprise Linux AS/ES 4.0
System
For more information on Red Hat, see:
http://www.redhat.com
Table 2–4 (Cont.) Software Requirements for Red Hat Enterprise Linux AS/ES 4.0
Item Requirement
64-bit Red Hat Enterprise Linux AS/ES 4.0, Update 1 or higher, is certified on
Certification AMD64 and Intel EM64T. The following packages (or higher versions) are
required:
binutils-2.15.92.0.2-13.x86_64.rpm
compat-db-4.1.25-9.i386.rpm (32-bit)
compat-db-4.1.25-9.x86_64.rpm
control-center-2.8.0-12.x86_64.rpm
gcc-3.4.3-22.1.x86_64.rpm
gcc-c++-3.4.3-22.1.x86_64.rpm
glibc-2.3.4-2.9.i686.rpm (32-bit)
glibc-2.3.4-2.9.x86_64.rpm
glibc-common-2.3.4-2.9.x86_64.rpm
gnome-libs-1.4.1.2.90-44.1.x86_64.rpm
libstdc++-3.4.3-22.1.i386.rpm (32-bit)
libstdc++-3.4.3-22.1.x86_64.rpm
libstdc++-devel-3.4.3-22.1.i386.rpm (32-bit)
libstdc++-devel-3.4.3-22.1.x86_64.rpm
make-3.80-5.x86_64.rpm
pdksh-5.2.14-30.x86_64.rpm
sysstat-5.0.5-1.x86_64.rpm
xscreensaver-4.18-5.rhel4.2.x86_64.rpm
setarch-1.6-1.x86_64
openmotif21-2.1.30-11.RHEL4.4.i386.rpm (32-bit)
To ensure that the system meets all the requirements, follow these steps:
1. Log in as the root user.
2. To determine which distribution and version of Linux is installed, enter the
following command:
# cat /etc/issue
Red Hat Enterprise Linux AS release 4 (Nahant Update 1)
Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux
Enterprise Server 9 are certified and supported. For the most current
list of supported Linux Operating Systems, check OracleMetaLink
(http://metalink.oracle.com).
Requirements 2-9
Software Requirements
When installing a package, make sure you are using the correct architecture and
optimization rpm file. To check the architecture of an rpm file, run the following
command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
5. If the hugemem kernel is used, set the architecture using following command:
prompt> setarch i386
Table 2–5 Software Requirements for SUSE Linux Enterprise Server 9 Systems
Item Requirement
Operating SUSE Linux Enterprise Server 9
System
For more information on SUSE Linux Enterprise Server, see:
http://www.suse.com
Table 2–5 (Cont.) Software Requirements for SUSE Linux Enterprise Server 9 Systems
Item Requirement
Software glibc-2.3.3-98.28
packages gcc-3.3.3-43.24
(check that these gcc-c++-3.3.3-43.24
versions or libstdc++-3.3.3-43.24
higher versions libstdc++-devel-3.3.3-43.24
are installed) openmotif21-libs-2.1.30MLI4-119.1
pdksh-5.2.14-780.1
make-3.80-184.1
gnome-libs-1.4.1.7-671.1
gnome-libs-devel-1.4.1.7-671.1
sysstat-5.0.1-35.1
binutils-2.15.90.0.1.1-32.5
64-bit SUSE Linux Enterprise Server is certified on AMD64 and Intel EM64T.
Certification The following packages (or higher versions) are required:
glibc-2.3.3-98.28.x86_64.rpm
glibc-32bit-9-200407011233.x86_64.rpm
glibc-devel-32bit-9-200407011229.x86_64.rpm
gcc-3.3.3-43.24.x86_64.rpm
gcc-3.2.3-20.x86_64.rpm
gcc-c++-3.3.3-43.24.x86_64.rpm
libgcc-3.2.3-20.i386.rpm (32-bit)
libstdc++-3.3.3-43.24.x86_64.rpm
libstdc++-devel-3.3.3-43.24.x86_64.rpm
libstdc++-devel-32bit-9-200407011229.x86_64.rpm
gnome-libs-1.4.1.7-671.1.x86_64.rpm
gnome-libs-devel-1.4.1.7-671.1.x86_64.rpm
gnome-libs-32bit-9-200407011229.x86_64.rpm
binutils-2.15.90.0.1.1-32.5.x86_64.rpm
binutils-32bit-9-200407011229.x86_64.rpm
compat-32bit-9-200407011229.x86_64.rpm
compat-sles8-1.3-93.3.x86_64.rpm
compat-2004.7.1-1.2.x86_64.rpm
pdksh-5.2.14-780.1.x86_64.rpm
make-3.80-184.1.x86_64.rpm
sysstat-5.0.1-35.1.x86_64.rpm
perl-32bit-9-200407011229.x86_64.rpm
libaio-devel-32bit-9-200407011229.x86_64.rpm
XFree86-devel-32bit-9-200407011229.x86_64.rpm
linux32-1.0-341.1.x86_64.rpm
db-32bit-9-200407011229.x86_64.rpm
db1-32bit-9-200407011229.x86_64.rpm
compat-32bit-9-200407011229.x86_64.rpm
Always use 32-bit shell emulation, use the following command before
running the installer and any other Oracle Application Server commands
or scripts:
# linux32 bash
To ensure that the system meets all the requirements, follow these steps:
1. Log in as the root user.
2. To determine which distribution and version of Linux is installed, enter the
following command:
Requirements 2-11
Software Requirements
Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux
Enterprise Server 9 are certified and supported. For the most
current list of supported Linux Operating Systems, check
OracleMetaLink (http://metalink.oracle.com).
When installing a package, make sure you are using the correct architecture and
optimization rpm file. To check the architecture of an rpm file, run the following
command:
prompt> rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
prompt> rpm -q glibc --queryformat "%{arch}\n"
i686
4. Create the following symbolic link for the Perl executable if it does not already
exist:
prompt> ln -sf /usr/bin/perl /usr/local/bin/perl
5. Create the following symbolic link for the fuser executable if it does not already
exist:
prompt> ln -sf /bin/fuser /sbin/fuser
6. If the orarun package was installed on a SUSE Linux Enterprise Server system,
complete the following steps as the oracle user to reset the environment:
a. Enter the following commands:
prompt> cd /etc/profile.d
prompt> mv oracle.csh oracle.csh.bak
prompt> mv oracle.sh oracle.sh.bak
prompt> mv alljava.sh alljava.sh.bak
prompt> mv alljava.csh alljava.csh.bak
b. Use any text editor to comment out the following line from the
$HOME/.profile file:
. ./.oracle
Note: Oracle recommends that you do not install any of the Java
packages supplied with the SUSE Linux Enterprise Server
distribution.
b. Make sure that the following line exists in the /etc/nsswitch.conf file:
hosts: files nis dns
9. Make sure that the localhost entry in the /etc/hosts file is an IPv4 entry. If
the IP entry for localhost is IPv6 format, installation cannot succeed. The
following example shows an IPv6 entry:
prompt> special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
::1 ipv6-localhost ipv6-loopback
To correct this example /etc/hosts file, comment the localhost entry as follows:
prompt> special IPv6 addresses
prompt> ::1 localhost ipv6-localhost ipv6-loopback
::1 ipv6-localhost ipv6-loopback
To comment the entries, you can use the perl script included in the
utils/4015045/ directory of CD-ROM Disk 1 and in the application_
server/utils/4015045/ directory on the DVD-ROM. Run the script as the
root user. This script is also available as patch 4015045. This patch is available
from:
http://metalink.oracle.com
2. Add the following line to the /etc/pam.d/login file, if it does not already exist:
Requirements 2-13
Ports
3. Depending on the oracle user's default shell, make the following changes to the
default shell start-up file:
■ For the Bourne, Bash, or Korn shell, add the following lines to the
/etc/profile file:
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
■ For the C or tcsh shell, add the following lines to the /etc/csh.login file:
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif
2.5 Ports
Many Oracle Application Server components, such as Oracle HTTP Server, use ports.
You can have the installer assign default port numbers, or use port numbers that you
specify.
■ Section 2.5.1, "Checking If a Port Is in Use"
■ Section 2.5.2, "Using Default Port Numbers"
■ Section 2.5.3, "Using Custom Port Numbers (the "Static Ports" Feature)"
Why the Default Port for Oracle HTTP Server Is Port 7777 and Not Port 80
By default, the installer configures Oracle HTTP Server to use port 7777, not port 80.
Port 7777 is the default port because on UNIX, components that use port numbers
lower than 1024 require additional steps to be done as the root user before the
components can run. Because the installer does not have root access, it has to use a
port greater than 1024.
If you want Oracle HTTP Server to use a different port, such as port 80, use the "static
ports" feature, which enables you to specify port numbers for components. Although
you can change the port number after installation, it is easier to set the port number
during installation.
numbers and ranges. Make sure that at least one port is available in the port range for
each component. If the installer is unable to find a free port in the range, the
installation will fail.
The easiest way to create the file is to use the staticports.ini file on the CD-ROM
(Disk 1) or DVD-ROM as a template:
1. Copy the staticports.ini file from the CD-ROM or DVD-ROM to your hard
disk.
2. Edit the local copy (the file on the hard disk) to include the desired port numbers.
You do not need to specify port numbers for all components in the
staticports.ini file. If a component is not listed in the file, the installer uses
the default port number for that component.
The following example sets the Oracle HTTP Server ports and some Oracle
Process Manager and Notification Server ports. For components not specified, the
installer will assign the default port numbers.
Oracle HTTP Server port = 2000
Oracle HTTP Server SSL port = 2001
Oracle Notification Server Request port = 2002
Oracle Notification Server Local port = 2003
When installation is complete, you can run the following commands to see the
assigned ports:
Requirements 2-15
Ports
The installer verifies that the ports specified in the file are available by checking
memory. This means that it can only detect ports that are being used by running
processes. It does not look in configuration files to determine which ports an
application is using.
If the installer detects that a specified port is not available, it displays an alert. The
installer will not assign a port that is not available. To fix this:
1. Edit the staticports.ini file to specify a different port, or shut down the
application that is using the port.
2. Click Retry. The installer re-reads the staticports.ini file and verifies the
entries in the file again.
2.5.3.2 Error Conditions that Will Cause the Installer to Use Default Ports Instead
of Specified Ports
Check your staticports.ini file carefully because a mistake can cause the installer
to use default ports without displaying any warning. Here are some things that you
should check:
■ If you specify the same port for more than one component, the installer will use
the specified port for the first component, but for the other components, it will use
the components’ default ports. The installer does not warn you if you have
specified the same port for multiple components.
■ If you specify different ports for one component on multiple lines, the installer
assigns the default port for the component. The installer does not warn you if you
have specified different ports for one component.
■ If you specify the same port for one component on multiple lines, the installer
assigns the default port for the component. The installer does not warn you if you
have specified the same port on multiple lines.
■ If you have syntax errors in the staticports.ini file (for example, if you
omitted the = character for a line), the installer ignores the line. For the
components specified on such lines, the installer assigns the default ports. The
installer does not display a warning for lines with syntax errors.
■ If you misspell a component name, the installer assigns the default port for the
component. Names of components in the file are case sensitive. The installer does
not display a warning for lines with unrecognized names.
■ If you specify a non-numeric value for the port number, the installer ignores the
line and assigns the default port number for the component. It does this without
displaying any warning.
■ If you specify a relative path to the staticports.ini file (for example,
"./staticports.ini" or just "staticports.ini"), the installer will not find
the file. The installer continues without displaying a warning and it will assign
default ports to all components. You must specify a full path to the
staticports.ini file.
To set the SSL version of these ports, use the following lines. As in the non-SSL
version, the port numbers must be the same.
Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443
Line in staticports.ini
Uses this directive
to set the value for the
in the httpd.conf file
directive
Note: You must specify the same port number for both directives.
2.5.3.3.1 staticports.ini Example In this scenario, configure Oracle HTTP Server to use
ports 80 and 443. Create a staticports.ini file that includes the following lines:
Oracle HTTP Server port = 80
Oracle HTTP Server Listen port = 80
Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443
Requirements 2-17
Operating System Groups
Note: Because you are using ports less than 1024, you have to
configure Oracle HTTP Server to run as the root user. You can
perform the configuration during installation or after installation.
■ You can choose to perform the configuration after installation,
but note that the installer will not be able to start up the
components (because they are not yet configured).
For details, see the Oracle HTTP Server Administrator’s Guide.
For more information about operating system users and groups, see your operating
system documentation or contact your system administrator.
If the computer contains other Oracle products, you might already have a user for this
purpose. Look in the /etc/oraInst.loc file. This file lists the location of the
inventory directory and the group who owns it. If the file does not exist, the computer
does not have Oracle products installed on it.
If you do not already have a user for installing Oracle products, create a user with the
following properties:
Table 2–7 Properties of the Operating System User Who Runs the Installer
Item Description
Login name You can use any name for the user. This guide refers to the user as the
oracle user.
Group identifier The primary group of the oracle user must have write permission for
the oraInventory directory. See Section 2.6.1, "Create a Group for the
Inventory Directory" for more information about this group.
You can use any name for the group. This guide uses the name
oinstall.
Home directory The home directory for the oracle user can be consistent with the
home directories of other users.
Login shell The default login shell can be the C, Bourne, or Korn shell.
Note: Use the oracle user only for installing and running Oracle
products. Do not use root as the oracle user.
In this command:
– The -g option specifies the primary group, which must be the Oracle
Inventory group, for example oinstall
– The -G option specifies the secondary groups, which must include the OSDBA
group and if required, the OSOPER group, for example dba or dba,oper
2. Set the password of the oracle user:
# passwd oracle
To check which groups an operating system user belongs to, run the groups
command with the name of the user. For example:
prompt> groups oracle
For more information about operating system users and groups, see your operating
system documentation or contact your system administrator.
Requirements 2-19
Installing Database Schemas
■ If you use the su command to switch users (for example, switching from the root
user to the oracle user), check the environment variables when you are the new
user because the environment variables might not be passed to the new user. This
can happen even if you run su with the - parameter (su - user).
# /* root user */
# su - oracle
% env
2.10.3 DISPLAY
Set the DISPLAY environment variable to point to the X server that will display the
installer. The format of the DISPLAY environment variable is:
hostname:display_number.screen_number
Example (C shell):
% setenv DISPLAY test.mydomain.com:0.0
Oracle Application Server requires a running X server during installation only. The
frame buffer X server installed with your operating system requires that you remain
logged in and have the frame buffer running during installation. If you do not wish to
Requirements 2-21
Environment Variables
do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer
(XVFB) or Virtual Network Computing (VNC).
Visit Oracle Technology Network (http://www.oracle.com/technology) for
information about obtaining and installing XVFB or other virtual frame buffer
solutions. Search OTN for "frame buffer".
2.10.4 TNS_ADMIN
This section describes two requirements:
■ The TNS_ADMIN environment variable must not be set. If set, it can cause errors
during installation.
■ The /etc directory must not contain a tnsnames.ora file.
These requirements are necessary to prevent conflicts between the Net configuration
files for different Oracle products.
If you need to set TNS_ADMIN or if you have the tnsnames.ora file in /etc, do the
following steps before installing Oracle Application Server.
1. If you have the tnsnames.ora file in /etc, move the file from this directory to a
different directory. Alternatively, you can rename the file.
2. Make sure the TNS_ADMIN environment variable is not set.
Example (C shell):
% unsetenv TNS_ADMIN
After installation, you can merge the contents of the newly created tnsnames.ora
file with your existing tnsnames.ora file.
If you do not set this environment variable, and the default directory does not have
enough space, then the installer displays an error message that says the environment
variable is not set. You can either set the environment variable to point to a different
directory or free up enough space in the default directory. In either case, you have to
restart the installation.
2.10.6 ANT_HOME
To make sure that the Oracle Application Server installation completes successfully,
unset this environment variable.
Example:
% unset ANT_HOME
Additionally, you must either remove the /etc/ant.conf file or comment out the
line in the /etc/ant.conf file that incorrectly sets the ANT_HOME environmental
variable.
2.10.7 ORA_NLS
To make sure that the Oracle Application Server installation completes successfully,
unset this environment variable.
Example:
$ unset ORA_NLS
2.10.8 LD_BIND_NOW
To make sure that the Oracle Application Server installation completes successfully,
unset this environment variable.
Example:
$ unset LD_BIND_NOW
Requirements 2-23
Network Topics
1. Find the IP address allocated from the DHCP server by running the following
command:
$ /sbin/ifconfig -a
b. Check that the hostname resolves to the loopback IP address by entering the
following command:
$ /bin/ping hostname.domainname
2.11.3 Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive
Instead of installing from the Oracle Application Server CD-ROMs or DVD-ROM, you
can copy the contents of the CD-ROMs or DVD-ROM to a hard drive and install from
there. This might be easier if you plan to install many instances of Oracle Application
Server on your network, or if the computers where you want to install Oracle
Application Server do not have CD-ROM or DVD-ROM drives.
(You can install from remote CD-ROM or DVD-ROM drives; see Section 2.11.4,
"Installing from a Remote CD-ROM or DVD-ROM Drive".)
When you install from the hard drive, the installer does not prompt you to swap
CD-ROMs. It can find all the files if they are in the proper locations (see Figure 2–2).
Space Requirement
Ensure that the hard drive contains enough space to hold the contents of the
CD-ROMs or the application_server directory on the DVD-ROM. Each CD-ROM
contains approximately 650 MB. This means that if you are copying three CD-ROMs,
you need approximately 1.9 GB of disk space.
On the DVD-ROM, the application_server directory is approximately 1.6 GB.
This space is in addition to the space required for installing Oracle Application Server
(listed in Table 2–2).
OracleAS_10g
To run the installer from the copied files, invoke the runInstaller executable from
the Disk1 directory. Run it from the computer that will be running Oracle Application
Server.
prompt> /path/to/hard/drive/Disk1/runInstaller
To run the installer from the copied files, invoke the runInstaller executable from
the computer that will be running Oracle Application Server:
prompt> /path/to/hard/drive/application_server/runInstaller
Requirements 2-25
Network Topics
If you do not run xhost, you might get an Xlib error similar to "Failed to connect
to server", "Connection refused by server," or "Can’t open display" when starting
the installer.
2. On local_computer, perform a remote login (using telnet or rlogin) to remote_
computer. Log in as the oracle user, as described in Section 2.7, "Operating
System User". Ensure that the user has set the environment variables correctly, as
described in Section 2.10, "Environment Variables".
local_computer> rlogin -l oracle remote_computer.mydomain.com
- OR -
local_computer> telnet remote_computer.mydomain.com
4. Run the installer. See Section 3.12, "Starting the Oracle Universal Installer".
If you do not run xhost, you might get an Xlib error similar to "Failed to connect
to server", "Connection refused by server," or "Can’t open display" when starting
the installer.
2. On local_computer, perform a remote login (using telnet or rlogin) to remote_
computer. Log in as the oracle user, as described in Section 2.7, "Operating
System User". Ensure that the user has set the environment variables correctly, as
described in Section 2.10, "Environment Variables".
local_computer> rlogin -l oracle remote_computer.mydomain.com
- OR -
local_computer> telnet remote_computer.mydomain.com
4. Run the installer. See Section 3.12, "Starting the Oracle Universal Installer".
Before installing, verify that the NFS mount setuid permission is set to suid. The
nosuid option will cause the install to fail.
To check the latest certification list for any updates, visit Oracle Technology Network
(http://www.oracle.com/technology).
Figure 2–3 Run Oracle Application Server Only on the Computer Where It Is Installed
Computer A
If OracleAS is installed
on this computer, OracleAS
components must run
on this computer only.
Although other computers can access OracleAS files installed on Computer A,
they should not run OracleAS components from that installation. For a computer
to run OracleAS components, it must have its own OracleAS installation.
Requirements 2-27
Prerequisite Checks Performed by the Installer
Requirements 2-29
Prerequisite Checks Performed by the Installer
Contents:
■ Section 3.1, "Oracle Home Directory"
■ Section 3.2, "First-Time Installation of Any Oracle Product"
■ Section 3.3, "Installing Additional Languages"
■ Section 3.4, "Oracle Application Server Instances and Instance Names"
■ Section 3.5, "The oc4jadmin User and Restrictions on its Password"
■ Section 3.6, "Where Does the Installer Write Files?"
■ Section 3.7, "Why Do I Need to be Able to Log In as Root at Certain Times During
Installation?"
■ Section 3.8, "Running root.sh During Installation"
■ Section 3.9, "Rules for Adding Instances to OracleAS Clusters"
■ Section 3.10, "Obtaining Software from Oracle E-Delivery"
■ Section 3.11, "Setting the Mount Point for the CD-ROM or DVD-ROM"
■ Section 3.12, "Starting the Oracle Universal Installer"
For example, if you are performing your first installation of Oracle Application Server
on this system, then your Oracle home is named oracleas1.
If you deinstall Oracle Application Server, you will need to know the Oracle home
name.
For other components, available languages are installed regardless of what you select
during installation. In this case, however, fonts are installed only for the languages that
are explicitly selected. When you access the application, it uses text in your language
because the language was installed. However, if you do not have the appropriate fonts
to render the text, the text appears as square boxes. This usually applies to the Chinese,
Japanese, and Korean languages.
You can install fonts after installation. See Section E.3.6, "User Interface Does Not
Display in the Desired Language, or Does Not Display Properly".
Note that you cannot install additional languages after installation. You must install
all languages that you need during installation. If you run Oracle Application Server
in an environment that uses a language that you did not install, the user interface can
display text in that language and/or in English, or it can display square boxes (caused
by missing fonts) instead of text.
Control is a browser-based administration tool for Oracle Application Server. See the
Oracle Application Server Administrator’s Guide for details about this administration tool.
Note: When entering your password, check that the state of the Caps
Lock key is what you want it to be. Passwords are case-sensitive.
You must remember the password because you need to enter it to perform the
following task:
■ When you log on to Application Server Control to manage Oracle Application
Server, you log on as the oc4jadmin user.
If you forget the password, you can reset it. See the Oracle Application Server
Administrator’s Guide for details.
3.10.1 Finding and Downloading the Oracle Application Server 10g Release 3
(10.1.3.1.0) E-Pack
Refer to the CD/Media Pack description or the list of products that you purchased on
your Oracle Ordering Document. Then, view the License List to help you decide which
Product Pack you need to select in order to search for the appropriate E-Pack(s) to
download. Prior to downloading, verify that the product you are looking for is in the
License and Options section of the E-Pack README. Oracle recommends that you
print the README for reference.
and then move the stage area to a Solaris Operating System (SPARC) machine, the
stage area files will be corrupted because Windows will not preserve the case
sensitivity or the permission bits of UNIX file names.
Then create a new directory for each Zip file you downloaded:
c:\oraAS10g\Disk1
c:\oraAS10g\Disk2
etc.
If you plan burn the files on a CD-ROM, create a separate CD-ROM from the contents
of each directory. Do not burn a CD-ROM containing the Zip file itself; you need the
unzipped contents of the Zip files to do the installation. When you burn the files to
CD-ROM, the contents of each disc must be at the root of the CD image.
To install from CD-ROM or from your hard drive, see Section 3.12, "Starting the Oracle
Universal Installer".
3. If the command in step 2 fails to display the contents of the disk, run the following
command:
■ Red Hat:
# mount -t iso9660 /dev/cdrom /mnt/cdrom
Notes:
■ Be sure you are not logged in as the root user when you start
the Oracle Universal Installer. The installer gives an error
message if you try to run it as the root user.
■ Do not start the installation inside the mount_point directory. If
you do, then you may not be able to eject the installation disk.
The cd command below changes your current directory to your
home directory.
CD-ROM:
prompt> cd
prompt> mount_point/10.1.3.1disk1/runInstaller
DVD-ROM:
prompt> cd
prompt> mount_point/application_server/runInstaller
This launches Oracle Universal Installer, through which you install Oracle Application
Server.
Figure 4–1 Oracle Application Server SOA Suite 10.1.3.1.0 Installation Screen
Installation Directory: Enter the directory where you want install Oracle
Application Server.
Select Basic Install.
AS Instance Name: The instance name identifies this Oracle Application Server
instance. If you have more than one Oracle Application Server instance on the
same host, the instances must have unique names.
Figure 4–2 Oracle Application Server SOA Suite 10.1.3.1.0 Installation Screen
Database Connect Information: Specify the hostname, port, and service name for
the database. Use the format hostname:port:service name.
User with DBA Privileges: Specify the login name for the DBA user.
Database User Password: Enter the password for the user specified in the User
with DBA Privileges field.
ORABPEL Schema Password: Enter the password for the ORABPEL schema in
the database specified in the Database Connect Information field.
ORAESB Schema Password: Enter the password for the ORAESB schema in the
database specified in the Database Connect Information field.
ORAWSM Schema Password: Enter the password for the ORAWSM schema in
the database specified in the Database Connect Information field.
4. Oracle Universal Installer: Install Screen
This screen tells you whether or not your installation was successful, and provides
links to various documentation, such as the product release notes and installation
log, as well as links to various Oracle Application Server pages such as the
Welcome Page or Application Server Control Console.
■ Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite"
■ Section 5.2.3, "Installing J2EE Server and Web Server"
■ Section 5.2.4, "Installing J2EE Server"
■ Section 5.2.5, "Installing Web Server"
Table 5–1 Steps for Installing J2EE Server, Web Server and SOA Suite
Screen Action
1. -- Start Oracle Universal Installer.
For more information, refer to Section 3.12, "Starting the Oracle Universal
Installer".
2. Oracle Application Specify the Oracle Home in the Installation Directory field.
Server SOA Suite
Select Advanced Install.
10.1.3.1.0 Installation
Click Next.
For more information, refer to Section 5.3.1, "Oracle Application Server SOA Suite
10.1.3.1.0 Installation Screen".
3. Select Installation Type Select J2EE Server, Web Server and SOA Suite.
Click Next.
For more information, refer to Section 5.3.2, "Select Installation Type Screen".
4. Specify Database Specify your Oracle database connection information.
Connect Information
Specify the DBA user in the User with DBA Privileges field.
Specify the password for the DBA user in the Database User Password field.
Specify the hostname and port for the database in the Hostname and Port field.
Specify the service name of the database in the Service Name field.
Click Next.
For more information, refer to Section 5.3.3, "Specify Database Connect
Information Screen".
5. Specify Database Schema Specify the passwords for the ORABPEL, ORAESB, and ORAWSM database schemas.
Passwords
Click Next.
For more information, refer to Section 5.3.4, "Specify Database Schema Passwords
Screen".
6. Specify Port Select whether you want to configure ports automatically or manually by
Configuration Options specifying the location of a port configuration file.
Click Next.
For more information, refer to Section 5.3.5, "Specify Port Configuration Options
Screen".
Table 5–1 (Cont.) Steps for Installing J2EE Server, Web Server and SOA Suite
Screen Action
7. Administration Settings Specify the Oracle Application Server instance name and oc4jadmin password.
Select Configure this as an Administration OC4J instance if you would like to run
Application Server Control on this instance.
Specify the Oracle Containers for J2EE instance name. The default instance name is
oc4j_soa.
Click Next.
For more information, refer to Section 5.3.6, "Administration Settings Screen".
8. Cluster Topology Select Access this OC4J Instance from a separate Oracle HTTP Server if you want
Configuration the default web site to run in AJP protocol mode and specify the hostname and
port of the Oracle HTTP Server.
Select Configure this instance to be a part of an Oracle Application Server cluster
topology if you would like to configure this instance to be part of an Oracle
Application Server cluster topology. Specify the IP address and port for the
multicast address.
Click Next.
For more information, refer to Section 5.3.8, "Cluster Topology Configuration
Screen - J2EE Server, Web Server, and SOA Suite Installation".
9. Summary Verify that the installation parameters shown on the screen are correct.
Click Install.
For more information, refer to Section 5.3.12, "Summary Screen".
10. Install None. This screen shows the progress of the installation.
For more information, refer to Section 5.3.13, "Install Screen".
11. Configuration Assistants None, unless you want to stop the installation of a particular configuration
assistant.
For more information, refer to Section 5.3.14, "Configuration Assistants Screen".
12. End of Installation None. This screen tells you whether or not your installation was successful, and
provides a link to the product release notes.
For more information, refer to Section 5.3.15, "End of Installation Screen".
Table 5–2 Steps for Installing J2EE Server and Web Server
Screen Action
1. -- Start Oracle Universal Installer.
For more information, refer to Section 3.12, "Starting the Oracle Universal
Installer".
2. Oracle Application Specify the Oracle Home in the Installation Directory field.
Server SOA Suite
Select Advanced Install.
10.1.3.1.0 Installation
Click Next.
For more information, refer to Section 5.3.1, "Oracle Application Server SOA Suite
10.1.3.1.0 Installation Screen".
Table 5–2 (Cont.) Steps for Installing J2EE Server and Web Server
Screen Action
3. Select Installation Type Select J2EE Server and Web Server.
Click Next.
For more information, refer to Section 5.3.2, "Select Installation Type Screen".
4. Specify Port Select whether you want to configure ports automatically or manually by
Configuration Options specifying the location of a port configuration file.
Click Next.
For more information, refer to Section 5.3.5, "Specify Port Configuration Options
Screen".
5. Administration Settings Specify the Oracle Application Server instance name and oc4jadmin password.
Select Configure this as an Administration OC4J instance if you would like to run
Application Server Control on this instance.
Specify the default Oracle Containers for J2EE instance name.
Click Next.
For more information, refer to Section 5.3.6, "Administration Settings Screen".
6. Cluster Topology Select if you would like to configure this instance to be part of an Oracle
Configuration Application Server cluster topology.
If you select Configure this instance to be part of an Oracle Application Server
cluster topology, specify the IP Address and Port.
Click Next.
For more information, refer to Section 5.3.9, "Cluster Topology Configuration
Screen - J2EE Server and Web Server Installation".
7. Summary Verify that the installation parameters shown on the screen are correct.
Click Install.
For more information, refer to Section 5.3.12, "Summary Screen".
8. Install None. This screen shows the progress of the installation.
For more information, refer to Section 5.3.13, "Install Screen".
9. Configuration Assistants None, unless you want to stop the installation of a particular configuration
assistant.
For more information, refer to Section 5.3.14, "Configuration Assistants Screen".
10. End of Installation None. This screen tells you whether or not your installation was successful, and
provides a link to the product release notes.
For more information, refer to Section 5.3.15, "End of Installation Screen".
Installation Directory
Specify the full path of the installation directory or Oracle home. This is the directory
where you want to install the software. For more information about the Oracle home,
refer to Section 3.1, "Oracle Home Directory".
To learn what components are installed with the different installation types, see
Section 5.1, "What Components Are Installed?".
On this screen, you can install additional languages by clicking on Product Languages.
See Section 3.3, "Installing Additional Languages" for more information.
Database Type
The type of database is set to Oracle Database and cannot be changed.
If the Oracle Database is a 10g or above Real Application Clusters database, specify all
the virtual hostnames and ports in the cluster. Use the following format, separating the
values with carets (^):
virtual_hostname_on_node1:port1^virtual_hostname_on_node2:port2^virtual_hostname_
on_node3:port3
If the Oracle Database is a 9i Real Application Clusters database, specify all the
physical hostnames and ports in the cluster. Use the following format, separating the
values with carets (^):
host1:port1^host2:port2^host3:port3
Service Name
Specify the service name of the database. This is typically the same as the global
database name.
If you are unsure what the service name for your database is, you can obtain it from
the SERVICE_NAMES parameter in the database's initialization parameter file. If the
initialization parameter file does not contain the SERVICE_NAMES parameter, then the
service name is the same as the global database name, which is specified in the DB_
NAME and DB_DOMAIN parameters.
If the database is in a Real Application Clusters database, all the instances of the
database must have the same service name.
Note: The ORABPEL, ORAESB, and ORAWSM schemas must exist in the
database prior to Oracle Application Server installation. Please refer to
Section 2.9, "Installing Database Schemas" for instructions on how to
install these schemas.
Figure 5–5 Oracle Universal Installer: Specify Database Schema Passwords Screen
ORABPEL Password
Specify the password for the ORABPEL schema.
ORAESB Password
Specify the password for the ORAESB schema.
ORAWSM Password
Specify the password for the ORAWSM schema.
Figure 5–6 Oracle Universal Installer: Specify Port Configuration Options Screen
Select Automatic if you want to use all default port numbers. Refer to Appendix B for
a list of all the default port numbers and ranges.
Select Manual if you want to customize your port numbers. You must supply the full
path and file name to an existing port configuration file containing the port numbers
you want to use for each component. Typically, this port configuration file is called
staticports.ini, although any name is valid as long as the format of the file is
correct. Refer to Section 2.5.3, "Using Custom Port Numbers (the "Static Ports"
Feature)" for more information about the staticports.ini file that is shipped with
the product.
AS Instance Name
The AS Instance Name uniquely identifies this Oracle Application Server instance.
For more information about instance names, see Section 3.4, "Oracle Application
Server Instances and Instance Names".
AS Administrator Username
The administrative username for Oracle Application Server instances is set to
oc4jadmin and cannot be changed. To manage Oracle Application Server instances
using Enterprise Manager, log in as the oc4jadmin user.
For more information about the oc4jadmin user, see Section 3.5, "The oc4jadmin User
and Restrictions on its Password".
Instance Name
Specify the Oracle Application Server instance name. The instance name uniquely
identifies this Oracle Application Server instance.
For more information about instance names, see Section 3.4, "Oracle Application
Server Instances and Instance Names".
5.3.8 Cluster Topology Configuration Screen - J2EE Server, Web Server, and SOA Suite
Installation
Select whether you would like to configure this instance to be part of an Oracle
Application Server cluster topology.
Figure 5–9 Oracle Universal Installer: Cluster Topology Configuration (J2EE Server, Web
Server, and SOA Suite Installation)
Specify the hostname and port of the load balancer or the Oracle HTTP Server
Specify the IP Address and the Port number of the load balancer or Oracle HTTP
Server from which you will accept requests.
Note:
■ When installing the first instance of the cluster, you only need to
provide the discovery address. You do not need to perform any
additional steps before installing the first instance of the cluster.
■ All nodes within the topology must be configured to use the same
multicast address and port.
■ The multicast address must be within the valid address range,
which is 224.0.1.0 to 239.255.255.255.
■ The installer does not validate the IP address or port of the cluster
discovery address.
If you are adding an instance to an existing cluster and do not know the multicast
address, find the <discover> element in the opmn.xml file on an Oracle Application
Server instance in the topology. The <discover> element should appear like this:
<notification-server>
<topology>
<discover list="*225.0.0.20:8001"/>
</topology>
...
</notification-server>
5.3.9 Cluster Topology Configuration Screen - J2EE Server and Web Server Installation
Select whether you would like to configure this instance to be part of an Oracle
Application Server cluster topology.
Figure 5–10 Oracle Universal Installer: Cluster Topology Configuration (J2EE Server and
Web Server Installation)
Note:
■ When installing the first instance of the cluster, you only need to
provide the discovery address. You do not need to perform any
additional steps before installing the first instance of the cluster.
■ All nodes within the topology must be configured to use the same
multicast address and port.
■ The multicast address must be within the valid address range,
which is 224.0.1.0 to 239.255.255.255.
■ The installer does not validate the IP address or port of the cluster
discovery address.
If you are adding an instance to an existing cluster and do not know the multicast
address, find the <discover> element in the opmn.xml file on an Oracle Application
Server instance in the topology. The <discover> element should appear like this:
<notification-server>
<topology>
<discover list="*225.0.0.20:8001"/>
</topology>
...
</notification-server>
Figure 5–11 Oracle Universal Installer: Cluster Topology Configuration (J2EE Server)
topology following installation. See Section 7.4, "Configuring OracleAS Clusters" for
details.
Note:
■ When installing the first instance of the cluster, you only need to
provide the discovery address. You do not need to perform any
additional steps before installing the first instance of the cluster.
■ All nodes within the topology must be configured to use the same
multicast address and port.
■ The multicast address must be within the valid address range,
which is 224.0.1.0 to 239.255.255.255.
■ The installer does not validate the IP address or port of the cluster
discovery address.
If you are adding an instance to an existing cluster and do not know the multicast
address, find the <discover> element in the opmn.xml file on an Oracle Application
Server instance in the topology. The <discover> element should appear like this:
<notification-server>
<topology>
<discover list="*225.0.0.20:8001"/>
</topology>
...
</notification-server>
Figure 5–12 Oracle Universal Installer: Cluster Topology Configuration (Web Server)
Note:
■ When installing the first instance of the cluster, you only need to
provide the discovery address. You do not need to perform any
additional steps before installing the first instance of the cluster.
■ All nodes within the topology must be configured to use the same
multicast address and port.
■ The multicast address must be within the valid address range,
which is 224.0.1.0 to 239.255.255.255.
■ The installer does not validate the IP address or port of the cluster
discovery address.
If you are adding an instance to an existing cluster and do not know the multicast
address, find the <discover> element in the opmn.xml file on an Oracle Application
Server instance in the topology. The <discover> element should appear like this:
<notification-server>
<topology>
<discover list="*225.0.0.20:8001"/>
</topology>
...
</notification-server>
Click Stop Installation if you want to abort the installation. You will be asked to verify
that you want to stop the installation.
This screen also provides the location of the install log, in case you want to view the
contents of the log.
A tool may have one of the following states, as shown in the status column:
■ Succeeded: The tool ran successfully.
■ Failed: The tool ran, but failed.
■ Pending: The tool is waiting to run.
■ Cancelled: The tool was cancelled by the user (by clicking Stop).
■ In Progress: The tool is currently running.
■ Skipped: A configuration assistant running before this tool was cancelled or
failed. Tools that follow a failed or cancelled tool are skipped.
When you select a tool, its details are shown in the Details box. Details are displayed
as the tool is running. If you want to stop a configuration assistant while it is running,
click Stop.
If all tools succeed on the first try, OUI automatically proceeds to the next page.
Otherwise, OUI remains on the Configuration Assistants page until all tools are
successful. You can then click Next to proceed.
If one or more tools fail, OUI does not proceed to the next page. Instead, you can read
the details of failed tools, fix the problems, and try running the configuration assistant
again. You should also consult the installation document for the product being
installed for instructions on what to do if a tool fails. For all failed or skipped tools,
OUI generates a list of the tool names and the commands used to run them; you can
copy/paste this information directly into a shell script or batch file to run these tools
after installation is complete.
By default, the check box in the Retry column will be checked for all tools that failed or
were skipped. To retry all checked configuration assistants, click Retry.
To continue without fixing the problem, click Next.
To view release notes for the products you have installed, click Release Information or
see the documentation page on OTN
(http://www.oracle.com/technology/documentation).
Click Exit to exit the Oracle Universal Installer.
The virtual hostname is associated with a virtual IP. This name-IP entry must be
added to the DNS that the site uses. For example, if the two physical hostnames of
the hardware cluster are node1.mycompany.com and node2.mycompany.com,
the single view of this cluster can be provided by the virtual hostname
apps.mycompany.com. In the DNS, apps maps to a virtual IP address that floats
between node1 and node2 via a hardware cluster. Clients access Oracle
Application Server using apps.mycompany.com; they do not know which
physical node is active and actually servicing a particular request.
You can specify the virtual hostname during installation. See Section 6.4, "Creating
the Active-Passive Topology".
■ Failover procedure
An active-passive configuration also includes a set of scripts and procedures to
detect failure of the active instance and fail over to the passive instance while
minimizing downtime.
Advantages of an OracleAS Cold Failover Cluster topology include:
■ Increased availability
If the active instance fails for any reason or must be taken offline, an identically
configured passive instance is prepared to take over at any time.
■ Reduced operating costs
In an active-passive topology only one set of processes is up and serving requests.
Managing the active instance is generally easier than managing an array of active
instances.
■ Application independence
Some applications may not be suited to an active-active topology. This may
include applications that rely heavily on application state or on information stored
locally. An active-passive topology has only one instance serving requests at any
particular time.
For instructions on creating the OracleAS Cold Failover Cluster configuration, see
Section 6.4, "Creating the Active-Passive Topology".
Since the oraInst.loc file and the Oracle Installer Inventory directory are required
only during the installation of Oracle software, and not at runtime, renaming them
and restoring them later does not affect the behavior of any installed Oracle software
on any node. Make sure that the appropriate oraInst.loc file and Oracle Installer
Inventory directory are in place before starting the Oracle Universal Installer.
Figure 6–1 Active-Active Topology with Oracle HTTP Server and OC4J in the Same Oracle Home
Load
Balancer
Node 1 Node 2
OHS OHS
OC4J OC4J Variation: You can use Oracle Identity Management
from 10.1.2 with this topology.
Figure 6–2 Active-Active Topology with Oracle HTTP Server and OC4J in Separate Oracle Homes
Load
Balancer
Node 1 Node 2
OHS OHS
Step 2 Install Oracle HTTP Server and OC4J and Cluster the Instances using
OPMN
You can install Oracle HTTP Server and OC4J in the same Oracle home (see
Figure 6–1), or in different Oracle homes (see Figure 6–2).
For Oracle Application Server instances that you want to group in the same
active-active topology, you need to place them in the same cluster. This enables
communication between the Oracle HTTP Server and OC4J instances, and simplifies
the management of Oracle Application Server instances. OracleAS Clusters enable you
to use the @cluster parameter for the opmnctl command to manage all the
instances in the cluster.
You can create clusters using one of the following methods:
■ Dynamic Discovery Method
In this method, each ONS node within the same subnet announces its presence
with a multicast message. The cluster topology map for each node is automatically
updated as nodes are added or removed, enabling the cluster to be self-managing.
If you use this method, you should specify the multicast address and port on the
Cluster Topology Configuration screen in the installer.
■ Discovery Server Method
In this method, specific nodes within a cluster are configured to serve as
"discovery servers", which maintain the topology map for the cluster; the
remaining nodes then connect with one another via this server.
If you use this method, you can define a cluster for OPMN by specifying the
names of the Oracle Application Server instances explicitly in the opmn.xml file of
each instance by following the steps in Section 6.3.5.1, "Setting up Clusters with
the Discovery Server Method" after installation.
■ Gateway Method
This configuration is used to connect topologies separated by firewalls or on
different subnets using specified "gateway" nodes.
If you use this method, see the section "Configuring Cross-Topology Gateways" in
the Oracle Containers for J2EE Configuration and Administration Guide for
configuration details.
You can perform either an integrated installation or a distributed installation.
■ For Integrated Installations (Oracle HTTP Server and OC4J in the Same Oracle
Home)
You install Oracle Application Server on the local storage of each node in the
active-active topology.
Perform an advanced installation by following the steps in Section 5.2.3, "Installing
J2EE Server and Web Server" so that both Oracle HTTP Server and OC4J will run
from the same Oracle home.
During the installation procedure, follow the prompts, ensuring you perform the
following:
■ On the Administration Instance Settings screen:
– If you want this node to administer the cluster using Application Server
Control, select Configure this as an Administration OC4J instance. In a
cluster topology, only one instance should be configured as an
– If you are installing Oracle HTTP Server, select Configure this HTTP
Server instance to be part of an Oracle Application Server cluster on the
"Cluster Topology Configuration" screen. Specify the IP Address and Port
for the multicast address shared by all the nodes in the cluster.
– If you are installing OC4J, select Configure this OC4J instance to be part
of an Oracle Application Server cluster topology on the "Cluster
Topology Configuration" screen. Specify the IP Address and Port for the
multicast address shared by all the nodes in the cluster and select Access
this OC4J Instance from a separate Oracle HTTP Server.
Note that the multicast address must be between 224.0.0.1 and 239.255.255.255.
If you are installing on the first node in the cluster, you may choose any IP
address and port, as long as it falls in the multicast address range.
Note the following:
■ Set the Oracle home to be on the local storage of each node.
■ Ensure that the same component uses the same port number in each Oracle
Application Server instance in the cluster. For example, ensure that Oracle
HTTP Server is listening at the same port number for all instances in the
cluster.
■ To simplify administering the instances, use the same Oracle home path and
the same instance name for each node.
■ If you are using the discovery server method to cluster the Oracle Application
Server instances for OPMN, be sure to perform the steps in Section 6.3.5.1,
"Setting up Clusters with the Discovery Server Method" after installation.
■ If you are using the gateway method to cluster the Oracle Application Server
instances for OPMN, see the section "Configuring Cross-Topology Gateways"
in the Oracle Containers for J2EE Configuration and Administration Guide for
configuration details.
To define properties at the application level, you define them in the application’s
orion-application.xml file. When you deploy the application, the file is located
in the ORACLE_HOME/j2ee/home/application-deployments/<app-name>/
directory.
Procedure
To create an application cluster at either the global or application level, you perform
these steps:
1. Add an empty <distributable/> tag to the web.xml file for all Web modules
that are part of an application configured for clustering.
2. Specify the mechanism for replicating state and session information between
Oracle Application Server instances. You choose one of the following replication
mechanisms:
3. Specify how often and which data are replicated. See Section 6.3.5.5, "Setting the
Replication Policy" for details.
4. Specify the number of nodes to replicate the data to. See Section 6.3.5.6,
"Specifying the Number of Nodes to Replicate To" for details.
For details, see the "Application Clustering in OC4J" chapter in the Oracle Containers for
J2EE Configuration and Administration Guide.
The 6201 specifies the port number at which the notification server is listening.
You can find this value in the opmn.xml file of that instance.
If you have more than one discovery server, you separate them with the comma
character.
3. On all the instances, run "opmnctl reload" to force OPMN to read the updated
opmn.xml file.
> ORACLE_HOME/opmn/bin/opmnctl reload
</orion-application>
You need to add the <cluster/> tag on all nodes where the application is deployed.
By default, multicast replication uses multicast address 230.230.0.1 and port 45566. If
you want to change these values, you specify the desired values in the ip and port
attributes of the multicast element. For example, the following snippet shows the
ip and port attributes set to customized values:
<orion-application ... >
...
<cluster allow-colocation="false">
<replication-policy trigger="onShutdown" scope="allAttributes"/>
<protocol>
<multicast ip="225.130.0.0" port="45577" bind-addr="226.83.24.10"/>
</protocol>
</cluster>
</orion-application>
You defined how OPMN discovers instances in a cluster in step 2, "Install Oracle
HTTP Server and OC4J and Cluster the Instances using OPMN" on page 6-9.
Another way of doing this is to have all the nodes specify the same node. In a
three-node example, you could also have nodes 1 and 2 specify node 3, and node 3 can
specify either node 1 or node 2.
Description of the tags and attributes used in the example above:
■ start-port: specifies the first port on the local node that Oracle Application
Server tries to bind to for peer communication. If this port is already in use, Oracle
Application Server increments the port number until it finds an available port. The
default is 7800.
■ timeout: specifies the length of time in milliseconds to wait for a response from
the specified peer node. The default is 3000 milliseconds.
■ host: specifies the name of the peer node.
■ port: specifies the port to use on the specified host (in the host attribute) for peer
communication. The default is 7800.
■ range: specifies the number of times to increment the port specified on the port
(not start-port) attribute. The default is 5.
Note the following:
■ In static peer-to-peer replication, the application’s orion-application.xml file
is different for each instance. When you deploy your application, you have to
make sure that you update the orion-application.xml accordingly.
The value for the data-source attribute must match the data source’s jndi-name as
specified in the data-sources.xml file. See the Oracle Containers for J2EE Services
Guide for details on creating and using data sources.
The default is 1.
Recommendations: For a two-node active-active topology, set write-quota to 1, so
that the data is replicated to the other node.
For topologies with three or more nodes, set write-quota to at least 2 to ensure that
the data is replicated to at least two other nodes.
To replicate data to all nodes in the topology, set write-quota to the total number of
nodes in the topology. It is possible to write back to the same node if there is another
instance running on that node.
The write-quota attribute is not used if you are replicating to database.
If the active node fails for any reason, a failover event occurs and the passive node
takes over and becomes the active node. It mounts the shared storage and runs all the
processes and handles all the requests. The virtual hostname and IP now point to the
passive node. Clients, because they access the nodes using the virtual hostname, do
not know that it is the passive node that is servicing their requests.
The nodes need to be in hardware cluster to enable failover.
Note: Installing the Oracle home on the local storage of each node in
the OracleAS Cold Failover Cluster topology is not supported. You
have to install it on the shared storage.
Vendor Clusterware
The two nodes in an active-passive topology are in a hardware cluster, which typically
includes some vendor clusterware. For a list of certified clusterware, visit the Oracle
Technology Network website (http://www.oracle.com/technology).
These products must be installed on both nodes (active and passive) in the topology.
Figure 6–3 Active-Passive Topology with Oracle HTTP Server and OC4J in the Same Oracle Home
Virtual Hostname:
oc4j_mydomain.com
Virtual IP: 123.45.67.89
HTTP(S) On Failover
OHS OHS
OC4J OC4J
On Failover
Figure 6–4 Active-Passive Topology with Oracle HTTP Server and OC4J in Separate Oracle Homes
Virtual Hostname:
ohs.mydomain.com
Virtual IP: 123.45.67.89
HTTP(S) On Failover
On Failover
Virtual Hostname:
oc4j.mydomain.com
Virtual IP: 123.45.67.89
HTTP(S) On Failover
Hardware Cluster
OC4J OC4J
On Failover
Table 6–5 Overview of Installation Steps for OracleAS Cold Failover Cluster
Step Description
1. Perform Preinstallation Steps Preinstallation tasks, described in Section 6.4.3 include:
■ Section 6.4.3.1, "Map the Virtual Hostname and Virtual IP
Address"
■ Section 6.4.3.2, "Set Up a File System That Can Be
Mounted from Both Nodes"
2. Set VIRTUAL_HOST_NAME Environment Set the VIRTUAL_HOST_NAME variable to the virtual
Variable hostname.
3. Install Oracle Application Server on the In this step, you run the installer from either node of the
Shared Disk hardware cluster to install Oracle HTTP Server and OPMN on
the shared disk.
4. (optional) Configure the Oracle Application If you want the Oracle Application Server instance to use SSL,
Server Instance for SSL enable SSL in the Oracle Application Server installation.
5. (optional) Create a File System on the Shared If you are using OracleAS JMS, create a file system on the
Disk for OracleAS JMS File-Based Persistence shared disk.
Note: Map the virtual hostname and virtual IP address only to the
active node. Do not map the virtual hostname and IP address to
both active and passive nodes at the same time. When you failover,
only then map the virtual hostname and IP address to the passive
node, which is now the active node.
3. Find an available index number for the primary public network interface.
For example, if the following is the output of the /sbin/ifconfig command
and eth0 is determined to be the primary public interface in step 2, then eth0:1 is
available for an additional IP address:
eth0 Link encap:Ethernet HWaddr 00:B0:D0:68:B4:3D
inet addr:130.35.137.46 Bcast:130.35.139.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:608598569 errors:8 dropped:0 overruns:0 frame:8
TX packets:578257570 errors:111 dropped:0 overruns:0 carrier:111
collisions:0 txqueuelen:100
RX bytes:2407934851 (2296.3 Mb) TX bytes:3386476912 (3229.5 Mb)
Interrupt:26 Base address:0xe0c0 Memory:fbefc000-fbefc038
4. Add the virtual IP address to the primary public network interface by running the
following command, as the root user, using the available index number from step
3:
/sbin/ifconfig <primary_public_interface>:<available_index> <virtual_ip_
address> netmask <netmask_value> up
b. Try to connect to the node using the virtual hostname and virtual IP address
from another node. For example, entering both of the following commands
from a different node should provide a login to the node you configured in
this procedure:
telnet hostname.domain
telnet ip_address
On Failover
If the active node fails, then the passive node takes over. If you do not have a
clusterware agent to map the virtual IP from the failed node to the passive node, then
you have to do it manually. You have to remove the virtual IP mapping from the failed
node, and map it to the passive node.
1. On the failed node, remove the virtual IP address by running the following
command as the root user:
/sbin/ifconfig configured_interface down
For example, enter the following command if eth0:1 is configured with the
virtual IP address:
/sbin/ifconfig eth0:1 down
6.4.3.2 Set Up a File System That Can Be Mounted from Both Nodes
Although the hardware cluster has shared storage, you need to create a file system on
this shared storage such that both nodes of the OracleAS Cold Failover Cluster can
mount this file system. You will use this file system for the following directories:
■ Oracle home directory for the Oracle Application Server instance
■ The oraInventory directory
For disk space requirements, see Section 2.2, "System Requirements".
If you are running a volume manager on the cluster to manage the shared storage,
refer to the volume manager documentation for steps to create a volume. Once a
volume is created, you can create the file system on that volume.
If you do not have a volume manager, you can create a file system on the shared disk
directly. Ensure that the hardware vendor supports this, that the file system can be
mounted from either node of the OracleAS Cold Failover Cluster, and that the file
system is repairable from either node if a node fails.
To check that the file system can be mounted from either node, do the following steps:
Step 4 (optional) Configure the Oracle Application Server Instance for SSL
If you want the Oracle Application Server instance to use SSL, follow the steps in the
Oracle Application Server Administrator’s Guide.
Step 5 (optional) Create a File System on the Shared Disk for OracleAS JMS
File-Based Persistence
If you are using OracleAS JMS with file-based persistence, create a file system on the
shared disk for the OracleAS JMS queues, and mount this file system from node 1.
Data Synchronization
For OracleAS Disaster Recovery to work, data between the production and standby
sites must be synchronized so that failover can happen very quickly. Configuration
changes done at the production site must be synchronized with the standby site.
You need to synchronize two types of data. The synchronization method depends on
the type of data:
■ Use Oracle Data Guard to synchronize data in the OracleAS Metadata Repository
databases on the production and standby sites. You can configure Oracle Data
Guard to perform the synchronization.
■ Use the backup and recovery scripts to synchronize data outside of the database
(such as data stored in configuration files).
See the Oracle Application Server High Availability Guide for details on how to use Oracle
Data Guard and the backup and recovery scripts.
Middle Tier External hostname: prodmid2 Middle Tier External hostname: standbymid2
IP: 138.1.2.444 IP: 213.2.2.331
Oracle Data
OracleAS Metadata Repository OracleAS Metadata Repository
Guard
■ The nodes have the same operating system patches and packages.
■ You can install Oracle Application Server in the same directory path on all nodes.
On the standby site, the following line sets the node’s alias to asinfra.
213.2.2.110 standbyinfra asinfra
When you install OracleAS Infrastructure on the production and standby sites, you
specify this alias (asinfra) in the Specify Virtual Hostname screen. The configuration
data will then contain this alias for the infrastructure nodes.
2. Enable the other nodes in the OracleAS Disaster Recovery environment to be able
to resolve the node using the new local hostname. You can do this in one of two
ways:
Method 1: Set up separate internal DNS servers for the production and standby
sites. This configuration allows nodes on each site (production or standby) to
resolve hostnames within the site. Above the internal DNS servers are the
corporate, or external, DNS servers. The internal DNS servers forward
non-authoritative requests to the external DNS servers. The external DNS servers
do not know about the existence of the internal DNS servers. See Figure 6–6.
Method 1 Details
a. Make sure the external DNS names are defined in the external DNS zone.
Example:
prodmid1.us.oracle.com IN A 138.1.2.333
prodmid2.us.oracle.com IN A 138.1.2.444
prodinf.us.oracle.com IN A 138.1.2.111
standbymid1.us.oracle.com IN A 213.2.2.330
standbymid2.us.oracle.com IN A 213.2.2.331
standbyinf.us.oracle.com IN A 213.2.2.110
b. At the production site, create a new zone at the production site using a
domain name different from your external domain name. To do this, populate
the zone data files with entries for each node in the OracleAS Disaster
Recovery environment.
For the infrastructure node, use the virtual name or alias.
For the middle-tier nodes, use the node name (the value in /etc/nodename).
The following example uses "asha" as the domain name for the new zone.
asmid1.asha IN A 138.1.2.333
asmid2.asha IN A 138.1.2.444
asinfra.asha IN A 138.1.2.111
Do the same for the standby site. Use the same domain name that you used for
the production site.
asmid1.asha IN A 213.2.2.330
asmid1.asha IN A 213.2.2.331
asinfra.asha IN A 213.2.2.110
c. Configure the DNS resolver to point to the internal DNS servers instead of the
external DNS server.
In the /etc/resolv.conf file for each node on the production site, replace
the existing name server IP address with the IP address of the internal DNS
server for the production site.
Do the same for the nodes on the standby site, but use the IP address of the
internal DNS server for the standby site.
d. Create a separate entry for Oracle Data Guard in the internal DNS servers.
This entry is used by Oracle Data Guard to ship redo data to the database on
the standby site.
In the next example, the "remote_infra" entry points to the infrastructure node
on the standby site. This name is used by the TNS entries on both the
production and standby sites so that if a switchover occurs, the entry does not
have to be changed.
Figure 6–7 Entry for Oracle Data Guard in the Internal DNS Servers
remote_infra = 138.1.2.111
Method 2: Edit the /etc/hostsfile on each node on both sites. This method does
not involve configuring DNS servers, but you have to maintain the hosts file on
each node in the OracleAS Disaster Recovery environment. For example, if an IP
address changes, you have to update the files on all the nodes, and restart the
nodes.
Method 2 Details
a. On each node on the production site, include these lines in the /etc/hosts
file. The IP addresses resolve to nodes on the production site.
Note: In the hosts file, be sure that the line that identifies the
current node comes immediately after the localhost definition (the
line with the 127.0.0.1 address).
127.0.0.1 localhost
138.1.2.333 asmid1.oracle.com asmid1
138.1.2.444 asmid2.oracle.com asmid2
138.1.2.111 asinfra.oracle.com asinfra
b. On each node on the standby site, include these lines in the hosts file. The IP
addresses resolve to nodes on the standby site.
Note: In the hosts file, be sure that the line that identifies the
current node comes immediately after the localhost definition (the
line with the 127.0.0.1 address).
127.0.0.1 localhost
213.2.2.330 asmid1.oracle.com asmid1
213.2.2.331 asmid2.oracle.com asmid2
213.2.2.110 asinfra.oracle.com asinfra
c. Ensure that the "hosts:" line in the /etc/nsswitch.conf file has "files" as
the first item:
hosts: files nis dns
The entry specifies the ordering of the name resolution. If another method is
listed first, then the node will use the other method to resolve the hostname.
■ On the middle-tier nodes on both sites, run the hostname command. This should
return the internal hostname. For example, the command should return "asmid1"
if you run it on prodmid1 and standbymid1.
prompt> hostname
asmid1
■ On each node, ping the other nodes in the environment using the internal
hostname as well as the external hostname. The command should be successful.
For example, from the first midtier node, prodmid1, run the following commands:
prompt> ping prodinfra ping the production infrastructure node
PING prodinfra: 56 data byes
64 bytes from prodinfra.oracle.com (138.1.2.111): icmp_seq=0. time=0. ms
^C
6.5.2.4 If You Want to Use OracleAS Cold Failover Cluster on the Production Site
(OracleAS 10.1.2.n.n only)
On the production site of a OracleAS Disaster Recovery system, you can set up the
OracleAS Infrastructure to run in a OracleAS Cold Failover Cluster configuration. In
this case, you have two nodes in a hardware cluster, and you install the OracleAS
Infrastructure on a shared disk. See Chapter 11, "Installing in High Availability
Environments: OracleAS Cold Failover Cluster" in the Oracle Application Server
Installation Guide 10g Release 2 (10.1.2) Documentation set for details.
To set up OracleAS Cold Failover Cluster in this environment, use the virtual IP
address (instead of the physical IP address) for asinfra.asha on the production site. The
following example assumes 138.1.2.120 is the virtual IP address.
asmid1.asha IN A 138.1.2.333
asmid2.asha IN A 138.1.2.444
asinfra.asha IN A 138.1.2.120 this is a virtual IP address
remote_infra.asha IN A 213.2.2.110
On the standby site, you still use the physical IP address for asinfra.asha, but the
remote_infra.asha uses the virtual IP address.
asmid1.asha IN A 213.2.2.330
asmid2.asha IN A 213.2.2.331
asinfra.asha IN A 213.2.2.110 physical IP address
remote_infra.asha IN A 138.1.2.120 virtual IP address
In an OracleAS Release 10.1.2.0.0 environment, you must install the Oracle Identity
Management and the OracleAS Metadata Repository components of OracleAS
Infrastructure on the same node. You cannot distribute the components over multiple
nodes. In an OracleAS Release 10.1.2.0.2 environment, you can distribute the
components over multiple nodes.
The installation steps are similar to that for OracleAS Cold Failover Cluster. See
Section 11.3, "Installing an OracleAS Cold Failover Cluster (Infrastructure)
Configuration" in the Oracle Application Server Installation Guide 10g Release 2 (10.1.2)
Documentation set for the screen sequence.
Note the following points:
■ Select Configuration Options screen: be sure you select High Availability and
Replication. See Table 11–5, step 2.
■ Specify Virtual Hostname screen: enter an alias as the virtual address (for example,
asinfra.oracle.com). See Table 11–5, step 6.
For installing J2EE Server, Web Server and SOA Suite, see Section 5.2.2, "Installing J2EE
Server, Web Server and SOA Suite".
On OracleAS Release 10.1.2.n.n, you can install any type of middle tier that you like:
For installing J2EE and Web Cache, see Section 7.9 "Installing J2EE and Web Cache in a
Database-Based Farm Repository and with Oracle Identity Management Access" in the
Oracle Application Server Installation Guide for 10g Release 2 (10.1.2).
For installing Portal and Wireless or Business Intelligence and Forms, see Section 7.13,
"Installing Portal and Wireless or Business Intelligence and Forms".
Note the following points on OracleAS 10.1.2.n.n:
■ When the installer prompts you to register with Oracle Internet Directory, and
asks you for the Oracle Internet Directory hostname, enter the alias of the node
running OracleAS Infrastructure (for example, asinfra.oracle.com).
6.5.4 Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into
Oracle Homes
OracleAS 10g (10.1.3.1.0) standalone install of OracleAS Guard is located on
Companion CD Disk 2. This standalone install of OracleAS Guard can be installed in
the following environments:
■ In its own home in the case when you are cloning an instance or topology to a new
standby system (see the section on standby site cloning in Oracle Application Server
High Availability Guide for more information).
■ Oracle database server home for an OracleAS Metadata Repository configuration
created using OracleAS Metadata Repository Creation Assistant.
■ OracleAS Disaster Recovery full site upgrade from OracleAS 10g (9.0.4) to
OracleAS 10g (10.1.3.1.0) (see the chapter on OracleAS Disaster Recovery site
upgrade procedure in Oracle Application Server High Availability Guide for more
information).
■ OracleAS Guard patch upgrade from OracleAS 10g (10.1.2.0.0) to OracleAS 10g
(10.1.2.0.2) (see Section 6.5.5, "Patching OracleAS Guard Release 10.1.2.n.n with
Release 10.1.3.1.0" for more information).
If this is an upgrade installation of OracleAS Guard, make a copy of your dsa.conf
configuration file to save your current settings for your OracleAS Guard environment.
After running the OracleAS 10g (10.1.3.1.0) standalone install kit of OracleAS Guard,
you can restore your saved dsa.conf configuration file with your settings to continue
using the same settings for the upgraded OracleAS Guard environment.
To run the OracleAS 10g (10.1.3.1.0) standalone install kit of OracleAS Guard, run the
kit in the following directory path:
On UNIX systems:
/Disk2/asg/install/runInstaller
Choose the type of install that you want. Choose Typical for most installations. Choose
Custom or Reinstall for upgrading from an older release of OracleAS Guard to the
current release.
Enter the oc4jadmin account password to continue the installation.
2. Install the OracleAS 10g (10.1.3.1.0) standalone install of OracleAS Guard into each
Oracle home on the production and standby sites.
If multiple Oracle homes exist on the same system, ensure that different ports are
configured for each of the OracleAS Guard servers in this configuration file.
Because this is an upgrade installation of OracleAS Guard, make a copy of your
dsa.conf configuration file to save your current settings for your OracleAS
Guard environment. After running the OracleAS 10g (10.1.3.1.0) standalone install
kit of OracleAS Guard, you can restore your saved dsa.conf configuration file
with your settings to continue using the same settings for the upgraded OracleAS
Guard environment.
On UNIX systems:
<ORACLE_HOME>/dsa/dsa.conf
3. Start the OracleAS Guard server in all OracleAS 10.1.3.1.0 Oracle homes on both
production and standby sites using the following opmnctl command:
On UNIX systems:
<ORACLE_HOME>/opmn/bin/opmnctl startall
<ORACLE_HOME>/opmn/bin/opmnctl startproc ias-component=ASG
Contents:
■ Section 7.1, "State of Oracle Application Server Instances After Installation"
■ Section 7.2, "Passwords for Oracle Application Server Components"
■ Section 7.3, "NFS Installations"
■ Section 7.4, "Configuring OracleAS Clusters"
■ Section 7.5, "Backup and Recovery"
■ Section 7.6, "SSL"
■ Section 7.7, "Operating System Locale and NLS_LANG Environment Variable"
■ Section 7.8, "Proxy Settings"
■ Section 7.9, "What to Do Next"
7.6 SSL
By default, all components are configured for SSL. For more information, see the SSL
section in the Oracle Application Server Administrator’s Guide.
<environment>
<variable id="TMP" value="/tmp"/>
<variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/>
</environment>
2. To set the proxy server for BPEL, modify the following lines in the ORACLE_
HOME/bpel/bin/obsetenv.sh file:
PROXY_SET="true"
...
if [ "${PROXY_SET}" = "true" ]
then
OB_JAVA_PROPERTIES="-Dhttp.proxySet=true -Dhttp.proxyHost=proxy_server_
hostname -Dhttp.proxyPort=proxy_server_port -Dhttp.nonProxyHosts=localhost|non_
proxy_host|other_non_proxy_hosts"
3. To set the proxy server for OC4J, modify the following lines for the OC4J module
in the ORACLE_HOME/opmn/config/opmn.xml file:
<process-type id="oc4j_instance_name" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value= ...
-Dhttp.proxySet=true -Dhttp.proxyHost=proxy_server_hostname
-Dhttp.proxyPort=proxy_server_port
-Dhttp.nonProxyHosts=localhost|non_proxy_host|other_non_proxy_hosts"/>
</category>
This appendix describes how to install Oracle Application Server in silent mode. This
appendix contains the following topics:
■ Section A.1, "Silent Installation"
■ Section A.2, "Non-Interactive Installation"
■ Section A.3, "Preinstallation"
■ Section A.4, "Create the Response File"
■ Section A.5, "Start the Installation"
■ Section A.6, "Postinstallation"
■ Section A.7, "Security Tips for Silent and Non-Interactive Installations"
■ Section A.8, "Deinstallation"
A.3 Preinstallation
1. Log in as the root user.
prompt> su
2. Create the /etc/oraInst.loc file. This file specifies the inventory directory that
the installer will use.
Using a text editor such as vi or emacs, enter the following line in the file:
inventory_loc=oui_inventory_directory
Replace oui_inventory_directory with the full path to the directory where you want
the installer to create the inventory directory. For example:
inventory_loc=/scratch/oraInventory
Make sure that the oinstall operating system group has write permissions to
this directory. For more information about the inventory directory and the group
that owns it, see Section 2.6.1, "Create a Group for the Inventory Directory".
3. Create an empty /etc/oratab file.
# touch /etc/oratab
See the template files for descriptions of the parameters in the file.
If you are performing a basic installation of J2EE Server and SOA Suite, you must set
the following variables in the response file:
b_oneClick=true
s_installOption="installSOABasic"
A.4.2 Creating Response Files by Using the Record Mode in the Installer
You can run the installer in record mode to save your inputs to a file that you can use
later as a response file. This feature is useful if you need to perform the same
installation on different computers.
To run the installer in record mode:
1. Start up the installer with the -record and -destinationFile parameters.
prompt> /path/to/runInstaller -record -destinationFile newResponseFile
Replace newResponseFile with the full path to the response file that you want the
installer to create. Example: /opt/oracle/myJ2EEResponse.rsp.
2. Enter your values in the installer screens. The installer will write these values to
the file specified in the -destinationFile parameter.
When you click the Install button, the installer automatically writes all your
values to the specified file. At this point, you can complete the installation on this
computer, or you can exit without performing the installation.
Secure information, such as passwords, is not written to the file, so you must modify
the response file before you can use it. To set the password, modify the sl_
adminDialogReturn parameter. See the generated response file for a description of
the parameter.
Note: Response files created by record mode can only be used for
non-interactive installations. You cannot use a response file created by
record mode in a silent installation.
A.4.3.1 Example Response File for Basic Installation: J2EE Server and SOA Suite
The following shows an example of a response file for a silent installation of Basic
Installation: J2EE Server and SOA Suite as described in Section 4.2, "Basic Installation
Steps".
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME="install"
FROM_LOCATION="/mount_point/Disk1/stage/products.xml"
FROM_LOCATION_CD_LABEL="LABEL1"
ORACLE_HOME="/local_location/oracle_home"
ORACLE_HOME_NAME="OHOME1"
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=false
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=false
SHOW_IAS_COMPONENT_CONFIG_PAGE=false
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=localhost.mycompany.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
SELECTED_LANGUAGES={"en"}
TOPLEVEL_COMPONENT={"oracle.as.j2ee.top","10.1.3.1.0"}
DEINSTALL_LIST={"oracle.as.j2ee.top","10.1.3.1.0"}
INSTALL_TYPE="allProducts"
b_oneClick=true
s_installOption="installSOABasic"
sl_DlgClusterInfoSOAReturn={"NO","","","NO","", ""}
n_DlgClusterInfoWebValidate=0
bMaskValidationClusterWebInfo=false
b_accessFromSeperateOHS=false
b_ohsType="oc4j"
s_deinstallOption="deinstallSOA"
nValidationSpecifyRepository=0
bMaskValidationRepository=false
s_asInstanceName="appserver"
s_adminName="oc4jadmin"
s_adminPassword="welcome1"
s_adminPasswordConfirm="welcome1"
b_useRemoteInstance=false
b_useLocalInstance=true
s_oc4jInstanceName="home"
oracle.as.j2ee.top:sl_
adminDialogReturn={"appserver","oc4jadmin","welcome1","welcome1","true", "home"}
s_selection="Using the local Application Server Control installed with this
instance"
oracle.as.j2ee.top:n_validateAdminDialogInfo=0
oracle.as.j2ee.top:bMaskValidationAdminInfo=false
sDBType="oracle"
sDBTypeName="Oracle Database"
s_dbHost="dbhost.mycompany.com"
s_dbPort="1521"
s_dbSid="orcl.mycompany.com"
oracle.as.j2ee.top:s_dbUser="SYS"
oracle.as.j2ee.top:s_dbPassword="welcome1"
oracle.as.j2ee.top:s_bpelPwd="orabpel"
oracle.as.j2ee.top:s_esbPwd="oraesb"
oracle.as.j2ee.top:s_wsmPwd="orawsm"
szl_PasswordUserInput={"orabpel", "oraesb", "orawsm"}
nValidationSpecifyPassword=0
bMaskValidationPassword=false
b_autoPortDetect=true
DEPENDENCY_
LIST={"oracle.iaspt:10.1.3.0.0","oracle.java.jdbc.datadirect:10.1.2.0.1","oracle.x
ds:10.1.3.0.0","oracle.as.welcomepages:10.1.3.1.0","oracle.askernel.common:10.1.3.
0.0","oracle.iappserver.iappcore:10.1.3.0.0","oracle.options.ano.fullssl:10.1.0.2.
0"}
A.4.3.2 Example Response File for Advanced Installation: J2EE Server, Web Server
and SOA Suite
The following shows an example of a response file for a silent installation of
Advanced Installation: J2EE Server, Web Server and SOA Suite as described in
Section 5.2.2, "Installing J2EE Server, Web Server and SOA Suite".
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME="install"
FROM_LOCATION="/mount_point/Disk1/stage/products.xml"
FROM_LOCATION_CD_LABEL="LABEL1"
ORACLE_HOME="/local_location/oracle_home"
ORACLE_HOME_NAME="OHOME1"
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=false
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=false
SHOW_IAS_COMPONENT_CONFIG_PAGE=false
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=localhost.mycompany.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
SELECTED_LANGUAGES={"en"}
TOPLEVEL_COMPONENT={"oracle.as.j2ee.top","10.1.3.1.0"}
DEINSTALL_LIST={"oracle.as.j2ee.top","10.1.3.1.0"}
INSTALL_TYPE="allProducts"
b_oneClick=false
s_installOption="installSOAAdvanced"
sl_DlgClusterInfoSOAReturn={"NO","", "", "NO", "",""}
b_configureCluster=false
n_DlgClusterInfoSOAValidate=0
bMaskValidationClusterInfoSOA=false
n_DlgClusterInfoWebValidate=0
bMaskValidationClusterWebInfo=false
b_accessFromSeperateOHS=false
b_ohsType="local"
s_deinstallOption="deinstallSOA"
nValidationSpecifyRepository=0
bMaskValidationRepository=false
s_asInstanceName="appserver"
s_adminName="oc4jadmin"
s_adminPassword="welcome1"
s_adminPasswordConfirm="welcome1"
b_useRemoteInstance=false
b_useLocalInstance=true
s_oc4jInstanceName="oc4j_soa"
oracle.as.j2ee.top:sl_
adminDialogReturn={"appserver","oc4jadmin","welcome1","welcome1","true", "oc4j_
soa"}
s_selection="Using the local Application Server Control installed with this
instance"
oracle.as.j2ee.top:n_validateAdminDialogInfo=0
oracle.as.j2ee.top:bMaskValidationAdminInfo=false
sDBType="oracle"
sDBTypeName="Oracle Database"
s_dbHost="dbhost.mycompany.com"
s_dbPort="1521"
s_dbSid="orcl.mycompany.com"
oracle.as.j2ee.top:s_dbUser="SYS"
oracle.as.j2ee.top:s_dbPassword="welcome1"
oracle.as.j2ee.top:s_bpelPwd="orabpel"
oracle.as.j2ee.top:s_esbPwd="oraesb"
oracle.as.j2ee.top:s_wsmPwd="orawsm"
szl_PasswordUserInput={"orabpel", "oraesb", "orawsm"}
nValidationSpecifyPassword=0
bMaskValidationPassword=false
szl_RepositoryUserInput={"Oracle
Database","SYS","welcome1","dbhost.mycompany.com:1521","", "",
"orcl.mycompany.com"}
szl_PortListSelect={"YES","/private/jdoe/mystaticports.ini"}
b_autoPortDetect=true
DEPENDENCY_
LIST={"oracle.iaspt:10.1.3.0.0","oracle.java.jdbc.datadirect:10.1.2.0.1","oracle.x
ds:10.1.3.0.0","oracle.as.welcomepages:10.1.3.1.0","oracle.askernel.common:10.1.3.
0.0","oracle.iappserver.iappcore:10.1.3.0.0","oracle.options.ano.fullssl:10.1.0.2.
0","oracle.apache:10.1.3.0.0"}
A.4.3.3 Example Response File for Advanced Installation: J2EE Server and Web
Server
The following shows an example of a response file for a silent installation of
Advanced Installation: J2EE Server and Web Server as described in Section 5.2.3,
"Installing J2EE Server and Web Server".
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME="install"
FROM_LOCATION="/mount_point/Disk1/stage/products.xml"
FROM_LOCATION_CD_LABEL="LABEL1"
ORACLE_HOME="/local_location/oracle_home"
ORACLE_HOME_NAME="OHOME1"
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=false
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=false
SHOW_IAS_COMPONENT_CONFIG_PAGE=false
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=localhost.mycompany.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
SELECTED_LANGUAGES={"en"}
TOPLEVEL_COMPONENT={"oracle.as.j2ee.top","10.1.3.1.0"}
DEINSTALL_LIST={"oracle.as.j2ee.top","10.1.3.1.0"}
INSTALL_TYPE="allProductsNoSOA"
b_oneClick=false
s_installOption="installSOAAdvanced"
sl_DlgClusterInfoWebReturn={"NO","",""}
b_configureCluster=false
n_DlgClusterInfoWebValidate=0
bMaskValidationClusterWebInfo=false
b_accessFromSeperateOHS=false
b_ohsType="local"
s_deinstallOption="deinstallSOA"
nValidationSpecifyRepository=0
bMaskValidationRepository=false
s_asInstanceName="appserver"
s_adminName="oc4jadmin"
s_adminPassword="welcome1"
s_adminPasswordConfirm="welcome1"
b_useRemoteInstance=false
b_useLocalInstance=true
s_oc4jInstanceName="my_OC4J"
oracle.as.j2ee.top:sl_
adminDialogReturn={"appserver","oc4jadmin","welcome1","welcome1","true", "my_
OC4J"}
s_selection="Using the local Application Server Control installed with this
instance"
oracle.as.j2ee.top:n_validateAdminDialogInfo=0
oracle.as.j2ee.top:bMaskValidationAdminInfo=false
sDBType="oracle"
sDBTypeName="Oracle Database"
s_dbHost=""
s_dbPort=""
s_dbSid=""
oracle.as.j2ee.top:s_dbUser=""
oracle.as.j2ee.top:s_dbPassword=""
oracle.as.j2ee.top:s_bpelPwd=""
oracle.as.j2ee.top:s_esbPwd=""
oracle.as.j2ee.top:s_wsmPwd=""
szl_PasswordUserInput={"", "", ""}
nValidationSpecifyPassword=0
bMaskValidationPassword=false
szl_RepositoryUserInput={"Oracle Database","","",":","", "", ""}
b_autoPortDetect=true
DEPENDENCY_
LIST={"oracle.iaspt:10.1.3.0.0","oracle.java.jdbc.datadirect:10.1.2.0.1","oracle.x
ds:10.1.3.0.0","oracle.as.welcomepages:10.1.3.1.0","oracle.askernel.common:10.1.3.
0.0","oracle.iappserver.iappcore:10.1.3.0.0","oracle.options.ano.fullssl:10.1.0.2.
0","oracle.apache:10.1.3.0.0"}
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME="install"
FROM_LOCATION="/mount_point/Disk1/stage/products.xml"
FROM_LOCATION_CD_LABEL="LABEL1"
NEXT_SESSION_RESPONSE=<Value Unspecified>
ORACLE_HOME="/local_location/oracle_home"
ORACLE_HOME_NAME="OHOME1"
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=false
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=false
SHOW_IAS_COMPONENT_CONFIG_PAGE=false
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=localhost.mycompany.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
SELECTED_LANGUAGES={"en"}
TOPLEVEL_COMPONENT={"oracle.as.j2ee.top","10.1.3.1.0"}
DEINSTALL_LIST={"oracle.as.j2ee.top","10.1.3.1.0"}
INSTALL_TYPE="core"
b_oneClick=false
s_installOption="installSOAAdvanced"
sl_DlgClusterInfoReturn={"NO","NO","",""}
b_configureCluster=false
n_DlgClusterInfoWebValidate=0
bMaskValidationClusterWebInfo=false
b_accessFromSeperateOHS=false
b_ohsType="local"
s_deinstallOption="deinstallSOA"
nValidationSpecifyRepository=0
bMaskValidationRepository=false
s_asInstanceName="appserver"
s_adminName="oc4jadmin"
s_adminPassword="welcome1"
s_adminPasswordConfirm="welcome1"
b_useRemoteInstance=false
b_useLocalInstance=true
s_oc4jInstanceName="home"
oracle.as.j2ee.top:sl_
adminDialogReturn={"appserver","oc4jadmin","welcome1","welcome1","true", "home"}
s_selection="Using the local Application Server Control installed with this
instance"
oracle.as.j2ee.top:n_validateAdminDialogInfo=0
oracle.as.j2ee.top:bMaskValidationAdminInfo=false
sDBType="oracle"
sDBTypeName="Oracle Database"
s_dbHost=""
s_dbPort=""
s_dbSid=""
oracle.as.j2ee.top:s_dbUser=""
oracle.as.j2ee.top:s_dbPassword=""
oracle.as.j2ee.top:s_bpelPwd=""
oracle.as.j2ee.top:s_esbPwd=""
oracle.as.j2ee.top:s_wsmPwd=""
szl_PasswordUserInput={"", "", ""}
nValidationSpecifyPassword=0
bMaskValidationPassword=false
szl_RepositoryUserInput={"Oracle Database","","",":","", "", "orcl.mycompany.com"}
szl_PortListSelect={"YES","/private/jdoe/mystaticports.ini"}
b_autoPortDetect=true
DEPENDENCY_
LIST={"oracle.iaspt:10.1.3.0.0","oracle.java.jdbc.datadirect:10.1.2.0.1","oracle.x
ds:10.1.3.0.0","oracle.as.welcomepages:10.1.3.1.0","oracle.askernel.common:10.1.3.
0.0","oracle.iappserver.iappcore:10.1.3.0.0","oracle.options.ano.fullssl:10.1.0.2.
0","oracle.apache:10.1.3.0.0"}
OUI_HOSTNAME=localhost.mycompany.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
SELECTED_LANGUAGES={"en"}
TOPLEVEL_COMPONENT={"oracle.as.j2ee.top","10.1.3.1.0"}
DEINSTALL_LIST={"oracle.as.j2ee.top","10.1.3.1.0"}
INSTALL_TYPE="httpServer"
b_oneClick=false
s_installOption="installSOAAdvanced"
sl_DlgClusterInfoWebReturn={"NO","",""}
b_configureCluster=false
n_DlgClusterInfoWebValidate=0
bMaskValidationClusterWebInfo=false
b_accessFromSeperateOHS=false
b_ohsType="local"
s_deinstallOption="deinstallSOA"
nValidationSpecifyRepository=0
bMaskValidationRepository=false
s_asInstanceName="appserver"
s_adminName="oc4jadmin"
s_adminPassword="welcome1"
s_adminPasswordConfirm="welcome1"
b_useRemoteInstance=false
b_useLocalInstance=true
s_oc4jInstanceName="home"
oracle.as.j2ee.top:sl_
adminDialogReturn={"appserver","oc4jadmin","welcome1","welcome1","true", "home"}
s_selection="Using the local Application Server Control installed with this
instance"
oracle.as.j2ee.top:n_validateAdminDialogInfo=0
oracle.as.j2ee.top:bMaskValidationAdminInfo=false
sDBType="oracle"
sDBTypeName="Oracle Database"
s_dbHost=""
s_dbPort=""
s_dbSid=""
oracle.as.j2ee.top:s_dbUser=""
oracle.as.j2ee.top:s_dbPassword=""
oracle.as.j2ee.top:s_bpelPwd=""
oracle.as.j2ee.top:s_esbPwd=""
oracle.as.j2ee.top:s_wsmPwd=""
szl_PasswordUserInput={"", "", ""}
nValidationSpecifyPassword=0
bMaskValidationPassword=false
szl_RepositoryUserInput={"Oracle Database","","",":","", "", ""}
szl_PortListSelect={"YES","/private/jdoe/mystaticports.ini"}
b_autoPortDetect=true
DEPENDENCY_
LIST={"oracle.iaspt:10.1.3.0.0","oracle.java.jdbc.datadirect:10.1.2.0.1","oracle.x
ds:10.1.3.0.0","oracle.as.welcomepages:10.1.3.1.0","oracle.askernel.common:10.1.3.
0.0","oracle.iappserver.iappcore:10.1.3.0.0","oracle.options.ano.fullssl:10.1.0.2.
0","oracle.apache:10.1.3.0.0"}
A.6 Postinstallation
The success or failure of the non-interactive and silent installations is logged in the
installActions<time_stamp>.log file. Additionally, the silent installation
creates the silentInstall<time_stamp>.log file. The log files are created in the
oraInventory/logs directory.
The silentInstall<time_stamp>.log file contains the following line if the
installation was successful:
The installation of OracleAS <Installation Type> was successful.
A.8 Deinstallation
You can perform a silent deinstallation of Oracle Application Server by supplying a
silent deinstallation parameter to the response file you used for installation.
Modify the following parameter in your installation response file:
REMOVE_HOMES={"<ORACLE_HOME to be removed>"}
For example:
REMOVE_HOME="/local_location/oracle_home"
To perform a silent deinstallation, use the -deinstall parameter when entering the
command:
By default, the installer assigns port numbers to components from a set of default port
numbers. This appendix contains a list of these port numbers.
If you want to use a different set of port numbers, you have to create a file called
staticports.ini, in which you list the port numbers that you want to use. See
Section 2.5.3, "Using Custom Port Numbers (the "Static Ports" Feature)" for details.
This appendix contains the following topics:
■ Section B.1, "Method of Assigning Default Port Numbers"
■ Section B.2, "Default Port Numbers"
■ Section B.3, "Ports to Open in Firewalls"
For a 10g Release 3 (10.1.3.1.0) middle-tier instance, you need access to Oracle
Notification Server and AJP ports. You need to open the following ports used by these
components in the firewall:
■ OPMN Oracle Notification Server remote port
■ OC4J AJP port
This appendix guides you through the deinstallation and reinstallation process for
Oracle Application Server.
■ Section C.1, "Deinstallation Procedure: Overview"
■ Section C.2, "Deinstalling Procedure"
■ Section C.3, "Cleaning Up Oracle Application Server Processes"
■ Section C.4, "Reinstallation"
6. Remove the line for the deinstalled instance from the /etc/oratab file.
Towards the end of the file, you should see lines that specify the Oracle home
directory. Remove the line for the Oracle home that you deinstalled. For example,
if your Oracle home is /private1/j2ee, the line would look like the following:
*:/private1/j2ee:N
C.4 Reinstallation
The installer does not allow reinstallation of an Oracle Application Server instance in a
directory that already contains an Oracle Application Server instance. To reinstall
Oracle Application Server in the same directory, you have to deinstall and then install
it.
This appendix lists the configuration assistants and the location of their log files.
■ Section D.1, "Troubleshooting Configuration Assistants"
■ Section D.2, "Description of Oracle Application Server Configuration Assistants"
This appendix describes solutions to common problems that you might encounter
when installing Oracle Application Server. It contains the following sections:
■ Section E.1, "Log Files"
■ Section E.2, "General Troubleshooting Tips"
■ Section E.3, "Installation Problems and Solutions"
■ Section E.4, "Need More Help?"
Troubleshooting E-1
Installation Problems and Solutions
Solution
Exit the installer and check the log files for any error message. In particular, check the
ORACLE_HOME/install/make.log file.
Remove the failed installation. Before reinstalling Oracle Application Server, make
sure that your computer meets all the requirements listed in Chapter 2,
"Requirements".
Check especially the following requirements:
■ Check that the kernel parameters are set to the proper values. Note that if you
change the value of a kernel parameter, you must exit the installer and restart your
computer for the new value to take effect.
■ Check that you are installing Oracle Application Server in a valid directory. For
example, you cannot install Oracle Application Server in a database Oracle home.
See Section 2.12 for a complete list.
Solution
If the prerequisite checks display warnings about missing operating system patches or
patch bundles, the patch may actually be missing, or it may have been superseded. If
your computer contains the patch that supersedes it, you can ignore the warning.
See Section 2.3, "Software Requirements" for a list of required operating system
patches.
Solution
The directory that is the mount point of the CD-ROM or DVD-ROM was mounted
with incorrect permissions, and this caused the pwd command to not work correctly.
When you run pwd, it returns "cannot determine current directory".
To fix:
1. Unmount the CD-ROM.
2. Change permissions of the mount directory to 755.
3. Remount the CD-ROM.
The installer should now run correctly.
E.3.6 User Interface Does Not Display in the Desired Language, or Does Not Display
Properly
Problem
Messages do not appear in the desired language, or messages are not displayed
correctly
Troubleshooting E-3
Need More Help?
Solution
Currently Oracle Application Server does not support adding or removing languages
after installation.
If you are serving non-English content, be sure you add all the languages that you
need during installation. To add languages during installation, click the Product
Languages button in the "Select Installation Type" screen. To see which languages are
installed by default, see Section 3.3, "Installing Additional Languages".
If you are serving non-English content and forgot to click the Product Languages in
the installation, the user interface might not display properly because the required
fonts were not installed. You can fix this by contacting Customer Service for the
requirement fonts.
Problem
Configuration assistant failed
Solution
Configuration assistants fail from a variety of causes. Some things you can check are:
■ Check the log files for the failed configuration assistant to determine the problem.
The log files are located in the ORACLE_HOME/cfgtoollogs directory.
Fix the problem indicated in the log file, and click Retry to rerun the failed
configuration assistant.
If the configuration assistant fails while running configuration assistant execution
commands on the command line, then run the configuration assistant execution
command again.
You can use the generated script file named configtoolcmds.pl located in the
ORACLE_HOME/bin directory to run the failed configuration assistant again. The
configtoolcmds.pl script is generated after you exit the installer. During silent or
non-interactive installation, the configtoolcmds.pl script is generated
immediately after configuration assistant failure.
C E
C shell
environment variables, 2-20
setting shell limits, 2-13
_CLUSTER_NETWORK_NAME_, 6-29
CD-ROM
CLASSPATH, 2-21
copying to hard drive, 2-24
Index-1
DISPLAY, 2-21 hosts file for name resolution (OracleAS Disaster
LD_BIND_NOW, 2-23 Recovery), 6-30
LD_LIBRARY_PATH, 2-21 httpd.conf file, 2-17
NLS_LANG, 7-2
ORA_NLS, 2-23
I
PATH, 2-21
set in .profile file, 2-21 installActions.log, A-12
su command and, 2-21 installation
TMP, 2-22 advanced
TMPDIR, 2-22 see advanced installation
TNS_ADMIN, 2-22 basic
error codes from configuration assistants, D-2 see basic installation
/etc directory, 3-5 J2EE Server, 5-5
oraInst.loc file, 2-18 J2EE Server and Web Server, 5-4
/etc/csh.login file, 2-14 J2EE Server, Web Server and SOA Suite, 5-3
/etc/csh.login.local file, 2-14 Web Server, 5-6
/etc/group file, 6-4 installation steps
/etc/pam.d/login file, 2-13 advanced installation, 5-2
/etc/profile file, 2-14 basic installation, 4-2
/etc/profile.local file, 2-14 installation types, 1-2
/etc/resolve.conf file, 6-30 installer
/etc/security/limits.so file, 2-13 see Oracle Universal Installer
installing additional languages, 3-2
installing from hard drive, 2-24
F instance names, 3-3
failover (OracleAS Cold Failover Cluster), 6-23 how they are used, 3-3
fatal errors, D-1 restrictions, 3-3
files valid characters, 3-3
default shell startup file, 2-14 inventory directory, 3-2, 3-5
/etc/csh.login, 2-14 group for, 2-18
/etc/csh.login.local, 2-14 location of, 2-18
/etc/pam.d/login, 2-13 IP
/etc/profile, 2-14 installing on a computer with multiple IP
/etc/profile.local, 2-14 addresses, 2-24
/etc/security/limits.so, 2-13 requirements, 2-2
firewalls
and ports, B-2
J
first-time installation of any Oracle product, 3-2
font problems, E-3 J2EE Server
installation, 5-5
J2EE Server and Web Server
G installation, 5-4
groupadd command, 2-18 J2EE Server, Web Server and SOA Suite
groups (operating system) installation, 5-3
see operating system groups
groups command, 2-19
K
Korn shell
H setting shell limits, 2-13
high availability environments, 6-1
active-active topology, 6-5
L
active-passive topology, 6-18
/etc/group file, 6-4 languages, installing additional, 3-2
inventory directory, 6-5 LD_BIND_NOW environment variable, 2-23
oracle user, 6-4 LD_LIBRARY_PATH environment variable, 2-21
OracleAS Clusters, 6-5 limit command, 2-14
OracleAS Cold Failover Cluster, 6-18 limits.so file, 2-13
overview, 6-1 linking failed, E-2
requirements, 6-4 log files, E-1
summary of differences, 6-3 from non-interactive installations, A-12
hostname requirement, 2-2 location of, E-2
Index-2
login file, 2-13 groups command, 2-19
oracle user, 2-19
ORA_NLS environment variable, 2-23
M
Oracle Data Guard (for OracleAS Disaster
memory requirements, 2-3 Recovery), 6-27, 6-30
middle tiers Oracle Database 10g, 2-20
installing in OracleAS Disaster Recovery, 6-34 Oracle E-Delivery, 3-6
monitor requirements, 2-4 Oracle Enterprise Manager Application Server
mount point for CD-ROM, 3-7 Control
mount point for DVD, 3-7 URL, 7-1
multihomed computers, installing on, 2-24 Oracle home
directory, 3-1
N installing in a non-empty, 3-2
installing in an existing, 3-2
name resolution (OracleAS Disaster Recovery), 6-29 naming, 3-1
using DNS servers, 6-29 Oracle HTTP Server
using hosts file, 6-30 configuring static ports, 2-17
names of instances in NFS installations, 7-2
see instance names Oracle MetaLink
Network Appliance filers, 2-27 using to obtain updates to 10.1.3.1.0, 2-2
network requirements, 2-2 oracle software owner user
network topics, 2-23 setting shell limits, 2-13
installing from hard drive, 2-24 Oracle Universal Installer
installing from remote CD-ROM/DVD disappears after preinstallation checks, E-3
drive, 2-25 log files, E-1
installing on DHCP computers, 2-23 prerequisite checks, 2-28
installing on multihomed computers, 2-24 starting, 3-8
NFS storage, 2-27 where it writes files, 3-5
remote installations, 2-26 oracle user, 2-18, 2-19, 6-4
NFS installations setting shell limits, 2-13
configuring Oracle HTTP Server, 7-2 OracleAS Clusters
NFS storage, 2-27 see active-active topology
NIS and NIS+, 2-27 OracleAS Cold Failover Cluster
NLS_LANG environment variable, 7-2 advantages, 6-3
nofile failover, 6-23
shell limit on Linux, 2-13 in OracleAS Disaster Recovery environment, 6-32
non-interactive installations, A-1 mapping virtual hostname, 6-21
deinstalling, A-12 mapping virtual IP address, 6-21
log files, A-12 preinstallation steps, 6-21
postinstallation steps, A-12 see active-passive topology
preinstallation steps, A-2 setting up mountable file system, 6-23
security tips, A-12 OracleAS Disaster Recovery
noproc data synchronization, 6-26
shell limit on Linux, 2-13 installation steps, 6-33
installing middle tiers, 6-34
O installing OracleAS Infrastructure, 6-34
name resolution, 6-29
oc4jadmin user, 3-4 Oracle Data Guard, 6-30
password for, 3-4 setting up, 6-27
oinstall group, 2-18, 3-2
setting up identical hostnames, 6-28
operating system staticports.ini file, 6-28
patches, 2-4 with OracleAS Cold Failover Cluster, 6-32
operating system groups, 2-18
OracleAS Infrastructure
for inventory directory, 2-18 installing in OracleAS Disaster Recovery, 6-34
groups command, 2-19 oraInst.loc file, 2-18
oinstall group, 2-18
creation (non-interactive installations), A-2
operating system patches oraInventory directory, 2-18, 3-2
Red Hat Enterprise Linux AS/ES 3.0, 2-5
Red Hat Enterprise Linux AS/ES 4.0, 2-7
SUSE Linux Enterprise Server 9, 2-10
operating system users, 2-18
Index-3
P on DVD, 3-8
passwd command, 2-19
passwords S
for oc4jadmin user, 3-4 security tips for silent and non-interactive
patches installations, A-12
see operating system. setting shell limits, 2-13
PATH environment variable, 2-21 shared storage, 6-2
ports, 2-14 shell
checking if a port is in use, 2-14 default shell startup file, 2-14
choosing port numbers, 2-16 shell limits, 2-13
list of default port numbers, B-1 silent installations, A-1
static ports, 2-15 deinstalling, A-12
to open in firewalls, B-2 postinstallation steps, A-12
using default port numbers, 2-14 preinstallation steps, A-2
postinstallation steps, 7-1 security tips, A-12
for silent or non-interactive installations, A-12 silentInstall.log, A-12
preinstallation steps SSL
for silent and non-interactive installations, A-2 postinstallation configuration, 7-2
prerequisite checks, 2-28 starting Oracle Universal Installer, 3-8
failures, E-3 startup file
processor, 2-3 default shell startup file, 2-14
Product Languages button, 3-2 static ports, 2-15
.profile file, 2-21 for Oracle HTTP Server, 2-17
profile file, 2-14 not working, 2-16
profile.local file, 2-14 staticports.ini file, 2-15
creating, 2-15
R format, 2-15
in OracleAS Disaster Recovery, 6-28
RAM requirements, 2-3
su command, 2-21
record mode in the installer, A-3 SUSE Linux Enterprise Server 9, patches required
Red Hat Enterprise Linux AS/ES 3.0, patches for, 2-10
required for, 2-5
swap space requirement, 2-4
Red Hat Enterprise Linux AS/ES 4.0, patches
system requirements, 2-2
required for, 2-7
remote installations, 2-25, 2-26
requirements T
browser, 2-4 tcsh shell
disk space, 2-3 setting shell limits, 2-13
environment variables, 2-20 /tmp directory, 2-22, 3-5
for DHCP computers, 2-23 space required in, 2-4
for multihomed computers, 2-24 TMP environment variable, 2-22
hostname, 2-2 TMPDIR environment variable, 2-22
IP, 2-2 TNS_ADMIN environment variable, 2-22
memory, 2-3 tnsnames.ora file, 2-22
monitor, 2-4 topologies
network, 2-2 10.1.3.1.0 middle tiers, 1-3
operating system patches, 2-4 high availability, 1-3
processor, 2-3 integrated web server and OC4J middle
swap space, 2-4 tier, 1-5
response files, A-1 J2EE server and separate SOA applications with
creating, A-2 a remote oracle HTTP server, 1-11
creating using the record mode, A-3 J2EE server and the SOA suite with a remote
examples, A-4 HTTP server, 1-8
specifying on command-line, A-11 J2EE server with the SOA suite, 1-6
templates, A-3 J2EE server, web server, and the SOA
root user, 3-5 suite, 1-7
root.sh, 3-5 multiple SOA middle tiers with a remote oracle
runInstaller command HTTP server, 1-14
-executeSysPrereqs parameter, 2-2 SOA administration instance, 1-6
on CD-ROM, 3-8
Index-4
standalone OC4J instance, 1-5
with 10.1.2 Oracle HTTP Server, 1-4
with 10.1.2 OracleAS Web Cache, 1-4
with 10.1.2 OracleAS Web Cache cluster, 1-4
with 10.1.4 or 10.1.2 OracleAS
Infrastructure, 1-4
supported, 1-2 to 1-17
trigger attribute (for replication-policy), 6-16
troubleshooting, E-1
configuration assistants, D-1
general tips, E-1
U
ulimit command, 2-14
UNIX commands
groupadd, 2-18
limit, 2-14
passwd, 2-19
ulimit, 2-14
useradd, 2-19
UNIX users
setting shell limits, 2-13
user interface problems, E-3
useradd command, 2-19
users
setting shell limits for UNIX users, 2-13
users (operating system)
see operating system users
V
virtual IP, 6-3
W
Web Server
installation, 5-6
Welcome page, URL for, 7-1
write-quota attribute (in cluster tag), 6-18
X
X Windows
installing from, 2-4
Index-5
Index-6