3 Detailed Reports Services Requirements

3.3.1 Memory Requirements for Running Multiple Instances on the Same Computer

If you plan to run OracleAS Infrastructure 10g and a middle tier on the same computer, ensure the computer meets the memory requirements listed in Section 3.3.

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.

3.3.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 Administrator's Guide for details.

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

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

3.4.1 Checking the Software Requirements for Linux on POWER

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

• Section 3.4.1.1, "Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems"

• Section 3.4.1.2, "Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems"

• Section 3.4.1.3, "Software Requirements for SUSE Linux Enterprise Server 9 Systems"

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

http://www.redhat.com

make-3.79.1-17.1
gcc-3.2.3-53
gcc-c++-3.2.3-53
glibc-2.3.2-95.37
glibc-common-2.3.2-95.37
glibc-devel-2.3.2-95.37
compat-db-4.0.14-5.1
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
libstdc++-3.2.3-53
libstdc++-devel-3.2.3-53
openmotif21-2.1.30-9.RHEL3.6
sysstat-5.0.5-5.rhel3
setarch-1.3-1
libaio-0.3.96-5
libaio-devel-0.3.96-5
binutils-2.14.90.0.4-39
pdksh-5.2.14-21

glibc-2.3.4-2.9 
glibc-common-2.3.4-2.9 
glibc-devel-2.3.4-2.9 
gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
binutils-2.15.92.0.2-13
make-3.80-5
pdksh-5.2.14-30
sysstat-5.0.5-1
openmotif21-2.1.30-11.RHEL4.4
libaio-devel-0.3.103-3
libaio-0.3.103-3

http://www.suse.com

glibc-2.3.3-98.61
gcc-3.3.3-43.41 
gcc-c++-3.3.3-43.41 
libstdc++-3.3.3-43.41 
libstdc++-devel-3.3.3-43.41
openmotif-libs-2.2.2-519.4 
pdksh-5.2.14-780.7 
make-3.80-184.1 
sysstat-5.0.1-35.7 
binutils-2.15.90.0.1.1-32.10 
glibc-devel-2.3.3-98.61
libaio-0.3.102-1.5
libaio-devel-0.3.102-1.5
compat-2004.7.1-1.2
db1-1.85-85.1

3.5.1 Configuring the Kernel Parameters on Linux

The computers on which you plan to install OracleAS Metadata Repository or OracleAS Web Cache require their kernel parameters to be set to the minimum values listed in the following sections:

Kernel Parameter Settings for OracleAS Web Cache

This section applies if you are installing OracleAS Web Cache:

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

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

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

   prompt> ulimit -Hn
   
   

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

   *       hard    nofile  65536
   
   

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

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

Kernel Parameter Settings for OracleAS Metadata Repository

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

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

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

   
   

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

   
   

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

   
   

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

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

      
      

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

      
      

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

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

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

      # /sbin/sysctl -p
      
      

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

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

      # chkconfig boot.sysctl on
      
      

Set Shell Limits for the oracle User

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

To increase the shell limits:

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

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

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

   session    required     /lib/security/pam_limits.so
   
   

3. Depending on the oracle user's default shell, make the following changes to the default shell start-up file:

   • For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:

     if [ $USER = "oracle" ]; then
             if [ $SHELL = "/bin/ksh" ]; then
                   ulimit -p 16384
                   ulimit -n 65536
             else
                   ulimit -u 16384 -n 65536
             fi
     fi
     
     

   • For the C or tcsh shell, add the following lines to the /etc/csh.login file:

     if ( $USER == "oracle" ) then
             limit maxproc 16384
             limit descriptors 65536
     endif
     
     

3.6.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.6.2 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. Refer to Appendix C, "Default Port Numbers" for a list of the default port numbers and ranges. Make sure that at least one port is available in the port range for each component. If the installer is unable to find a free port in the range, then the installation fails.

3.6.3 Using Custom Port Numbers (the Static Ports Feature)

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

1. Create a file containing the component names and port numbers. Section 3.6.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.

# 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

3.6.3.3 Ports for Oracle HTTP Server and OracleAS Web Cache

Ensure that 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 the components that 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 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"

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

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

3.7.1 Create a Group for the Inventory Directory

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

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

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

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

The default name of the inventory directory is oraInventory.

If you are unsure if there is already an inventory directory on the computer, look in the /etc/oraInst.loc file on Linux systems. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

3.7.2 Create Groups for Database Administrators

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

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

You need to create operating system groups for these groups.

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

1. Create the dba group.

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

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

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

3.9.1 Tips on Environment Variables

Here are some tips when working with environment variables:

• If you set environment variables in the 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.9.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.9.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.

The shared library path environment variable is LD_LIBRARY_PATH.

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

Oracle Business Intelligence 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 Oracle Technology Network 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.9.5 TMP and TMPDIR

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.

Example (C shell):

% setenv TMP /tmp2
% setenv TMPDIR /tmp2

Example (Bourne or Korn shell):

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

If you do not set this environment variable, and the default directory does not have enough space, then the installer displays an error message that says the environment variable is not set. You can either set the environment variable to point to a different directory or free up enough space in the default directory. In either case, you have to restart the installation.

3.9.6 TNS_ADMIN

This section describes two requirements:

• The TNS_ADMIN environment variable must not be set.

• The /etc and the directory must not contain a tnsnames.ora file.

These requirements are necessary to prevent conflicts between the Net configuration files for different Oracle products.

If you need to set TNS_ADMIN or have the tnsnames.ora file in /etc or , perform the following steps before installing Oracle Business Intelligence.

1. If you have the tnsnames.ora file in /etc or 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 the existing tnsnames.ora file.

3.9.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 variable. For more information about REPORTS_DEFAULT_DISPLAY, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.

3.9.8 ORA_NLS

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

Example:

$ unset ORA_NLS

3.9.9 LD_BIND_NOW (Linux Only)

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

Example:

$ unset LD_BIND_NOW

3.11.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 Oracle Business Intelligence 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.11.2 Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Oracle Business Intelligence 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 Oracle Business Intelligence on your network, or if the computers on which you want to install Oracle Business Intelligence do not have CD-ROM or DVD-ROM drives.

You can also install from remote CD-ROM or DVD-ROM drives. See Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive".)

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

To Copy the CD-ROMs:

1. Create a parent directory (for example, orafrs) 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.

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

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

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

To Copy the orafrs Directory from the DVD-ROM

Copy the orafrs 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 runInstallersetup.exe executable from the computer that will be running Oracle Business Intelligence:

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

3.11.3 Installing from a Remote CD-ROM or DVD Drive

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

• You need to 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 Oracle Business Intelligence Disk 1 into the CD-ROM drive.

     DVD-ROM: Insert the Oracle Business Intelligence 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.

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

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

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

   Example (C shell):

   remote_computer> setenv DISPLAY local_computer.mydomain.com:0.0
   
   

   Example (Bourne or Korn shell):

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

4. Run the installer. For information on running the installer, see Section 4.1, "Starting the 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.

   
   

If you want to install and run Forms and Reports Services on a remote computer (that is, the remote computer has the hard drive and will run Forms and Reports Services components), but you do not have physical access to the computer, you can still perform the installation on the remote computer if it is running remote control software such as VNC or Symantec pcAnywhere. You also need the remote control software running on your local computer.

You can install Forms and Reports Services on the remote computer in one of these two ways:

• If you have copied the contents of the Forms and Reports Services CD-ROM or DVD to a hard drive, then you can install from the hard drive.

• You can insert the CD-ROM or DVD into a drive on your local computer, and install from the CD-ROM or DVD.

Installing from a Hard Drive

If you have copied the contents of the Forms and Reports Services CD-ROM or DVD to a hard drive, then you can install from the hard drive. To install from the hard drive:

1. Ensure that the remote control software is installed and running on the remote and local computers.

2. Share the hard drive that contains the Forms and Reports Services CD-ROM or DVD.

3. On the remote computer, map a drive letter to the shared hard drive. Use the remote control software to do this on the remote computer.

4. Using the remote control software, run the installer on the remote computer. You can access the installer from the shared hard drive.

Installing from a Remote CD-ROM or DVD Drive

You can insert the CD-ROM or DVD into a drive on your local computer, and install from the CD-ROM or DVD. This is similar to the scenario described in Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive". To install from a remote CD-ROM or DVD:

1. Ensure that the remote control software is installed and running on the remote and local computers.

2. On the local computer, share the CD-ROM or DVD drive.

   On the remote computer, map a drive letter to the shared CD-ROM or DVD drive. Use the remote control software to do this on the remote computer.

   These steps are described in Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive".

3. Using the remote control software, run the installer on the remote computer. You can access the installer from the shared CD-ROM or DVD drive.

3.11.5 Installing on NFS-Mounted Storage

You cannot install and run Oracle Business Intelligence on Sun computers with standard NFS. You must use a certified NFS-mounted storage system, such as Network Appliance (NetApp) Filers. Oracle Business Intelligence 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.11.6 Running Multiple Instances from One Installation

Oracle Business Intelligence 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.11.7 Support for NIS and NIS+

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

3.11.8 Installing on Computers With Multiple Network Cards

If you are installing Oracle Business Intelligence 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 required hostname appears first. You can change the file back to its original state after installation.