Skip Headers

Oracle® Application Server Forms and Reports Services Installation Guide 10g Release 2 (10.1.2) for Solaris Operating System (SPARC) B16391-02 |
| Library | Product | Contents | Index

Previous | Next |

# 3 Requirements

Before installing Forms and Reports Services, ensure that your computer meets the requirements described in this chapter.

This chapter contains the following sections:

- System Requirements

- Operating System Patches

- Operating System Packages

- Kernel Parameters

- Ports

- Operating System Groups

- Operating System User

- Environment Variables

- The Hosts File

- Network Topics

- Prerequisite Checks Performed by the Installer

## 3.1 System Requirements

Table 3-1 lists the system requirements for installing Forms and Reports Services.

The installer checks many of these requirements at the start of the installation and displays a warning if any of the requirements is not met.

You can also run the system checks performed by the installer by running the `runInstaller` command. The `runInstaller` command is on the Forms and Reports Services CD-ROM (Disk 1) or DVD-ROM (in the `application_server` directory).

CD-ROM:

    prompt> mount_point/1012disk1/runInstaller -executeSysPrereqs

DVD-ROM:

    prompt> mount_point/application_server/runInstaller -executeSysPrereqs

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

You can also run the system checks performed by the installer by running the command. The command is on the Forms and Reports Services CD-ROM (Disk 1) or DVD-ROM (in the directory).

Table 3-1 System Requirements

Item | Requirement | Checked by Installer
--- | --- | ---
Operating system | Solaris 8 Solaris 9 See Section 3.2, "Operating System Patches" for a list of required patches. | Yes
IP | The computer's IP address must be static. Forms and Reports Services 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 uses the Sun Java 1.4.1 HotSpot Server VM, which no longer supports SPARC v8 and older processors. To determine the processor type, run the `psrinfo` command with the `-v` option. The output must show `sparcv9`:
    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 sparcv9 processor operates at 450 MHz,
            and has a sparcv9 floating point processor.
| 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 | 512 MB 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 Forms and Reports Services instance on each computer. If you do not meet the memory requirements, the installer displays a warning. The installer lets 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 have sufficient memory. | Yes
Disk space | 1 GB To determine the amount of free disk space, use the `df` command:
    prompt> df -k dir
Replace dir with the directory in which you plan to install Forms and Reports Services or with the parent directory if the directory does not exist yet. For example, if you plan to install Forms and Reports Services in `/opt/oracle/`, replace dir with `/opt/oracle` or `/opt/oracle/orasolfrs`. | No
Space in `/tmp` directory | 250 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 3.8.5, "TMP" for details. | Yes
Swap space | 640 MB or greater of available swap space To determine the amount of available swap space, use the `swap` command:
    prompt> /usr/sbin/swap -l
1. 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: Log on as the root user, and create an empty swap file:
       prompt> su
       Password: root_user_password
       # mkfile sizem swap_file_name
2. 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 540 MB. 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 does not persist when you restart the computer.
       /path/to/swap/file   -   -   swap   -   no   -
4. Replace /path/to/swap/file with the location of the swap file. Verify the new swap space size:
       prompt> /usr/sbin/swap -l
| Yes
2. Monitor | 256 color display To determine your monitor's display capabilities: Ensure that the `DISPLAY` environment variable is set properly. See Section 3.8.4, "DISPLAY" for details. To test, see if you are able to run `/usr/openwin/bin/xclock`. 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). Note: The `DISPLAY` environment variable is needed only by Oracle Universal Installer during the installation of Forms and Reports Services. It is not used by Oracle Forms and Oracle Reports. | Yes
Supported browsers | For the most current list of supported browsers, check the OracleMetaLink site (`http://metalink.oracle.com`). The following browsers are supported: Microsoft Internet Explorer 5.5, 6.0 and higher (supported on Microsoft Windows only) On Windows XP with SP2, use the Microsoft Internet Explorer 6.0.2900.2180.xpsp_sp2_rtm.040803-2158. This is the version packaged with SP2. Netscape 7.1, 7.2 Mozilla 1.5, Mozilla 1.7. You can download Mozilla from `http://www.mozilla.org`. Note that Firefox, the standalone Mozilla browser, is currently not certified. But check the OracleMetaLink site (`http://metalink.oracle.com`) for the most current list of certified browsers. Safari 1.2 (on Apple Macintosh computers) Adobe Acrobat Forms applications require a JVM running within a browser. The following browsers and JVM combinations are currently supported: Microsoft Internet Explorer 6.0 and higher with native JVM or JInitiator 1.3.1.13 and higher Netscape 4.7x, 7.0x and higher with JInitiator 1.3.1.13 and higher or Sun Java Plugin 1.4.1 and higher More browsers and JVMs will be certified over time. For the latest information on the browsers and JVMs certified for Forms, check Oracle Technology Network (OTN): (`http://otn.oracle.com/products/forms/htdocs/10g/clientsod_forms10g.html`) | No

Tips for Reducing/Fine Tuning Memory Usage

If you need to reduce memory consumption:

- After installation, use Oracle Enterprise Manager to stop services not used. This reduces the memory usage. For details, see the Oracle Application Server Administrator's Guide.

- For OracleAS Reports Services, you can control the JVM heap size by specifying small values using the `REPORTS_JVM_OPTIONS` environment variable.

  For Reports Engine, the JVM options are specified in the `server_name``.conf` file in the `jvmoptions` attribute of the `engine` element. If specified, the JVM options set in `server_name``.conf` override the value of the `REPORTS_JVM_OPTIONS` environment variable. If not specified in `server_name``.conf`, Oracle Reports uses the JVM options specified by the `REPORTS_JVM_OPTIONS` environment variable. For Reports Server, you can use the command line to specify the JVM options. For details about JVM option support, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.

## 3.2 Operating System Patches

Table 3-2 lists the Solaris operating system patches that you must install before installing Forms and Reports Services. You can download the patches from:

    http://sunsolve.sun.com

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

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 3-2 are current at the time of publication, Sun Microsystems, Inc. often updates the list of required patches for J2SE. Click the Readme link at the following URL for the most current list of patches: `http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE`

Table 3-2 Required Patches for Solaris Operating Systems

Operating System | Patches Required
--- | ---
Solaris 8 | 108652-82 or higher: X11 6.4.1: Xsun patch 108921-21 or higher: CDE 1.4: dtwm patch 108940-62 or higher: Motif 1.2.7 and 2.1.1: Runtime library patch 108773-18 or higher: IIIM and X input and output method patch 111310-01 or higher: /usr/lib/libdhcpagent.so.1 patch 109147-28 or higher: Linker patch 111308-04 or higher: /usr/lib/libmtmalloc.so.1 patch 112438-03 or higher: /kernel/drv/random patch 108434-17 or higher: 32-bit shared library patch for C++ 108435-17 or higher: 64-bit shared library patch for C++ 111111-04 or higher: /usr/bin/nawk patch 112396-02 or higher: /usr/bin/fgrep patch 110386-03 or higher: RBAC feature patch 111023-03 or higher: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch 111317-05 or higher: /sbin/init and /usr/sbin/init patch 113648-03 or higher: /usr/sbin/mount patch 115827-01 or higher: /sbin/sulogin and /sbin/netstrategy patch 116602-01 or higher: /sbin/uadmin and /sbin/hostconfig patch 108987-13 or higher: Patch for patchadd and patchrm 108528-29 or higher: Kernel update patch 108989-02 or higher: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch 108993-36 or higher: LDAP2 client, libc, libthread and libnsl libraries patch 109326-14 or higher: libresolv.so.2 and in.named patch 110615-11 or higher: sendmail patch
Solaris 9 | 113096-03 or higher: X11 6.6.1: OWconfig patch 112785-35 or higher: X11 6.6.1: Xsun patch

### 3.2.1 Installing a List of Operating System Patches on Your Computer

To determine the patches that 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.

### 3.2.2 Checking for Operating System Patches

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

    CD-ROM: prompt> mount_point/10.1.2disk1/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 that all the required patches are installed.

## 3.3 Operating System Packages

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

- `SUNWarc`

- `SUNWbtool`

- `SUNWhea`

- `SUNWlibm`

- `SUNWlibms`

- `SUNWsprot`

- `SUNWsprox`

- `SUNWtoo`

- `SUNWi1of` (the character after the `i` is the number `1`, not the letter `ell`)

- `SUNWxwfnt`

- `SUNWi1cs` (the character after the `i` is the number `1`, not the letter `ell`)

- `SUNWi15cs` (the character after the `i` is the number `1`, not the letter `ell`)

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

## 3.4 Kernel Parameters

The computers on which you plan to install Forms and Reports Services require their kernel parameters to be set to the minimum values shown in Table 3-3 and Table 3-4.

Kernel parameter values are stored in the `/etc/system` file. If your `/etc/system` file does not specify the parameters, you have to add lines to the file to specify them.

Notes: The values for kernel parameters are required only for computers that will be running the Oracle Application Server Metadata Repository or Oracle Application Server Web Cache. The installer checks the kernel parameter values only if you are installing these components. 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, restart your computer for the new values to take effect.

Table 3-3 Kernel Parameters Required by OracleAS Web Cache

Parameter | Line in /etc/system Showing the Minimum Value | Description
--- | --- | ---
`rlim_fd_max` | `set rlim_fd_max=65536` | Defines the hard limit on file descriptors that a single process can have open.

Table 3-4 Kernel Parameters Required by OracleAS Metadata Repository

Parameter | Line in /etc/system Showing the 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=1024` | Defines the maximum semaphores on the system. The 256 is only a minimum value for computers that will be running a single database (the OracleAS Metadata Repository that you are installing). If you are already running a database on the computer, see "To determine the minimum value for the semmns parameter" in Section 3.4, "Kernel Parameters".
`semmsl` | `set semsys:seminfo_semmsl=256` | Defines the minimum recommended value, for initial installation only.
`shmmax` | `set shmsys:shminfo_shmmax=4294967295` | Defines the maximum allowable size of one shared memory segment (4 GB = 4294967295).
`shmmin` | `set shmsys:shminfo_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:shminfo_shmmni=100` | Defines the maximum number of shared memory segments in the entire system.
`shmseg` | `set shmsys:shminfo_shmseg=10` | Defines the maximum number of shared memory segments one process can attach. Note: This parameter is not used in Solaris 9.

To determine the minimum value for the semmns parameter

If you are installing the OracleAS Metadata Repository on a computer that is not already running an Oracle database (that is, the OracleAS Metadata Repository will be the only Oracle database running on the computer), set the `semmns` parameter to a minimum of 256.

If you are installing the OracleAS Metadata Repository on a computer that is already running an Oracle database, set the `semmns` parameter to the sum of the `processes` initialization parameter for each Oracle database (including the OracleAS Metadata Repository), adding the largest one twice, and then adding an additional 10 for each database.

The default value of the `processes` parameter for the OracleAS Metadata Repository database is 150.

Example: The computer is already running an Oracle database, and its `processes` parameter is set at 200. In this case, you must set the `semmns` parameter to at least 770:

- Sum of the `processes` parameter for all Oracle database: 200 for the existing database + 150 for the OracleAS Metadata Repository that you are installing = 350

- Add the largest one twice: 200 + 200 = 400

- Add 10 for each database: 10 + 10 = 20

- Total: 350 + 400 + 20 = 770

To determine the value of the `processes` parameter for an Oracle database, run the following command in SQL*Plus:

    prompt> sqlplus "sys/password as sysdba"
    SQL> show parameters processes

`password` specifies the password for the SYS user.

To add or update kernel parameter values

1. Log on as the 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=1024
       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.

## 3.5 Ports

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

- Section 3.5.1, "Checking If a Port Is in Use"

- Section 3.5.2, "Using Default Port Numbers"

- Section 3.5.3, "Using Custom Port Numbers (the Static Ports Feature)"

Why the Default Port for Oracle HTTP Server Is Port 7777 and Not Port 80

By default, the installer configures Oracle HTTP Server to use port `7777`, not port `80`. Port `7777` is the default port because on UNIX, components that use port numbers lower than `1024` require additional steps to be done as the root user before the components can run. Because the installer does not have root access, it has to use a port greater than `1024`.

If you want Oracle HTTP Server to use a different port, such as port `80`, use the static ports feature, which enables you to specify port numbers for components. Although you can change the port number after installation, it is easier to set the port number during installation.

### 3.5.1 Checking If a Port Is in Use

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

    prompt> netstat -an | grep portnum

### 3.5.2 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. Ensure 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 fails.

### 3.5.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 3.5.3.1, "Format of the staticports.ini File" describes the file format. This file is typically called `staticports.ini`, but you can name it anything you want.

2. In the installer, on the Specify Port Configuration Options screen, select Manual and enter the complete path to the `staticports.ini` file.

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

Difference from Previous Release: In Release 10g (9.0.4), you used command-line options to specify the `staticports.ini` file. In this release, you specify the file in the new Specify Port Configuration Options screen.

#### 3.5.3.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
    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

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

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

   Table 3-5 Location of the staticports.ini File on CD-ROM and DVD-ROM

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

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

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

   The following example sets the Application Server Control port and some OracleAS Web Cache ports. For components not specified, the installer assigns 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 `portlist.ini` file to see the assigned ports.

Notes on Choosing Port Numbers: Port numbers cannot be greater than `65535`. 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 starting it. 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. If you plan to set port numbers for Oracle HTTP Server and OracleAS Web Cache, be sure you read Section 3.5.3.3, "Ports for Oracle HTTP Server and OracleAS Web Cache".

The installer verifies that the ports specified in the file are available by checking the 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 does 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 using the port.

2. Click Retry. The installer rereads the `staticports.ini` file and verifies the entries in the file again.

Using portlist.ini as the staticports.ini File

The `staticports.ini` file uses the same format as the `portlist.ini` file, which is created after a Forms and Reports Services installation. If you have installed Forms and Reports Services and want to use the same port numbers in another installation, use the `portlist.ini` file from the first installation as the `staticports.ini` file for subsequent installations.

Note: In `staticports.ini`, the `Oracle Management Agent port` line corresponds to the `Enterprise Manager Agent port` line in `portlist.ini`.

#### 3.5.3.2 Error Conditions That Cause the Installer to Use Default Ports Instead of Specified Ports

Check the `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 uses the specified port for the first component, but for the other components, it uses 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 specify a relative path to the `staticports.ini` file, the installer will not find the file. The installer continues without displaying a warning and assigns default ports to all components. You must specify a complete path to the `staticports.ini` file.

#### 3.5.3.3 Ports for Oracle HTTP Server and OracleAS Web Cache

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 the components that you are configuring.

Ensure that you understand the following when setting ports for these components.

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 3-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 the `staticports.ini` file contains both the `Oracle HTTP Server port` and the `Web Cache HTTP Listen port` lines, 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 is 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 3-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

Description of "Figure 3-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 3-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 are ignored because you are not configuring OracleAS Web Cache.

Figure 3-2 Configuring Only Oracle HTTP Server

Description of "Figure 3-2 Configuring Only Oracle HTTP Server"

#### 3.5.3.4 Examples

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

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

- Configuring Oracle HTTP Server to Use Ports 80 and 443 Without OracleAS Web Cache

##### 3.5.3.4.1 Configuring 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`, start 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 perform the configuration after installation, then the installer does not start 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.

##### 3.5.3.4.2 Configuring 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 on page 3-22 for details.

## 3.6 Operating System Groups

You must create operating system groups if you plan to install Forms and Reports Services on a computer that does not have Oracle products installed. In this case, create a group to own the inventory directory. See "Creating a Group for the Inventory Directory" in Section 3.6, "Operating System Groups".

U se the Solaris Management Console to create a local operating system group. To do this:

1. Set the `DISPLAY` environment variable to point to the monitor on which you want the Solaris Management Console window to appear. For information on setting the environment variable, see Section 3.8.4, "DISPLAY".

2. Start the Solaris Management Console.

       prompt> /usr/sadm/bin/smc

3. In the left frame, expand This Computer, and then expand System Configuration.

4. Click Users to display the Log In window.

5. Log on as the root user.

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

7. Select Action, and then select Add Group.

8. In the Group Name field, enter a name for the group.

9. In the Group ID Number field, enter an ID for the group. The ID must be a number. This is an optional field.

10. Click OK.

You have created a local operating system group. For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

Creating a Group for the Inventory Directory

If you plan to install Forms and Reports Services on a computer that does not have Oracle products installed, 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 `oinstall` name for this operating system group.

By having a separate group for the inventory directory, different users can install Oracle products on the computer. Users must have write permission for the inventory directory. To have write permission, users must belong to the `oinstall` group.

When an Oracle product is installed for the first time on a computer, the installer displays a screen where you enter a group name for the inventory directory. After this the installer displays a screen where you enter the location of the inventory directory.

The default name of the inventory directory is `oraInventory`.

If you are not sure whether an inventory directory already exists on the computer, check the `/var/opt/oracle/oraInst.loc` file. This file lists the location of the inventory directory and the group that owns it. If this file does not exist, it means that no Oracle products are installed on the computer.

## 3.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 the following directories:

- `ORACLE_HOME`, which contains files for the product you are installing

- The inventory directory, which is used by the installer for all Oracle products

If the computer contains other Oracle products, then it means that you may already have an operating system user. Check the `/var/opt/oracle/oraInst.loc` file. This file lists the location of the inventory directory and the group that owns it. If this file does not exist, it means that no Oracle products are installed on your computer.

If you do not already have a user for installing Oracle products, create a user with the properties listed in Table 3-6.

Table 3-6 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. 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 the `oracle` user for purposes unrelated to the installer. Do not use `root` as the `oracle` user.

Creating a Local Operating System User

Use the Solaris Management Console to create a local operating system user. To do this:

1. Set the `DISPLAY` environment variable to point to the monitor where you want the Solaris Management Console window to appear. For information on setting the environment variable, see Section 3.8.4, "DISPLAY".

2. Start the Solaris Management Console.

       prompt> /usr/sadm/bin/smc

3. In the left frame, expand This Computer, then expand System Configuration.

4. Click Users to display the Log In window.

5. In the User Name field, enter `root`. In the Password field, enter the root password.

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

7. Select Action, Add User, and then With Wizard.

8. In the User Name field, enter the name of the user. For example, enter `oracle`. The Full Name and Description fields are optional.

9. Click Next.

10. In the User ID Number field, accept the default value.

11. Click Next.

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

13. Click Next.

14. From the Primary Group list, select the primary group for the user. This is the group you created earlier to own the inventory directory. See "Creating a Group for the Inventory Directory".

15. Click Next.

16. In the Path field, enter a home directory for the user.

17. Click Next.

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

19. Review the user information and click Finish.

The local operating system user has been created.

To check the groups to which an operating system user belongs, 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 the operating system documentation or contact your system administrator.

## 3.8 Environment Variables

The operating system user who will be installing Forms and Reports Services needs to set (or unset) the environment variables listed in Table 3-7.

Table 3-7 Summary of Environment Variables

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 on which you want to the installer window to appear.
TMP | Optional. If unset, defaults to `/tmp`.
TNS_ADMIN | Must not be set.
REPORTS_DEFAULT_DISPLAY | Default set to YES. If set to NO, ensure that you specify the appropriate display.

### 3.8.1 Tips on Environment Variables

Here are some tips when working with environment variables:

- If you set environment variables in the `.profile` file, they may not be read. To ensure environment variables are set to the correct values, check their values in the shell where you run the installer.

- To check the value of environment variables, use the `env` command. This command 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 may 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

### 3.8.2 ORACLE_HOME and ORACLE_SID

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

### 3.8.3 PATH, CLASSPATH, and LD_LIBRARY_PATH

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

### 3.8.4 DISPLAY

Set the `DISPLAY` environment variable to point to the X server that displays 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 &

Forms and Reports Services 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 want to do this, then use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).

Visit OTN at `http://www.oracle.com/technology/products/` for information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for `frame buffer`.

### 3.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 the alternate directory. This directory must meet the requirements listed in Table 3-1.

Example (C shell):

    % setenv TMP /tmp2

Example (Bourne or Korn shell):

    $ TMP=/tmp2; export TMP

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.

### 3.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 have the `tnsnames.ora` file in `/etc` or `/var/opt/oracle`, perform the following steps before installing Forms and Reports Services.

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. Ensure 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 the existing `tnsnames.ora` file.

### 3.8.7 REPORTS_DEFAULT_DISPLAY

The `REPORTS_DEFAULT_DISPLAY` environment variable specifies whether to implement the following for Oracle Reports:

- Elimination of dependency on `DISPLAY`

- Elimination of dependency on having a valid printer defined for font information

- ScreenPrinter (`screenprinter.ppd`) for surface resolution for images and font information

- Advanced Imaging Support

For Oracle Reports, if `REPORTS_DEFAULT_DISPLAY=YES`, it overrides any value set for the `DISPLAY` environment var``iable. For more information about `REPORTS_DEFAULT_DISPLAY`, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.

Note: `REPORTS_DEFAULT_DISPLAY` is used for Oracle Reports only and is not applicable to the Oracle Application Server installer. The installer continues to use the `DISPLAY` environment variable even if `REPORTS_DEFAULT_DISPLAY` is set to `YES`.

## 3.9 The Hosts File

The contents of the `/etc/hosts` file affect the location of the default Oracle Identity Management realm and the host name for Oracle Application Server Single Sign-On.

The installer provides alternative methods for you to enter the values that you want without editing the `hosts` file. For more information, see the Oracle Application Server Installation Guide.

## 3.10 Network Topics

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

This section describes the procedure to install Forms and Reports Services on computers that do not meet the typical scenario. It covers the following cases:

- Installing on Multihomed (Multi-IP) Computers

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

- Installing from a Remote CD-ROM or DVD-ROM Drive

- Installing on Remote Computers

- Installing on NFS-Mounted Storage

- Running Multiple Instances from One Installation

- Support for NIS and NIS+

- Font Packages for Java

- Installing on Computers with Multiple Network Cards

### 3.10.1 Installing on Multihomed (Multi-IP) Computers

A multihomed computer is associated with multiple IP addresses. This is 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 Forms and Reports Services 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.

### 3.10.2 Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Forms and Reports Services CD-ROMs or DVD-ROM, you can copy the contents of the CD-ROMs or DVD-ROM to a hard drive and install from the hard drive. This might be easier if you plan to install many instances of Forms and Reports Services on your network, or if the computers on which you want to install Forms and Reports Services do not have CD-ROM or DVD-ROM drives.

You can also install from remote CD-ROM or DVD-ROM drives. See Installing from a Remote CD-ROM or DVD-ROM Drive.

When you install from the hard drive, the installer does not prompt you to swap CD-ROMs. It can find all the files if they are in the proper locations.

To copy the CD-ROMs:

1. Create a parent directory (for example, `orasolfrs`) and, under the parent directory, create subdirectories called `Disk1`, `Disk2`, and so on. The names of the subdirectories must be `Disk` `N`, where `N` is the CD-ROM number.

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 Forms and Reports Services.

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

To copy the orasolfrs Directory from the DVD-ROM

Copy the `orasolfrs` directory from the DVD-ROM to your hard disk:

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

To run the installer from the copied files, invoke the `runInstaller` executable from the computer that will be running Forms and Reports Services:

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

### 3.10.3 Installing from a Remote CD-ROM or DVD-ROM Drive

If the computer on which you want to install Forms and Reports Services does not have a CD-ROM or DVD-ROM drive, you can perform the installation from a remote CD-ROM or DVD-ROM drive. Check that you have performed these steps:

- Share the remote CD-ROM or DVD-ROM drive through NFS.

  On the remote computer that has the CD-ROM or DVD-ROM drive:

  1. CD-ROM: Insert Forms and Reports Services Disk 1 into the CD-ROM drive.

     DVD-ROM: Insert the Forms and Reports Services DVD-ROM into the DVD-ROM drive.

  2. Share the CD-ROM or DVD-ROM drive.

     CD-ROM:

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

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

     DVD-ROM:

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

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

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

  CD-ROM:

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

  DVD-ROM:

      prompt> /net/remote_computer_hostname/cdrom/orasolfrs/runInstaller

  Replace `remote_computer_hostname` with the name of the remote computer.

- For CD-ROMs only:

  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/disk1
      # 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/disk2

### 3.10.4 Installing on Remote Computers

You can run the installer on a remote computer (`remote_computer`), but have the installer screens display on your local computer (`local_computer`). The installer installs Forms and Reports Services on the remote computer.

1. Allow `remote_computer` to display on `local_computer`. Run this command on the local computer's console.

       local_computer> xhost +remote_computer

   If you do not run `xhost`, you may 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 on as the `oracle` user, as described in Section 3.7, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 3.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. For information on running the installer, see Section 4.9, "StartingOracle 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 changing the color model or visual settings.

### 3.10.5 Installing on NFS-Mounted Storage

You cannot install and run Forms and Reports Services on Sun computers with standard NFS. You must use a certified NFS-mounted storage system, such as Network Appliance (NetApp) Filers. Forms and Reports Services is certified to run on NFS-mounted storage systems.

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

    prompt> exportfs -i /vol/vol1

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

### 3.10.6 Running Multiple Instances from One Installation

Forms and Reports Services components are intended to be run only on the computer on which they are installed. You cannot run the components on remote computers even though the computers can access the files through NFS.

### 3.10.7 Support for NIS and NIS+

You can install and run Forms and Reports Services in NIS and NIS+ environments. See the Oracle Application Server Installation Guide for more information on these environments.

### 3.10.8 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`

### 3.10.9 Installing on Computers with Multiple Network Cards

If you are installing Forms and Reports Services on a computer with multiple network cards, the installer uses the first name in the `/etc/hosts` file. You may need to reorder the lines in this file so the required hostname appears first. You can change the file back to its original state after installation.

## 3.11 Prerequisite Checks Performed by the Installer

Table 3-8 lists the checks performed by the installer:

Table 3-8 Prerequisite Checks Performed by the Installer

Item | Description
--- | ---
CPU | Checks that the CPU meets the minimum speed requirement.
Operating system version | See Table 3-1 for supported versions.
Operating system patches | See Section 3.2, "Operating System Patches" for a list of required patches.
Operating system packages | See Section 3.3, "Operating System Packages" for a list of required packages.
Operating system kernel parameters | See Section 3.4, "Kernel Parameters" for a list of required kernel parameters.
Memory | See Table 3-1 for recommended values.
Swap space | See Table 3-1 for recommended values.
TMP space | See Table 3-1 for recommended values.
Instance name | The installer checks that the computer on which you are installing Forms and Reports Services 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 may interfere with the installation.
Oracle home directory | You should install Forms and Reports Services in a new directory, unless you are expanding middle tier or installing middle tier in an Oracle home that contains Oracle Developer Suite. Here are some examples of installations that are not allowed: Any type of Oracle Application Server 10g into an 8.0, 8i, 9.0.1, or 9.2 database Oracle home Any type of Oracle Application Server 10g into an Oracle Management Service Oracle home Any type of Oracle Application Server 10g into an Oracle Collaboration Suite Oracle home Any type of Oracle Application Server 10g into an Oracle HTTP Server standalone Oracle home Any type of Oracle Application Server 10g into an OracleAS Web Cache standalone Oracle home Any type of Oracle Application Server 10g into an Oracle9i Developer Suite 9.0.2 Oracle home Any type of Oracle Application Server 10g into an Oracle Application Server Containers for J2EE standalone Oracle home Any type of Oracle Application Server 10g into an Oracle9iAS 1.0.2.2 Oracle home Oracle Application Server 10g Forms and Reports Services middle tier into an Oracle9iAS9.0.2 or 9.0.3 middle tier Oracle home OracleAS Developer Kits 10g into an OracleAS Infrastructure 9.0.2 or Release 10g 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 Release 10g Oracle home OracleAS Infrastructure 10g into any Oracle9iAS 9.0.2 Oracle home OracleAS Infrastructure 10g into an Oracle Application Server 10g Forms and Reports Services middle tier or OracleAS Developer Kits 10g Oracle home OracleAS Infrastructure 10g into an Oracle Developer Suite 9.0.2 or Release 10g 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 must stop the application using port 1521, then click Retry in the warning dialog box. If a database listener is using port 1521, you may be able to use it for the metadata repository database. If another application is using port 1521, 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 Administrator's Guide for details.
Static port conflicts | The installer checks the ports listed in the `staticports.ini` file, if specified. For more information about the `staticports.ini` file, see Section 3.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.
Oracle Enterprise Manager directories are writable | The installer runs this check only if you are expanding a middle tier or reinstalling Forms and Reports Services 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 Forms and Reports Services 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`