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.

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

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.

For more information, refer to the "System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1" document, available on the following page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK. For 32-bit JVM support, refer to the Oracle Fusion Middleware Release Notes for information on how to configure your environment for 32-bit JVM support for your platform.

2.3.1 Installing Oracle Web Tier in Stand-Alone Mode

If you do not want your Oracle Web Tier components to be associated with an existing Oracle Fusion Middleware stack, or if you want to install Oracle Web Tier without installing Oracle WebLogic Server, make sure you do not select Associate Selected Components with WebLogic Domain. By default, this option is not selected.

2.3.2 Using Oracle Enterprise Manager for GUI-Based Administration

1. Create a WebLogic Domain.

   Oracle Web Tier requires an existing WebLogic Domain; you cannot create a WebLogic Domain during the Oracle Web Tier installation.

   1. Read "Before you Begin" in Oracle Fusion Middleware Installation Planning Guide for information about whether or not you need a database and database schemas, and also for information about installing Oracle WebLogic Server.

   2. After you have installed Oracle WebLogic Server, install (do not configure) any Oracle Fusion Middleware product.

      Installation of an Oracle Fusion Middleware product creates the Oracle Common home directory (MW_HOME/oracle_common on UNIX operating systems, or MW_HOME\oracle_common on Windows operating systems). This directory contains the domain templates for Enterprise Manager and Java Required Files (JRF).

   3. Run the Configuration Wizard from the Oracle Common home directory (config.sh on UNIX operating systems or config.cmd on Windows operating systems).

      On the Select Domain Source screen, select the Oracle Enterprise Manager and Oracle JRF templates associated with the oracle_common directory. The Oracle JRF template is selected automatically when the Oracle Enterprise Manager template is selected.

2. Install Oracle Web Tier as described in Oracle Fusion Middleware Installation Guide for Oracle Web Tier.

   On the Configure Components screen, select Associate Selected Components with WebLogic Domain.

   On the Specify WebLogic Domain screen, provide the credentials to the WebLogic Domain you just created.

3. After the installation is complete, start the Administration Server in the domain, and then verify that the Oracle Web Tier components are listed by accessing the following URL:

   http://host:port/em
   

2.3.3 Starting Node Manager When Registering Oracle Web Tier with a WebLogic Domain

If you are registering your Oracle Web Tier instance with an existing WebLogic Domain, you must start Node Manager as described below:

1. On UNIX operating systems, run the ORACLE_HOME/common/bin/setNMProps.sh script.

   On Windows operating systems, run the ORACLE_HOME\common\bin\setNMProps.cmd script.

   This script appends the required properties to the nodemanager.properties file. These properties can also be appended manually, or provided as command-line arguments.

   Note:

   The StartScriptEnabled=true property is required for Managed Servers to receive proper classpath and command arguments.

2. On UNIX operating systems, start Node Manager by running the WebLogic_Server_Home/server/bin/startNodeManager.sh script.

   On Windows operating systems, start Node Manager by running the WebLogic_Server_Home\server\bin\startNodeManager.cmd script.

For more information about Node Manager, refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

2.4.1 Obtaining the Software

See "Obtain the Oracle Fusion Middleware Software" in Oracle Fusion Middleware Installation Planning Guide for information on where to obtain the software.

Select one of the download locations and download "Oracle Web Tier." This will be saved to your system as a .zip archive file.

After you download the archive file, unpack the archive file into a directory of your choice on the machine where you will be performing the installation.

2.4.2 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.4.3 Starting the Installer

To start the installer, gpo to the directory where you unpacked the archive file and run the following command:

On UNIX operating systems:

./runInstaller

On Windows operating systems:

setup.exe

2.4.4 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.4.5 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.5.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.5.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.6.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.6.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.6.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.6.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: