|
Oracle® Application Server Forms and Reports Services Installation Guide
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25338-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Forms and Reports Services Installation Guide
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25338-01 |
|
|
Previous |
Next |
Before installing Forms and Reports Services, ensure that your computer meets the requirements described in this chapter.
This chapter contains the following sections:
Table 3-1 lists the system requirements for running Forms and reports services. The installer checks many of these requirements at the start of the installation process and displays a warning if any of the requirement is not met.
You can also run the system checks performed by running the setup.exe command. The setup.exe command is on the Forms and Reports Services CD-ROM (Disk 1) or DVD (in the application_server directory).
CD-ROM (assumes E: is the CD-ROM drive):
E:\> setup.exe -executeSysPrereqs
DVD (assumes E: is the DVD drive):
E:\> cd application_server E:\application_server> setup.exe -executeSysPrereqs
The results are displayed on the screen as well as written to a log file. For more information on the types of checks performed, see Section 3.8, "Prerequisite Checks Performed by the Installer".
It contains the following sections:
Table 3-1 System Requirements
| Item | Requirement |
|---|---|
|
Microsoft Windows 2003 (64 bit) with Service Pack 1 or later Checked by Installer: Yes |
|
|
64-bit Certification |
The 32-bit version of Oracle Application Server for Windows runs on Intel x86, AMD64, and Intel EM64T processors. For additional information, visit OracleMetaLink at The following 64-bit operating systems are supported:
Note: All products and components except OracleAS Infrastructure 10g are certified on AMD64 and Intel EM64T processors. |
|
You can install Oracle Application Server on a computer that is connected to a network, or on a "standalone" computer (not connected to the network). If you are installing Oracle Application Server on a standalone computer, you can connect the computer to a network after installation. You have to perform some configuration tasks when you connect it to the network. Refer to Oracle Application Server Administrator's Guide for details. Checked by Installer: No |
|
|
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. |
|
|
Intel Itanium 2 (900 MHz or higher) Checked by Installer: No |
|
|
OracleAS Infrastructure:
Oracle Application Server middle tier:
OracleAS Developer Kits: 256 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 |
|
|
OracleAS Infrastructure:
Oracle Application Server middle tier:
OracleAS Developer Kits: 256 MB Checked by Installer: No |
|
|
55 MB to run the installer, but you need 256 MB to install certain installation types. If the TEMP directory does not have enough free space, you can specify a different directory by setting the TEMP environment variable. See Section 3.5.4, "TEMP" for details. 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. OracleAS Infrastructure:
Oracle Application Server middle tier:
OracleAS Developer Kits: 512 MB If you plan to use OracleAS Personalization, you must use a pagefile size that is at least 1.5 times the amount of physical memory on your computer. If you plan to use OracleAS Clusters, Oracle recommends a minimum of 1 GB. In a production environment, Oracle recommends a minimum of 1 GB. To view and change the total pagefile size (virtual memory):
Checked by Installer: Yes |
|
|
256 color display Checked by Installer: Yes |
|
|
Oracle Enterprise Manager 10g 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. |
If you plan to run OracleAS Infrastructure and a middle tier on the same computer, ensure the computer meets the memory and pagefile requirements listed in Table 3-2.
The pagefile values below were suggested by Windows based on the amount of memory on the computer. Use the value suggested for your computer.
Note that these values have been tested against a small number of users. If you have many users, you might have to increase the amount of memory.
Table 3-2 Memory and Pagefile Requirements for Running Multiple Instances on the Same Computer
| Description | Memory | Pagefile |
|---|---|---|
|
OracleAS Infrastructure plus J2EE and Web Cache |
1 GB |
1.5 GB |
|
OracleAS Infrastructure plus Portal and Wireless |
1.5 GB |
2.0 - 2.5 GB |
|
OracleAS Infrastructure plus Business Intelligence and Forms |
1.5 GB |
2.0 - 2.5 GB |
If you need to reduce memory consumption:
After installation, use Oracle Enterprise Manager to stop services not used. This reduces the memory usage. For details, see the Oracle Application Server Administrator's Guide.
For OracleAS Reports Services, you can control the JVM heap size by specifying small values using the REPORTS_JVM_OPTIONS environment variable.
For Reports Engine, the JVM options are specified in the server_name.conf file in the jvmoptions attribute of the engine element. If specified, the JVM options set in server_name.conf override the value of the REPORTS_JVM_OPTIONS environment variable. If not specified in server_name.conf, Oracle Reports uses the JVM options specified by the REPORTS_JVM_OPTIONS environment variable. For Reports Server, you can use the command line to specify the JVM options. For details about JVM option support, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.
|
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 (assumes E: is the DVD drive):
E:\> cd application_server E:\> wsf.exe
Follow the screens in the installer:
Table 3-3 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, OracleAS Web Cache, and Oracle Enterprise Manager 10g, use ports. You can have the installer assign default port numbers, or use port numbers that you specify.
An ephemeral port is a port number that an operating system can temporarily assign to a service or process. Some services or processes have conventionally assigned permanent port numbers. In other cases, an ephemeral port number is assigned temporarily (for the duration of the request and its completion) from a range of assigned port numbers.
Ephemeral Port Range
The ephemeral port range on Microsoft Windows is ports 1024 through 5000, inclusive.
Only the upper end of this range is adjustable in Windows. In most other operating systems, the ephemeral range by default is much larger, and the lower and upper bounds of the range are adjustable.
Several Application Server processes, including Oracle HTTP Server, OracleAS Web Cache, Oracle Enterprise Manager 10g Application Server Control, and OC4J, use ports in the ephemeral port range. These processes cannot start up if the ports that they need are already in use by clients.
Problem: Components Cannot Start Up Because of Conflicts with Ephemeral Ports
On rare occasions, Oracle Application Server processes are unable to start up because required ports are not available. Processes may fail to start up or report that they are unable to "bind" to ports. The behavior may be transient in that if you try to restart the affected process later, it does start successfully.
The cause of this problem is that by default, Oracle Application Server uses a number of ports that fall into the range of "ephemeral" ports. Ephemeral ports are usually used on the client ends of client/server TCP/IP connections. Because client processes usually are unconcerned with which port value is used on the client side of the connection, all TCP/IP implementations allow clients to defer to the operating system the choice of which port value to use for the client side. The operating system selects a port from the "ephemeral" port range for each client connection of this type.
On the other hand, server processes (for example, Oracle Application Server processes) cannot use ephemeral ports. They must use fixed port values so that clients can always connect to the same server port to communicate with the server.
Port conflicts with ephemeral ports arise when an Oracle Application Server process is configured to use a port in the ephemeral port range. The Oracle Application Server process tries to start up, but discovers that the port that it needs is already in use by a client process (the client received the ephemeral port assignment from the operating system). This client can be any process on the computer capable of communicating via TCP/IP. The Oracle Application Server process fails to start up when the port that it needs is unavailable.
This problem occurs relatively more frequently on Microsoft Windows than on other operating systems because by default Windows uses a small range of ports for ephemeral client connections.
Avoiding Conflicts with Ephemeral Ports
To avoid conflicts with ephemeral ports, you have these options:
Install Forms and Reports Services using staticports.ini so that Forms and Reports Services components do not use ports within the ephemeral range. In the staticports.ini file, use port numbers below 1024 or above 5000.
See Section 3.3.4, "Using Custom Port Numbers (the Static Ports Feature)" for details.
If you have already installed Forms and Reports Services, you can reconfigure the components to use ports below 1024 or above 5000. See the Oracle Application Server Administrator's Guide to learn how to change the current ports used by Application Server processes.
(This option can be done post-installation.) Modify the ephemeral port range on your computer. Use this option only if you cannot use any of the alternatives above. This option is the least preferred because it makes changes to the Windows registry, and it affects all products that you run on your computer.
This option moves the ephemeral port range to a new location. Before making the change, you must verify that none of the products you are using (Oracle or non-Oracle) on your computer use non-ephemeral ports within the ephemeral port range. If any products do so, you must relocate them to the new ReservedPorts range (see below), above the new ephemeral range, or below port 1024.
To implement this option, perform these steps:
Raise the upper bound of the ephemeral port range to expand the size of the range.
Set the MaxUserPort value in the registry to at least 13000, but no higher than 65534. MaxUserPort is the upper bound of the ephemeral port range.
For steps, see Microsoft Knowledge Base article 196271: http://support.microsoft.com/default.aspx?scid=kb;[LN];196271.
Reserve a portion of the newly expanded ephemeral port range for use by Oracle Application Server.
Set the ReservedPorts value in the registry so that ports 1024 through 8000 are reserved for Oracle Application Server. The reserved range incorporates the range of ports normally used by Oracle Application Server.
For steps, see Microsoft Knowledge Base article 812873: http://support.microsoft.com/default.aspx?scid=kb;[LN];812873.
Restart your computer for the changes to take effect.
After performing the steps, you end up with the following: ports from 1024 through 8000 are reserved for Oracle Application Server, and ports 8001 through 13000 are the new ephemeral port range (assuming you set the MaxUserPort to 13000). The reserved range incorporates the range of ports normally used by Oracle Application Server, and the ephemeral range has the same size as the original.
To check if a port is being used, run the netstat command as follows:
C:\> netstat -an | find portnum
If you want to use the default port numbers for components, you do not have to do anything. Ensure 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 fails.
Note the following points:
The installer assigns the default ports to components only if the ports are not in use by other applications. If the default port is in use, the installer tries other ports in the port number range for the component. For example, the default non-SSL port for Oracle HTTP Server for the middle tier is port 80. If this port is in use by another application, the installer assigns a port in the 7777 - 7877 range.
The default ports for Oracle HTTP Server depend on the installation type (Table 3-4). The middle tier gets ports 80 and 443 because it is where you would deploy your applications. Users would send requests to the middle tier's Oracle HTTP Server/OracleAS Web Cache to access the applications.
In Table 3-4, the values in parenthesis indicate the ports that the installer tries to assign to Oracle HTTP Server if the default port is already in use.
To instruct the installer to assign custom port numbers for components:
Create a file containing the component names and port numbers. Section 3.3.4.1, "Format of the staticports.ini File" describes the file format. This file is typically called staticports.ini, but you can name it anything you want.
In the installer, on the Specify Port Configuration Options screen, select Manual and enter the complete path to the staticports.ini file.
If you do not specify the complete path to the file, the installer will not be able to find the file. The installer then assigns default ports for all the components, and it does 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.
# J2EE and Web Cache Oracle HTTP Server port = port_num Oracle HTTP Server Listen port = port_num Oracle HTTP Server SSL port = port_num Oracle HTTP Server Listen (SSL) port = port_num Oracle HTTP Server Diagnostic port = port_num Java Object Cache port = port_num DCM Java Object Cache port = port_num DCM Discovery port = port_num Oracle Notification Server Request port = port_num Oracle Notification Server Local port = port_num Oracle Notification Server Remote port = port_num Application Server Control port = port_num Application Server Control RMI port = port_num Oracle Management Agent port = port_num Web Cache HTTP Listen port = port_num Web Cache HTTP Listen (SSL) port = port_num Web Cache Administration port = port_num Web Cache Invalidation port = port_num Web Cache Statistics port = port_num Log Loader port = port_num ASG port = port_num # Business Intelligence and Forms Reports Services SQL*Net port = port_num Reports Services discoveryService port = port_num Reports Services bridge port = port_num # Infrastructure Oracle Internet Directory port = port_num Oracle Internet Directory (SSL) port = port_num Oracle Certificate Authority SSL Server Authentication port = port_num Oracle Certificate Authority SSL Mutual Authentication port = port_num Ultra Search HTTP port number = port_num
The easiest way to create the file is to use the staticports.ini file on the CD-ROM (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 required 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 Application Server Control port and some OracleAS Web Cache ports. For components not specified, the installer assigns the default port numbers.
Application Server Control port = 2000 Web Cache Administration port = 2001 Web Cache Invalidation port = 2002 Web Cache Statistics port = 2003
When installation is complete, you can check the portlist.ini file to see the assigned ports.
|
The installer verifies that the ports specified in the file are available by checking the 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 does 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 using the port.
Click Retry. The installer rereads the staticports.ini file and verifies the entries in the file again.
Using portlist.ini as the staticports.ini File
The staticports.ini file uses the same format as the portlist.ini file, which is created after a Forms and Reports Services installation. If you have installed Forms and Reports Services and want to use the same port numbers in another installation, use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.
|
Note: Instaticports.ini, the Oracle Management Agent port line corresponds to the Enterprise Manager Agent port line in portlist.ini.
|
Check the 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 uses the specified port for the first component, but for the other components, it uses the components' default ports. The installer does not warn you if you have specified the same port for multiple components.
If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), 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, the installer will not find the file. The installer continues without displaying a warning and assigns default ports to all components. You must specify a complete path to the staticports.ini file.
In the httpd.conf file for Oracle HTTP Server, the Port and the Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server. The correct lines in the staticports.ini file for setting these ports depend on the components that you are configuring.
Ensure that you understand the following when setting ports for these components.
If You Are Configuring OracleAS Web Cache and Oracle HTTP Server
Set the port for OracleAS Web Cache.
OracleAS Web Cache uses the port specified by the Port directive (Figure 3-1). To set this port, use this line in the staticports.ini file:
Web Cache HTTP Listen port = port_number
To configure the SSL port for OracleAS Web Cache, use the following line:
Web Cache HTTP Listen (SSL) port = port_number
You cannot set the port number using the Oracle HTTP Server port line in this case. If the staticports.ini file contains both the Oracle HTTP Server port and the Web Cache HTTP Listen port lines, the Oracle HTTP Server port line is ignored. For example, if you have these lines in staticports.ini:
Web Cache HTTP Listen port = 7979 Oracle HTTP Server port = 8080
the Port directive is set to 7979.
Set the port for Oracle HTTP Server.
Oracle HTTP Server uses the port specified by the Listen directive. To set this port, use this line in the staticports.ini file:
Oracle HTTP Server Listen port = port_number
To configure the SSL Listen port, use the following line:
Oracle HTTP Server Listen (SSL) port = port_number
Figure 3-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server
If You Are Configuring Oracle HTTP Server Only (no OracleAS Web Cache)
If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives (Figure 3-2). In this case, you must set both directives to use the same port number.
To set these ports, use the Oracle HTTP Server port and Oracle HTTP Server Listen port lines in the staticports.ini file. For example:
Oracle HTTP Server port = 8080 Oracle HTTP Server Listen port = 8080
To set the SSL version of these ports, use the following lines. As in the non-SSL version, the port numbers must be the same.
Oracle HTTP Server SSL port = 443 Oracle HTTP Server Listen (SSL) port = 443
If you also specify the Web Cache lines in staticports.ini, they are ignored because you are not configuring OracleAS Web Cache.
Figure 3-2 Configuring Only 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 2003 server for itanium: 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 Forms and Reports Services needs to set (or unset) the environment variables listed in Table 3-6.
It includes the following sections:
Table 3-6 Summary of Environment Variables
| Environment Variable | Set or Unset |
|---|---|
|
|
Does not matter (the installer unsets these two environment variables). |
|
|
Must not contain references to directories in any Oracle home directories. Must not be longer than 1023 characters. |
|
|
Optional. If unset, defaults to |
|
|
Must not be set. |
|
|
Default set to YES. If set to NO, ensure that you specify the appropriate display. |
This section describes how to set environment variables in Windows:
Display the System control panel.
On Windows 2003 server for Itanium: Select Start > Control Panel > System.
Select the Advanced tab.
Click Environment Variables.
To change the value of a variable, select the variable and click Edit.
It does not matter if these environment variables are set or unset when you start the installer because the installer unsets these environment variables.
Edit the PATH, CLASSPATH environment variables so that they do not reference any Oracle home directories.
During installation, the installer needs to write temporary files to a "temporary" directory. By default, the "temporary" directory is C:\temp.
If you want the installer to use a directory other than C:\temp, set the TEMP environment variable to the full path of an alternate directory. This directory must meet the requirements listed in Table 3-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.
Ensure that the TNS_ADMIN environment variable is not set when you run the installer. If set, then it can cause errors during installation.
The REPORTS_DEFAULT_DISPLAY environment variable specifies whether to implement the following for Oracle Reports:
Elimination of dependency on DISPLAY
Elimination of dependency on having a valid printer defined for font information
ScreenPrinter (screenprinter.ppd) for surface resolution for images and font information
Advanced Imaging Support
For Oracle Reports, if REPORTS_DEFAULT_DISPLAY=YES, it overrides any value set for the DISPLAY environment variable. For more information about REPORTS_DEFAULT_DISPLAY, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.
|
Note: REPORTS_DEFAULT_DISPLAY is used for Oracle Reports only and is not applicable to the Oracle Application Server installer. The installer continues to use the DISPLAY environment variable even if REPORTS_DEFAULT_DISPLAY is set to YES.
|
Although the contents of the %WINDIR%\system32\drivers\etc\hosts file affect these items:
the installer provides alternative methods for you to enter the values that you want without editing the hosts file. See the following subsections for details.
%WINDIR% specifies the Windows operating system directory. Typically, it is C:\WINDOWS for Windows 2003 server for Itanium.
The installer reads the hosts file to construct the location of the default Oracle Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.
The hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname
Example:
123.45.67.89 primaryHost.mydomain.com primaryHost
In the preceding example, the location of the default Oracle Identity Management realm would look like "dc=mydomain,dc=com".
If the file uses a different format, the installer displays an incorrect value in the screen. For example, if the hosts file contains:
123.45.67.89 primaryHost primaryHost.mydomain.com <--- incorrect format
the installer would display "dc=primaryHost,dc=com" as the default Oracle Identity Management realm. This is probably not the value that you want for the default Oracle Identity Management realm.
|
Tip: If you need 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 |
If you are installing OracleAS Single Sign-On, and your hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).
If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:
E:\> setup.exe OUI_HOSTNAME=myserver.mydomain.com
Typically, the computer on which you want to install Forms and Reports Services is connected to the network, has local storage to contain the Forms and Reports Services installation, has a display monitor, and has a CD-ROM or DVD-ROM drive.
This section describes the procedure to install Forms and Reports Services on computers that do not meet the typical scenario. It covers the following cases:
Installing on Static IP Computers that You Want to Disconnect from the Network Later
Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive
Note this limitation when running Forms and Reports Services on DHCP computers: Forms and Reports Services instances on DHCP computers cannot communicate with instances running on other computers. All the instances that need to communicate with each other must run on the same computer. There are no limitations on clients; clients from other computers can access instances running on the DHCP computer, as long as the client computer can resolve the DHCP computer on the network.
A multihomed computer is associated with multiple IP addresses. This is achieved by having multiple network cards on the computer. Each IP address is associated with a hostname; additionally, you can set up aliases for the hostname. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the hostname. If ORACLE_HOSTNAME is not set and you are installing Forms and Reports Services on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the hosts file (typically located in DRIVE_LETTER:\WINDOWS\system32\drivers\etc)
You may need to reorder the lines in this file so that the required hostname appears first. You can change the file back to its original state after installation.
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.
A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Application Server on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose hostname you want to use.
For information on setting environment variables, see Section 3.5.1, "How to Set Environment Variables".
You can install Forms and Reports Services on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer. Examples:
You can install a J2EE and Web Cache middle tier without Oracle Identity Management or farm repository.
If you install a middle tier that requires infrastructure services, you need to install both OracleAS Infrastructure and middle tier on the computer. Ensure your computer has enough resources to run both instances. See Section 3.1.1, "Memory and Pagefile Requirements for Running Multiple Instances on the Same Computer".
Note that to install Forms and Reports Services 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 Forms and Reports Services 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 Forms and Reports Services on the non-networked computer.
Install a loopback adapter on the computer. See Section 3.7.6, "Installing a Loopback Adapter".
The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Forms and Reports Services 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 Forms and Reports Services 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 Forms and Reports Services on a networked computer with static IP and you want to be able to run Forms and Reports Services when you disconnect the computer from the network, you need to do the following steps before installing Forms and Reports Services:
Install a loopback adapter on your computer. See Section 3.7.6, "Installing a Loopback Adapter" for details.
Without a loopback adapter, Forms and Reports Services 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. To check, ping the computer from itself using (1) the hostname only and (2) the fully qualified name.
For example, if you installed a loopback adapter on a computer called mycomputer, you can run these commands:
prompt> ping mycomputer Ping itself using just the hostname. Reply from 10.10.10.10 Returns loopback adapter IP. prompt> ping mycomputer.mydomain.com Ping using a fully qualified name. Reply from 10.10.10.10 Returns loopback adapter IP.
When you ping a computer from itself, the ping command should return the IP of the loopback adapter. It should not return the network IP of the computer.
These steps are required regardless of whether the computer is using static IP or DHCP. If this is a DHCP computer, you already know you need a loopback adapter; see Section 3.7.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 3.7.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 3.7.4, "Installing on Non-Networked Computers"), or
you are installing on a computer with multiple aliases (see Section 3.7.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 3.7.6.1, "Checking If a Loopback Adapter Is Installed on Your Computer"
Section 3.7.6.2, "Installing a Loopback Adapter on Windows 2003 server for Itanium"
Section 3.7.6.4, "Removing a Loopback Adapter on Windows 2003 server for Itanium"
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
To install a loopback adapter on Windows 2003 or Windows XP:
Open the Windows Control Panel.
Windows 2003: Select Start > Control Panel > System.
Windows XP: Select Start > Control Panel, then double-click System.
Double-click Add Hardware to start the Add Hardware wizard.
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 2003 server for Itanium:
Display the System control panel.
Windows 2003: Select Start > Control Panel > 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 Forms and Reports Services CD-ROMs or DVD-ROM, you can copy the contents of the CD-ROMs or DVD-ROM to a hard drive and install from the hard drive. This might be easier if you plan to install many instances of Forms and Reports Services on your network, or if the computers on which you want to install Forms and Reports Services do not have CD-ROM or DVD-ROM drives.
You can also install from remote CD-ROM or DVD-ROM drives. See 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.
Accessing the Hard Drive from Other Computers:
If you want to install Forms and Reports Services on remote computers from the hard drive where you copied the contents of the CD-ROM or DVD-ROM, perform the following steps:
On the local computer, share the hard drive.
On the computers where you want to install Forms and Reports Services, map to the shared hard drive.
Run the installer from the remote computers on which you want to install Forms and Reports Services.
|
Note: You need to use the drive letter for the mapped drive to access the installer (for example,H:\orawinfrs_10_1_2\setup.exe).
|
You cannot use the universal naming convention (UNC) syntax (\\hostname\sharename) to access the installer.
To copy the CD-ROMs:
Create a parent directory (for example, orawinfrs) 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.
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:\orawinfrs\DiskN are the directories that you want to copy the CD-ROMs to.
E:\> xcopy /e /i E:\1012disk1 C:\orawinfrs\Disk1 E:\> xcopy /e /i E:\1012disk2 C:\orawinfrs\Disk2 ... Repeat for each CD-ROM.
To run the installer from the copied files, invoke the runInstaller executable from the Disk1 directory. Run it from the computer that will be running Forms and Reports Services.
C:\> cd orawinfrs\Disk1 C:\orawinfrs\Disk1> setup.exe
To copy the orawinfrs Directory from the DVD-ROM
You can copy the orawinfrs 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 orawinfrs directory.
Copy the orawinfrs directory from the DVD-ROM to your hard disk.
The example assumes E: is the DVD-ROM drive, and C:\orawinfrs is the destination directory:
E:\> xcopy /e /i E:\orawinfrs C:\orawinfrs
To run the installer from the copied files, invoke the setup.exe executable from the computer that will be running Forms and Reports Services:
C:\> cd orawinfrs C:\orawinfrs> setup.exe
If the computer on which you want to install Forms and Reports Services 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 (the computer that has the CD-ROM or DVD-ROM drive):
Log on 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).
On the Sharing tab (Figure 3-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.
Click Permissions. The user who accesses this folder to install Forms and Reports Services will need at least read permission.
Click OK when done.
CD-ROM: Insert Forms and Reports Services Disk 1 into the CD-ROM drive.
DVD-ROM: Insert the Forms and Reports Services DVD into the DVD-ROM drive.
If you want to install and run Forms and Reports Services on a remote computer (that is, the remote computer has the hard drive and will run Forms and Reports Services 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 Forms and Reports Services on the remote computer in one of two ways:
If you have copied the contents of the Forms and Reports Services 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 Forms and Reports Services 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 Forms and Reports Services 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 3.7.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 3.7.8, "Installing from a Remote CD-ROM or DVD-ROM Drive".
Using 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 3-7 lists the checks performed by the installer:
Table 3-7 Prerequisite Checks Performed by the Installer
| Item | Description |
|---|---|
|
User |
The installer checks that the user has administrative privileges. |
|
CPU |
Checks that the CPU meets the minimum speed requirement. |
|
Operating system version |
See Table 3-1 for supported versions. |
|
Windows service pack |
See Table 3-1 for supported service packs. |
|
Memory |
See Table 3-1 for recommended values. |
|
Total pagefile (virtual memory) size |
See Table 3-1 for recommended values. |
|
Swap space |
See Table 3-1 for recommended values. |
|
TMP space |
See Table 3-1 for recommended values. |
|
Instance name |
The installer checks that the computer on which you are installing Forms and Reports Services 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 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 may interfere with the installation. |
|
Oracle home directory |
You should install Forms and Reports Services in a new directory, unless you are expanding middle tier or installing middle tier in an Oracle home that contains Oracle Developer Suite. Here are some examples of installations that are not allowed:
|
|
Static port conflicts |
The installer checks the ports listed in the |
|
Monitor |
The installer checks that the monitor is configured to display at least 256 colors. |
|
Cluster file system |
The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS). |
|
Display permission |
The installer checks that the user has permissions to display on the monitor specified by the |
|
|
The installer checks that the |
|
Oracle Enterprise Manager directories are writable |
The installer runs this check only if you are expanding a middle tier or reinstalling Forms and Reports Services in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:
|
|
Oracle Enterprise Manager files exist |
The installer runs this check only if you are expanding a middle tier or if you are reinstalling Forms and Reports Services in the same Oracle home. The installer checks that these files exist:
|
