4 Requirements

4.2.1 Memory Requirements for Running Multiple Instances on the Same Computer

If you plan to run OracleAS Infrastructure and 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.2.2 Installing from the Console or X Windows

If you are performing the installation from the console or X Windows, then add the following line to the /etc/pamd.d/xdm file:

session required pam_limits.so

4.2.3 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. Refer to Oracle Application Server Administrator's Guide for details.

• Run Application Server Control only when you need to administer an instance. In most cases, you do not need Application Server Control running all the time.

  If you are running multiple Oracle Application Server instances on one computer, each Application Server Control can consume a lot of memory. Running Application Server Control only when you need it can free up memory for other components.

• Configure Application Server Control so that it can manage multiple instances. Refer to Oracle Application Server Administrator's Guide for details.

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

Table 4-4 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 your system meets these requirements and any additional requirements for installing Oracle Application Server.

http://www.redhat.com

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, follow these steps:

1. Log in as the root user.

2. To determine which distribution and version of Linux is installed, run 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, 4.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, errata 49 is installed and all the required software packages are installed.

4. To determine which version of the Linux kernel is installed, run 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. If necessary, refer to your operating system documentation for information on upgrading the kernel.

   For more information on Red Hat patches, refer to:

   http://www.redhat.com
   
   

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

   # rpm -q package_name
   
   

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

   # rpm -i package_name
   
   

   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 
   
   

4.3.2 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems

Table 4-5 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.

http://www.redhat.com

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
gnome-libs-devel-1.4.1.2.90-34.1
sysstat-4.0.7-4.EL3.3
compat-db-4.0.14-5

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.

2. To determine which distribution and version of Linux is installed, run the following command:

   # cat /etc/issue
   Red Hat Enterprise Linux AS release 3 (Taroon) 
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0, 4.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, run a command similar to the following:

   # rpm -q package_name
   
   

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

   # rpm -i package_name
   
   

   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
   
   

4.3.3 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems

Table 4-5 lists the software requirements for Red Hat Enterprise Linux AS/ES 4.0. 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.4-2.9
glibc-common-2.3.4-2.9
binutils-2.15.92.0.2-13
compat-libstdc++-296-2.96-132.7.2
gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
openmotif21-2.1.30-11.RHEL4.4
pdksh-5.2.14-30
setarch-1.6-1
make-3.80-5
gnome-libs-1.4.1.2.90-44.1
sysstat-5.0.5-1
compat-db-4.1.25-9
control-center-2.8.0-12
xscreensaver-4.18-5.rhel4.2

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, run the following command:

   # cat /etc/issue
   Red Hat Enterprise Linux AS release 4 (Nahant Update 1)
   
   
   

3. To check that Update 1 is installed:

   # cat /etc/redhat-release
   Red Hat Enterprise Linux AS release 4 (Nahant Update 1)
   
   

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

   # rpm -q package_name
   
   

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

   # rpm -i package_name
   
   

   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
   
   

4.3.4 Software Requirements for SUSE Linux Enterprise Server 8 Systems

Table 4-7 lists the software requirements for SUSE Linux Enterprise Server 8 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.

http://www.suse.com

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, follow these steps:

1. Log in as the root user.

2. To determine which distribution and version of Linux is installed, run the following command:

   prompt> 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, 4.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 determine the service pack version, run the following command:

   prompt> uname -r
   k_smp-2.4.21-138
   
   

   If the kernel version contains the string 2.4.21, 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, run a command similar to the following:

   prompt> rpm -q package_name
   
   

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

   prompt> rpm -i package_name
   
   

   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 
   
   

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

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

   prompt> ln -sf /bin/fuser /sbin/fuser
   
   

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

   1. Run 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 into the oracle user account for the changes to take effect.

8. If any Java packages are installed on the system, 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 make sure 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 10g (console)

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

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

   If necessary, remove entries from the /etc/services file and restart the system. 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 . Run the script as the root user. This script is also available as patch 3167528. This patch is available from:

   http://metalink.oracle.com
   
   

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

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

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

       hostname.domainname broadcast 
       
       

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

       hosts: files nis dns 
       
       

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

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

    http://metalink.oracle.com
    

4.3.5 Software Requirements for SUSE Linux Enterprise Server 9 Systems

Table 4-8 lists the software requirements for SUSE Linux Enterprise Server 9 systems. The procedure after the table describes how to ensure that the system meets these requirements and any additional installation requirements.

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 

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-c++-3.3.3-43.24.x86_64.rpm
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
openmotif21-libs-2.1.30MLI4-119.1

# 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, run the following command:

   prompt> cat /etc/issue
   Welcome to SuSE Linux 9.0 (i686) - Kernel \r (\l).
   
   

   
   

   Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0, and 4.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 determine the kernel version, run the following command:

   prompt> uname -r
   kernel-bigsmp-2.6.5-7.97
   
   

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

   prompt> rpm -q package_name
   
   

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

   prompt> rpm -i package_name
   
   

   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 
   
   

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

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

   prompt> ln -sf /bin/fuser /sbin/fuser
   
   

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

   1. Run 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 into the oracle user account for the changes to take effect.

8. If any Java packages are installed on the system, 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 make sure 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 10g (console)

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

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

   If necessary, removDVDe entries from the /etc/services file and restart the system. 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 from:

   http://metalink.oracle.com
   
   

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

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

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

       hostname.domainname broadcast 
       
       

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

       hosts: files nis dns 
       
       

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

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

    http://metalink.oracle.com
    
    

4.3.6 Certification on Linux x86-64

Oracle Application Server 10g Release 2 (10.1.2) is certified to run as a 32-bit application on the following Linux x86-64 platforms:

• Section 4.3.6.1, "Red Hat Enterprise Linux AS/ES 3.0, Update 3 or higher (AMD64 / Intel EM64T)"

• Section 4.3.6.2, "SUSE LINUX Enterprise Server 9 (AMD64 / Intel EM64T)"

4.4.1 Kernel Parameter Settings for OracleAS Web Cache

This section applies if you are installing OracleAS Web Cache:

• If you are installing the J2EE and Web Cache middle tier, the OracleAS Web Cache component is optional.

• If you are installing the Portal and Wireless middle tier, the OracleAS Web Cache component is always installed.

Complete the following tasks to set the kernel parameters for OracleAS Web Cache:

1. Run the following command to check that the nofile kernel parameter is set to at least 65536:

   prompt> ulimit -Hn
   
   

2. If the command returns a value less than 65536, add this line to the /etc/security/limits.conf file (use a text editor to edit the file):

   *       hard    nofile  65536
   
   

   You need to be the root user to edit the /etc/security/limits.conf file.

3. Restart the computer for the new value to take effect.

4.4.2 Kernel Parameter Settings for OracleAS Metadata Repository

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. Run 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 from 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 = 4096
      # semaphores: semmsl, semmns, semopm, semmni
      kernel.sem = 256 32000 100 142
      fs.file-max = 131072
      net.ipv4.ip_local_port_range = 10000 65000
      kernel.msgmni = 2878 
      kernel.msgmax = 8192 
      kernel.msgmnb = 65535
      
      

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

   2. Run 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 run this command again.

   3. On SUSE Linux Enterprise Server only, run the following command to cause the system to read the /etc/sysctl.conf file when it restarts:

      # chkconfig boot.sysctl on
      
      

4.6.1 Checking If a Port Is in Use

To check if a port is being used, you can run the netstat command as follows:

prompt> netstat -an | grep portnum

4.6.2 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. Refer to Appendix C, "Default Port Numbers" for a list of the default port 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.

4.6.3 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.6.3.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. In the installer, on the Specify Port Configuration Options screen, select Manual and enter the full path to the staticports.ini file.

   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
Java Object Cache port = port_num
DCM Java Object Cache port = port_num
DCM Discovery 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
ASG port = port_num

# Business Intelligence and Forms
Reports Services SQL*Net port = port_num
Reports Services discoveryService port = port_num
Reports Services bridge 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
Ultra Search HTTP port number = port_num

4.6.3.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 "Figure 4-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server"

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 "Figure 4-2 Configuring Only Oracle HTTP Server"

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.6.4 If Port 1521 Is in Use

The installer configures port 1521 for the OracleAS Metadata Repository listener (version 10.1.0.3). 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 Oracle database listener or some other application, you might have to take some action before running the installer. Refer to the following sections for details.

• Section 4.6.4.1, "If Port 1521 Is In Use by an Existing Oracle Database"

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

prompt> $ORACLE_HOME/bin/lsnrctl VERSION

prompt> lsnrctl VERSION
LSNRCTL for UNIX: Version 10.1.0.4.2 - Production on 12-JUL-2005 16:08:16

Copyright (c) 1991, 2004, Oracle Corporation.  All rights reserved.

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

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

4.7.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 (refer to Table 4-11). You can enter the same operating system group for both fields.

4.9.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 - parameter (su - user).

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

4.9.2 ORACLE_HOME and ORACLE_SID

These environment variables must not be set.

4.9.3 PATH, CLASSPATH, and Shared Library Path Environment Variables

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

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

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

For information about obtaining and installing XVFB or other virtual frame buffer solutions, search for "frame buffer" on the Oracle Technology Network site. You can access the site at:

http://www.oracle.com/technology

4.9.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 Table 4-2.

Example (C shell):

% setenv TMP /tmp2
% setenv TMPDIR /tmp2

Example (Bourne or Korn shell):

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

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.

4.9.6 TNS_ADMIN

This section describes two requirements:

• The TNS_ADMIN environment variable must not be set. If set, it can cause errors during installation. Section G.2.11, "Database Configuration Assistant (DBCA) Failures" shows such an error.

• 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 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.9.7 ORA_NLS

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

Example:

$ unset ORA_NLS

4.9.8 LD_BIND_NOW

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

Example:

$ unset LD_BIND_NOW

4.10.1 Location of the Default Oracle Identity Management Realm

The installer reads the hosts file to construct the location of the default Oracle 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 Oracle 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 hosts file contains:

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

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

4.10.2 Hostname for OracleAS Single Sign-On

If you are installing OracleAS Single Sign-On, and your 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 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 hosts. For example:

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

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

4.11.2 Installing on Multihomed (Multi-IP) Computers

You can install Oracle Database on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a hostname; additionally, you can set up aliases for the hostname. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the hostname. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the /etc/hosts file.

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

4.11.3 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 4.11.4, "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 4-3).

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 4-2).

To Copy the CD-ROMs:

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

   You need to create a parent directory (called OracleAS_10g 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 4-3 Directory Structure for Copying CD-ROMs to Disk

   
   Description of "Figure 4-3 Directory Structure for Copying CD-ROMs to Disk"
   
   

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 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 Copy the application_server Directory from the DVD

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
   
   

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

4.11.4 Installing from a Remote CD-ROM or DVD Drive

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.8, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 4.9, "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.19, "Starting Oracle Universal Installer".

4.11.5 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.8, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 4.9, "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.19, "Starting Oracle Universal Installer".

4.11.6 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 these 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

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

http://www.oracle.com/technology

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

Description of "Figure 4-4 Run Oracle Application Server Only on the Computer Where It Is Installed"

4.11.8 Support for NIS and NIS+

You can install and run Oracle Application Server in NIS and NIS+ environments.