Oracle® Application Server Installation Guide 10g Release 3 (10.1.3.2.0) for Microsoft Windows Part Number B32197-01 |
|
|
View PDF |
Before installing Oracle Application Server, ensure that your computer meets the requirements described in this chapter.
Table 2-1 Sections in This Chapter
Section | Highlights |
---|---|
|
Describes how to find the most current requirements for Oracle Application Server 10g Release 3 (10.1.3.2.0). |
Section 2.2, "System Requirements" |
Lists requirements such as supported operating systems, processor speed, memory, disk space, and virtual memory. |
Section 2.3, "Requirements for Oracle Content Database" |
Lists the requirements for installing Oracle Content Database. |
Section 2.4, "Windows System Files (wsf.exe)" |
Describes how to run |
|
Describes how to configure components to use ports other than the default ports. |
Section 2.6, "Operating System User" |
Describes how to ensure that the user who will be doing the installation belongs to the Administrators group. |
Section 2.7, "Environment Variables" |
Describes how to set or unset environment variables required for installation. |
|
Describes network issues such as installing Oracle Application Server on a remote computer, or on a computer that uses DHCP, or even on a non-networked computer. |
Section 2.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. |
The Oracle Application Server 10g Release 3 (10.1.3.2.0) 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. From the resulting Web page, you can view the latest certifications by product, platform, and product availability.
Table 2-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 2-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 (Disk 1) or DVD-ROM (in the application_server
directory).
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 as well as written to a log file. For more information on the types of checks performed, see Section 2.9, "Prerequisite Checks Performed by the Installer".
Table 2-2 System Requirements
Item | Requirement |
---|---|
Microsoft Windows 2000 with Service Pack 3 or above Microsoft Windows Server 2003 (32-bit) with Service Pack 1 or above Microsoft Windows XP Professional with Service Pack 2 or above If you are running Windows XP with Service Pack 2, please see Document ID 280874.1 on the OracleMetaLink site ( Checked by Installer: Yes Note: Oracle Application Server can be installed on Windows operating systems that include Terminal Services. However, Oracle Application Server cannot be installed or controlled by the Terminal Services remote client. |
|
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 The following 64-bit operating systems are supported:
|
|
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; see the Oracle Application Server Administrator's Guide for details. Checked by Installer: No |
|
You can install Oracle Application Server on a computer that uses static IP or DHCP-based IP. Notes:
Checked by Installer: No |
|
Ensure that your hostnames are not longer than 255 characters. Checked by Installer: No |
|
300 MHz or higher Intel Pentium processor recommended For the Basic Installation and Advanced Installation: Oracle Content Database installation types, the processor speed should be at least 450 MHz, and 2 GHz or faster is recommended. Checked by Installer: Yes |
|
160 MB Notes:
Checked by Installer: Yes |
|
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 |
|
Basic Installation: 760 MB Advanced Installation
Checked by Installer: No |
|
55 MB to run the installer, but you need 150 MB to install Oracle Application Server. If the TEMP directory does not have enough free space, you can specify a different directory by setting the TEMP environment variable. See Section 2.7.4, "TEMP" for details. Checked by Installer: Yes |
|
512 MB of virtual memory 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): Windows 2000:
Windows XP / Windows 2003:
Checked by Installer: Yes |
|
256 color display Checked by Installer: Yes |
|
Oracle Enterprise Manager 10g Application Server Control is supported on the following browsers:
For the most current list of supported browsers, check the OracleMetaLink site ( Checked by Installer: No. However, if you access Oracle Enterprise Manager 10g using a non-supported browser, you will get a warning message. |
This section includes requirements for Oracle Content Database (Oracle Content DB), which is installed during a Basic Installation and Advanced Installation: Oracle Content Database. It includes the following topics:
Oracle Content DB supports three types of user repository: Oracle Internet Directory, a third-party LDAP server (such as iPlanet or Open LDAP), or a file-based user repository.
To use Oracle Internet Directory as your Oracle Content DB user repository, you must first install OracleAS Infrastructure, which contains Oracle Identity Management. Then, provide required details about Oracle Internet Directory during Oracle Content DB installation.
You can install Oracle Identity Management versions 10.1.2 and 10.1.4. When choosing Oracle Identity Management components, you must install at least Oracle Internet Directory.
See Also:
Oracle Content Database for Oracle WebCenter Suite Administrator's Guide for additional information about using Oracle Internet Directory as your Oracle Content DB user repository
Oracle Application Server Certification Information for the most up-to-date information about the Oracle Identity Management versions supported with Oracle Content DB
To use a third-party LDAP solution as your user repository for Oracle Content DB, you must first install the third-party LDAP server. Then, provide required details about your third-party LDAP server during Oracle Content DB installation.
Oracle Content DB supports the following third-party LDAP solutions:
Microsoft Windows Server 2003 Active Directory
Microsoft Windows Server 2000 Active Directory
Sun Java System Directory Server 5.2
OpenLdap 2.2
Novel eDirectory 8.73
See Also:
Oracle Application Server Certification Information for the most up-to-date information about the third-party LDAP server versions supported with Oracle Content DBThere are no preinstallation requirements if you choose to use a file-based user repository. To use a file-based user repository as your user repository for Oracle Content DB, select File-Based in the Specify User Repository screen during Oracle Content DB installation.
Oracle Content DB requires an Oracle Database version 10.1.0.5.0 or 10.2.0.2.0. Oracle Database version 9.2, as well as Oracle Database version 10.2 XE, are not supported. For the most up-to-date certification information, see Oracle Application Server Certification Information.
Refer to Chapter 2, "Preinstallation Tasks" in Oracle Database Installation Guide for complete information about hardware, software, and other requirements. In particular, refer to the following sections:
Section 2.1, "Oracle Database Hardware Requirements"
Section 2.2, "Oracle Database Software Requirements"
See Also:
Chapter 2, "Planning for Oracle Content DB Deployment" in Oracle Content Database for Oracle WebCenter Suite Administrator's Guide for additional information about database computer sizing requirements for Oracle Content DBThis section includes the following topics:
Section 2.3.2.1, "Setting the Required Database Character Set"
Section 2.3.2.3, "Firewall Requirement for Oracle Database on Windows"
Section 2.3.2.4, "Setting Required Database Initialization Parameters"
Section 2.3.2.5, "Using the Raw Storage Type with Oracle Content DB"
You must set the database character set to AL32UTF8 in order to use the database with Oracle Content DB.
To set the database character set during installation, choose the Advanced installation type (recommended). To set the database character set for an existing database, you can use the Database Configuration Assistant (DBCA) to re-create the database with the correct character set.
See Also:
Chapter 2, "Choosing a Character Set" and Chapter 11, "Character Set Migration" in Oracle Database Globalization Support Guide for additional information about setting or changing the database character set.You must configure a password file for the database in order to use the database with Oracle Content DB. See Oracle Database Administrator's Guide for information about how to do this.
If you do not set up a password file for the database, the Oracle Content DB installation will display an error.
If you are running Oracle Database on Windows, you must disable the firewall on the database computer before you install the Oracle Content DB middle tier. Otherwise, Oracle Content DB installation will fail. Be sure to enable the firewall again after completing Oracle Content DB middle-tier installation.
You must set initialization parameters for the Oracle Database you want to use with Oracle Content DB.
To set initialization parameters during installation, choose the Advanced installation type. Select Advanced on the Select Database Configuration screen. You can set the initialization parameters after the DBCA launches.
To set initialization parameters for an existing database, you can run the cdb_alter_system.sql
script, which is located on Oracle Application Server Disk 1 at the following location:
DRIVE_LETTER:\cdb_alter_system.sql
Alternatively, you can set initialization parameters manually using Oracle Enterprise Manager 10g Database Control to update the server parameter file.
See Also:
Section 5.2, "Logging In to Oracle Enterprise Manager Database Control" in Oracle Database Installation Guide for information about how to access the Database Control.You can also use the following SQL command to set individual parameters:
SQL> alter system set parameter_name=parameter_value scope=both;
For example:
SQL> alter system set shared_pool_size=184549376 scope=both;
Table 2-3 lists the required database initialization parameters for Oracle Content DB.
Table 2-3 Required Database Initialization Parameters for Oracle Content DB
Parameter Name | Minimum Value |
---|---|
aq_tm_processes |
1 |
db_recovery_file_dest_size |
2147483648 |
dml_locks |
200 |
job_queue_processes |
10 |
max_commit_propagation_delay |
0 This parameter was deprecated in Oracle Database 10g 10.2. If you are using a 10.2 database, you do not need to set this parameter. |
open_cursors |
400 |
processes |
250 |
remote_login_passwordfile |
EXCLUSIVE |
session_max_open_files |
50 |
sessions |
400 |
undo_management |
AUTO |
|
INTERPRETED |
db_create_file_dest |
Set this parameter to identify the default location for the database server to create the following files:
The following example sets DB_CREATE_FILE_DEST = '/u01/oradata' Note: Do not set this parameter if the storage is in raw volumes. If you are using the Raw storage type, you must create required tablespaces before installing Oracle Content DB. See Section 2.3.2.5, "Using the Raw Storage Type with Oracle Content DB" for more information. |
If you choose to use raw devices for database file storage, you must create tablespaces manually before installing Oracle Content DB. Table 2-4 shows the minimum size of each tablespace.
Table 2-4 Minimum Tablespace Sizes for Oracle Content DB
Tablespace Name | Minimum Size |
---|---|
|
60MB |
|
270MB |
|
270MB |
|
10MB |
|
10MB |
|
15MB |
|
130MB |
|
10MB |
For more information about the tablespaces used by Oracle Content DB, see Chapter 2, "Planning for Oracle Content DB Deployment" in Oracle Content Database for Oracle WebCenter Suite Administrator's Guide.
To create tablespaces manually, you can issue the create tablespace
SQL command. Example 2-1 shows a command to create the CONTENT_IFS_MAIN
tablespace, with a size of 270 MB.
You may need to upgrade your Oracle Database to one of the versions certified with Oracle Content DB. If you upgrade, make sure to read the upgrade documentation carefully, follow all instructions, and perform all required post-upgrade tasks. Otherwise, you may encounter problems. Post-upgrade tasks may include running the following scripts:
catupgrd.sql
(10.2.0.2)
utlrp.sql
(10.2.0.2)
changePerm.sh
(10.2.0.2)
catpatch.sql
(10.1.0.5)
Refer to the database upgrade documentation for additional details.
You can download database patches from OracleMetaLink at:
http://metalink.oracle.com
If you have a support contract with Oracle, the steps to download a patch from the OracleMetaLink site are:
Log in to OracleMetaLink.
Click Patches & Updates.
Ensure that Patch Number is selected in the Simple Search list, then enter the required patch number in the adjacent field.
If you do not know the patch number that you need to download, select Product or Family in the Simple Search list.
Select the appropriate operating system from the Platform or Language list.
Click Go.
Under Results, click View Readme to go through the information in the readme before downloading the patch. Then, return to the Results page and click Download to download the patch.
Make sure to stop all database processes before applying database patches. After the upgrade completes, you need to run root.sh
. Refer to the patch upgrade documentation for additional details; follow all instructions, and perform all required post-upgrade tasks.
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:
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-ROM (assumes E: is the DVD-ROM drive):
E:\> cd application_server E:\> wsf.exe
Follow the screens in the installer:
Table 2-5 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. |
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.
Many Oracle Application Server components, such as Oracle HTTP Server, use ports. You can have the installer assign default port numbers, or use port numbers that you specify.
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.
One Application Server process, Oracle HTTP Server SSL, uses ports in the ephemeral port range. This process cannot start up if the port that it needs is 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 2.5.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 postinstallation.) 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.
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.
If you want to use the default port numbers for components, you do not have to do anything. See Appendix C, "Default Port Numbers" for a list of the default port numbers and ranges. Make sure that at least one port is available in the port range for each component. If the installer is unable to find a free port in the range, the installation will fail.
Note the following points:
The installer assigns the default ports to components only if the ports are not in use by other applications. If the default port is in use, the installer tries other ports in the port number range for the component. For example, the default non-SSL port for Oracle HTTP Server is port 80. If this port is in use by another application, the installer assigns a port in the 7777 - 7877 range.
The installer no longer checks the services
file to determine if a port is in use. In earlier releases, the installer would not assign a port number if the port number is listed in the file.
The services
file is located in the C:\
%SystemRoot%
\system32\drivers\etc
directory, where %SystemRoot%
is winnt
on Windows 2000, and windows
on Windows XP and Windows 2003.
To instruct the installer to assign custom port numbers for components:
Create a file containing the component names and port numbers. Section 2.5.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.
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.
The staticports.ini
file has the following format. Replace port_num with the port number that you want to use for the component.
Oracle HTTP Server port = port_num Oracle HTTP Server SSL port = port_num Oracle Notification Server Request port = port_num Oracle Notification Server Local port = port_num Oracle Notification Server Remote port = port_num ASG 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:
Copy the staticports.ini
file from the CD-ROM or DVD-ROM to your hard disk.
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.
The following example sets the Oracle HTTP Server ports and some Oracle Process Manager and Notification Server ports. For components not specified, the installer will assign the default port numbers.
Oracle HTTP Server port = 2000 Oracle HTTP Server SSL port = 2001 Oracle Notification Server Request port = 2002 Oracle Notification Server Local port = 2003
When installation is complete, you can run the following commands to see the assigned ports:
C:\> ORACLE_HOME/opmn/bin/opmnctl startall C:\> ORACLE_HOME/opmn/bin/opmnctl status -l
Notes on Choosing Port Numbers:
Port numbers cannot be greater than 65535.
If you plan to set port numbers for Oracle HTTP Server, be sure you read Section 2.5.4.3, "Ports for Oracle HTTP Server".
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:
Edit the staticports.ini
file to specify a different port, or shut down the application that is using the port.
Click Retry. The installer re-reads the staticports.ini
file and verifies the entries in the file again.
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.
Be sure you understand the following when setting ports for this component.
In the httpd.conf
file for Oracle HTTP Server, the Port
and the Listen
directives specify the ports used by Oracle HTTP Server (Figure 2-1). 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
Figure 2-1 Configuring Oracle HTTP Server
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:
Display the Computer Management dialog.
On Windows 2000 or Windows XP: Right-click My Computer on the desktop and select Manage.
On Windows 2003: Right-click the local computer icon on the desktop and select Manage.
On the left side, expand Local Users and Groups, and select Users.
On the right side, right-click the user and select Properties. This displays the Properties dialog.
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.
The operating system user who will be installing Oracle Application Server needs to set (or unset) the following environment variables.
Table 2-7 summarizes whether you set or unset an environment variable.
Table 2-7 Environment Variable Summary
Environment variable | Set or Unset |
---|---|
|
Must not be longer than 1023 characters. |
|
Must not be set. |
|
Optional. If unset, defaults to |
This section describes how to set environment variables in Windows:
Display the System control panel.
On Windows 2000: Select Start > Settings > Control Panel > System.
On Windows 2003: Select Start > Control Panel > System.
On Windows XP: Select Start > Control Panel, then double-click System.
Select the Advanced tab.
Click Environment Variables.
To change the value of a variable, select the variable and click Edit.
The PATH environment variable cannot be longer than 1023 characters. Otherwise, the installation may fail.
Ensure that the TNS_ADMIN environment variable is not set when you run the installer. If set, it can cause errors during installation.
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 2-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.
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:
Section 2.8.2, "Installing on Multihomed (Multi-IP) Computers"
Section 2.8.3, "Installing on Computers with Multiple Aliases"
Section 2.8.7, "Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive"
Section 2.8.8, "Installing from a Remote CD-ROM or DVD-ROM Drive"
Section 2.8.9, "Installing on Remote Computers Through Remote Control Software"
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:
Install a loopback adapter on the DHCP computer.
When you install a loopback adapter, the loopback adapter assigns a local IP for your computer. Having a loopback adapter and a local IP address means that you do not have to run the chgiphost
script after installation each time the IP address changes (due to DHCP).
Which Is the Primary Network Adapter?
Windows considers loopback adapters as a type of network adapter. After installing a loopback adapter on your computer, you have at least two network adapters on your computer: your network adapter and the loopback adapter.
You want Windows to use the loopback adapter as the primary adapter. The primary adapter is determined by the order in which you installed the adapters:
On Windows 2000, the primary adapter is the last adapter installed. You can just install the loopback adapter. However, if you install additional network adapters after you install the loopback adapter, you need to deinstall the loopback adapter and reinstall it.
To install a loopback adapter on the different Windows platforms, see Section 2.8.6, "Installing a Loopback Adapter".
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.
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.
You can install Oracle Application Server 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. You can set the hostname used by the Oracle Universal Installer by running the installer with the OUI_HOSTNAME
variable. For example:
CD-ROM (assumes E: is the CD-ROM drive):
E:\> setup.exe OUI_HOSTNAME=hostname
DVD-ROM (assumes E: is the DVD-ROM drive):
E:\> cd application_server E:\application_server> setup.exe OUI_HOSTNAME=hostname
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 2.7.1, "How to Set Environment Variables".
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 2.7.1, "How to Set Environment Variables".
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 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.
Install a loopback adapter on the computer. See Section 2.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.
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, theping
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.
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:
Install a loopback adapter on your computer. See Section 2.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.
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 2.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.
A loopback adapter is required in any of these scenarios:
you are installing on a DHCP computer (see Section 2.8.1, "Installing on DHCP Computers"), or
you are installing on a non-networked computer and plan to connect the computer to a network after installation (see Section 2.8.4, "Installing on Non-Networked Computers"), or
you are installing on a computer with multiple aliases (see Section 2.8.3, "Installing on Computers with Multiple Aliases"), or
you are installing on a networked computer (with static IP or DHCP), but you want to be able to run Oracle Application Server when you take the computer off the network.
The procedure for installing a loopback adapter depends on the version of Windows:
Section 2.8.6.1, "Checking If a Loopback Adapter Is Installed on Your Computer"
Section 2.8.6.2, "Installing a Loopback Adapter on Windows 2000"
Section 2.8.6.3, "Installing a Loopback Adapter on Windows 2003 or Windows XP"
Section 2.8.6.5, "Removing a Loopback Adapter on Windows 2000, Windows 2003, or Windows XP"
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
Windows 2000 reports on the last network adapter installed. This means that if you install additional network adapters after you install the loopback adapter, you need to remove and reinstall the loopback adapter. The loopback adapter must be the last network adapter installed on the computer.
To install a loopback adapter on Windows 2000:
From the Start menu, select Settings, then Control Panel.
Double-click Add/Remove Hardware to start the Add/Remove Hardware wizard.
In the Welcome window, click Next.
In the Choose a Hardware Task window, select Add/Troubleshoot a device, and click Next.
In the Choose a Hardware Device window, select Add a new device, and click Next.
In the Find New Hardware window, select No, I want to select the hardware from a list, and click Next.
On the Hardware Type window, select Network adapters, and click Next.
In the Select Network Adapter window, do the following:
Manufacturers: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
In the Start Hardware Installation window, click Next.
In the Completing the Add/Remove Hardware Wizard window, click Finish.
Right-click My Network Places on the desktop and choose Properties. This displays the Network and Dial-up Connections control panel.
Right-click the connection that was just created. This is usually "Local Area Connection 2". Choose Properties.
On the General tab, select Internet Protocol (TCP/IP), and click Properties.
In the Properties dialog box, click Use the following IP address and do the following:
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
Subnet mask: Enter 255.255.255.0
.
Record the values you entered, which you will need later in this procedure.
Leave all other fields empty.
Click OK.
Close the Network Connections window.
Restart the computer.
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
Check the network configuration:
Open System in the Control Panel, and select the Network Identification tab.
In Full computer name, make sure you see the host name and the domain name, for example, sales.us.mycompany.com
.
Click Properties.
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
.
Click More. In Primary DNS suffix of this computer, the domain name, for example, us.mycompany.com
, should appear.
Exit the System Control Panel.
To install a loopback adapter on Windows 2003 or Windows XP:
Open the Windows Control Panel.
Windows 2003: Select Start > Control Panel > Add Hardware.
Windows XP: Select Start > Control Panel, then double-click Add Hardware.
In the Welcome window, click Next.
In the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.
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.
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.
In the From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.
In the Select Network Adapter window, make the following selections:
Manufacturer: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
In the The wizard is ready to install your hardware window, click Next.
In the Completing the Add Hardware Wizard window, click Finish.
If you are using Windows 2003, restart your computer.
Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.
Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.
On the General tab, select Internet Protocol (TCP/IP), and click Properties.
In the Properties dialog box, click Use the following IP address and do the following:
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
Subnet mask: Enter 255.255.255.0
.
Record the values you entered, which you will need later in this procedure.
Leave all other fields empty.
Click OK.
Click OK in the Local Area Connection 2 Properties dialog.
Close Network Connections.
Restart the computer.
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
Check the network configuration:
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
.
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
.
Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.mycompany.com
.
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.
To remove a loopback adapter on Windows 2000, Windows 2003, or Windows XP:
Display the System control panel.
Windows 2000: Select Start > Settings > Control Panel, then double-click System.
Windows 2003: Select Start > Control Panel > System.
Windows XP: Select Start > Control Panel, then double-click System.
In the Hardware tab, click Device Manager.
In the Device Manager windows, expand Network adapters. You should see Microsoft Loopback Adapter.
Right-click Microsoft Loopback Adapter and select Uninstall.
Click OK.
Instead of installing from the Oracle Application Server CD-ROMs or DVD-ROM, you can copy the contents of the CD-ROMs or DVD-ROM to a hard drive and install from there. This might be easier if you plan to install many instances of Oracle Application Server on your network, or if the computers where you want to install Oracle Application Server do not have CD-ROM or DVD-ROM drives.
(You can install from remote CD-ROM or DVD-ROM drives; see Section 2.8.8, "Installing from a Remote CD-ROM or DVD-ROM Drive".)
When you install from the hard drive, the installer does not prompt you to swap CD-ROMs. It can find all the files if they are in the proper locations (see Figure 2-2).
Accessing the Hard Drive from Other Computers
If you want to install Oracle Application Server on remote computers from the hard drive where you copied the contents of the CD-ROM or DVD-ROM, you have to do the following steps:
On the local computer, share the hard drive.
On the computers where you want to install Oracle Application Server, map to the shared hard drive.
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:\WC_101320_1\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-2).
To Copy the CD-ROMs:
Create a directory structure on your hard drive as shown in Figure 2-2.
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 Disk
N
, where N
is the CD-ROM number.
Figure 2-2 Directory Structure for Copying CD-ROMs to Disk
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\Disk
N
are the directories that you want to copy the CD-ROMs to.
E:\> xcopy /e /i E:\WC_101320_1 C:\OracleAS_10g\Disk1 E:\> xcopy /e /i E:\WC_101320_2 C:\OracleAS_10g\Disk2 ... Repeat for each CD-ROM.
To run the installer from the copied files, invoke the setup.exe
executable from the Disk1
directory. Run it from the computer that will be running Oracle Application Server.
C:\> cd OracleAS_10g\Disk1 C:\OracleAS_10g\Disk1> setup.exe
To Copy the application_server Directory from the DVD-ROM
You can copy the application_server
directory using Windows Explorer or the command line. If you are using the command line, here are the steps:
(optional) Create a directory to contain the application_server
directory.
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
If the computer where you want to install Oracle Application Server does not have a CD-ROM or DVD-ROM drive, you can perform the installation from a remote CD-ROM or DVD-ROM drive. Check that you have performed these steps:
On the Remote Computer, Share the CD-ROM or DVD-ROM Drive
The remote CD-ROM or DVD-ROM drive that you want to use must allow shared access. To set this up, perform these steps on the remote computer (which has the CD-ROM or DVD-ROM drive):
Log in to the remote computer as an Administrator user.
Start up Windows Explorer.
Right-click the CD-ROM or DVD-ROM drive letter and choose Sharing (Windows 2000) or Sharing and Security (Windows 2003, Windows XP).
In the Sharing tab (Figure 2-3):
Select Share this folder.
Share name: Give it a share name such as cdrom
or dvd
. You will use this name when you map the CD-ROM or DVD-ROM drive on the local computer. See step d.
Click Permissions. You need at least "read" permission for the user who will be accessing it to install Oracle Application Server.
Click OK when done.
CD-ROM: Insert Oracle Application Server Disk 1 into the CD-ROM drive.
DVD-ROM: Insert the Oracle Application Server DVD-ROM into the DVD-ROM drive.
On the Local Computer, Map the CD-ROM or DVD-ROM Drive
Perform these steps on the local computer to map the CD-ROM or DVD-ROM drive and to run the installer:
Map the remote CD-ROM or DVD-ROM drive.
Start up Windows Explorer on the local computer.
Select Tools > Map Network Drive. This displays the Map Network Drive dialog.
Select a drive letter to use for the remote CD-ROM or DVD-ROM drive.
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
If you need to connect to the remote computer as a different user:
Click different user name, and enter the username.
Click Finish.
Run the installer from the mapped CD-ROM or DVD-ROM drive.
When the installer prompts you to switch CD-ROMs, eject the CD-ROM and insert the requested CD-ROM.
Note:
The installer must be running when you are switching CD-ROMs. Do not exit the installer when switching CD-ROMs. If you exit the installer, it is unable to continue from where it left off. In addition, the partial installation that it created is not usable, and may need to be removed manually.If you want to install and run Oracle Application Server on a remote computer (that is, the remote computer has the hard drive and will run Oracle Application Server components), but you do not have physical access to the computer, you can still perform the installation on the remote computer if it is running remote control software such as VNC or Symantec pcAnywhere. You also need the remote control software running on your local computer.
You can install Oracle Application Server on the remote computer in one of two ways:
If you have copied the contents of the Oracle Application Server CD-ROM or DVD-ROM to a hard drive, you can install from the hard drive.
You can insert the CD-ROM or DVD-ROM into a drive on your local computer, and install from the CD-ROM or DVD-ROM.
Installing from a Hard Drive
If you have copied the contents of the Oracle Application Server CD-ROM or DVD-ROM to a hard drive, you can install from the hard drive.
The steps that you have to do are:
Make sure that the remote control software is installed and running on the remote and local computers.
Share the hard drive that contains the Oracle Application Server CD-ROM or DVD-ROM.
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.
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.8.8, "Installing from a Remote CD-ROM or DVD-ROM Drive".
The steps that you have to do are:
Make sure that the remote control software is installed and running on the remote and local computers.
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.8.8, "Installing from a Remote CD-ROM or DVD-ROM Drive".
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.
Table 2-8 lists the checks performed by the installer:
Table 2-8 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 2-2 for supported versions. |
Windows service pack |
See Table 2-2 for supported service packs. |
Memory |
See Table 2-2 for recommended values. |
Total pagefile (virtual memory) size |
See Table 2-2 for recommended values. |
Space in TEMP directory |
See Table 2-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. |
Oracle home directory |
You should install Oracle Application Server in a new directory. Here are some examples of installations that are not allowed:
|
Static port conflicts |
The installer checks the ports listed in the |
Cluster file system |
The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS). |