4 Requirements

4.1.1 Memory Requirements for Running Multiple Instances on the Same Computer

If you plan to run OracleAS Infrastructure 10g plus a middle tier on the same computer, ensure the computer meets the memory requirements listed in Table 4-3.

Note that these values have been tested against a small number of users. If you have many users, you might have to increase the amount of memory.

4.1.2 Tips for Reducing Memory Usage

If you need to reduce memory consumption:

• Configure only the components that you need.

• Choose the smallest middle tier type that contains the components that you need.

• After installation, start up only the components that you need. See the Oracle Application Server 10g Administrator's Guide for details.

• After installation, if you installed multiple instances on the same computer, you can consolidate the Oracle Enterprise Manager component. For example, if you installed an OracleAS Infrastructure 10g and a middle tier on the same computer, you can configure one Oracle Enterprise Manager component to manage both OracleAS Infrastructure 10g and middle tier (instead of having two Oracle Enterprise Manager components, one for the infrastructure and one for the middle tier). See the Oracle Application Server 10g Administrator's Guide for details.

4.2.1 Checking the Software Requirements for HP-UX

Depending on the version of HP-UX, check that the software listed in Table 4-4 or Table 4-5 is installed on the system. The procedure that follows the tables describes how to ensure the correct software is installed on the system.

To ensure that the system meets these requirements, follow these steps:

1. To determine which version of HP-UX is installed, enter the following command:

   # uname -a
   HP-UX hostname B.11.11 U 9000/800 109444686 unlimited-user license
   
   

   In this example, the version of HP-UX 11i is 11.11.

2. To determine which JDK is installed, enter the following command:

   # JDK_location/bin/java -fullversion
   
   

   If the version displayed is less than 1.4.1.05, download JDK 1.4.1.05 or higher from the following Web site and install it:

   http://www.hp.com/products1/unix/java/index.html
   
   

3. To determine whether the Quality Pack is installed, enter the following command:

   # /usr/sbin/swlist | grep QPK
   
   

   If the quality pack is not installed, download it from the following web site and install it:

   http://www.software.hp.com/SUPPORT_PLUS/qpk.html
   
   

4. To determine whether a bundle or product is installed, enter the following command:

   # /usr/sbin/swlist -l product | more
   
   

   If a required product is not installed, you must install it. See your operating system or software documentation for information on installing products.

5. To determine whether a patch is installed, enter a command similar to the following:

   # /usr/sbin/swlist -l patch | grep PHKL_27813
   
   

   Alternatively, to list all installed patches, enter the following command:

   # /usr/sbin/swlist -l patch | more
   
   

   If a required patch is not installed, download it from the following URL and install it:

   http://itresourcecenter.hp.com
   
   

6. If the Motif package listed in Table 4-5 and Table 4-4 is not installed on the computer, create the following symbolic links:

   1. Log in as root.

   2. Change to the /usr/lib directory:

      # cd /usr/lib
      
      

   3. Create the required links:

      # ln -s libX11.3 libX11.sl
      # ln -s libXIE.2 libXIE.sl
      # ln -s libXext.3 libXext.sl
      # ln -s libXhp11.3 libXhp11.sl
      # ln -s libXi.3 libXi.sl
      # ln -s libXm.4 libXm.sl
      # ln -s libXp.2 libXp.sl
      # ln -s libXt.3 libXt.sl
      # ln -s libXtst.2 libXtst.sl
      

4.2.2 Checking the Software Requirements for Linux

Depending on your distribution of Linux, see one of the following sections for information on checking the software requirements:

• Software Requirements for Red Hat 2.1 Systems

• Software Requirements for Red Hat 3.0 Systems

• Software Requirements for UnitedLinux 1.0 Systems

Oracle does not support customized kernels or modules not supported by the Linux vendor.

You can install Oracle Application Server 10g (9.0.4) on a Linux system that is not on a network and you can install Oracle Application Server 10g (9.0.4) 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.

http://www.redhat.com

http://www.redhat.com

$ rpm -ivh openmotif21-2.1.30-8

http://www.unitedlinux.com

4.3.1 Configuring Kernel Parameters on HP-UX

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.

To view the current value or formula specified for these kernel parameters, and to change them if necessary, follow these steps:

1. Optionally, set the DISPLAY environment variable to specify the display of the local system:

   • Bourne, Bash, or Korn shell:

     $ DISPLAY=localhost:0.0 ; export DISPLAY
     
     

   • C shell:

     $ setenv DISPLAY localhost:0.0
     
     

2. Start System Administration Manager (SAM):

   # /usr/sbin/sam
   
   

3. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

4. Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

   If necessary, see the SAM online help for more information on completing this step.

5. Exit from SAM.

6. If you modified the value specified for any parameter, reboot the system:

   # /sbin/shutdown -r now
   
   

7. If necessary, when the system restarts, log in and switch user to root.

4.3.2 Configuring the Kernel Parameters on Linux

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedures following the table describe how to verify and set the values.

To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

1. Enter commands similar to the following to view the current values of the kernel parameters:

   
   

   Note: Make a note of the current values and identify any values that you must change.

   
   

   Parameter	Command
   semmsl, semmns, semopm, and semmni	# /sbin/sysctl -a | grep sem This command displays the value of the semaphore parameters in the order listed.
   shmall, shmmax, and semmni	# /sbin/sysctl -a | grep shm
   msgmax, msgmnb, and msgmni	# /sbin/sysctl -a | grep msg
   file-max	# /sbin/sysctl -a | grep file-max
   ip_local_port_range	# /sbin/sysctl -a | grep ip_local_port_range This command displays a range of port numbers.

   
   

2. If the value of any kernel parameter is different to the recommended value, complete the following steps:

   1. Using any text editor, create or edit the /etc/sysctl.conf file and add or edit lines similar to the following:

      
      

      Note: Include lines only for the kernel parameter values that you want to change. For the semaphore parameters (kernel.sem), you must specify all four values. However, if any of the current values are larger than the recommended value, specify the larger value.

      
      

      kernel.shmall = 2097152
      kernel.shmmax = 2147483648
      kernel.shmmni = 142
      # semaphores: semmsl, semmns, semopm, semmni
      kernel.sem = 256 32000 100 142
      fs.file-max = 131072
      net.ipv4.ip_local_port_range = 20000 65000
      kernel.msgmni = 2878 
      kernel.msgmax = 8192 
      kernel.msgmnb = 65535
      
      

      By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.

   2. Enter the following command to change the current values of the kernel parameters.

      # /sbin/sysctl -p
      
      

      Review the output from this command to verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then enter this command again.

   3. On UnitedLinux only, enter the following command to cause the system to read the /etc/sysctl.conf file when it reboots:

      # chkconfig boot.sysctl on
      
      

To improve the performance of the software on Linux systems, you must increase the following shell limits for the oracle user, depending on the user’s default shell:

To increase the shell limits:

1. Add the following lines to /etc/security/limits.conf file where -> represents the tab character:

   * -> -> soft -> nproc -> -> 2047
   * -> -> hard -> nproc -> -> 16384
   * -> -> soft -> nofile -> -> 2048
   * -> -> hard -> nofile -> -> 16384
   
   

2. Add the following line to the /etc/pam.d/login file, if it does not already exist:

   session    required     /lib/security/pam_limits.so
   
   

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 16384
             else
                   ulimit -u 16384 -n 16384
             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 16384
     endif
     
     

4.4.1 Using Default Port Numbers

If you want to use the default port numbers for such components, you do not have to do anything. See Appendix E, " Default Port Numbers" for a list of default port numbers that the installer will assign to components.

myApplication      7777/tcp

# ldap   389/tcp   # Lightweight Directory Access Protocol
# ldap   389/udp   # Lightweight Directory Access Protocol
# ldaps  636/tcp   # LDAP protocol over TLS/SSL (was sldap)
# ldaps  636/udp   # LDAP protocol over TLS/SSL (was sldap)

4.4.2 Using Custom Port Numbers (the "Static Ports" Feature)

To instruct the installer to assign custom port numbers for components:

1. Create a file containing the component names and port numbers. Section 4.4.2.1, "Format of the staticports.ini File" describes the file format. This file is typically called the staticports.ini file, but you can name it anything you want.

2. When you start up the installer, specify the appropriate parameter and the full path to the staticports.ini file on the command line.

   Table 4-9 shows the parameters for specifying the static ports file on the command line. The text in bold highlights the differences in the names.

   
   

   Note: The static ports parameters on the command line are different for each installation type. Be sure you use the parameter that matches the installation type you are doing. If the parameter you specify does not match the installation type, the installer assigns default ports for all components.

   
   

   Table 4-9 Parameters for Specifying Static Port File on the Command Line

   Installation Type	Parameter for Specifying Static Ports File
   OracleAS Infrastructure 10g	oracle.iappserver.infrastructure:s_staticPorts=/fullpath/to/local/ staticports.ini
   Middle tier	oracle.iappserver.iapptop:s_staticPorts=/fullpath/to/local/ staticports.ini
   OracleAS Developer Kits 10g	oracle.iappserver.devcorner:s_staticPorts=/fullpath/to/local/ staticports.ini

   
   

   For example, if you are installing OracleAS Infrastructure 10g, use the following syntax (enter the command on one line):

   prompt> mount_point/904disk1/runInstaller
      oracle.iappserver.infrastructure:s_staticPorts=/fullpath/to/local/
      staticports.ini
   
   

   Note that you always have to specify the full path to the staticports.ini file. The reason is that the installer changes the current directory to a directory different from the one where you started the installer from.

   If you do not specify the full path to the file, the installer will not be able to find the file. The installer will then assign default ports for all the components, and it will do this without displaying any warning.

# J2EE and Web Cache
Oracle HTTP Server port = port_num
Oracle HTTP Server Listen port = port_num
Oracle HTTP Server SSL port = port_num
Oracle HTTP Server Listen (SSL) port = port_num
Oracle HTTP Server Diagnostic port = port_num
Oracle HTTP Server Jserv port = port_num
Java Object Cache port = port_num
DCM Java Object Cache port = port_num
Oracle Notification Server Request port = port_num
Oracle Notification Server Local port = port_num
Oracle Notification Server Remote port = port_num
Application Server Control port = port_num
Application Server Control RMI port = port_num
Oracle Management Agent port = port_num
Web Cache HTTP Listen port = port_num
Web Cache HTTP Listen (SSL) port = port_num
Web Cache Administration port = port_num
Web Cache Invalidation port = port_num
Web Cache Statistics port = port_num
Log Loader port = port_num

# Business Intelligence and Forms
Discoverer OSAgent port = port_num
Reports Services SQL*Net port = port_num

# Infrastructure
Oracle Internet Directory port = port_num
Oracle Internet Directory (SSL) port = port_num
Oracle Certificate Authority SSL Server Authentication port = port_num
Oracle Certificate Authority SSL Mutual Authentication port = port_num

4.4.2.3 Ports for Oracle HTTP Server and OracleAS Web Cache

Be sure you understand the following when setting ports for these components.

In the httpd.conf file for Oracle HTTP Server, the Port and the Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server. The correct lines in the staticports.ini file for setting these ports depend on which components you are configuring.

If You Are Configuring OracleAS Web Cache and Oracle HTTP Server

1. Set the port for OracleAS Web Cache.

   OracleAS Web Cache uses the port specified by the Port directive (Figure 4-1). To set this port, use this line in the staticports.ini file:

   Web Cache HTTP Listen port = port_number
   
   

   To configure the SSL port for OracleAS Web Cache, use the following line:

   Web Cache HTTP Listen (SSL) port = port_number
   
   

   You cannot set the port number using the "Oracle HTTP Server port" line in this case. If your staticports.ini file contains both "Oracle HTTP Server port" and "Web Cache HTTP Listen port", the "Oracle HTTP Server port" line is ignored. For example, if you have these lines in staticports.ini:

   Web Cache HTTP Listen port = 7979
   Oracle HTTP Server port = 8080
   
   

   the Port directive would be set to 7979.

2. Set the port for Oracle HTTP Server.

   Oracle HTTP Server uses the port specified by the Listen directive. To set this port, use this line in the staticports.ini file:

   Oracle HTTP Server Listen port = port_number
   
   

   To configure the SSL Listen port, use the following line:

   Oracle HTTP Server Listen (SSL) port = port_number
   
   

Figure 4-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

Description of the illustration ports_wc.gif

If You Are Configuring Oracle HTTP Server Only (no OracleAS Web Cache)

If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives (Figure 4-2). In this case, you must set both directives to use the same port number.

To set these ports, use the "Oracle HTTP Server port" and "Oracle HTTP Server Listen port" lines in the staticports.ini file. For example:

Oracle HTTP Server port = 8080
Oracle HTTP Server Listen port = 8080

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

If you also specify the Web Cache lines in staticports.ini, they will be ignored because you are not configuring OracleAS Web Cache.

Figure 4-2 Configuring Only Oracle HTTP Server

Description of the illustration ports_no_wc.gif

Web Cache HTTP Listen port = 80
Oracle HTTP Server Listen port = 81
Web Cache HTTP Listen (SSL) port = 443
Oracle HTTP Server Listen (SSL) port = 444 

Oracle HTTP Server port = 80
Oracle HTTP Server Listen port = 80
Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443

4.4.3 If Port 1521 Is in Use

The installer configures port 1521 for the OracleAS Metadata Repository listener (version 9.0.1.5). This port cannot be changed through the staticports.ini file.

If port 1521 on your computer is already in use by an existing application, such as Oracle9i database listener or some other application, you might have to take some action before running the installer. See the following sections for details.

• Section 4.4.3.1, "If Port 1521 Is In Use by an Existing Oracle9i Database"

• Section 4.4.3.2, "If Port 1521 Is In Use by Some Other Application"

prompt> $ORACLE_HOME/bin/lsnrctl VERSION

$ lsnrctl VERSION
LSNRCTL for UNIX: Version 9.0.1.5.0 - Production on 29-APR-2003 19:26:18

Copyright (c) 1991, 2001, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=test.mydomain.com)(PORT=1521)))
TNSLSNR for UNIX: Version 9.0.1.5.0 - Production
        TNS for UNIX: Version 9.0.1.5.0 - Production
        Unix Domain Socket IPC NT Protocol Adaptor for UNIX: Version 9.0.1.5.0 - Production
        Oracle Bequeath NT Protocol Adapter for UNIX: Version 9.0.1.5.0 - Production
The command completed successfully

4.5.1 Create a Group for the Inventory Directory

If you plan to install Oracle Application Server on a computer that does not have Oracle products, create a group to own the inventory directory. The installer writes its files in the inventory directory to keep track of the Oracle products installed on the computer.

This guide uses the name oinstall for this operating system group.

By having a separate group for the inventory directory, you allow different users to install Oracle products on the computer. Users need write permission for the inventory directory. They can achieve this by belonging to the oinstall group.

For the first time installation of any Oracle product on a computer, the installer displays a screen where you enter a group name for the inventory directory, and a screen where you enter the location of the inventory directory.

The default name of the inventory directory is oraInventory.

If you are unsure if there is already an inventory directory on the computer, look in the /var/opt/oracle/oraInst.loc file for HP systems and the /etc/oraInst.loc file on Linux systems. 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.

4.5.2 Create Groups for Database Administrators

This section applies only if you plan to install the OracleAS Metadata Repository in a new database created by the installer.

When the database is not mounted and database authentication is unavailable, the database uses operating system groups to determine user privileges. The database recognizes these groups and privileges:

You need to create operating system groups for these groups.

If you want an operating system group called dba to have SYSDBA privileges:

1. Create the dba group.

2. Ensure that the user running the installer is a member of the dba group.

If you want a different operating system group to have SYSDBA privileges, or if you want to associate SYSDBA and SYSOPER privileges with different groups, ensure the user running the installer does not belong to the dba group.

If the user running the installer does not belong to the dba group, the installer displays a screen where you can enter the names of groups to have the database administrator privileges. The screen has two fields: one for the OSDBA group and one for the OSOPER group (see Table 4-12). You can enter the same operating system group for both fields.

4.7.1 Environment Variable Tips

Here are some tips when working with environment variables:

• If you set environment variables in the .profile file, they might not be read. To ensure environment variables are set to the correct values, check their values in the shell where you will be running the installer.

• To check the value of environment variables, use the env command. This displays all the currently defined environment variables and their values.

  % env
  
  

• 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 - option (su - user).

  # /* root user */
  # su - oracle
  % env
  
  

4.7.2 ORACLE_HOME and ORACLE_SID

It does not matter if these environment variables are set or unset when you start up the installer because the installer unsets these environment variables.

4.7.3 PATH, CLASSPATH, and Shared Library Path Environment Variables

Edit your PATH, CLASSPATH, and shared library path environment variables so that they do not reference any Oracle home directories.

Table 4-15 lists the shared library path environment variables for different platforms

4.7.4 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

Example (Bourne or Korn shell):

$ DISPLAY=test.mydomain.com:0.0; export DISPLAY

You can test the display by running the xclock program:

$ /usr/openwin/bin/xclock &

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 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://otn.oracle.com) for information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".

4.7.5 TMP and TMPDIR

The installer uses a temporary directory for swap space. The installer checks for the TMP and TMPDIR environment variables to locate the temporary directory. If this environment variable does not exist, the installer uses the /tmp directory.

If you want the installer to use a temporary directory other than /tmp, set the TMP and TMPDIR environment variables to the full path of an alternate directory. The oracle user must have right permission for this directory and the directory must meet the requirements listed in Section 4.1, "Check Hardware Requirements".

Example (C shell):

% setenv TMP /tmp2
% setenv TMPDIR /tmp2

Example (Bourne or Korn shell):

$ TMP=/tmp2; export TMP
$ TMPDIR=/tmp2; export TMPDIR

4.7.6 TNS_ADMIN

This section describes two requirements:

• The TNS_ADMIN environment variable must not be set.

• The /etc and the /var/opt/oracle directories 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 or /var/opt/oracle, do the following steps before installing Oracle Application Server.

1. If you have the tnsnames.ora file in /etc or /var/opt/oracle, move the file from these directories 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
   
   

   Example (Bourne or Korn shell):

   $ unset TNS_ADMIN
   
   

After installation, you can merge the contents of the newly created tnsnames.ora file with your existing tnsnames.ora file.

4.7.7 ORA_NLS

To make sure that the Oracle Application Server installation completes successfully, unset this environment variable.

Example:

$ unset ORA_NLS

4.7.8 LD_BIND_NOW (Linux Only)

To make sure that the Oracle Application Server installation completes successfully on Linux systems, unset this environment variable.

Example:

$ unset LD_BIND_NOW

4.8.1 Location of the Default Identity Management Realm

The installer reads the /etc/hosts file to construct the location of the default Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.

The /etc/hosts file should use the following format:

ip_address   fully_qualified_hostname   short_hostname

Example:

123.45.67.89   primaryHost.mydomain.com   primaryHost

In the previous example, the location of the default Identity Management realm would look like "dc=mydomain,dc=com".

If the file uses a different format, the installer displays an incorrect value in the screen. For example, if the /etc/hosts contains:

123.45.67.89   primaryHost   primaryHost.mydomain.com  <--- incorrect format

the installer would display "dc=primaryHost,dc=com" as the default Identity Management realm. This is probably not the value that you want for the default Identity Management realm.

4.8.2 Hostname for OracleAS Single Sign-On

If you are installing OracleAS Single Sign-On, and your /etc/hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).

If you want to require a domain name when connecting to the Single Sign-On server, you can edit the /etc/hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in /etc/hosts. For example:

prompt> mount_point/904disk1/runInstaller OUI_HOSTNAME=myserver.mydomain.com

4.9.1 Installing on Computers With Multiple Network Cards

If you are installing Oracle Application Server on a computer with multiple network cards, the installer uses the first name in the /etc/hosts file. You may need to re-order the lines in this file so the desired hostname appears first. You can change the file back to its original state after installation.

4.9.2 Installing on NFS-Mounted Storage

Currently, Oracle Application Server is certified to run on the following NFS-mounted storage system:

• Network Appliance filers

The NFS-mounted system should be exported to at least the remote install user and remote root user.

To check the latest certification list for any updates, visit Oracle Technology Network (http://otn.oracle.com).

4.9.3 Running Multiple Instances from One Installation

Oracle Application Server components are intended to be run only on the computer where they are installed. You cannot run the components on remote computers, even though the computers can access the files through NFS.

Figure 4-3 Run Oracle Application Server Only on the Computer Where It Is Installed

Description of the illustration nfs_multi_inst.gif

4.9.4 Copying the Discs to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Oracle Application Server discs, you can copy the contents of the discs 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 the correct drives.

Ensure that the computers on which you want to install Oracle Application Server can access the hard drive where you copied the discs. You run the installer from the computers that will run Oracle Application Server.

When you install from the hard drive, the installer does not prompt you to swap discs. It can find all the files if they are in the proper locations (see Figure 4-4).

Space requirement: Ensure that the hard drive contains enough space to hold the contents of the discs. Each CD-ROM contains approximately 650 MB. This means that if you are copying four CD-ROMs, you need approximately 2.6 GB of disk space. This space is in addition to the space required for installing Oracle Application Server (listed in Section 4.1).

To copy the contents of the discs, follow these steps:

1. Create a directory structure on your hard drive as shown in Figure 4-4. You need to create a parent directory (called OracleAS_10g_904 in the example, but you can name it anything you like), and, under the parent directory, create subdirectories called Disk1, Disk2, and so on. The names of the subdirectories must be DiskN, where N is the disc number.

   Figure 4-4 Directory Structure for Copying CD-ROMs to Disk

   
   Description of the illustration copyToDisk.gif
   
   

2. Copy the contents of each disc into the corresponding directory.

   prompt> cp -pr /cdrom_mount_point/* /path/to/hard/drive/Disk1/
   prompt> cp -pr /cdrom_mount_point/* /path/to/hard/drive/Disk2/
   ... Repeat for each disc.
   
   

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

4.9.5 Installing on a Computer Without the Appropriate Disc Drive

If the computer where you want to install Oracle Application Server does not have the appropriate disc drive, you can copy the discs to the hard drive of a computer with the proper disc drive as described in Section 4.9.4 and then perform a remote installation from that computer using the instructions described in Section 4.9.6.

4.9.6 Installing on Remote Computers

You can run the installer on a remote computer ("remote_computer"), but have the installer screens display on your local computer ("local_computer"). The installer will install Oracle Application Server on the remote computer.

1. Allow remote_computer to display on local_computer. You need to run this command on the local computer’s console.

   local_computer> xhost +remote_computer
   
   

   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 4.6, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 4.7, "Environment Variables".

   local_computer> rlogin -l oracle remote_computer.mydomain.com
   - OR -
   local_computer> telnet remote_computer.mydomain.com
   
   

3. Set the DISPLAY environment variable on remote_computer to point to local_computer.

   Example (C shell):

   remote_computer> setenv DISPLAY local_computer.mydomain.com:0.0
   
   

   Example (Bourne or Korn shell):

   remote_computer> DISPLAY=local_computer.mydomain.com:0.0; export DISPLAY
   
   

4. Run the installer. See Section 5.15, "Starting the Oracle Universal Installer".

4.9.7 Installing on a DHCP Host

If you are installing Oracle Application Server in a DHCP network you must use a loopback configuration. To access the Oracle Application Server, you need to use a local browser. Perform the following steps to install Oracle Application Server in a DHCP network:

1. Find the IP address allocated from the DHCP server by running the following command:

   $ /sbin/ifconfig -a
   
   

   The IP address is associated with the interface configured to use DHCP.

2. Configure the host to resolve hostname to loopback IP address:

   1. Configure the host to resolve hostname to loopback IP address, by modifying the /etc/hosts file to contain the following entries:

      127.0.0.1 hostname.domainname hostname 
      127.0.0.1 localhost.localdomain localhost 
      
      

   2. Check that the hostname resolves to the loopback IP address by entering the following command:

      $ /bin/ping hostname.domainname
      
      

3. Complete the Oracle Application Server installation as described in this guide using the hostname used in step 2.