2 Installing Oracle Web Tier

2.1.1 Installing 32-bit Oracle Web Tier on a 64-bit Operating System

This section contains important information regarding the installation of 32-bit Oracle Web Tier products on a 64-bit operating system. If this does not describe your environment, you can skip this section.

2.1.2 Oracle Fusion Middleware Support of 64-bit JDK

If you are using a 64-bit JVM in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

Refer to the Oracle Fusion Middleware Certifications matrix for information on the platforms that support a 64-bit JDK:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2.3.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section D.2.1, "Installation Log Files" for more information about the log files and their contents.

2.3.2 Starting the Installer

To start the installer, insert the CD-ROM and run the following command:

On UNIX operating systems:

% ./runInstaller

On Windows operating systems:

G:\ setup.exe

2.3.3 Inventory Screens (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 2-1 to configure the inventory directory information. For more help, click on the screen name in the table below, or click the Help button in the GUI.

2.3.4 Installing and Configuring Oracle Web Tier

Follow the instructions in this section to install and configure the latest Oracle Web Tier software.

Web_Tier_ORACLE_HOME/bin/config.sh

Web_Tier_ORACLE_HOME\bin\config.bat

2.4.1 Configuring Routing Between Oracle HTTP Server and Oracle WebLogic Server

By default, routing between Oracle HTTP Server and Oracle WebLogic Server is not configured. In order to allow requests to be proxied from Oracle HTTP Server to Oracle WebLogic Server, you must configure a plug-in.

For instructions on how to do this, see "mod_wl_ohs" in the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server.

2.4.2 Using Oracle Web Cache with Oracle BAM

If you are using Oracle Web Cache with Oracle BAM, you must perform the configuration steps detailed in "Basic Tasks for Configuring and Monitoring Caching Rules" in Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

Use the following Oracle BAM settings:

Expression Type : Regular Expression
URL Expression : oracle.bam.web (or Event=viewReport, for the second rule)
HTTP Methods : Select all
Leave URL and POST Body Parameters empty.
POST Body Expression : .*
Caching Policy : Don't Cache
Leave Comment as it is.
Compression : Off
Enabled : yes 

2.5.1 Verify the Installation Logs

Check for the presence of installation log files in logs directory inside your Oracle Inventory directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the WebTier_ORACLE_HOME/oraInst.loc file. On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

2.5.2 Verifying the Domain Server Logs

Check the domain server logs, which are located in the servers directory inside the domain home directory. For example, on UNIX systems:

Web_Tier_ORACLE_HOME/user_projects/domains/domain_name/servers/server_name

On Windows systems:

Web_Tier_ORACLE_HOME\user_projects\domains\domain_name\servers\server_name

2.5.3 Verifying OPMN Status

Run the opmnctl status command from the INSTANCE_HOME/bin (on UNIX operating systems) or INSTANCE_HOME\bin (on Windows operating systems) directory in your instance home location. For example:

> ./opmnctl status

Processes in Instance: instance2
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status  
---------------------------------+--------------------+---------+---------
webcache1                        | WebCache-admin     |   24057 | Alive   
webcache1                        | WebCache           |   24056 | Alive   
ohs1                             | OHS                |   23890 | Alive   

This information shows the components configured for this installation. The status "Alive" means the component is up and running.

2.5.4 Check Browser URLs

Run the opmnctl status -l command from the INSTANCE_HOME/bin (on UNIX operating systems) or INSTANCE_HOME\bin (on Windows operating systems) directory in your instance home location to obtain a list of ports used by the components. For example:

> ./opmnctl status -l

---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component                    | process-type       |     pid | status   |        uid |  memused |    uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
webcache1                        | WebCache-admin     |   24057 | Alive    | 1067146469 |    43712 |  14:43:29 | http_admin:7799
webcache1                        | WebCache           |   24056 | Alive    | 1067146468 |    64072 |  14:43:29 | http_stat:7800,http_invalidation:7801,https_listen:7802,http_listen:7798
ohs1                             | OHS                |   23890 | Alive    | 1067146467 |    50260 |  14:43:39 | https:9999,https:4447,http:7777

Use the port numbers in this display to point your browser to the appropriate pages. Use the format:

http://system_name:port_number

Based on the information above, you would use the URLs in Table 2-4 to access the various pages from this configuration: