Skip Headers

Oracle® Application Server 10g Installation Guide
10g (9.0.4) for Solaris Operating System (SPARC)
Part No. B10427-01
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

4 Requirements

Before installing Oracle Application Server, ensure that your computer meets the requirements described in this chapter.

Contents of this chapter:

4.1 System Requirements

Table 4-1 lists the system requirements for running Oracle Application Server. The installer checks many of the requirements at the start of the installation process and warns you if any of them is not met. To save time, you can manually check only the remaining requirements. Refer to Table 4-1 to see which requirements are not checked by the installer.

You can also run the system checks performed by the installer without doing an installation, by running the runInstaller command as shown. The runInstaller command is on the Oracle Application Server CD-ROM (Disk 1) or DVD (in the application_server directory).

CD-ROM:

prompt> mount_point/904disk1/runInstaller -executeSysPrereqs

DVD:

prompt> mount_point/application_server/runInstaller -executeSysPrereqs

The results are displayed on the screen as well as written to a log file. For more information on the types of checks performed, see Section 4.12, "Prerequisite Checks Performed by the Installer".

Table 4-1 System Requirements

Item Requirement Checked by Installer
Operating system
  • Solaris 8
  • Solaris 9

See Section 4.2, "Operating System Patches" for a list of required patches.

Yes
IP The computer’s IP address must be static. Oracle Application Server does not support computers using Solaris DHCP.

DHCP is supported on Linux and Microsoft Windows.

No
Processor Type The processor must have a SPARC v9 architecture. This is because Oracle Application Server 10g (9.0.4) uses the Sun Java 1.4.1 HotSpot Server VM, which no longer supports SPARC v8 and older processors. No
Processor Speed 300 MHz or greater (450 MHz recommended). Oracle recommends a multiple CPU computer.

To determine the processor speed, run the psrinfo command with the -v option:

prompt> /usr/sbin/psrinfo -v
Status of processor 0 as of: 02/10/03 13:21:20
  Processor has been on-line since 02/04/03 15:45:07.
  The sparc processor operates at 450 MHz,
        and has a sparc floating point processor.
Yes
Memory The memory requirements provided for the various installation types represents enough physical memory to install and run Oracle Application Server. However, for most production sites, you should configure at least 1 GB of physical memory. For sites with substantial traffic, increasing the amount of memory further may improve your performance. For Java applications, you should either increase the maximum heap allocated to the OC4J processes, or configure additional OC4J processes to utilize this memory. See the Oracle Application Server 10g Performance Guide for details.

In determining the optimal amount of memory for your installation, the best practice is to load test your site. Resource requirements can vary substantially for different applications and different usage patterns. In addition, some operating system utilities for monitoring memory can overstate memory usage (partially due to the representation of shared memory). The preferred method for determining memory requirements is to monitor the improvement in performance resulting from the addition of physical memory in your load test. Refer to your platform vendor documentation for information on how to configure memory and processor resources for testing purposes.

OracleAS Infrastructure 10g:

  • OracleAS Metadata Repository and Identity Management: 1 GB

  • Identity Management only: 512 MB

  • OracleAS Metadata Repository only: 750 MB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 512 MB

  • Portal and Wireless: 1 GB

  • Business Intelligence and Forms: 1 GB

OracleAS Developer Kits 10g: 256 MB, but 512 MB recommended

To determine the amount of memory, use the prtconf command:

prompt> /usr/sbin/prtconf | grep Memory

Note: These values assume you are running only one Oracle Application Server instance per computer. If you plan to run multiple instances on the same computer, see Section 4.1.1, "Memory Requirements for Running Multiple Instances on the Same Computer".

If you do not meet the memory requirements, the installer displays a warning. The installer allows you to dismiss the warning and continue because you might configure some but not all components and thus require less memory. However, you should test your site to ensure that you do have sufficient memory.

Yes
Disk space OracleAS Infrastructure 10g: 2.6 GB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 450 MB

  • Portal and Wireless: 975 MB

  • Business Intelligence and Forms: 1.5 GB

OracleAS Developer Kits 10g: 520 MB

To determine the amount of free disk space, use the df command:

prompt> df -k dir

Replace dir with the directory where you plan to install Oracle Application Server or with the parent directory if the directory does not exist yet. For example, if you plan to install Oracle Application Server in /opt/oracle/infra, replace dir with /opt/oracle or /opt/oracle/infra.

No
Space in /tmp directory 150 MB

To determine the amount of free space in the /tmp directory, use the df command:

prompt> df -k /tmp

If the /tmp directory does not have enough free space, you can specify a different directory by setting the TMP environment variable. See Section 4.8.5, "TMP" for details.

Yes
Swap space 1.5 GB or greater of available swap space

To determine the amount of available swap space, use the swap command:

prompt> /usr/sbin/swap -l

The value in the "free" column indicates the number of free blocks, where a block is 512 bytes. To convert blocks to KB, divide the number by 2. For example, 2,000,000 free blocks is equivalent to 1,000,000 KB.

If you do not have enough swap space, perform the following tasks:

  1. Log in as the root user, and create an empty swap file:

    prompt> su
    Password: root_user_password
    # mkfile sizem swap_file_name
    
    

    Append an "m" to the size to specify the size in megabytes (example: 900m). The minimum size of this file must be greater than the difference between the currently available swap space and required swap space. For example, if you have 100 MB of free swap space, then this swap file must be at least 1400 MB.

  2. Add the file to the swap space using the following command:

    # /usr/sbin/swap -a swap_file_name
    
    
  3. Add a line to /etc/vfstab file. If you do not add the line, the new swap space will not persist when you reboot the computer.

    /path/to/swap/file   -   -   swap   -   no   -
    
    

    Replace /path/to/swap/file with the location of the swap file.

  4. Verify the new swap space size:

    prompt> /usr/sbin/swap -l
    
Yes
Monitor 256 color display

To determine your monitor’s display capabilities:

  1. Check that the DISPLAY environment variable is set properly. See Section 4.8.4, "DISPLAY" for details. To test, see if you are able to run /usr/openwin/bin/xclock.

  2. Run the xwininfo command.

    prompt> /usr/openwin/bin/xwininfo
    
    

    Look for the "Depth" line. You need a depth of at least 8 (bits per pixel).

Yes
Supported browsers The following browsers are supported:
  • Microsoft Internet Explorer 5.5, 6.0 and higher

  • Netscape 4.78, 4.79, 7 and higher

  • Mozilla 1.3.1 and higher

However, Oracle Enterprise Manager is optimized for the following browsers:

  • Microsoft Internet Explorer 5.5, 6.0 and higher

  • Netscape 7 and higher

  • Mozilla 1.3.1 and higher

For the most current list of supported browsers, check the OracleMetaLink site (http://metalink.oracle.com).

No

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

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.

Table 4-2 Memory Requirements for Multiple Instances on the Same Computer

Description Memory Required
OracleAS Infrastructure 10g plus J2EE and Web Cache 1 GB
OracleAS Infrastructure 10g plus Portal and Wireless 1.5 GB
OracleAS Infrastructure 10g plus Business Intelligence and Forms 1.5 GB

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 Operating System Patches

Table 4-3 lists the Solaris operating system patches that you must install before installing. You can download the patches from:

http://sunsolve.sun.com

Refer to the README file included with any patch for instructions on installing it.

You can fulfill all the patch requirements by installing the J2SE patch cluster along with the domain name patch (112138-01 or greater).


Note:

Although the patches listed in Table 4-3 are current at the time of publication, Sun Microsystems, Inc. often updates the list of required patches for J2SE. Click the "Readme" link on the following URL for the most current list of patches: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE

Table 4-3 Required Patches for Solaris Operating Systems

Operating System Patches Required
Solaris 8
  • 108652-74 or higher: X11 6.4.1: Xsun patch
  • 108921-17 or higher: CDE 1.4: dtwm patch

  • 108940-57 or higher: Motif 1.2.7 and 2.1.1: Runtime library patch

  • 112003-03 or higher: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15

  • 108773-18 or higher: IIIM and X input and output method patch

  • 111310-01 or higher: /usr/lib/libdhcpagent.so.1 patch

  • 109147-26 or higher: Linker patch

  • 111308-04 or higher: /usr/lib/libmtmalloc.so.1 patch

  • 112438-02 or higher: /kernel/drv/random patch

  • 108434-13 or higher: 32-bit shared library patch for C++

  • 111111-03 or higher: /usr/bin/nawk patch

  • 112396-02 or higher: /usr/bin/fgrep patch

  • 110386-03 or higher: RBAC feature patch

  • 111023-02 or higher: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch

  • 108987-13 or higher: Patch for patchadd and patchrm

  • 108528-24 or higher: Kernel update patch

  • 108989-02 or higher: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch

  • 108993-26 or higher: LDAP2 client, libc, libthread and libnsl libraries patch

  • 112138-01 or higher: usr/bin/domainname patch

Solaris 9
  • 113096-03 or higher: X11 6.6.1: OWconfig patch
  • 112785-26 or higher: X11 6.6.1: Xsun patch



How to Get a List of Operating System Patches Installed on Your Computer

Follow this procedure to determine which patches are installed on your computer:

  1. Run the showrev command with the -p option. The following command saves the sorted output to a file called patchList.

    prompt> showrev -p | sort > patchList
    
    
  2. Open the file in a text editor, such as vi or emacs, and search for patch numbers.


How the Installer Checks for Operating System Patches

The installer searches for the required patch versions on your computer. If it does not find an exact match, it displays a warning message in the shell where you started the installer.

CD-ROM: prompt> mount_point/904disk1/runInstaller
DVD:    prompt> mount_point/application_server/runInstaller
...
Some optional pre-requisite checks have failed. Continue? (y/n) [n] n

The installer gives you a choice to exit or continue.

Type n to exit the installer if you do not have all the patches. You can then download and install the patches.

Type y to continue only if you are sure all required patches are installed.

4.3 Operating System Packages

Check that your computer contains the following operating system packages. If the packages are not present, the installer cannot continue.

The last two packages (SUNWi1cs and SUNWi15cs) are required for the ISO8859-1 and ISO8859-15 codesets.

To check if an operating system package is installed on your computer, run the pkginfo command with the name of the package. The syntax for running pkginfo is:

pkginfo package_name1 package_name2 ...

For example, to check if all of the listed packages are installed on your computer, run the following command:

prompt> pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt SUNWi1cs SUNWi15cs

If your computer is missing a package, contact your system administrator.

4.4 Kernel Parameters

Check that the kernel parameters are set to the minimum values shown in Table 4-4. The kernel parameter values are stored in the /etc/system file on your computer.

If your /etc/system file does not specify the parameters, you have to add lines to the file to specify them. The lines for the parameters are shown in Table 4-4.


Notes:

  • The values for kernel parameters are required only for computers that will be running the OracleAS Metadata Repository. The installer checks the kernel parameter values only if you are installing the OracleAS Metadata Repository.

  • If any kernel parameter values do not meet the requirements, the installer displays an error message. You will not be able to continue the installation until you update the kernel parameters to the required values.

  • If you update kernel parameter values, you need to reboot your computer for the new values to take effect.


Table 4-4 Values for Kernel Parameters

Parameter Line in /etc/system showing minimum value Description
semmni set semsys:seminfo_semmni=100 Defines the maximum number of semaphore sets in the entire system.
semmns set semsys:seminfo_semmns=256 Defines the maximum semaphores on the system. This setting is a minimum recommended value, for initial installation only.

The semmns parameter should be set to the sum of the processes parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database.

semmsl set semsys:seminfo_semmsl=256 Defines the minimum recommended value, for initial installation only.
shmmax set shmsys:seminfo_shmmax=4294967295 Defines the maximum allowable size of one shared memory segment (4 GB = 4294967295).
shmmin set shmsys:seminfo_shmmin=1 Defines the minimum allowable size of a single shared memory segment.

Note: This parameter is not used in Solaris 9.

shmmni set shmsys:seminfo_shmmni=100 Defines the maximum number of shared memory segments in the entire system.
shmseg set shmsys:seminfo_shmseg=10 Defines the maximum number of shared memory segments one process can attach.

Note: This parameter is not used in Solaris 9.


To add or update kernel parameter values:

  1. Become root user on the computer where you need to change the values.

  2. Make a backup copy of the /etc/system file. For example, the following command makes a backup copy called system.back.

    # cp /etc/system /etc/system.back
    
    
  3. Using a text editor such as vi or emacs, update the values or add new lines in the /etc/system file as necessary. For example, the following lines show sample values for the parameters:

    set semsys:seminfo_semmni=300
    set semsys:seminfo_semmns=800
    set semsys:seminfo_semmsl=256
    set shmsys:shminfo_shmmax=4294967295
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=512
    set shmsys:shminfo_shmseg=150
    
    

    Tip:

    The comment character for the /etc/system file is the asterisk (*), not #.

  4. Restart the computer for the new values to take effect.

4.5 Ports

Many Oracle Application Server components, such as Oracle HTTP Server, OracleAS Web Cache, and Oracle Enterprise Manager, use ports. You can have the installer assign default port numbers, or use port numbers that you specify.

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


Tip:

The installer will not assign port numbers that are specified in the /etc/services file. If you do not want the installer to assign a specific port number, add the port number to the /etc/services file. For example, if you want to reserve port 7777 for an application, you can add something like the following line to /etc/services:
myApplication      7777/tcp

The installer will not assign port 7777 to any component if this line exists in the /etc/services file.



Note:

In the default configuration of the Solaris operating system, the /etc/services file includes ports 389 and 636 (for LDAP and LDAP/SSL). These happen to be the default ports for Oracle Internet Directory. This means that if you want to use these port numbers for Oracle Internet Directory, you must either delete or comment out these lines in the /etc/services file. To comment out a line, add a # at the beginning of the line, as shown:
# 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)

If you do not comment out or remove the lines from /etc/services, then the installer will not assign ports 389 and 636. It assigns a number from the port number range for Oracle Internet Directory. See Appendix E, " Default Port Numbers" for a list of default port numbers.


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

4.5.2.1 Format of the staticports.ini File

The staticports.ini file has the following format. Replace port_num with the port number that you want to use for the component.

# 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

The easiest way to create the file is to use the staticports.ini file on the CD-ROM (Disk 1) or DVD as a template:

  1. Copy the staticports.ini file from the CD-ROM or DVD to your hard disk.

    Table 4-6 Location of the staticports.ini File on CD-ROM and DVD

    Media Location of staticports.ini File
    CD-ROM Disk 1: mount_point/904disk1/stage/Response/staticports.ini
    DVD mount_point/application_server/stage/Response/staticports.ini

  2. Edit the local copy (the file on the hard disk) to include the desired port numbers.

    You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.

    You cannot change the port used by the OracleAS Metadata Repository (port 1521) during installation, but you can do so after installation. See the Oracle Application Server 10g Administrator's Guide for details.

    The following example sets the Application Server Control port and the some ports for OracleAS Web Cache. For components not specified, the installer will assign the default port numbers.

    Application Server Control port = 2000
    Web Cache Administration port = 2001
    Web Cache Invalidation port = 2002
    Web Cache Statistics port = 2003
    
    

    When installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to see the assigned ports.


Notes on Choosing Port Numbers:

  • Port numbers cannot be greater than 65536.

  • If you use a port number less than 1024 for a component, you must run the component as the root user.

  • If you use a port number less than 1024 for a component, the installer will not be able to start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details.

  • You still have to comment out ports 389 and 636 in the /etc/services file if you want to use these port numbers for Oracle Internet Directory. See the Note for details.

  • If you plan to set port numbers for Oracle HTTP Server and OracleAS Web Cache, be sure you read Section 4.5.2.3, "Ports for Oracle HTTP Server and OracleAS Web Cache".


The installer verifies that the ports specified in the file are available by checking memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.

If the installer detects that a specified port is not available, it displays an alert. The installer will not assign a port that is not available. To fix this:

  1. Edit the staticports.ini file to specify a different port, or shut down the application that is using the port.

  2. Click Retry. The installer re-reads the staticports.ini file and verifies the entries in the file again.


Tip:

The staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after an Oracle Application Server installation. If you have installed Oracle Application Server and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

4.5.2.2 Error Conditions That Will Cause the Installer to Use Default Ports Instead of Specified Ports

Check your staticports.ini file carefully because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:

  • If you specify the same port for more than one component, the installer will use the specified port for the first component, but for the other components, it will use the components’ default ports. The installer does not warn you if you have specified the same port for multiple components.

  • If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.

  • If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case sensitive. The installer does not display a warning for lines with unrecognized names.

  • If you specify a non-numeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.

  • If you misspell the parameter on the command line, the installer does not display a warning. It continues and assigns default ports to all components.

  • If you specify a relative path to the staticports.ini file (for example, "./staticports.ini") on the command line, the installer will not find the file. The installer continues without displaying a warning and it will assign default ports to all components. You must specify a full path to the staticports.ini file.

  • If the parameter you specify on the command line does not match the installation type that you are performing (for example, if you specify the parameter for middle tier but you are installing the infrastructure), the installer does not give a warning. It continues and assigns default ports to all components.

4.5.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 ports_wc.gif follows
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 ports_no_wc.gif follows
Description of the illustration ports_no_wc.gif

4.5.2.4 Examples

This section describes some common scenarios for using staticports.ini.

4.5.2.4.1 Configure Oracle HTTP Server to Use Ports 80 and 443 With OracleAS Web Cache as the Front-End

In this scenario, create a staticports.ini file that includes the following lines:

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

The ports for Oracle HTTP Server Listen and SSL Listen can be any available port. The example uses ports 81 and 444. These port numbers do not have to be less than 1024. If you select port numbers less than 1024, you have to start up Oracle HTTP Server and OracleAS Web Cache as the root user.


Note:

Because you are using ports less than 1024, you have to configure Oracle HTTP Server and OracleAS Web Cache to run as the root user. You can perform the configuration during installation or after installation.
  • If you want to do the configuration during installation, you must follow the steps listed in Section 7.17, "Install Fragment: The Last Few Screens of the Installation" after running root.sh but before clicking OK. You run root.sh near the end of the installation.

  • You can choose to perform the configuration after installation, but note that the installer will not be able to start up the components (because they are not yet configured).

For details, see these guides: Oracle HTTP Server Administrator's Guide and Oracle Application Server Web Cache Administrator's Guide.


4.5.2.4.2 Configure Oracle HTTP Server to Use Ports 80 and 443 Without OracleAS Web Cache

In this scenario, create a staticports.ini file that includes the following lines:

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


Note:

Because you are using ports less than 1024, you have to configure Oracle HTTP Server to run as the root user. See the Note for details.

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


Note:

If your computer has a listener that uses the IPC protocol with the EXTPROC key, you should change the key to have some other value. This is because the OracleAS Metadata Repository listener requires access to the EXTPROC key.

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.

4.5.3.1 If Port 1521 Is In Use by an Existing Oracle9i Database

If you are installing a new database for the OracleAS Metadata Repository on a computer that is already running an Oracle9i database, ensure that the listeners for both databases do not conflict.

You might be able to use the same listener for both the existing database and the OracleAS Metadata Repository database. You have to consider the version of the existing listener as well as the port number. Table 4-7 shows scenarios and outcomes.

You can change the OracleAS Metadata Repository listener to use a different port after installation. See the Oracle Application Server 10g Administrator's Guide for details.

Table 4-7 Scenarios and Outcomes if You Have an Existing Database on the Computer Where You Want to Install the OracleAS Metadata Repository

Version of the Existing Listener Existing Listener Uses Port 1521 Existing Listener Uses a Port Other Than 1521
Earlier than 9.0.1 The OracleAS Metadata Repository listener supports both the existing database and the OracleAS Metadata Repository.

See Section 4.5.3.1.1, "Scenario 1: Existing Listener Uses Port 1521 and Listener Version Is Earlier Than 9.0.1".

You will end up with two listeners.

See Section 4.5.3.1.3, "Scenario 3: Existing Listener Uses a Port Other Than 1521".

9.0.1 or later The existing listener supports both the existing database and the OracleAS Metadata Repository.

See Section 4.5.3.1.2, "Scenario 2: Existing Listener Uses Port 1521 and Listener Version Is 9.0.1 or Later"

You will end up with two listeners.

See Section 4.5.3.1.3, "Scenario 3: Existing Listener Uses a Port Other Than 1521".


To check the listener version, run the following command:

prompt> $ORACLE_HOME/bin/lsnrctl VERSION

where ORACLE_HOME is the home directory for your database.

You can also use the same command to check the listener port.

Here is an example of the command’s output:

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

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

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

4.5.3.1.1 Scenario 1: Existing Listener Uses Port 1521 and Listener Version Is Earlier Than 9.0.1

Listeners earlier than version 9.0.1 are incompatible with the OracleAS Metadata Repository. What you can do is to install the OracleAS Metadata Repository, which installs a version 9.0.1.5 listener, and use this new listener for both databases.

  1. Stop the existing listener before you install the OracleAS Metadata Repository.

    prompt> $ORACLE_HOME/bin/lsnrctl stop
    
    

    ORACLE_HOME is the home directory for your existing database.

    If you do not stop the existing listener, the installation will fail.

  2. Install the OracleAS Metadata Repository.

    See any of the procedures that install an OracleAS Metadata Repository in Chapter 6, " InstallingOracleAS Infrastructure 10g" (for example, Section 6.17, "Installing OracleAS Infrastructure 10g" or Section 6.18, "Installing OracleAS Infrastructure 10g Against an Existing Oracle Internet Directory").

  3. Update the configuration file of the new listener, as necessary. The name of the listener configuration file is listener.ora, located in the ORACLE_HOME/network/admin directory.

    1. Check network address entries in the existing listener’s configuration file.

      If the existing listener’s configuration file contains only the following network addresses:

      • TCP Port 1521

      • IPC key EXTPROC

      you do not have to edit the version 9.0.1.5 listener’s configuration file for network addresses.

      If the configuration file contains other network addresses, you need to add them to the new listener’s configuration file.

    2. Check SID_DESC entries in the existing listener’s configuration file.

      If the existing listener’s configuration file contains SID_DESC entries for the existing database, you need to add these entries to the new listener’s configuration file.

    3. Do not start the existing listener (version earlier than 9.0.1). Now that the new listener supports both databases, you do not need to run the existing listener any more.


Note:

Step c above is very important. You only need to run one listener (the new listener) to support both databases.

4.5.3.1.2 Scenario 2: Existing Listener Uses Port 1521 and Listener Version Is 9.0.1 or Later

The existing listener will support both the existing database and the OracleAS Metadata Repository. The installer will perform this configuration automatically. You do not have to do anything.

The existing listener must be stopped during installation.

4.5.3.1.3 Scenario 3: Existing Listener Uses a Port Other Than 1521

You will end up running two listeners: one for the existing database and one for the OracleAS Metadata Repository, regardless of the version of the existing listener.

The existing listener can be running during installation, because it is not using port 1521.

4.5.3.2 If Port 1521 Is In Use by Some Other Application

If you have some other application listening on port 1521, you need to reconfigure it to listen on a different port. If that is not possible, shut it down while you install the OracleAS Metadata Repository. After installation, you can reconfigure the OracleAS Metadata Repository to use a port other than 1521. See the Oracle Application Server 10g Administrator's Guide for instructions on how to do this.

4.6 Operating System Groups

You need to create operating system groups in these situations:

To create a local operating system group, use the Solaris Management Console:

  1. Set the DISPLAY environment variable to point to the monitor where you want the Solaris Management Console window to appear. See Section 4.8.4, "DISPLAY" if you need help setting the environment variable.

  2. Start up the Solaris Management Console.

    prompt> /usr/sadm/bin/smc
    
    
  3. In the left frame, expand This Computer, then expand System Configuration.

  4. Click Users. This displays the Log In window.

  5. In the Log In window, log in as the root user.

  6. In the left frame, expand Users and select Groups.

  7. Select Action > Add Group.

  8. In Group Name, enter the name of the group.

  9. (optional) In Group ID Number, enter an ID number for the group.

    Group IDs are important if you are setting up an OracleAS Active Failover Cluster environment because you need to set up identical groups on each node. See Section 9.3.1.5, "Create Identical Users and Groups on All Nodes in the Cluster" for details.

  10. Click OK.

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

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

Table 4-8 Privileges for the OSOPER and OSDBA Groups

Group Description
OSDBA This is the database administrator group. Users in this group are granted SYSDBA privileges.
OSOPER Users in this group are granted SYSOPER privileges, which comprise privileges required for basic maintenance. These include database startup and shutdown, and other privileges required for database operation. SYSOPER privileges are a subset of SYSDBA 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-8). You can enter the same operating system group for both fields.

4.7 Operating System User

Create an operating system user to install and upgrade Oracle products. The operating system user running the installer must have write permission for these directories:

If the computer contains other Oracle products, you might already have a user for this purpose. Look in the /var/opt/oracle/oraInst.loc file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

If you do not already have a user for installing Oracle products, create a user with the following properties:

Table 4-9 Properties of the Operating System User Who Runs the Installer

Item Description
Login name You can use any name for the user. This guide refers to the user as the oracle user.
Group identifier The primary group of the oracle user must have write permission for the oraInventory directory. See Section 4.6.1, "Create a Group for the Inventory Directory" for more information about this group.

You can use any name for the group. This guide uses the name oinstall.

Home directory The home directory for the oracle user can be consistent with the home directories of other users.
Login shell The default login shell can be the C, Bourne, or Korn shell.


Note:

Use the oracle user only for installing and maintaining Oracle products. Never use it for purposes unrelated to the installer. Do not use root as the oracle user.

To create a local operating system user, use the Solaris Management Console:

  1. Set the DISPLAY environment variable to point to the monitor where you want the Solaris Management Console window to appear. See Section 4.8.4, "DISPLAY" if you need help setting the environment variable.

  2. Start up the Solaris Management Console.

    prompt> /usr/sadm/bin/smc
    
    
  3. In the left frame, expand This Computer, then expand System Configuration.

  4. Click Users. This displays the Log In window.

  5. In the Log In window, in User Name, enter root. In Password, enter the root password.

  6. In the left frame, expand Users and select User Accounts.

  7. Select Action > Add User > With Wizard.

  8. In User Name, enter the name of the user (oracle). The Full Name and Description fields are optional. Click Next.

  9. In User ID Number, accept the default value. Click Next.

  10. Select User Must Use This Password At First Login, and enter a password for the user. Click Next.

  11. In Primary Group, select the primary group for the user. This is the group you created earlier to own the inventory directory. See Section 4.6.1, "Create a Group for the Inventory Directory". Click Next.

  12. In Path, enter a home directory for the user. Click Next.

  13. Review the mail server information for the user and click Next.

  14. Review the user information and click Finish to create the user.

To check which groups an operating system user belongs to, run the groups command with the name of the user. For example:

prompt> groups oracle

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

4.8 Environment Variables

The operating system user who will be installing Oracle Application Server needs to set (or unset) the following environment variables. Table 4-10 summarizes whether you set or unset an environment variable.

Table 4-10 Environment Variable Summary

Environment variable Set or Unset
ORACLE_HOME and ORACLE_SID
Does not matter (the installer unsets these two environment variables).
PATH, CLASSPATH, and LD_LIBRARY_PATH
Must not contain references to directories in any Oracle home directories
DISPLAY
Set it to the monitor where you want to the installer window to appear.
TMP
Optional. If unset, defaults to /tmp.
TNS_ADMIN
Unset

4.8.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.8.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.8.3 PATH, CLASSPATH, and LD_LIBRARY_PATH

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

4.8.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.8.5 TMP

During installation, the installer needs to write temporary files to a "temporary" directory. By default, the "temporary" directory is /tmp.

If you want the installer to use a directory other than /tmp, set the TMP environment variable to the full path of an alternate directory. This directory must meet the requirements listed in Table 4-1.

Example (C shell):

% setenv TMP /tmp2

Example (Bourne or Korn shell):

$ TMP=/tmp2; export TMP

4.8.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.9 The /etc/hosts File

Although the /etc/hosts file affects these items:

the installer provides alternative methods for you to enter the values that you want without editing the /etc/hosts file. See the following subsections for details.

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


Tip:

If you need the /etc/hosts file to use a different format, you can edit the file to use the required format, perform the installation, then revert the file back to its original format after installation.

If you are unable, or unwilling, to edit the /etc/hosts file, you can always enter the desired value for the default Identity Management realm in the Custom Namespace field on the "Specify Namespace in Internet Directory" screen.


4.9.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.10 Network Topics

Typically, the computer on which you want to install Oracle Application Server is connected to the network, has local storage to contain the Oracle Application Server installation, has a display monitor, and has a CD-ROM or DVD-ROM drive.

This section describes how to install Oracle Application Server on computers that do not meet the typical scenario. It covers the following cases:

4.10.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.10.2 Installing on NFS-Mounted Storage

You cannot install and run Oracle Application Server on Sun machines with regular NFS. 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

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

4.10.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 nfs_multi_inst.gif follows
Description of the illustration nfs_multi_inst.gif

4.10.4 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; see Section 4.10.5, "Installing from a Remote CD-ROM or DVD Drive".)

Ensure that the computers on which you want to install Oracle Application Server can access the hard drive where you copied the CD-ROMs or DVD. 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 CD-ROMs. 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 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-1).


To Copy the Contents of the CD-ROMs:
  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 CD-ROM number.

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

    Description of copyToDisk.gif follows
    Description of the illustration copyToDisk.gif

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

    prompt> cp -pr /cdrom_mount_point/904disk1/* /path/to/hard/drive/Disk1/
    prompt> cp -pr /cdrom_mount_point/904disk2/* /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 Contents of the application_server Directory from the DVD

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.10.5 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, you can perform the installation from a remote CD-ROM or DVD drive. Check the following points:

  • You need to share the remote CD-ROM or DVD drive through NFS.

    On the remote computer (which has the CD-ROM or DVD drive):

    1. CD-ROM: Insert Oracle Application Server Disk 1 into the CD-ROM drive.

      DVD: Insert the Oracle Application Server DVD into the DVD drive.

    2. Share the CD-ROM or DVD drive.

      CD-ROM:

      prompt> su
      Password: root_password
      # share -F nfs -o ro /cdrom/904disk1
      
      

      The path /cdrom/904disk1 specifies the path to the CD-ROM in the CD-ROM drive. You can use any path you like.

      DVD:

      prompt> su
      Password: root_password
      # share -F nfs -o ro /cdrom
      
      

      The path /cdrom specifies the path to the DVD in the DVD drive. You can use any path you like.

    On the local computer, access the CD-ROM or DVD and run the installer as follows:

    CD-ROM:

    prompt> /net/remote_computer_hostname/cdrom/904disk1/runInstaller
    
    

    DVD:

    prompt> /net/remote_computer_hostname/cdrom/application_server/runInstaller
    
    

    Replace remote_computer_hostname with the name of the remote computer.

  • This bullet point, switching CD-ROMs, does not apply to DVDs.

    When the installer prompts you to switch CD-ROMs, you need to unshare the CD-ROM drive, eject the CD-ROM, insert the requested CD-ROM, and share the CD-ROM drive again. If you do not unshare, you will not be able to eject the CD-ROM.


    Note:

    The installer must be running when you are switching CD-ROMs. Do not exit the installer when switching CD-ROMs. If you exit the installer, it is unable to continue from where it left off. In addition, the partial installation that it created is not usable, and may need to be removed manually.

    On the remote computer (which has the CD-ROM drive):

    prompt> su
    Password: root_password
    # unshare /cdrom/904disk1
    # eject cdrom
    ... Remove the CD-ROM, and insert the CD-ROM requested by the installer (for
    ... example, Disk 2).
    ... Share the CD-ROM.
    # share -F nfs -o ro /cdrom/904disk2
    
    

4.10.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.7, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 4.8, "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 theOracle Universal Installer".


Note:

You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

4.10.7 Support for NIS and NIS+

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

4.11 Font Packages for Java

You may need different character settings for different locales. For Solaris Font Packages for Java, you always need both SUNWi1of and SUNWxwfnt font packages for all locales. You may need additional font packages depending on your locale. For a list of Solaris Font Packages, see:

http://java.sun.com/j2se/1.4.1/font-requirements.html

4.12 Prerequisite Checks Performed by the Installer

Table 4-11 lists the checks performed by the installer:

Table 4-11 Prerequisite Checks Performed by the Installer

Item Description
CPU The installer checks that the CPU meets the minimum speed requirement.
Operating system version See Table 4-1 for supported versions.
Operating system patches See Section 4.2, "Operating System Patches" for a list of required patches.
Operating system packages See Section 4.3, "Operating System Packages" for a list of required packages.
Operating system kernel parameters See Section 4.4, "Kernel Parameters" for a list of required kernel parameters.
Memory See Table 4-1 for recommended values.
Swap space See Table 4-1 for recommended values.
TMP space See Table 4-1 for recommended values.
Instance name The installer checks that the computer on which you are installing Oracle Application Server does not already have an instance of the same name.
Oracle home directory name The installer checks that the Oracle home directory name does not contain any spaces.
Path to Oracle home directory The installer checks that the path to the Oracle home directory is not longer than 127 characters.
Oracle home directory contents The installer checks that the Oracle home directory does not contain any files that might interfere with the installation.
Oracle home directory You should install Oracle Application Server in a new directory, unless you are expanding a middle tier (see Section 7.14, "Expanding a MiddleTier") or installing a middle tier in an Oracle home that contains Oracle Developer Suite 10g (9.0.4) (see Section 5.4, "Oracle Home Directory"). Here are some examples of installations that are not allowed:
  • Any type of Oracle Application Server into an 8.0, 8i, 9.0.1, or 9.2 database Oracle home

  • Any type of Oracle Application Server into an Oracle Management Service Oracle home

  • Any type of Oracle Application Server into an Oracle Collaboration Suite Oracle home

  • Any type of Oracle Application Server into an Oracle HTTP Server standalone Oracle home

  • Any type of Oracle Application Server into an OracleAS Web Cache standalone Oracle home

  • Any type of Oracle Application Server into an Oracle9i Developer Suite 9.0.2 Oracle home

  • Any type of Oracle Application Server into an Oracle Application Server Containers for J2EE standalone Oracle home

  • Any type of Oracle Application Server into an Oracle9iAS 1.0.2.2 Oracle home

  • Oracle Application Server middle tier into an infrastructure 9.0.2 or 10g (9.0.4) Oracle home

  • Oracle Application Server middle tier into an Oracle9iAS 9.0.2 or 9.0.3 middle tier Oracle home

  • OracleAS Developer Kits 10g into an infrastructure 9.0.2 or 10g (9.0.4) Oracle home

  • OracleAS Developer Kits 10g into an Oracle9iAS middle tier 9.0.2 or 9.0.3 Oracle home

  • OracleAS Developer Kits 10g into an Oracle Developer Suite 9.0.2 or 10g (9.0.4) Oracle home

  • OracleAS Infrastructure 10g into any Oracle9iAS 9.0.2 Oracle home

  • OracleAS Infrastructure 10g into an Oracle Application Server middle tier10g (9.0.4) or OracleAS Developer Kits 10g Oracle home

  • OracleAS Infrastructure 10g into an Oracle Developer Suite 9.0.2 or 10g (9.0.4) Oracle home

Port 1521 The installer displays a warning if port 1521 is in use by any application, including database listeners of any version. You need to stop the application that is using port 1521, then click Retry in the warning dialog.

If it is a database listener that is using port 1521, you might be able to use it for the metadata repository database. See Section 4.5.3, "If Port 1521 Is in Use" for details.

If it is another application that is using port 1521, you need to stop it or configure it to use a different port. Alternatively, you can change the database listener to use a port other than 1521, but you can do this only after installation. See the Oracle Application Server 10g Administrator's Guide for details.

Static port conflicts The installer checks the ports listed in the staticports.ini file, if specified. See Section 4.5, "Ports".
Monitor The installer checks that the monitor is configured to display at least 256 colors.
Display permission The installer checks that the user has permissions to display on the monitor specified by the DISPLAY environment variable.
DISPLAY environment variable The installer checks that the DISPLAY environment variable is set.
TNS_ADMIN environment variable The TNS_ADMIN environment variable must not be set.

There must not be a tnsnames.ora file in the /etc or /var/opt/oracle directories.

DBCA_RAW_CONFIG environment variable If you are installing the OracleAS Infrastructure 10g in a Real Application Clusters or OracleAS Active Failover Cluster environment, you need to set this environment variable to point to a file that describes the locations of your raw partitions.
Cluster file system The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS).
Oracle Enterprise Manager directories are writable The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:
  • ORACLE_HOME/sysman/emd

  • ORACLE_HOME/sysman/config

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config

Oracle Enterprise Manager files exist The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that these files exist:
  • ORACLE_HOME/sysman/config/iasadmin.properties

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml