Skip Headers
Oracle® Application Server Installation Guide
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium
B25331-01
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

3 Requirements

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

Table 3-1 Sections in This Chapter

Section Highlights

Section 3.1, "Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and Software Requirements"


Describes how to find the most current requirements for Oracle Application Server 10g Release 2 (10.1.2).

Section 3.2, "System Requirements"


Lists requirements such as supported operating systems, processor speed, memory, disk space, and swap space.

Section 3.3, "Windows System Files (wsf.exe)"


Describes how to run wsf.exe to update Windows system files. Applicable only if the installer prompts you to do so.

Section 3.4, "Ports"


Describes how to configure components to use ports other than the default ports.

Section 3.5, "Operating System User"


Describes why you should create an operating system user to install Oracle Application Server.

Section 3.6, "Environment Variables"


Describes how to set or unset environment variables required for installation.

Section 3.7, "The %WINDIR%\system32\drivers\etc\hosts File"


Describes how the installer uses the information in the hosts file. This section also describes how to specify the same information without editing the file.

Section 3.8, "Network Topics"


Describes network issues such as installing Oracle Application Server on a remote computer, using a remote CD-ROM/DVD drive, or installing from a hard disk.

Section 3.9, "Prerequisite Checks Performed by the Installer"


Lists the items checked by the installer, such as length of the Oracle home name and whether or not the Oracle home directory already contains another Oracle product.


3.1 Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and Software Requirements

The Oracle Application Server 10g (10.1.2.0.2) hardware and software requirements included in this guide were accurate at the time this manual was released to manufacturing. For the most up-to-date information about hardware and software requirements, refer to OracleMetaLink:

http://metalink.oracle.com/

After logging into OracleMetaLink, click Certify and Availability. From the resulting Web page, you can view the latest certifications by product, platform, and product availability.

3.2 System Requirements

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

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

CD-ROM (assumes E: is the CD-ROM drive):

E:\> setup.exe -executeSysPrereqs

DVD (assumes E: is the DVD drive):

E:\> cd application_server
E:\application_server> setup.exe -executeSysPrereqs

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

Table 3-2 System Requirements

Item Requirement

Operating system

Microsoft Windows 2003 (64 bit) with Service Pack 1 or later

Checked by Installer: Yes

64-bit Certification

The 32-bit version of Oracle Application Server for Windows runs on Intel x86, AMD64, and Intel EM64T processors. For additional information, visit OracleMetaLink at http://metalink.oracle.com.

The following 64-bit operating systems are supported:

  • Microsoft Windows XP Professional x64 Edition

  • Microsoft Windows Server 2003, Standard x64 Edition

  • Microsoft Windows Server 2003, Enterprise x64 Edition

  • Microsoft Windows Server 2003, Datacenter x64 Edition

Note: All products and components except OracleAS Infrastructure are certified on AMD64 and Intel EM64T processors.

Network

You can install Oracle Application Server on a computer that is connected to a network, or on a "standalone" computer (not connected to the network).

If you are installing Oracle Application Server on a standalone computer, you can connect the computer to a network after installation. You have to perform some configuration tasks when you connect it to the network.

Refer to Oracle Application Server Administrator's Guide for details.

Checked by Installer: No

IP

You can install Oracle Application Server on a computer that uses static IP or DHCP-based IP.

Notes:

Checked by Installer: No

Hostname

Ensure that your hostnames are not longer than 255 characters.

Processor Speed

Intel Itanium 2 (900 MHz or higher)

Checked by Installer: No

Memory

OracleAS Infrastructure:

  • OracleAS Metadata Repository and Oracle Identity Management: 3.7GB

  • Oracle Identity Management only: 1.25 GB

  • OracleAS Metadata Repository only: 3.7 GB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 846 MB

  • Portal and Wireless: 1.2 GB

  • Business Intelligence and Forms: 1.7 GB

OracleAS Developer Kits: 256 MB

Note:

  • The installer checks the amount of memory on your computer and will warn you if your computer does not meet the minimum memory requirements.

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

  • These are minimum values that are enough to install and run Oracle Application Server. For most production sites, you should configure at least 512 MB of physical memory. For sites with substantial traffic, increasing the amount of memory further may improve performance. For Java applications, you should either increase the maximum heap allocated to the OC4J processes or configure additional OC4J processes to utilize this memory. See Oracle Application Server Performance Guide for details.

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

Checked by Installer: Yes

File system type

NTFS is recommended over FAT32 or FAT file system types because NTFS includes security features such as enforcing permission restrictions on files.

Checked by Installer: No

Disk space

OracleAS Infrastructure:

  • OracleAS Metadata Repository and Oracle Identity Management: 3.07 GB

    You can install the data files for the OracleAS Metadata Repository database on a disk that is different from the disk where you are installing OracleAS Infrastructure. If you do this, make sure the disk for the data files has at least 1.85 GB of free space.

  • Oracle Identity Management only: 1.25 GB

  • OracleAS Metadata Repository only: 3.7 GB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 846 MB

  • Portal and Wireless: 1.2 GB

  • Business Intelligence and Forms: 1.7 GB

OracleAS Developer Kits: 256 MB

Checked by Installer: No

Space in TEMP directory

55 MB to run the installer, but you need 256 MB to install certain installation types.

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

Checked by Installer: Yes

Total Pagefile size (Virtual Memory)

These values are estimates. You should use the values recommended by Windows based on the amount of memory on your computer.

OracleAS Infrastructure:

  • OracleAS Metadata Repository and Oracle Identity Management: 1 GB

  • Oracle Identity Management only: 1 GB

  • OracleAS Metadata Repository only: 1 GB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 512 MB

  • Portal and Wireless: 512 MB

  • Business Intelligence and Forms: 1 GB

OracleAS Developer Kits: 512 MB

If you plan to use OracleAS Personalization, you must use a pagefile size that is at least 1.5 times the amount of physical memory on your computer.

If you plan to use OracleAS Clusters, Oracle recommends a minimum of 1 GB.

In a production environment, Oracle recommends a minimum of 1 GB.

To view and change the total pagefile size (virtual memory):

  1. Display the System control panel.

    To do this, select Start > Control Panel > System.

  2. Select the Advanced tab.

  3. Click Settings in the Performance section.

  4. Select the Advanced tab.

  5. Click Change to review and change the virtual memory setting.

Checked by Installer: Yes

Monitor

256 color display

Checked by Installer: Yes

Supported browsers

Oracle Enterprise Manager 10g is supported on the following browsers:

  • Microsoft Internet Explorer 6.0 (supported on Microsoft Windows only)

  • Netscape 7.2

  • Mozilla 1.7. You can download Mozilla from http://www.mozilla.org.

  • Firefox 1.0.4. You can download Firefox from http://www.mozilla.org.

  • Safari 1.2 (on Apple Macintosh computers)

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

Checked by Installer: No. However, if you access Oracle Enterprise Manager 10g using a non-supported browser, you will get a warning message.


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

Table 3-3 Memory and Pagefile Requirements for Running Multiple Instances on the Same Computer

Description Memory Pagefile

OracleAS Infrastructure plus J2EE and Web Cache

1 GB

1.5 GB

OracleAS Infrastructure plus Portal and Wireless

1.5 GB

2.0 - 2.5 GB

OracleAS Infrastructure plus Business Intelligence and Forms

1.5 GB

2.0 - 2.5 GB


3.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. Refer to 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. Refer to Oracle Application Server Administrator's Guide for details.

3.3 Windows System Files (wsf.exe)


Note:

Perform this procedure only if prompted by the installer.

Oracle Application Server requires minimum versions of some system files in the Windows system directory (typically C:\Windows\system32 or C:\Winnt\system32). When you run the installer for Oracle Application Server, the installer checks the Windows system files on your computer. If it finds old versions of these files, and the files are in use by other processes, then it prompts you to exit the installer and run wsf.exe to install the latest Windows system files. (If it finds old versions of the files, but the files are not in use by other processes, then it just replaces the files and you do not have to run wsf.exe.)

You can find wsf.exe in the same directory as the installer.

To run wsf.exe, which you need to do only if prompted by the installer, perform these steps:

  1. Start wsf.exe, which starts up Oracle Universal Installer to install the Windows system files.

    CD-ROM (assumes E: is the CD-ROM drive):

    E:\> wsf.exe
    
    

    DVD (assumes E: is the DVD drive):

    E:\> cd application_server
    E:\> wsf.exe
    
    
  2. Follow the screens in the installer:

    Table 3-4 Screens for Installing Windows System Files


    Screen Action

    1.

    Welcome

    Click Next.

    2.

    Specify File Locations

    Destination Name: Enter a name for the Oracle home for wsf.

    Destination Path: Enter any full path. The installer installs the files in the proper system directories, regardless of the value you enter in this field.

    Click Next.

    3.

    Warning: System Reboot Required

    If you see this screen, the installer will reboot your computer automatically at the end of this installation to complete the Windows system files installation. Save and close applications (other than this installer) that you have running on your computer.

    Click Next.

    4.

    Summary

    Click Next to start installing the Windows system files.

    5.

    End of Installation

    Click Exit to exit the installer.


  3. If the installer displayed the "Warning: System Reboot Required" screen during installation, the installer now reboots your computer. If not, please reboot your computer before continuing.

3.4 Ports

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

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

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

3.4.3 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, 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 3-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 3-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 3-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 dose not checks the services file to determine if a port is in use.

    The services file is located in the C:\%SystemRoot%\system32\drivers\etc directory, where %SystemRoot% is winnt on 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:

Table 3-6 Oracle HTTP Server Ports in Different Scenarios

Scenario Non-SSL Port SSL Port

OracleAS Infrastructure and a middle tier installed on the same computer

Oracle HTTP Server on the OracleAS Infrastructure: 7777

Oracle HTTP Server on the middle tier: 80

Oracle HTTP Server on the OracleAS Infrastructure: 4443

Oracle HTTP Server on the middle tier: 443

Two middle tiers installed on the same computer

Oracle HTTP Server on the first middle tier: 80

Oracle HTTP Server on the second middle tier: 7777

Oracle HTTP Server on the first middle tier: 443

Oracle HTTP Server on the second middle tier: 4443


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

3.4.4.1 Format of the staticports.ini File

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

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

# Business Intelligence and Forms
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
Ultra Search HTTP port number = port_num

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

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

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

    Media Location of staticports.ini File (assumes E: is your CD-ROM or DVD drive)

    CD-ROM

    Disc 1: E:\stage\Response\staticports.ini

    DVD

    E:\application_server\stage\Response\staticports.ini


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

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

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

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

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

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


Notes on Choosing Port Numbers:


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

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

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

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

Using portlist.ini as the staticports.ini File

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

However, note this difference: in staticports.ini, the line "Oracle Management Agent port" corresponds to "Enterprise Manager Agent port" in portlist.ini.

3.4.4.2 Error Conditions that Will Cause the Installer to Use Default Ports Instead of Specified Ports

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

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

  • If you specify different ports for one component on multiple lines, the installer assigns the default port for the component. The installer does not warn you if you have specified different ports for one component.

  • If you specify the same port for one component on multiple lines, the installer assigns the default port for the component. The installer does not warn you if you have specified the same port on multiple lines.

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

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

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

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

3.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 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 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 3-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

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

Figure 3-2 Configuring Only Oracle HTTP Server

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

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


Note:

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

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

3.4.5.1 If Port 1521 Is In Use by an Existing Oracle Database

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

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

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

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

Version of the Existing Listener Existing Listener Uses Port 1521 Existing Listener Uses a Port Other Than 1521

Earlier than 10.1.0.2

You need two listeners: one for the existing database and one for the OracleAS Metadata Repository.

You need two listeners: one for the existing database and one for the OracleAS Metadata Repository.

10.1.0.2 or later

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

You need two listeners: one for the existing database and one for the OracleAS Metadata Repository.


To check the listener version, run the following command:

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

where ORACLE_HOME is the home directory for your database.

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

Here is an example of the command's output:

C:\OraHome_1\BIN>lsnrctl VERSION
LSNRCTL for 64-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 64-bit Windows: Version 10.1.0.4.2 - Production
        TNS for 64-bit Windows: Version 10.1.0.4.0 - Production
        Oracle Bequeath Windows 2003 Protocol Adapter for 64-bit Windows: Version 10.1.0.4.0 - Production
        Windows 2003 Named Pipes NT Protocol Adapter for 64-bit Windows: Version 10.1.0.4.0 - Production
        Windows 2003 TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.1.0.4.0 - Production,,
The command completed successfully

3.4.5.2 If Port 1521 Is In Use by Some Other Application

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

3.5 Operating System User

The operating system user performing the installation must belong to the Administrators group.


Note:

The user must be listed directly in the Administrators group. The user cannot belong to the Administrators group indirectly (for example, by being a member of a group that is part of the Administrators group).

Perform the following steps to check if you belong to the Administrators group:

  1. Display the Computer Management dialog.

    On Windows 2003: Right-click the local computer icon on the desktop and select Manage.

  2. On the left side, expand Local Users and Groups, and select Users.

  3. On the right side, right-click the user and select Properties. This displays the Properties dialog.

  4. In the Properties dialog, select the Member Of tab.

If you are not a member of the Administrators group, get an administrator to add you to the group or log in as a user who is a member of the Administrators group.

3.6 Environment Variables

The operating system user who will be installing Oracle Application Server needs to set (or unset) the following environment variables.

Table 3-9 summarizes whether you set or unset an environment variable.

Table 3-9 Environment Variable Summary

Environment variable Set or Unset

ORACLE_HOME and ORACLE_SID


Must not be set.

PATH


Must not be longer than 1023 characters.

TNS_ADMIN


Must not be set.

TEMP


Optional. If unset, defaults to C:\temp.


3.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 2003: Select Start > Control Panel > System.

  2. Select the Advanced tab.

  3. Click Environment Variables.

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

3.6.2 ORACLE_HOME and ORACLE_SID

These environment variables must not be set.

3.6.3 PATH

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

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

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

3.7 The %WINDIR%\system32\drivers\etc\hosts File

Although the contents of the %WINDIR%\system32\drivers\etc\hosts file affect these items:

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

%WINDIR% specifies the Windows operating system directory. Typically, it is C:\WINDOWS for Windows 2003.

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


Tip:

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

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


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

3.8 Network Topics

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

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

3.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 2003, 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 3.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.

3.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 3.6.1, "How to Set Environment Variables".

3.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 3.6.1, "How to Set Environment Variables".

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

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

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

3.8.6 Installing a Loopback Adapter

A loopback adapter is required in any of these scenarios:

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

3.8.6.1 Checking If a Loopback Adapter Is Installed on Your Computer

To check if a loopback adapter is installed on your computer, run the "ipconfig /all" command:

prompt> ipconfig /all

If there is a loopback adapter installed, you would see a section that lists the values for the loopback adapter. For example:

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.8.6.2 Installing a Loopback Adapter on Windows 2003

To install a loopback adapter on Windows 2003:

  1. Open the Windows Control Panel.

    Windows 2003: Select Start > Control Panel > System.

  2. Double-click Add Hardware to start the Add Hardware wizard.

  3. In the Welcome window, click Next.

  4. In the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.

  5. In the The following hardware is already installed on your computer window, in the list of installed hardware, select Add a new hardware device, and click Next.

  6. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

  7. In the From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.

  8. In the Select Network Adapter window, make the following selections:

    • Manufacturer: select Microsoft.

    • Network Adapter: select Microsoft Loopback Adapter.

  9. Click Next.

  10. In the The wizard is ready to install your hardware window, click Next.

  11. In the Completing the Add Hardware Wizard window, click Finish.

  12. If you are using Windows 2003, restart your computer.

  13. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.

  14. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

  15. On the General tab, select Internet Protocol (TCP/IP), and click Properties.

  16. In the Properties dialog box, click Use the following IP address and do the following:

    1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

      • 192.168.x.x (x is any value between 1 and 255)

      • 10.10.10.10

    2. Subnet mask: Enter 255.255.255.0.

    3. Record the values you entered, which you will need later in this procedure.

    4. Leave all other fields empty.

    5. Click OK.

  17. Click OK in the Local Area Connection 2 Properties dialog.

  18. Close Network Connections.

  19. Restart the computer.

  20. Add a line to the C:\winnt\system32\drivers\etc\hosts file with the following format, right after the localhost line:

    IP_address   hostname.domainname   hostname
    
    

    where:

    • IP_address is the non-routable IP address you entered in step 14.

    • hostname is the name of the computer.

    • domainname is the name of the domain.

    For example:

    10.10.10.10   mycomputer.mydomain.com   mycomputer
    
    
  21. Check the network configuration:

    1. Open System in the Control Panel, and select the Computer Name tab. In Full computer name, make sure you see the host name and the domain name, for example, sales.us.mycompany.com.

    2. Click Change. In Computer name, you should see the host name, and in Full computer name, you should see the host name and domain name. Using the previous example, the host name would be sales and the domain name would be us.mycompany.com.

    3. Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.mycompany.com.

3.8.6.3 Checking the Hostname

If your DHCP server also assigns the hostname for your computer (in addition to assigning an IP address), the installer might use this hostname instead of the hostname you defined locally.

To ensure that the installer uses the local hostname, you have two options:

  • Option 1: Start up the installer with the OUI_HOSTNAME parameter. This parameter specifies the hostname that you want to use.

    E:\> setup.exe OUI_HOSTNAME=myhostname.mydomain.com
    
    
  • Option 2: Before running the installer, add a line to the C:\winnt\system32\drivers\etc\hosts file with the following format:

    IP_address   hostname.domainname   hostname
    
    

    This line should come after the localhost line in the file.

    Replace IP_address with the loopback adapter's IP address. This should be a non-routable IP address.

    Replace hostname and domainname with the appropriate values.

    Example:

    10.10.10.10   mycomputer.mydomain.com   mycomputer
    
    

If you have already installed Oracle Application Server, you can change the hostname after installation using the change IP/hostname procedures documented in the Oracle Application Server Administrator's Guide.

3.8.6.4 Removing a Loopback Adapter on Windows 2003

To remove a loopback adapter on Windows 2003:

  1. Display the System control panel.

    Windows 2003: Select Start > Control Panel > System.

  2. In the Hardware tab, click Device Manager.

  3. In the Device Manager windows, expand Network adapters. You should see Microsoft Loopback Adapter.

  4. Right-click Microsoft Loopback Adapter and select Uninstall.

  5. Click OK.

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

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

(You can install from remote CD-ROM or DVD drives; see Section 3.8.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 (see Figure 3-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, 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. Each CD-ROM contains approximately 650 MB. This means that if you are copying 4 CD-ROMs, you need approximately 2.1 GB of disk space.

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

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

To Copy the CD-ROMs:

  1. Create a directory structure on your hard drive as shown in Figure 3-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 3-3 Directory Structure for Copying CD-ROMs to Disk

    Description of Figure 3-3  follows
    Description of "Figure 3-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

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 to your hard disk.

    The example assumes E: is the DVD 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

3.8.8 Installing from a Remote CD-ROM or DVD Drive

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

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 (which has the CD-ROM or DVD 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 drive letter and choose Sharing or Sharing and Security (Windows 2003).

  4. In the Sharing tab (Figure 3-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 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 3-4 Sharing a CD-ROM Drive

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

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

    DVD: Insert the Oracle Application Server 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.

    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 that it created is not usable, and may need to be removed manually.

3.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 to a hard drive, 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 Application Server CD-ROM or DVD 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.

  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 Drive

You can insert the CD-ROM or DVD into a drive on your local computer, and install from the CD or DVD. This is similar to the scenario described in Section 3.8.8, "Installing from a Remote CD-ROM or DVD 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 drive.

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

    These steps are described in Section 3.8.8, "Installing from a Remote CD-ROM or DVD 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 drive.

3.9 Prerequisite Checks Performed by the Installer

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

Table 3-10 Prerequisite Checks Performed by the Installer

Item Description

User

The installer checks that the user has administrative privileges.

Monitor

The installer checks that the monitor is configured to display at least 256 colors.

Operating system version

See Table 3-2 for supported versions.

Windows service pack

See Table 3-2 for supported service packs.

Memory

See Table 3-2 for recommended values.

Total pagefile (virtual memory) size

See Table 3-2 for recommended values.

Space in TEMP directory

See Table 3-2 for recommended values.

Instance name

The installer checks that the computer on which you are installing Oracle Application Server does not already have an instance of the same name.

Oracle home directory name

The installer checks that the Oracle home directory name does not contain any spaces.

Path to the Oracle home directory

The installer checks that the path to the Oracle home directory is not longer than 127 characters.

Oracle home directory contents

The installer checks that the Oracle home directory does not contain any files that might interfere with the installation.

Port 1521

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

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

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

Static port conflicts

The installer checks the ports listed in the staticports.ini file, if specified. See Section 3.4, "Ports".

DBCA_RAW_CONFIG environment variable

If you are installing the OracleAS Infrastructure in a Real Application Clusters environment, you need to set this environment variable to point to a file that describes the locations of your raw partitions.

Cluster file system

The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS).

Oracle Enterprise Manager 10g directories are writable

The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:

  • %ORACLE_HOME%\sysman\emd

  • %ORACLE_HOME%\sysman\config

  • %ORACLE_HOME%\sysman\webapps\emd\WEB-INF\config

Oracle Enterprise Manager 10g files exist

The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that these files exist:

  • %ORACLE_HOME%\sysman\config\iasadmin.properties

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