|
Oracle® Application Server Installing and Getting Started with Standard Edition One
10g Release 2 (10.1.2) for Microsoft Windows (32 Bit) Part No. B15881-02 |
|
![]() Previous |
![]() Next |
Before installing Oracle Application Server Standard Edition One, ensure that your computer meets the requirements described in this chapter.
The following topics are covered:
Table 2-1 lists the system requirements for running Oracle Application Server Standard Edition One. The installer checks many of these requirements at the start of the installation process (before the Oracle Universal Installer GUI is launched) and warns you if any of them is not met. When this happens, you have the option of stopping the installation, or fixing the problem and then continuing.
To save time, you can manually check only the requirements that are not checked by the installer. Refer to Table 2-1 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 by the installer, see Section 2.7.
Table 2-1 System Requirements
| Item | Requirement |
|---|---|
|
Oracle Application Server Standard Edition One is supported on several versions of the Microsoft Windows operating system. For the most current list of supported operating systems, as well as Windows Terminal Services support, check the OracleMetaLink site ( Checked by Installer: Yes |
|
|
You can install Oracle Application Server Standard Edition One 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 Standard Edition One 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 Standard Edition One 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. |
|
|
300 MHz or higher Intel Pentium processor recommended Checked by Installer: Yes |
|
|
J2EE and Web Services: 512 MB OracleAS Portal:
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 |
|
|
J2EE and Web Services: 450 MB OracleAS Portal:
Checked by Installer: Yes. |
|
|
55 MB to run the installer, 256 MB for the installation. 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.4.5, " Checked by Installer: Yes |
|
|
These values are estimates. You should use the values recommended by Windows based on the amount of memory on your computer. J2EE and Web Services: 1.5 GB OracleAS Portal:
In a production environment, Oracle recommends a minimum of 1.5 GB. To view and change the total pagefile size (virtual memory): Windows 2000:
Windows XP / Windows 2003:
Checked by Installer: Yes. If this check does not pass initially, the installation will pause, asking you if you want to continue. You can change the virtual memory size as described above, then answer "y" to continue with the installation. |
|
|
256 color display. Checked by Installer: Yes |
|
|
Oracle Enterprise Manager Application Server Control and Oracle Instant Portal have various browser support requirements. For the most current list of supported browsers, check the OracleMetaLink site ( Checked by Installer: No. However, if you access Oracle Enterprise Manager Application Server Control or Oracle Instant Portal using a non-supported browser, you will get a warning message. |
If you need to reduce memory consumption:
Configure only the components that you need.
After installation, start up only the components that you need. See the Oracle Application Server Administrator's Guide for details.
Run Application Server Control only when you need to administer an instance. In most cases, you do not need Application Server Control running all the time.
|
Note: Perform this procedure only if prompted by the installer. |
Oracle Application Server Standard Edition One requires minimum versions of some system files in the Windows system directory (typically C:\Windows\system32 or C:\Winnt\system32). When the installer is run, it 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-2 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.
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 Standard Edition One needs to set (or unset) the following environment variables.
Table 2-3 summarizes whether you set or unset an environment variable.
Table 2-3 Environment Variable Summary
| Environment variable | Set or Unset |
|---|---|
|
|
Must not be set. |
|
|
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.
PATH Environment Variable
During the installation, the installer will update the PATH environment variable. Upon completion, the PATH environment variable cannot be longer than 1023 characters. Otherwise, you may receive a warning, or the installation may fail. If you receive a warning, you can shorten the PATH environment variable at that time.
TNS_ADMIN Environment Variable
Ensure that the TNS_ADMIN environment variable is not set when you run the installer. If set, it can cause errors during installation. Section H.3.11, "Database Configuration Assistant (DBCA) Failures" shows such an error.
TEMP Environment Variable
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-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.
Although the contents of the %WINDIR%\system32\drivers\etc\hosts file affect these items:
Section 2.5.1, "Location of the Default Identity Management Realm"
Section 2.5.2, "Hostname for Oracle Application Server Single Sign-On"
the installer provides alternative methods for you to enter the values that you want without editing the hosts file. See the following subsections for details.
%WINDIR% specifies the Windows operating system directory. Typically, it is C:\WINDOWS for Windows 2003, and C:\WINNT for Windows 2000.
The installer reads the hosts file to construct the location of the default Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.
The hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname
Example:
123.45.67.89 primaryHost.mydomain.com primaryHost
In the preceding example, the location of the default Identity Management realm would look like "dc=mydomain,dc=com".
If the file uses a different format, the installer displays an incorrect value in the screen. For example, if the hosts file contains:
123.45.67.89 primaryHost primaryHost.mydomain.com <--- incorrect format
the installer would display "dc=primaryHost,dc=com" as the default Identity Management realm. This is probably not the value that you want for the default Identity Management realm.
|
Tip: If you need thehosts file to use a different format, you can edit the file to use the required format, perform the installation, then revert the file back to its original format after installation.
If you are unable, or unwilling, to edit the |
For Oracle Application Server Single Sign-On, if your hosts file contains only the hostname of your computer (without the domain name), then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).
If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:
E:\> setup.exe OUI_HOSTNAME=myserver.mydomain.com
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.6.2, "Installing on Computers with Multiple IP Addresses"
Section 2.6.3, "Installing on Computers with Multiple Aliases"
Section 2.6.7, "Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive"
Section 2.6.8, "Installing from a Remote CD-ROM or DVD-ROM Drive"
Section 2.6.9, "Installing on Remote Computers Through Remote Control Software"
This section discusses the installation of Oracle Application Server Standard Edition One on DHCP computers.
Oracle Application Server Standard Edition One instances on DHCP computers cannot communicate with other instances running on other computers. For example, you cannot have a Metadata Repository 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 Standard Edition One 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).
Ping the computer where you plan to install Oracle Application Server Standard Edition One.
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.
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.6.6, "Installing a Loopback Adapter".
A computer with multiple IP addresses is usually configured with multiple network cards on that computer. Each IP address, in turn, is associated with a hostname. Additionally, you can set up aliases for the hostname.
When you install Oracle Application Server Standard Edition One on a computer with multiple IP addresses, the installer configures Oracle Application Server Standard Edition One 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.
How Windows determines the primary network adapter is described in Section 2.6.1.2.
If you want to use a network adapter that is not the primary adapter, 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
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 Standard Edition One on such computers, you must:
Install a loopback adapter on the computer
Make sure the loopback adapter is the primary network adapter
The loopback adapter ensures that when Oracle Application Server Standard Edition One 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 Windows determines which adapter is the primary adapter, see Section 2.6.1.2.
For steps on how to install a loopback adapter, see Section 2.6.6.
You can install Oracle Application Server Standard Edition One on a non-networked computer, such as a laptop. To do so, 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 Standard Edition One 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 Standard Edition One 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 Standard Edition One on the non-networked computer.
Install a loopback adapter on the computer. For more information, see Section 2.6.6.
The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Oracle Application Server Standard Edition One 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 Standard Edition One 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 Standard Edition One on a networked computer with static IP and you want to be able to run Oracle Application Server Standard Edition One when you disconnect the computer from the network, you need to do the following steps before installation:
Install a loopback adapter on your computer. For more information, see Section 2.6.6.
Without a loopback adapter, Oracle Application Server Standard Edition One 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. For more information, see Section 2.6.1.2. 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.6.1.
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.6.1).
You are installing on a non-networked computer and plan to connect the computer to a network after installation (see Section 2.6.4).
You are installing on a computer with multiple aliases (see Section 2.6.3).
You are installing on a networked computer (with static IP or DHCP), but you want to be able to run Oracle Application Server Standard Edition One when you take the computer off the network.
The procedure for installing a loopback adapter depends on the version of Windows:
Section 2.6.6.1, "Checking If a Loopback Adapter Is Installed on Your Computer"
Section 2.6.6.2, "Installing a Loopback Adapter on Windows 2000"
Section 2.6.6.3, "Installing a Loopback Adapter on Windows 2003 or Windows XP"
Section 2.6.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:
Select Start > Settings > Control Panel.
Double-click Add/Remove Hardware. This starts up the Add/Remove Hardware wizard.
"Welcome page": Click Next.
"Choose a Hardware Task" page: Select Add/Troubleshoot a device, and click Next.
"Choose a Hardware Device" page: Select Add a new device, and click Next.
"Find New Hardware" page: Select No, I want to select the hardware from a list, and click Next.
"Hardware Type" page: Select Network adapters, and click Next.
"Select Network Adapter" page
Manufacturers: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
"Start Hardware Installation" page: Click Next.
"Completing the Add/Remove Hardware Wizard" page: 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 (Figure 2-1), 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.
Click OK in the Local Area Connection 2 Properties dialog.
Restart the computer.
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 non-routable IP address you entered in step 14.
Replace hostname and domainname with the appropriate values.
Example:
10.10.10.10 mycomputer.mydomain.com mycomputer
Check the network configuration:
Open the System control panel, and select the Network Identification tab. In Full computer name, make sure you see the hostname and the domain name (Figure 2-2).
Click Properties. In Computer name, you should see the hostname, and in Full computer name, you should see the hostname and domain name (Figure 2-3).
Click More. In Primary DNS suffix of this computer, you should see the domain name (Figure 2-4).
To install a loopback adapter on Windows 2003 or Windows XP:
Select Start > Control Panel.
Double-click Add Hardware. This starts up the Add Hardware wizard.
"Welcome" page: Click Next.
"Is the hardware connected?" page: Select Yes, I have already connected the hardware, and click Next.
"The following hardware is already installed on your computer" page: Select Add a new hardware device, and click Next.
"The wizard can help you install other hardware" page: Select Install the hardware that I manually select from a list, and click Next.
"From the list below, select the type of hardware you are installing" page: Select Network adapters, and click Next.
"Select Network Adapter" page
Manufacturer: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
"The wizard is ready to install your hardware": Click Next.
"Completing the Add Hardware Wizard" page: Click Finish.
(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 "Local Area Connection 2". Choose Properties.
On the General tab, select Internet Protocol (TCP/IP), and click Properties.
In the Properties dialog (Figure 2-1), 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.
Click OK in the Local Area Connection 2 Properties dialog.
Restart the computer.
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 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
Check the network configuration:
Open the System control panel, and select the Computer Name tab. In Full computer name, make sure you see the hostname and the domain name.
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-3).
Click More. In Primary DNS suffix of this computer, you should see the domain name (Figure 2-4).
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.
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.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 (see Figure 2-5).
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:\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:
Create a directory structure on your hard drive as shown in Figure 2-5.
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-5 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_10_1_2\DiskN are the directories that you want to copy the CD-ROMs to.
E:\> xcopy /e /i E:\1012disk1 C:\OracleAS_SEOne\Disk1 E:\> xcopy /e /i E:\1012disk2 C:\OracleAS_SEOne\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 Standard Edition One.
C:\> cd OracleAS_SEOne\Disk1 C:\OracleAS_SEOne\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 Standard Edition One:
C:\> cd application_server C:\application_server> setup.exe
If the computer where you want to install Oracle Application Server Standard Edition One 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-6):
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 Standard Edition One Disk 1 into the CD-ROM drive.
DVD-ROM: Insert the Oracle Application Server Standard Edition One 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 Standard Edition One 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 Standard Edition One on the remote computer in one of two ways:
If you have copied the contents of the Oracle Application Server Standard Edition One 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.
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.
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".
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.6.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-4 lists the checks performed by the installer:
Table 2-4 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-1 for supported versions. |
|
Windows service pack |
See Table 2-1 for supported service packs. |
|
Processor speed |
See Table 2-1 for recommended values. |
|
Memory |
See Table 2-1 for recommended values. |
|
Total pagefile (virtual memory) size |
See Table 2-1 for recommended values. |
|
Space in TEMP directory |
See 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. For more information about instance names, see Section 1.4.3. |
|
Oracle home directory name |
The installer checks that the Oracle home directory name does not contain any spaces. For more information about Oracle home names, see Section 1.4.2.1. |
|
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 recommends that you 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. If it is a database listener that is using port 1521, you might be able to use it for the metadata repository database. See Section 1.4.8 for details. If it is another application that is using port 1521, you need to stop it or configure it to use a different port. Alternatively, you can change the database listener to use a port other than 1521, but you can do this only after installation. See the Oracle Application Server Administrator's Guide for details. |
|
Static port conflicts |
The installer checks the ports listed in the |