4 Requirements

4.2.1 Memory and Pagefile Requirements for Running Multiple Instances on the Same Computer

If you plan to run OracleAS Infrastructure and a middle tier on the same computer, ensure the computer meets the memory and pagefile requirements listed in Table 4-3.

The pagefile values below were suggested by Windows based on the amount of memory on the computer. Use the value suggested for your computer.

Note that these values have been tested against a small number of users. If you have many users, you might have to increase the amount of memory.

4.2.2 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 instances on one computer, each Application Server Control can consume a lot of memory. Running Application Server Control only when you need it can free up memory for other components.

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

4.4.1 About Ephemeral Ports

An ephemeral port is a port number that an operating system can temporarily assign to a service or process. Some services or processes have conventionally assigned permanent port numbers. In other cases, an ephemeral port number is assigned temporarily (for the duration of the request and its completion) from a range of assigned port numbers.

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.

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

On rare occasions, Oracle Application Server processes are unable to start up because required ports are not available. Processes may fail to start up 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 which port value is used on the client side of the connection, all TCP/IP implementations allow clients to defer to the operating system the choice of which 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.

How to Avoid Conflicts with Ephemeral Ports

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

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

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

• If you have already installed Oracle Application Server, you can reconfigure the components to use ports below 1024 or above 5000. See the Oracle Application Server Administrator's Guide to learn how 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.

4.4.2 Checking If a Port Is in Use

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

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

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

4.4.3 Using Default Port Numbers

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

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 4-5). 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 4-5, the values in parenthesis indicate the ports that the installer will try to assign to Oracle HTTP Server if the default port is already in use.

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

If You Plan to Install OracleAS Infrastructure and Middle Tier on the Same Computer

If you plan to install multiple instances (such as an OracleAS Infrastructure and a middle tier, or multiple middle tiers) on the same computer, only the first instance that you install on the computer will use the default ports. When you install additional instances, the installer will detect that the default ports are already in use by the first instance, and it will assign other ports to the additional instances.

The components where this is most visible are Oracle HTTP Server and OracleAS Web Cache, as shown in the following scenarios:

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

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

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

# J2EE and Web Cache
Oracle HTTP Server port = port_num
Oracle HTTP Server Listen port = port_num
Oracle HTTP Server SSL port = port_num
Oracle HTTP Server Listen (SSL) port = port_num
Oracle HTTP Server Diagnostic port = port_num
Java Object Cache port = port_num
DCM Java Object Cache port = port_num
DCM Discovery port = port_num
Oracle Notification Server Request port = port_num
Oracle Notification Server Local port = port_num
Oracle Notification Server Remote port = port_num
Application Server Control port = port_num
Application Server Control RMI port = port_num
Oracle Management Agent port = port_num
Web Cache HTTP Listen port = port_num
Web Cache HTTP Listen (SSL) port = port_num
Web Cache Administration port = port_num
Web Cache Invalidation port = port_num
Web Cache Statistics port = port_num
Log Loader port = port_num
ASG port = port_num

# Business Intelligence and Forms
Discoverer Preference port = port_num
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

4.4.4.3 Ports for Oracle HTTP Server and OracleAS Web Cache

Be sure you understand the following when setting ports for these components.

In the httpd.conf file for Oracle HTTP Server, the Port and the Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server. The correct lines in the staticports.ini file for setting these ports depend on which components you are configuring.

If You Are Configuring OracleAS Web Cache and Oracle HTTP Server

1. Set the port for OracleAS Web Cache.

   OracleAS Web Cache uses the port specified by the Port directive (Figure 4-1). To set this port, use this line in the staticports.ini file:

   Web Cache HTTP Listen port = port_number
   
   

   To configure the SSL port for OracleAS Web Cache, use the following line:

   Web Cache HTTP Listen (SSL) port = port_number
   
   

   You cannot set the port number using the "Oracle HTTP Server port" line in this case. If your staticports.ini file contains both "Oracle HTTP Server port" and "Web Cache HTTP Listen port", the "Oracle HTTP Server port" line is ignored. For example, if you have these lines in staticports.ini:

   Web Cache HTTP Listen port = 7979
   Oracle HTTP Server port = 8080
   
   

   the Port directive would be set to 7979.

2. Set the port for Oracle HTTP Server.

   Oracle HTTP Server uses the port specified by the Listen directive. To set this port, use this line in the staticports.ini file:

   Oracle HTTP Server Listen port = port_number
   
   

   To configure the SSL Listen port, use the following line:

   Oracle HTTP Server Listen (SSL) port = port_number
   
   

Figure 4-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

Description of "Figure 4-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server"

If You Are Configuring Oracle HTTP Server Only (no OracleAS Web Cache)

If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives (Figure 4-2). In this case, you must set both directives to use the same port number.

To set these ports, use the "Oracle HTTP Server port" and "Oracle HTTP Server Listen port" lines in the staticports.ini file. For example:

Oracle HTTP Server port = 8080
Oracle HTTP Server Listen port = 8080

To set the SSL version of these ports, use the following lines. As in the non-SSL version, the port numbers must be the same.

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

If you also specify the Web Cache lines in staticports.ini, they will be ignored because you are not configuring OracleAS Web Cache.

Figure 4-2 Configuring Only Oracle HTTP Server

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

4.4.5 If Port 1521 Is in Use

The installer configures port 1521 for the OracleAS Metadata Repository listener (version 10.1.0.3). This port cannot be changed through the staticports.ini file.

If port 1521 on your computer is already in use by an existing application, such as Oracle database listener or some other application, you might have to take some action before running the installer. See the following sections for details.

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

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

C:\> cd ORACLE_HOME\bin
C:\> lsnrctl version

C:\OraHome_1\BIN>lsnrctl VERSION
LSNRCTL for 32-bit Windows: Version 10.1.0.4.2 - Production on 13-JUL-2005 16:47:00
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=as-pc.oracle.com)(PORT=1521)))
TNSLSNR for 32-bit Windows: Version 10.1.0.4.2 - Production
        TNS for 32-bit Windows: Version 10.1.0.4.0 - Production
        Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.1.0.4.0 - Production
        Windows NT Named Pipes NT Protocol Adapter for 32-bit Windows: Version 10.1.0.4.0 - Production
        Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 10.1.0.4.0 - Production,,
The command completed successfully

4.6.1 How to Set Environment Variables

This section describes how to set environment variables in Windows:

1. Display the System control panel.

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

   On Windows 2003: Select Start > Control Panel > System.

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

2. Select the Advanced tab.

3. Click Environment Variables.

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

4.6.2 ORACLE_HOME and ORACLE_SID

These environment variables must not be set.

4.6.3 PATH

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

4.6.4 TNS_ADMIN

Ensure that the TNS_ADMIN environment variable is not set when you run the installer. If set, it can cause errors during installation. Section H.3.12, "Database Configuration Assistant (DBCA) Failures" shows such an error.

4.6.5 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. This directory must meet the requirements listed in Table 4-2.

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

4.7.1 Location of the Default Oracle Identity Management Realm

The installer reads the hosts file to construct the location of the default Oracle Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.

The hosts file should use the following format:

ip_address   fully_qualified_hostname   short_hostname

Example:

123.45.67.89   primaryHost.mydomain.com   primaryHost

In the preceding example, the location of the default Oracle Identity Management realm would look like "dc=mydomain,dc=com".

If the file uses a different format, the installer displays an incorrect value in the screen. For example, if the hosts file contains:

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

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

4.7.2 Hostname for OracleAS Single Sign-On

If you are installing OracleAS Single Sign-On, and your hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).

If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:

E:\> setup.exe OUI_HOSTNAME=myserver.mydomain.com

4.8.1 Installing on DHCP Computers

Note this limitation when running Oracle Application Server on DHCP computers: Oracle Application Server instances on DHCP computers cannot communicate with other instances running on other computers. For example, you cannot have OracleAS Infrastructure on one computer and a middle tier on another computer if any one of those computers uses DHCP. All the instances that need to communicate with each other need to run on the same computer. There are no limitations on clients: clients from other computers can access the instances running on the DHCP computer, as long as the client computer can resolve the DHCP computer on the network.

Before installing Oracle Application Server 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.

   You want Windows to 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 you install the loopback adapter, you need to deinstall the loopback adapter and reinstall it.

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

2. Ping each computer where you plan to install Oracle Application Server.

   • Ping the computer from itself, using only the hostname and using 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 loopback adapter IP.
     prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
     Reply from 10.10.10.10                    Returns loopback adapter IP.
     
     

     
     

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

     
     

   • Ping the computer from other computers on the network, using only the hostname and using 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 consult your network administrator.

4.8.2 Installing on Multihomed (Multi-IP) Computers

You can install Oracle Database on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a hostname; additionally, you can set up aliases for the hostname. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the hostname. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the hosts file (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, see Section 4.6.1, "How to Set Environment Variables".

4.8.3 Installing on Computers with Multiple Aliases

A computer with multiple aliases is 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 Application Server on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose hostname you want to use.

For information on setting environment variables, see Section 4.6.1, "How to Set Environment Variables".

4.8.4 Installing on Non-Networked Computers

You can install Oracle Application Server on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer. Examples:

• You can install a J2EE and Web Cache middle tier without Oracle Identity Management or farm repository. See Section 7.1, "Middle-tier Types" for details.

• If you install a middle tier that requires infrastructure services, you need to install both OracleAS Infrastructure and middle tier on the computer. Ensure your computer has enough resources to run both instances. See Section 4.2.1, "Memory and Pagefile Requirements for Running Multiple Instances on the Same Computer".

Note that to install Oracle Application Server on a non-networked computer, the computer must have networking capabilities. Non-networked means that the computer is not connected to a network.

If you want to install Oracle Application Server on a non-networked computer, and you never want to connect the computer to a network after installation, ever, then you can just go ahead and install Oracle Application Server on your non-networked computer.

However, if you plan to connect the computer to a network after installation, perform these steps before you install Oracle Application Server on the non-networked computer.

1. Install a loopback adapter on the computer. See Section 4.8.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 Application Server still uses the local IP and hostname.

2. Ping the computer from itself, using only the hostname and using 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 loopback adapter IP.
   prompt> ping mycomputer.mydomain.com   Ping using a fully qualified name.
   Reply from 10.10.10.10                    Returns loopback adapter IP.
   
   

   
   

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

   
   

   If ping fails, then you need to talk with your network administrator.

Connecting the Computer to the Network After Installation

If you connect the computer to a network after installation, your Oracle Application Server 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.

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

If you plan to install Oracle Application Server on a networked computer with static IP and you want to be able to run Oracle Application Server when you disconnect the computer from the network, you need to do the following steps before installing Oracle Application Server:

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

   Without a loopback adapter, Oracle Application Server 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 4.8.1, "Installing on DHCP Computers".

When you disconnect the computer from the network, the computer has no access to any network resources. Make sure you have all the instances (for example, OracleAS Infrastructure and middle tier) you need on your computer.

4.8.6 Installing a Loopback Adapter

A loopback adapter is required in any of these scenarios:

• you are installing on a DHCP computer (see Section 4.8.1, "Installing on DHCP Computers"), or

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

• you are installing on a computer with multiple aliases (see Section 4.8.3, "Installing on Computers with Multiple Aliases"), or

• you are installing on a networked computer (with static IP or DHCP), but you want to be able to run Oracle Application Server when you take the computer off the network.

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

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

• Section 4.8.6.2, "Installing a Loopback Adapter on Windows 2000"

• Section 4.8.6.3, "Installing a Loopback Adapter on Windows 2003 or Windows XP"

• Section 4.8.6.4, "Checking the Hostname"

• Section 4.8.6.5, "Removing a Loopback Adapter on Windows 2000, Windows 2003, or 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

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

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

(You can install from remote CD-ROM or DVD-ROM drives; see Section 4.8.8, "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 (see Figure 4-3).

Accessing the Hard Drive from Other Computers

If you want to install Oracle Application Server on remote computers from the hard drive where you copied the contents of the CD-ROM or DVD-ROM, you have to do the following steps:

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

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

3. Run the installer from the remote computers where you want to install Oracle Application Server.

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

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

Space Requirement

Ensure that the hard drive contains enough space to hold the contents of the CD-ROMs or the application_server directory on the DVD-ROM. Each CD-ROM contains approximately 650 MB. This means that if you are copying three CD-ROMs, you need approximately 1.9 GB of disk space.

On the DVD-ROM, the application_server directory is approximately 1.6 GB.

This space is in addition to the space required for installing Oracle Application Server (listed in Table 4-2).

To Copy the CD-ROMs:

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

   You need to create a parent directory (called OracleAS_10g in the example, but you can name it anything you like), and, under the parent directory, create subdirectories called Disk1, Disk2, and so on. The names of the subdirectories must be DiskN, where N is the CD-ROM number.

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

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

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

   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:\OracleAS_10g\DiskN are the directories that you want to copy the CD-ROMs to.

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

To run the installer from the copied files, invoke the setup.exe executable from the Disk1 directory. Run it from the computer that will be running Oracle Application Server.

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

To Copy the application_server Directory from the DVD-ROM

You can copy the application_server 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 application_server directory.

2. Copy the application_server directory from the DVD-ROM to your hard disk.

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

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

To run the installer from the copied files, invoke the setup.exe executable from the computer that will be running Oracle Application Server:

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

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

If the computer where you want to install Oracle Application Server 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:

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

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

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

2. Start up Windows Explorer.

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

4. In the Sharing tab (Figure 4-4):

   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-ROM drive on the local computer. See step d.

   Click Permissions. You need at least "read" permission for the user who will be accessing it to install Oracle Application Server.

   Click OK when done.

   Figure 4-4 Sharing a CD-ROM Drive

   
   Description of "Figure 4-4 Sharing a CD-ROM Drive"
   
   

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

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

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

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

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

   1. Start up Windows Explorer on the local computer.

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

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

   4. In Folder, enter the location of the remote CD-ROM or DVD-ROM 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-ROM 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-ROM 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 that it created is not usable, and may need to be removed manually.

   
   

4.8.9 Installing on Remote Computers Through Remote Control Software

If you want to install and run Oracle Application Server on a remote computer (that is, the remote computer has the hard drive and will run Oracle Application Server 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 Application Server on the remote computer in one of two ways:

• If you have copied the contents of the Oracle Application Server CD-ROM or DVD-ROM to a hard drive, you can install from the hard drive.

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

Installing from a Hard Drive

If you have copied the contents of the Oracle Application Server CD-ROM or DVD-ROM to a hard drive, you can install from the hard drive.

The steps that you have to do are:

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

2. Share the hard drive that contains the Oracle Application Server CD-ROM or DVD-ROM.

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

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

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

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

The steps that you have to do are:

1. Make sure 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-ROM drive.

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

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

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