2 System and Installation Requirements

2.2.1 Software Requirements for Red Hat Enterprise Linux AS/ES 2.1 Systems

Table 2-2 lists the software requirements for Red Hat Enterprise Linux AS/ES 2.1 systems and the procedure that follows the table describes how to ensure that your computer meets these requirements and any additional requirements for installing Oracle Application Server.

glibc-2.2.4-32.17
glibc-common-2.2.4-32.17
gcc-2.96-128.7.2
gcc-c++-2.96-128.7.2
pdksh-5.2.14-22
openmotif-2.1.30-12
sysstat-4.0.1-15.2.1as
compat-glibc-6.2-2.1.3.2
compat-libstdc++-6.2-2.9.0.16
libstdc++-2.96-128.7.2
gnome-libs-1.2.13-16
binutils-2.11.90.0.8-12.4
make-3.79.1-8
db1-1.85-7
db3-3.3.11-5

To ensure that the system meets all the requirements:

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 Linux Advanced Server release 2.1AS/\m (Pensacola)
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink http://metalink.oracle.com

   
   

3. To check that Update 5 is installed:

   # cat /etc/redhat-release
   Red Hat Linux Advanced Server release 2.1AS/\m (Pensacola Update 5)
   
   

   If Update 5 is installed, then errata 49 is installed and all the required software packages are installed.

4. To determine which version of the Linux kernel is installed, enter the following command:

   # uname -r
   kernel-smp-2.4.9-e.49
   
   

   In this example, the version shown is 2.4.9 with errata 49. Refer to the operating system documentation for information about upgrading the kernel if necessary.

   
   

   See Also: http://www.redhat.com for more information about Red Hat patches

   
   

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

   # rpm -q package_name
   
   

   If a package is missing, then download and install it using the following command:

   # rpm -i package_name
   
   

   When installing a package, ensure that 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 
   
   

2.2.2 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 that your computer meets these requirements and any additional requirements for installing Oracle Application Server Standard Edition One.

glibc-2.3.2-95.27
glibc-common-2.3.2-95.27
binutils-2.14.90.0.4-35
compat-glibc-7.x-2.2.4.32.6
compat-libstdc++-7.3-2.96.128
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
control-center-2.2.0.1-13.i386.rpm
xscreensaver-4.10-8.i386.rpm

$ rpm -ivh openmotif21-2.1.30-8

To ensure that the system meets all the requirements:

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 Linux Advanced Server release 3 (Taroon)
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink http://metalink.oracle.com.

   
   

3. To check that Update 3 is installed:

   # cat /etc/redhat-release
   Red Hat Enterprise Linux AS release 3 (Taroon Update 3)
   
   

4. To determine whether any other package is installed, enter a command similar to the following:

   # rpm -q package_name
   
   

   If a package is missing, then download it and install it using the following command:

   # rpm -i package_name
   
   

   When installing a package, ensure that you use 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, then set the architecture using the following command:

   prompt> setarch i386
   
   

2.2.3 Software Requirements for SUSE Linux Enterprise Server 8 Systems

Table 2-4 lists the software requirements for SUSE Linux Enterprise Server 8 systems and the procedure that follows the table describes how to ensure that your system meets these requirements and any additional requirements for installing Oracle Application Server.

glibc-2.2.2-124
gcc-3.2.2-38
gcc-c++-3.2.2-38
pdksh-5.2.14
openmotif-2.1.30MLI4
sysstat-4.0.3
libstdc++-3.2.2
make-3.79.1-407
binutils-2.12.90.0.15-50
compat-2003.1.10-0

To ensure that the system meets all the requirements:

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
   Welcome to SUSE Linux Enterprise Server 8 (i586) - Kernel \r (\l)
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink at http://metalink.oracle.com.

   
   

3. To determine the service pack version, enter the following command:

   # uname -r
   k_smp-2.4.21-138
   
   

   If the kernel version contains the string 2.4.21, then SP3 is installed. SP3 is certified for Oracle Application Server 10g Release 2 (10.1.2).

4. To determine whether any other package is installed, enter a command similar to the following:

   # rpm -q package_name
   
   

   If a package is missing, then download it and install it using the following command:

   # rpm -i package_name
   
   

   When installing a package, ensure that 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. Create the following symbolic link for the Perl executable if it does not already exist:

   # ln -sf /usr/bin/perl /usr/local/bin/perl
   
   

6. Create the following symbolic link for the fuser executable if it does not already exist:

   # ln -sf /bin/fuser /sbin/fuser
   
   

7. If the orarun package was installed on a SUSE Linux Enterprise Server system, then complete the following steps as the oracle user to reset the environment:

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

   2. Use any text editor to comment out the following line from the $HOME/.profile file:

      . ./.oracle
      
      

   3. Log out of the oracle user account.

   4. Log in to the oracle user account for the changes to take effect.

8. If any Java packages are installed on the system, then unset the Java environment variables, for example JAVA_HOME.

   
   

   Note: Oracle recommends that you do not install any of the Java packages supplied with the SUSE Linux Enterprise Server distribution.

   
   

9. Check the /etc/services file to ensure that the following port ranges are available on the computer:

   • ports 3060-3129 required for Oracle Internet Directory

   • ports 3130-3199 required for Oracle Internet Directory (SSL)

   • ports 1812-1829 required for Oracle Enterprise Manager (console)

   • ports 1830-1849 required for Oracle Enterprise Manager (agent)

   • ports 1850-1869 required for Oracle Enterprise Manager (RMI)

   Remove entries from the /etc/services file and restart the computer, if necessary. To remove the entries, you can use the perl script included in the utils/3167528/ directory of CD-ROM Disk 1 or in the application_server/utils/3167528/ directory on the DVD. Run the script as the root user. This script is also available as patch 3167528. This patch is available at

   http://metalink.oracle.com

   If these ports are not available, then the associated configuration assistants will fail during the installation.

10. If you use Network Information Service (NIS):

    1. Ensure that the following line exists in the /etc/yp.conf file:

       hostname.domainname broadcast
       
       

    2. Ensure that the following line exists in the /etc/nsswitch.conf file:

       hosts: files nis dns
       
       

11. Ensure that the localhost entry in the /etc/hosts file is an IPv4 entry. If the IP entry for localhost is in IPv6 format, installation cannot succeed. The following example shows an IPv6 entry:

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

    # special IPv6 addresses
    # ::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. Run the script as the root user. This script is also available as patch 4015045. This patch is available at

    http://metalink.oracle.com

2.2.4 Software Requirements for SUSE Linux Enterprise Server 9 Systems

Table 2-5 lists the software requirements for SUSE Linux Enterprise Server 9 systems and the procedure that follows the table describes how to ensure that your system meets these requirements and any additional requirements for installing Oracle Application Server.

glibc-2.3.3-98.28
gcc-3.3.3-43.24
gcc-c++-3.3.3-43.24
libstdc++-3.3.3-43.24
libstdc++-devel-3.3.3-43.24
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
db1-1.85-85.1
compat-2004.7.1-1.2

To ensure that the system meets all the requirements:

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
   Welcome to SUSE Linux Enterprise Server 9 (i686) - Kernel \r (\l)
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink at http://metalink.oracle.com.

   
   

3. To determine the service pack version, enter the following command:

   # uname -r
   kernel-bigsmp-2.6.5-7.97
   
   

   If the kernel version contains the string 2.4.21, then SP3 is installed. SP3 is certified for Oracle Application Server 10g Release 2 (10.1.2).

4. To determine whether any other package is installed, enter a command similar to the following:

   # rpm -q package_name
   
   

   If a package is missing, then download it and install it using the following command:

   # rpm -i package_name
   
   

   When installing a package, ensure that 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. Create the following symbolic link for the Perl executable if it does not already exist:

   # ln -sf /usr/bin/perl /usr/local/bin/perl
   
   

6. Create the following symbolic link for the fuser executable if it does not already exist:

   # ln -sf /bin/fuser /sbin/fuser
   
   

7. If the orarun package was installed on a SUSE Linux Enterprise Server system, then complete the following steps as the oracle user to reset the environment:

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

   2. Use any text editor to comment out the following line from the $HOME/.profile file:

      . ./.oracle
      
      

   3. Log out of the oracle user account.

   4. Log in to the oracle user account for the changes to take effect.

8. If any Java packages are installed on the system, then unset the Java environment variables, for example JAVA_HOME.

   
   

   Note: Oracle recommends that you do not install any of the Java packages supplied with the SUSE Linux Enterprise Server distribution.

   
   

9. Check the /etc/services file to ensure that the following port ranges are available on the system:

   • ports 3060-3129 required for Oracle Internet Directory

   • ports 3130-3199 required for Oracle Internet Directory (SSL)

   • ports 1812-1829 required for Oracle Enterprise Manager (console)

   • ports 1830-1849 required for Oracle Enterprise Manager (agent)

   • ports 1850-1869 required for Oracle Enterprise Manager (RMI)

   Remove entries from the /etc/services file and restart the computer, if necessary. To remove the entries, you can use the Perl script included in the utils/3167528/ directory of CD-ROM Disk 1 and in the application_server/utils/3167528/ directory on the DVD. Run the script as the root user. This script is also available as patch 3167528. This patch is available at

   http://metalink.oracle.com

   If these ports are not available, then the associated configuration assistants will fail during the installation.

10. If you use Network Information Service (NIS), then:

    1. Ensure that the following line exists in the /etc/yp.conf file:

       hostname.domainname broadcast
       
       

    2. Ensure that the following line exists in the /etc/nsswitch.conf file:

       hosts: files nis dns
       
       

11. Enure that the localhost entry in the /etc/hosts file is an IPv4 entry. If the IP entry for localhost is IPv6 format, then installation cannot succeed. The following example shows an IPv6 entry:

    # special IPv6 addresses
    ::1             localhost ipv6-localhost ipv6-loopback
    ::1             ipv6-localhost ipv6-loopback
    
    

    To correct this sample /etc/hosts file, comment the localhost entry as follows:

    # special IPv6 addresses
    # ::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 or in the application_server/utils/4015045/ directory on the DVD. Run the script as the root user. This script is also available as patch 4015045. This patch is available at

    http://metalink.oracle.com

2.3.1 Configuring the Kernel Parameters on Linux

The computers on which you plan to install OracleAS Metadata Repository or OracleAS Web Cache require the kernel parameters to be set to the minimum values. In addition, you need to set the shell limits to improve the performance of the software.

This section provides information about the kernel parameter settings for OracleAS Metadata Repository and OracleAS Web Cache. It covers the following topics:

• Section 2.3.1.1, "Kernel Parameter Settings for OracleAS Web Cache"

• Section 2.3.1.2, "Kernel Parameter Settings for OracleAS Metadata Repository"

2.3.2 Shell Limits for the oracle User

To improve the performance of the software on Linux systems, you must increase the following shell limits for the oracle user, depending on the default shell. The following table lists the limits different shells:

To increase the shell limits:

1. Add the following lines to /etc/security/limits.conf file:

   *        soft   nproc         2047
   *        hard   nproc         16384
   *        soft   nofile        2048
   *        hard   nofile        65536
   
   

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 default shell of the oracle user, make the following changes to the default shell startup 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.4.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, then 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 not sure whether there is already an inventory directory on the computer, then 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, then the computer does not have Oracle products installed on it.

2.4.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, then:

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, then 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, then 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 (refer to Table 2-6). You can enter the same operating system group for both fields.

2.6.1 Environment Variable Tips

Here are some tips when working with environment variables:

• If you set environment variables in the .profile file, then 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), then 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.7.1 Location of the Default Identity Management Realm

The installer reads the 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 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 preceding example, the location of the default Identity Management realm would look like dc=mydomain,dc=com.

If the file uses a different format, then the installer displays an incorrect value on the screen. For example, if the hosts file 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.

2.7.2 Host Name for Oracle Application Server Single Sign-On

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

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

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

2.8.1 Installing on Multihomed (Multi-IP) Computers

If you are installing Oracle Application Server on a computer with multiple network cards, then the installer uses the first name in the /etc/hosts file. If this is not the name that you want to use, then you can do one of the following:

• Reorder the lines in the /etc/hosts file so the desired host name appears first, run the installer, then revert the file to its original state after installation.

• If you do not want to edit the /etc/hosts file, then you can start up the installer with the OUI_HOSTNAME parameter. Specify the host name that you want to use in this parameter. For example:

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

2.8.2 Copying CD-ROMs or DVD to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Oracle Application Server CD-ROMs or DVD, you can copy the contents of the CD-ROMs or DVD 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 drives.

(You can install from remote CD-ROM or DVD drives. Refer to Section 2.8.3, "Installing from a Remote CD-ROM or DVD 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 (refer to Figure 2-1).

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. 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, 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-1).

To Copy the CD-ROMs:

1. Create a directory structure on your hard drive as shown in Figure 2-1.

   You need to create a parent directory (called OracleAS_10g_10_1_2 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 CD-ROM number.

   Figure 2-1 Directory Structure for Copying CD-ROMs to Disk

   
   Description of the illustration copyToDisk.gif
   
   

2. Copy the contents of each CD-ROM into the corresponding directory.

   prompt> cp -pr /cdrom_mount_point/10.1.2disk1/* /path/to/hard/drive/Disk1/
   prompt> cp -pr /cdrom_mount_point/10.1.2disk2/* /path/to/hard/drive/Disk2/
   ... Repeat for each CD-ROM.
   
   

To run the installer from the copied files, invoke the runInstallersetup.exe 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 Copy the application_server Directory from the DVD

Perform the following steps to copy the application_server directory using the command line:

1. (optional) Create a directory to contain the application_server directory.

2. Copy the application_server directory from the DVD to your hard disk.

   prompt> cp -pr /dvd_mount_point/application_server /path/to/hard/drive
   
   

   The following example assumes /dvdrom is the DVD drive, and /> application_server is the destination directory:

   /> cp -rp /dvdrom/application_server /application_server
   
   

To run the installer from the copied files, invoke the runInstaller script executable from the computer that will be running Oracle Application Server:

prompt> /path/to/hard/drive/application_server/runInstaller

/> cd /application_server
/> ./runInstaller

2.8.3 Installing from a Remote CD-ROM or DVD Drive

If the computer where you want to install Oracle Application Server does not have a CD-ROM or DVD drive, then you can copy the discs to the hard drive of a computer with the proper disc drive as described in Section 4.9.2 and then perform a remote installation from that computer using the instructions described in Section 2.8.4, "Installing on Remote Computers".

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

To perform a remote installation:

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

   local_computer> xhost +remote_computer
   
   

   If you do not run xhost, then 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.5, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 2.6, "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. Refer to Section 5.2, "Starting Oracle Universal Installer".

2.8.5 Installing on NFS-Mounted Storage

To run Oracle Application Server on NFS systems, you have to use a certified NFS-mounted storage system.

Currently, Oracle Application Server is certified to run on the following NFS systems:

• Network Appliance (NetApp) filers

The NetApp system should be exported to at least the remote install user and remote root user. You can do this using exportfs command:

prompt> exportfs -i /vol/vol1

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

2.8.6 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 2-2 Run Oracle Application Server Only on the Computer Where It Is Installed

Description of the illustration nfs_multi_inst.gif

2.8.7 Support for NIS and NIS+

You can install and run Oracle Application Server in Network Information Service (NIS) and NIS+ environments.

2.8.8 Installing on a DHCP Host (Linux Only)

If you are installing Oracle Application Server Standard Edition One in a DHCP network, then you must use a loopback configuration. To access the Oracle Application Server Standard Edition One, 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 host name to loopback IP address:

   1. Configure the host to resolve host name 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 host name 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 host name used in step 2