3 Detailed Reports Services Requirements

3.6.1 About Ephemeral Ports

Problem: Components Cannot Start Up Because of Conflicts with Ephemeral Ports

On rare occasions, Oracle Application Server processes are unable to start because required ports are not available. Processes may fail to start or report that they are unable to bind to ports. The behavior may be transient in that if you try to restart the affected process later, it does start successfully.

The cause of this problem is that by default, Oracle Application Server uses a number of ports that fall into the range of ephemeral ports. Ephemeral ports are usually used on the client ends of client/server TCP/IP connections. Because client processes usually are unconcerned with the port value used on the client side of the connection, all TCP/IP implementations enable clients to defer to the operating system the choice of the port value to use for the client side. The operating system selects a port from the ephemeral port range for each client connection of this type.

On the other hand, server processes (for example, Oracle Application Server processes) cannot use ephemeral ports. They must use fixed port values so that clients can always connect to the same server port to communicate with the server.

Port conflicts with ephemeral ports arise when an Oracle Application Server process is configured to use a port in the ephemeral port range. The Oracle Application Server process tries to start up, but discovers that the port that it needs is already in use by a client process (the client received the ephemeral port assignment from the operating system). This client can be any process on the computer capable of communicating via TCP/IP. The Oracle Application Server process fails to start up when the port that it needs is unavailable.

This problem occurs relatively more frequently on Microsoft Windows than on other operating systems because by default Windows uses a small range of ports for ephemeral client connections.

Ephemeral Port Range

The ephemeral port range on Microsoft Windows is ports 1024 through 5000, inclusive.

Only the upper end of this range is adjustable in Windows. In most other operating systems, the ephemeral range by default is much larger, and the lower and upper bounds of the range are adjustable.

Several Application Server processes, including Oracle HTTP Server, OracleAS Web Cache, Oracle Enterprise Manager 10g Application Server Control, and OC4J, use ports in the ephemeral port range. These processes cannot start up if the ports that they need are already in use by clients.

Avoiding Conflicts with Ephemeral Ports

To avoid conflicts with ephemeral ports, you have these options:

• Install Oracle Business Intelligence using staticports.ini so that Oracle Business Intelligence components do not use ports within the ephemeral range. In the staticports.ini file, use port numbers below 1024 or above 5000.

  See Section 3.6.4, "Using Custom Port Numbers (the Static Ports Feature)" for details.

• If you have already installed Oracle Business Intelligence, you can reconfigure the components to use ports below 1024 or above 5000. See the Oracle Application Server Administrator's Guide to learn to change the current ports used by Application Server processes.

• (This option can be done post-installation.) Modify the ephemeral port range on your computer. Use this option only if you cannot use any of the alternatives above. This option is the least preferred because it makes changes to the Windows registry, and it affects all products that you run on your computer.

  This option moves the ephemeral port range to a new location. Before making the change, you must verify that none of the products you are using (Oracle or non-Oracle) on your computer use non-ephemeral ports within the ephemeral port range. If any products do so, you must relocate them to the new ReservedPorts range (see below), above the new ephemeral range, or below port 1024.

  To implement this option, perform these steps:

  • Raise the upper bound of the ephemeral port range to expand the size of the range.

    Set the MaxUserPort value in the registry to at least 13000, but no higher than 65534. MaxUserPort is the upper bound of the ephemeral port range.

    For steps, see Microsoft Knowledge Base article 196271: http://support.microsoft.com/default.aspx?scid=kb;[LN];196271.

  • Reserve a portion of the newly expanded ephemeral port range for use by Oracle Application Server.

    Set the ReservedPorts value in the registry so that ports 1024 through 8000 are reserved for Oracle Application Server. The reserved range incorporates the range of ports normally used by Oracle Application Server.

    For steps, see Microsoft Knowledge Base article 812873: http://support.microsoft.com/default.aspx?scid=kb;[LN];812873.

  • Restart your computer for the changes to take effect.

  After performing the steps, you end up with the following: ports from 1024 through 8000 are reserved for Oracle Application Server, and ports 8001 through 13000 are the new ephemeral port range (assuming you set the MaxUserPort to 13000). The reserved range incorporates the range of ports normally used by Oracle Application Server, and the ephemeral range has the same size as the original.

3.6.2 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

C:\> netstat -an | find "portnum"

Note that you need double-quotes around the port number.

3.6.3 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. Make sure that at least one port is available in the port range for each component. If the installer is unable to find a free port in the range, the installation fails.

Note the following points:

• The installer assigns the default ports to components only if the ports are not in use by other applications. If the default port is in use, the installer tries other ports in the port number range for the component. For example, the default non-SSL port for Oracle HTTP Server for the middle tier is port 80. If this port is in use by another application, the installer assigns a port in the 7777 - 7877 range.

• The default ports for Oracle HTTP Server depend on the installation type (Table 3-4). The middle tier gets ports 80 and 443 because it is where you would deploy your applications. Users would send requests to the middle tier's Oracle HTTP Server/OracleAS Web Cache to access the applications.

  In Table 3-4, the values in parenthesis indicate the ports that the installer tries to assign to Oracle HTTP Server if the default port is already in use.

  Table 3-4  Default Ports for Oracle HTTP Server

  Installation Type	Default Non-SSL Port	Default SSL Port
  OracleAS Infrastructure	7777 (7777 - 7877)	4443 (4443 - 4543)
  Middle tier	80 (7777 - 7877)	443 (4443 - 4543)

  
  

• The installer no longer checks the services file to determine if a port is in use. In earlier releases, the installer would not assign a port number if the port number was listed in the file.

  The services file is located in the C:\%SystemRoot%\system32\drivers\etc directory, where %SystemRoot% is winnt on Windows 2000, and windows on Windows XP and Windows 2003.

3.6.4 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.4.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.4.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.10.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.10.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.10.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.10.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 &

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

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

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

3.10.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.11.1 Setting Environment Variables (on Windows)

To set environment variables in Windows:

1. Display the System control panel.

   Windows 2000: Select Start > Settings > Control Panel > System.

   Windows 2003: Select Start > Control Panel> System.

   Windows XP: Select Start > Control Panel, and then double-click System.

2. Click the Advanced tab.

3. Click Environment Variables.

4. To change the value of a variable, select the variable and click Edit.

3.11.2 ORACLE_HOME and ORACLE_SID

The installer unsets the ORACLE_HOME and ORACLE_SID environment variables when you start the installer regardless of whether these environment variables were set or unset.

3.11.3 PATH and CLASSPATH

The PATH environment variable cannot be longer than 1023 characters. Otherwise, the installation may fail.

3.11.4 TEMP

During installation, the installer needs to write temporary files to a temporary directory. By default, the temporary directory is C:\temp.

If you want the installer to use a directory other than C:\temp, set the TEMP environment variable to the full path of an alternate directory.

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.13.1 Installing on DHCP Computers

Note this limitation when running Oracle Business Intelligence on DHCP computers: Oracle Business Intelligence instances on DHCP computers cannot communicate with instances running on other computers. All the instances that need to communicate with each other must run on the same computer. There are no limitations on clients; clients from other computers can access instances running on the DHCP computer, as long as the client computer can resolve the DHCP computer on the network.

Before installing Oracle Business Intelligence on a DHCP computer, perform these steps:

1. Install a loopback adapter on the DHCP computer.

   When you install a loopback adapter, the loopback adapter assigns a local IP for your computer. Having a loopback adapter and a local IP address means that you do not have to run the chgiphost script after installation each time the IP address changes (due to DHCP).

   Which Is the Primary Network Adapter?

   Windows considers loopback adapters as a type of network adapter. After installing a loopback adapter on your computer, you have at least two network adapters on your computer: your network adapter and the loopback adapter.

   Windows must use the loopback adapter as the primary adapter. The primary adapter is determined by the order in which you installed the adapters:

   • On Windows 2000, the primary adapter is the last adapter installed. You can just install the loopback adapter. However, if you install additional network adapters after installing the loopback adapter, deinstall the loopback adapter and reinstall it.

   To install a loopback adapter on the different Windows platforms, see Section 3.13.6, "Installing a Loopback Adapter".

2. Ping each computer on which you plan to install Oracle Business Intelligence.

   • Ping the computer from itself, using only the hostname and the fully qualified name.

     For example, if you installed a loopback adapter on a computer called mycomputer, check the following:

     prompt> ping mycomputer                Ping itself using just the hostname.
     Reply from 10.10.10.10                    Returns local IP.
     prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
     Reply from 10.10.10.10                    Returns local IP.
     
     

     
     

     Note: When you ping a computer from itself, the ping command should return the local IP (the IP of the loopback adapter). It should not return the network IP of the computer.

     
     

   • Ping the computer from other computers on the network, using only the hostname and the fully qualified name.

     In this case, the ping command returns the network IP of the computer.

     prompt> ping mycomputer                Ping using the hostname.
     Reply from 139.185.140.166                Returns network IP.
     prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
     Reply from 139.185.140.166                Returns network IP.
     
     

   If ping fails, then contact your network administrator.

3.13.2 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 (on Solaris) or the hosts file on Microsoft Windows (typically located in DRIVE_LETTER:\WINDOWS\system32\drivers\etc).

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.

For information on setting environment variables on Microsoft Windows, see Section 3.11.1, "Setting Environment Variables (on Windows)".

3.13.3 Installing on Computers With Multiple Aliases

A computer with multiple aliases refers to a computer registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer.

Before installing Oracle Business Intelligence on such computers, you must:

• Install a loopback adapter on the computer.

• Make sure the loopback adapter is the primary network adapter.

The loopback adapter ensures that when Oracle Business Intelligence queries for the hostname, it always gets the same name (because the queries are done locally). Without the loopback adapter, the queries can return any of the aliases for the computer (because the queries get the response from the naming service).

For information on the method in which Windows determines the primary adapter, see "Which Is the Primary Network Adapter?".

For steps on installing a loopback adapter, see Section 3.13.6, "Installing a Loopback Adapter".

3.13.4 Installing on Non-Networked Computers

You can install Oracle Business Intelligence on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you must install all the components that you need on the computer.

If you want to install Oracle Business Intelligence on a non-networked computer and do not want to connect the computer to a network after installation, then install Oracle Business Intelligence on your non-networked computer.

However, if you want to connect the computer to a network after installation, perform these steps before installing Oracle Business Intelligence on the non-networked computer.

1. Install a loopback adapter on the computer. See Section 3.13.6, "Installing a Loopback Adapter".

   The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Oracle Business Intelligence uses the local IP and hostname.

2. Ping the computer from itself, using only the hostname and the fully qualified name.

   For example, if you installed a loopback adapter on a computer called mycomputer, check the following:

   prompt> ping mycomputer                Ping itself using just the hostname.
   Reply from 10.10.10.10                    Returns local IP.
   prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
   Reply from 10.10.10.10                    Returns local IP.
   
   

   
   

   Note: When you ping a computer from itself, the ping command should return the local IP (the IP of the loopback adapter).

   
   

   If ping fails, then contact your network administrator.

Connecting the Computer to the Network After Installation

If you connect the computer to a network after installation, then the Oracle Business Intelligence instance on your computer can work with other instances on the network. Recall that you must have installed a loopback adapter on your computer. Your computer can use a static IP or DHCP, depending on the network to which you are connected.

See the Oracle Application Server Administrator's Guide for details.

3.13.5 Installing on Static IP Computers that You Want to Disconnect from the Network Later

If you plan to install Oracle Business Intelligence on a networked computer with static IP and be able to run Oracle Business Intelligence when you disconnect the computer from the network, perform the following steps before installing Oracle Business Intelligence:

1. Install a loopback adapter on your computer. See Section 3.13.6, "Installing a Loopback Adapter" for details.

   Without a loopback adapter, Oracle Business Intelligence cannot function correctly when you disconnect the computer from the network because the static IP is no longer available.

2. Make sure the loopback adapter is the primary network adapter. See "Which Is the Primary Network Adapter?". To check, ping the computer from itself using (1) the hostname only and (2) the fully qualified name.

   For example, if you installed a loopback adapter on a computer called mycomputer, you can run these commands:

   prompt> ping mycomputer                Ping itself using just the hostname.
   Reply from 10.10.10.10                    Returns loopback adapter IP.
   prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
   Reply from 10.10.10.10                    Returns loopback adapter IP.
   
   

   When you ping a computer from itself, the ping command should return the IP of the loopback adapter. It should not return the network IP of the computer.

These steps are required regardless of whether the computer is using static IP or DHCP. If this is a DHCP computer, you already know you need a loopback adapter; see Section 3.13.1, "Installing on DHCP Computers".

When you disconnect the computer from the network, the computer has no access to any network resources.

3.13.6 Installing a Loopback Adapter

A loopback adapter is required if:

• You are installing on a DHCP computer (see Section 3.13.1, "Installing on DHCP Computers").

• You are installing on a non-networked computer and plan to connect the computer to a network after installation (see Section 3.13.4, "Installing on Non-Networked Computers").

The procedure for installing a loopback adapter depends on the version of Windows:

• Section 3.13.6.1, "Checking If a Loopback Adapter Is Installed on Your Computer"

• Section 3.13.6.2, "Installing a Loopback Adapter - Windows 2000"

• Section 3.13.6.3, "Installing a Loopback Adapter - Windows 2003 / Windows XP"

• Section 3.13.6.4, "Removing a Loopback Adapter - Windows 2000 / Windows 2003 / Windows XP"

prompt> ipconfig /all

Ethernet adapter Local Area Connection 2:
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft Loopback Adapter
  Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Autoconfiguration IP Address. . . : 169.254.25.129
  Subnet Mask . . . . . . . . . . . : 255.255.0.0

3.13.7 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.13.8, "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.

Accessing the Hard Drive from Other Computers

If you want to install Oracle Business Intelligence on remote computers from the hard drive where you copied the contents of the CD-ROM or DVD-ROM, perform the following steps:

1. On the local computer, share the hard drive.

2. On the computers where you want to install Oracle Business Intelligence, map to the shared hard drive.

3. Run the installer from the remote computers on which you want to install Oracle Business Intelligence.

   Note that you have to use the drive letter for the mapped drive to access the installer (for example, H:\orawinfrs_10_1_2\setup.exe).

   You cannot use the universal naming convention (UNC) syntax (\\hostname\sharename) to access the installer.

To Copy the CD-ROMs:

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

   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.
   
   

   You can copy the files using Windows Explorer or the command line. If you are using the command line, you can use the xcopy command.

   The following example assumes E: is the CD-ROM drive, and C:\orawinfrs\DiskN are the directories that you want to copy the CD-ROMs to.

   E:\> xcopy /e /i  E:\1012disk1  C:\orawinfrs\Disk1
   E:\> xcopy /e /i  E:\1012disk2  C:\orawinfrs\Disk2
   ... Repeat for each CD-ROM.
   
   

To run the installer from the copied files, invoke the runInstallersetup.exe executable from the Disk1 directory. Run it from the computer that will be running Oracle Business Intelligence.

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

C:\> cd orawinfrs\Disk1
C:\orawinfrs\Disk1> setup.exe

To Copy the orasolfrsorawinfrs 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

You can copy the orawinfrs directory using Windows Explorer or the command line. If you are using the command line, here are the steps:

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

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

   The example assumes E: is the DVD-ROM drive, and C:\orawinfrs is the destination directory:

   E:\> xcopy /e /i  E:\orawinfrs C:\orawinfrs
   
   

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/orasolfrs/runInstaller

C:\> cd orawinfrs
C:\orawinfrs> setup.exe

3.13.8 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
  
  

On the Remote Computer, Share the CD-ROM or DVD Drive

The remote CD-ROM or DVD drive that you want to use must allow shared access. To set this up, perform these steps on the remote computer (the computer that has the CD-ROM or DVD drive):

1. Log on to the remote computer as an Administrator user.

2. Start up Windows Explorer.

3. Right-click the CD-ROM or DVD drive letter and choose Sharing (Windows 2000) or Sharing and Security (Windows 2003, Windows XP).

4. On the Sharing tab (Figure 3-7):

   Select Share this folder.

   Share name: Give it a share name such as cdrom or dvd. You will use this name when you map the CD-ROM or DVD drive on the local computer. See step d.

   Click Permissions. The user who accesses this folder to install Oracle Business Intelligence will need at least read permission.

   Click OK when done.

   Figure 3-7 Sharing a CD-ROM Drive

   
   Description of "Figure 3-7 Sharing a CD-ROM Drive"
   
   

5. CD-ROM: Insert Oracle Business Intelligence Disk 1 into the CD-ROM drive.

   DVD: Insert the Oracle Business Intelligence DVD into the DVD drive.

On the Local Computer, Map the CD-ROM or DVD Drive

Perform these steps on the local computer to map the CD-ROM or DVD drive and to run the installer:

1. Map the remote CD-ROM or DVD drive.

   1. Start up Windows Explorer on the local computer.

   2. Select Tools > Map Network Drive. This displays the Map Network Drive dialog box.

   3. Select a drive letter to use for the remote CD-ROM or DVD drive.

   4. In Folder, enter the location of the remote CD-ROM or DVD drive using the following format:

      \\remote_hostname\share_name
      
      

      Replace remote_hostname with the name of the remote computer with the CD-ROM or DVD drive.

      Replace share_name with the share name that you entered in step 4.

      Example: \\computer2\cdrom

   5. If you need to connect to the remote computer as a different user, click Different User Name, and enter the username.

   6. Click Finish.

2. Run the installer from the mapped CD-ROM or DVD drive.

   When the installer prompts you to switch CD-ROMs, eject the CD-ROM and insert the requested 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 created is not usable and may need to be removed manually.

   
   

3.13.9 Installing on Remote Computers Using Remote Control Software

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 Oracle Business Intelligence 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 for Solaris". Ensure that the user has set the environment variables correctly, as described in Section 3.10, "Environment Variables for Solaris".

   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.

   
   

   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 Oracle Business Intelligence on a remote computer (that is, the remote computer has the hard drive and will run Oracle Business Intelligence 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 Oracle Business Intelligence on the remote computer in one of these two ways:

• If you have copied the contents of the Oracle Business Intelligence 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 Oracle Business Intelligence 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 Oracle Business Intelligence 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.13.8, "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.13.8, "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.13.10 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.13.11 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.13.12 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.13.13 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.13.14 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.