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

2 Requirements

Before installing Oracle Application Server, ensure that your computer meets the requirements described in this chapter. This chapter contains the following sections:

2.1 System Requirements

Table 2-1 lists the system requirements for installing and 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 2-1 to see what 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 (Disk 1), or in the application_server directory of the DVD-ROM.

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

E:\> setup.exe -executeSysPrereqs

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

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

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

Table 2-1 System Requirements

Item Requirement
Operating System Microsoft Windows Server 2003 Enterprise Edition for 64-bit Intel Itanium 2 systems

Microsoft Windows XP 64-bit Edition Version 2003

Microsoft Windows Server 2003 Datacenter Edition for 64-bit Intel Itanium 2 systems

Checked by Installer: Yes

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, then you can connect the computer to a network after installation. To connect it to the network, you have to perform some configuration tasks. For details, refer to Oracle Application Server Administrator's Guide.

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.
Memory Oracle Application Server Middle Tier:

  • J2EE and Web Cache: 400 MB

Notes:

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

  • 400 MB is the minimum memory requirement to install and run Oracle Application Server. For most production sites, you should configure at least 1 GB 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. For further details, refer to Oracle Application Server Performance Guide.

  • 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 the memory requirement 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 Oracle Application Server Middle Tier:

  • J2EE and Web Cache:400 MB

Checked by Installer: No

Space in TEMP directory 140 MB.

If the TEMP directory does not have enough free space, then you can specify a different directory by setting the TEMP environment variable. For details, refer to Section 2.5.5, "TEMP".

Checked by Installer: Yes

Total Pagefile size (Virtual Memory) The following values are estimates. You should use the values recommended by Microsoft Windows corresponding to the memory on your computer.

Oracle Application Server Middle Tier:

  • J2EE and Web Cache: 512 MB

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.

    On Microsoft Windows XP, select Start, Control Panel, then double-click System.

    On Microsoft Windows 2003, select Start, Control Panel, and System.

  2. Click the Advanced tab.

  3. Click the Performance Options button.

  4. 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 is supported on the following browsers:

  • Microsoft Internet Explorer 5.5, 6.0 (supported on Microsoft Windows only).

  • Microsoft Internet Explorer 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 (supported on Microsoft Windows XP with SP2). This is the version packaged with SP2.

  • Netscape 7.1, 7.2.

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

    Note that Firefox, the standalone Mozilla browser, is currently not certified.

  • Safari 1.2 (supported on Apple Macintosh computers).

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


2.1.1 Tips for Reducing Memory Usage

To reduce memory consumption:

  • Configure only the components that you need.

  • After installation, start up only the components that you need. For further details, refer to Oracle Application Server Administrator's Guide.

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

2.2 Microsoft 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 Microsoft Windows system directory (typically C:\Windows\system32). When you run the installer for Oracle Application Server, the installer checks the Microsoft 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 Microsoft 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 the following steps:

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

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

    E:\> wsf.exe

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

    E:\> cd application_server
E:\> wsf.exe

  2. Follow the screens in the installer in the order mentioned in Table 2-2.

    Table 2-2 Screens for Installing Microsoft Windows System Files


    		 Screen Action
    1. Welcome Click Next.
    2. Specify File Locations Destination Name: Enter a name for the Oracle home for wsf.exe.

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

    Click Next.

    3. Warning: System Reboot Required If you see this screen, then the installer will restart your computer automatically at the end of this installation to complete the Microsoft Windows system files installation. Save and close applications (other than this installer) that are running on computer.

    Click Next.

    4. Summary Click Next to start installing the Microsoft 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, then the installer now restarts your computer. If not, then please restart your computer before continuing.

2.3 Ports

Many Oracle Application Server components, such as Oracle HTTP Server, OracleAS Web Cache, and Oracle Enterprise Manager, use ports. You can have the installer assign default port numbers, or specify the port numbers yourself. Further details are discussed in the following topics.

2.3.1 About Ephemeral Ports

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

On rare occasions, Oracle Application Server processes are unable to start up because required ports are not available. Processes may either 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. Client processes, usually, are unconcerned with the port value being used on the client side. So 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 through 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 Microsoft Windows uses a small range of ports for ephemeral client connections.

Ephemeral Port Range

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

Only the upper end of this range is adjustable in Microsoft 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 of the Application Server processes, including Oracle HTTP Server, OracleAS Web Cache, Oracle Enterprise Manager Application Server Control, and Oracle Application Server Containers for J2EE, use ports in the ephemeral port range. These processes cannot start up if the ports that they need are already in use by clients.

How to Avoid Conflicts with Ephemeral Ports

To avoid conflicts with ephemeral ports, you have the following 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 less than 1024 or higher than 5000.

    For details, refer to Section 2.3.4, "Using Custom Port Numbers (the Static Ports Feature)".

  • If you have already installed Oracle Application Server, then you can reconfigure the components to use ports less than 1024 or higher than 5000. Refer to 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 mentioned earlier. This option is the least preferred because it makes changes to the Microsoft Windows registry, and it affects all products that you run on the 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. In this case, you must relocate them to the new ReservedPorts range (refer to the following paragraph), higher than the new ephemeral range, or less than port 1024.

    To implement this option, perform the following steps:

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

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

      For the detailed procedure, refer to 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 the detailed procedure, refer to 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 have the following ranges: 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.

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

2.3.3 Using Default Port Numbers

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

Note the following points:

  • The installer assigns default ports to components only if the ports are not in use by other applications. If the default port is in use, then 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, then the installer assigns a port in the range 7777 through 7877.

  • Default ports for Oracle HTTP Server depend on the installation type (Table 2-3). The Middle Tier gets ports 80 and 443 because it is where you would deploy your applications. Requests would be sent to the Middle Tier Oracle HTTP Server or OracleAS Web Cache to access the applications.

    In Table 2-3, 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 2-3 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 does not check 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 windows on Microsoft Windows XP and Microsoft Windows 2003.

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

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

2.3.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
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
Enterprise Manager 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

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

  1. Copy the staticports.ini file from the CD-ROM or DVD-ROM to the computer.

  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, then the installer uses the default port number for that component.

    The following example sets the Application Server Control port and some OracleAS Web Cache ports. For components not specified, the installer will assign 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.

The installer verifies that the ports specified in the file are available by checking memory. Only ports that are being used by running processes are detected. The configuration files are not checked to determine which ports an application is using.

The installer will not assign a port that is not available. If the installer detects that a specified port is not available, then it displays an alert. 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, then you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

2.3.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. Following are some things that you should check:

  • If you specify the same port for more than one component, then the installer will use the specified port for the first component only. For the other components, it will use default ports. The installer does not display a warning if you have specified the same port for multiple components.

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

  • If you misspell a component name, then 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, then the installer ignores the line and assigns the default port number for the component. The installer does not display a warning for lines with non-numeric values.

  • If you specify a relative path to the staticports.ini file, then 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.

2.3.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 Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server respectively. The correct lines in the staticports.ini file for setting these ports depend on which components you are configuring.

To Configure 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 2-1). To set this port, use the following 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, then the Oracle HTTP Server port line is ignored. For example, if you have the following lines in the staticports.ini file: 

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

    then 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 the following 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 2-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

Description of ports_wc.gif follows
Description of the illustration ports_wc.gif

To Configure Oracle HTTP Server Without OracleAS Web Cache

If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives (Figure 2-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, then they will be ignored because you are not configuring OracleAS Web Cache.

Figure 2-2 Configuring Only Oracle HTTP Server

Description of ports_no_wc.gif follows
Description of the illustration ports_no_wc.gif

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

    On Microsoft Windows XP: Right-click My Computer on the desktop, and select Manage.

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

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

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

  4. In the Properties dialog box, click the Member Of tab.

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

2.5 Environment Variables

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

Table 2-4 summarizes whether you set or unset an environment variable.

Table 2-4 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.
TNS_ADMIN
Optional. If not set, then defaults to C:\temp

2.5.1 How to Set Environment Variables

This section describes how to set environment variables in Microsoft Windows:

  1. Display the System control panel.

    On Microsoft Windows 2003: Select Start, Control Panel, System.

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

  2. Click the Advanced tab.

  3. Click Environment Variables.

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

2.5.2 ORACLE_HOME and ORACLE_SID

These environment variables must not be set.

2.5.3 PATH

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

2.5.4 TNS_ADMIN

Ensure that the TNS_ADMIN environment variable is not set when you run the installer. If set, then it can cause errors during installation.

2.5.5 TEMP

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

If you want the installer to use a directory other than /tmpC:\temp, then set the TEMP environment variable to the full path of an alternate directory. This directory must meet the requirements listed in Table 2-1.

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.

2.6 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-ROM drive.

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

2.6.1 Installing on DHCP Computers

Note the following 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. 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 the following steps:

  1. Install a loopback adapter on the DHCP computer.

    When you install a loopback adapter, it 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?

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

    To install a loopback adapter on a different Microsoft Windows platforms, refer to Section 2.6.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, then 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.

2.6.2 Installing on Multihomed (Multi-IP) Computers

A multihomed computer is associated with multiple IP addresses. This is typically achieved by multiple network cards on the computer. Each IP address is associated with a hostname, and in addition, you can set up aliases for the hostname.

When you install Oracle Application Server on a multihomed computer, the installer configures Oracle Application Server to use the hostname/IP address on the primary network adapter.

Clients must be able to access the computer using this hostname (or aliases for this hostname). To check, ping the hostname from the client computers using the short name (hostname only) and the full name (hostname.domainname). Both must work.

For details on how Microsoft Windows determines the primary network adapter, refer to "Which Is the Primary Network Adapter?".

If you want to use a network adapter that is not the primary adapter, then start up the installer with the OUI_HOSTNAME command-line parameter. Specify the hostname that you want to use in the parameter. For example:

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

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

2.6.3 Installing on Computers with Multiple Aliases

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

Before installing Oracle Application Server on such computers, you must do the following:

  • Install a loopback adapter on the computer

  • Ensure the loopback adapter is the primary network adapter

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

To learn how Microsoft Windows determines which adapter is the primary adapter, refer to "Which Is the Primary Network Adapter?".

For steps on how to install a loopback adapter, refer to Section 2.6.6, "Installing a Loopback Adapter".

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

Note that to install Oracle Application Server on a non-networked computer, the computer must, however, 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, then you can install Oracle Application Server on your non-networked computer.

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

  1. Install a loopback adapter on the computer. Refer to Section 2.6.6, "Installing a Loopback Adapter".

    The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, then 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, then 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 consult your network administrator.

Connecting the Computer to a Network After Installation

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

For details, refer to Oracle Application Server Administrator's Guide.

2.6.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, then you need to do the following steps before installing Oracle Application Server:

  1. Install a loopback adapter on your computer. For details, refer to Section 2.6.6, "Installing a Loopback Adapter".

    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. Ensure the loopback adapter is the primary network adapter. Refer to "Which Is the Primary Network Adapter?". To check, ping the computer from itself using only the hostname, and only the fully qualified name.

    For example, if you installed a loopback adapter on a computer called mycomputer, then you can run the following 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, refer to Section 2.6.1, "Installing on DHCP Computers".

2.6.6 Installing a Loopback Adapter

A loopback adapter is required in any of the following scenarios:

The procedure for installing a loopback adapter depends on the version of Microsoft Windows. The following sections explain the requirements:

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

2.6.6.2 Installing a Loopback Adapter on Microsoft Windows 2003 or Microsoft Windows XP

To install a loopback adapter on Microsoft Windows 2003 or Microsoft Windows XP:

  1. Select Start, Control Panel.

  2. Double-click Add Hardware. This starts up the Add Hardware wizard.

  3. In the Welcome screen, click Next.

  4. Select Yes, I have already connected the hardware, and click Next.

  5. Select Add a new hardware device, and click Next.

  6. Select Install the hardware that I manually select from a list, and click Next.

  7. Select Network adapters, and click Next.

  8. From the Manufacturer list, select Microsoft.

    From the Network Adapter list, select Microsoft Loopback Adapter.

    Click Next.

  9. The wizard is ready to install your hardware. Click Next.

  10. Click Finish to complete the Add Hardware wizard.

  11. If you are a Microsoft Windows 2003 user, then you must restart your computer.

  12. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections control panel.

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

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

    Figure 2-3 Internet Protocol (TCP/IP) Properties Dialog Box Showing Values for the Loopback Adapter

    Description of tcpip_2000.gif follows
    Description of the illustration tcpip_2000.gif

  15. In the Properties dialog box (Figure 2-3), enter the following values:

    IP Address: Enter a non-routable IP for the loopback adapter. The following non-routable addresses are recommended:

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

    • 10.10.10.10

    Subnet mask: Enter 255.255.255.0

    Leave all other fields empty.

    Click OK.

  16. Click OK in the Local Area Connection 2 Properties dialog box.

  17. Restart the computer.

  18. Add a line to the file, C:\windows\system32\drivers\etc\hosts, 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 non-routable IP address you entered in step 15.

    Replace hostname and domainname with the appropriate values.

    Example: 

    10.10.10.10   mycomputer.mydomain.com   mycomputer

  19. Check the network configuration:

    1. Select Start, Control Panel. Double-click System, and click the Computer Name tab. In Full computer name, make sure you see the hostname and the domain name.

    2. Click Change. In Computer name, you should see the hostname, and in Full computer name, you should see the hostname and domain name (Figure 2-5).

    3. Click More. In Primary DNS suffix of this computer, you should see the domain name.

2.6.6.3 Checking the Hostname

If your DHCP server also assigns the hostname for your computer (in addition to assigning an IP address), then 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:\windows\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, then you can change the hostname after installation using the Change IP/Hostname procedures documented in Oracle Application Server Administrator's Guide.

2.6.6.4 Removing a Loopback Adapter on Microsoft Windows 2003 or Microsoft Windows XP

To remove a loopback adapter on Microsoft Windows 2003 or Microsoft Windows XP:

  1. Display the System control panel.

    Microsoft Windows 2003: Select Start, Control Panel, System.

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

  2. In the Hardware tab, click Device Manager.

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

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

2.6.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 also install from remote CD-ROM or DVD-ROM drives. For details, refer to Section 2.6.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 (refer to Figure 2-4).

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, then 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 2-1).

To Copy the CD-ROMs:

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

    You need to create a parent directory (called OracleAS_10g_10_1_2 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 2-4 Directory Structure for Copying CD-ROMs to Disk

    Description of copyToDisk.gif follows
    Description of the illustration copyToDisk.gif

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

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

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

    E:\> xcopy /e /i  E:\1012disk1  C:\OracleAS_10g_10_1_2\Disk1
E:\> xcopy /e /i  E:\1012disk2  C:\OracleAS_10g_10_1_2\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_10_1_2\Disk1
C:\OracleAS_10g_10_1_2\Disk1> setup.exe

To Copy the application_server Directory from the DVD-ROM

You can copy the application_server directory using Microsoft Windows Explorer or the command line. If you are using the command line, then perform the following 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

2.6.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, then you can perform the installation from a remote CD-ROM or DVD-ROM drive. Check that you have performed the following 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 the following 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 Microsoft Windows Explorer.

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

  4. In the Sharing tab (Refer to Figure 2-5):

    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. Refer to 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 2-5 Sharing a CD-ROM Drive

    Description of cdrom_share.gif follows
    Description of the illustration cdrom_share.gif

  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 the following 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 Microsoft Windows Explorer on the local computer.

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

    3. Select a drive letter to use for the remote CD-ROM or DVD-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. Windows 2003, Windows XP: To connect to the remote computer as a different user, click different user name, and enter the username.

    6. Click Finish (Windows 2003, Windows XP).

  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, then it will be 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.

2.6.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, if the remote computer has the hard drive and will run Oracle Application Server components), but you do not have physical access to the computer, then you can do it 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, then 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, then you can install from the hard drive.

Perform the following steps:

  1. Make sure that the remote control software is installed and running on both 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 2.6.8, "Installing from a Remote CD-ROM or DVD-ROM Drive".

Perform the following steps:

  1. Make sure that the remote control software is installed and running on both 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 2.6.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.

2.7 Prerequisite Checks Performed by the Installer

Table 2-5 lists the checks performed by the installer:

Table 2-5 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 Refer to Table 2-1 for supported versions.
Microsoft Windows service pack Refer to Table 2-1 for supported service packs.
Memory Refer to Table 2-1 for recommended values.
Total pagefile (virtual memory) size Refer to Table 2-1 for recommended values.
Space in TEMP directory Refer to Table 2-1 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.
Oracle home directory You should install Oracle Application Server in a new directory.
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 box.

If another application is using port 1521, then 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. Refer to Oracle Application Server Administrator's Guide for details.

Static port conflicts The installer checks the ports listed in the staticports.ini file, if specified. Refer to Section 2.3, "Ports".
Cluster file system The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS).
Oracle Enterprise Manager directories are writable The installer runs this check only if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that the following directories are writable by the operating system user running the installer:

  • ORACLE_HOME\sysman\emd

  • ORACLE_HOME\sysman\config

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

Oracle Enterprise Manager files exist The installer runs this check only if you are reinstalling Oracle Application Server in the same Oracle home. The installer checks that the following files exist:

  • ORACLE_HOME\sysman\config\iasadmin.properties

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


  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents		 Go To Index
Index