How to Install FMW 11g Web Tier Managed by Enterprise Manager Fusion Middleware Control(fmwc)
(Doc ID 1074140.1)
Last updated on AUGUST 29, 2023
Applies to:
Oracle HTTP Server - Version 11.1.1.2.0 to 11.1.1.9.0 [Release Oracle11g]Oracle Fusion Middleware - Version 11.1.1.2.0 to 11.1.1.9.0 [Release Oracle11g]
Enterprise Manager for Fusion Middleware - Version 11.1.1.2.0 to 11.1.1.9.0
Information in this document applies to any platform.
- Without following this, you may receive error:
"'Unable to validate NonJ2EEManagement Application deployment on admin server'
or
"INST-07281 : JRF Is Not Set Up In The Specific Domain"
Purpose
Oracle Fusion Middleware (FMW) 11g Web-Tier information can be obtained from the following:
<Note 1304604.1> Oracle Fusion Middleware 11g Web-Tier FAQ
The purpose of this document is to outline the installation and configuration of an FMW 11g Web-Tier where products are installed with FMW Control as an administration utility. There are two different end goals for an FMW 11g Web-Tier installation, depending on your needs and requirements:
- Standalone Oracle HTTP Server and/or Oracle Web Cache
FMW 11g Web-Tier products are configured without a domain and administered from the command line. In this case, Choose Install+Configure on the Installer screens, but be sure to UN-check the selection for "Associate to WebLogic Domain" during the subsequent screen prompts. See the latest FMW 11g Web-Tier Installation Guide for details within Chapters 1-4 and screen shots in the appendix. - Using Fusion Middleware Control for Administration After Initial Install+Config
This approach requires the FMW 11g Web Tier to be associated with a properly configured Oracle WebLogic Server domain. When following this approach, both the Oracle WebLogic Server and FMW 11g Web-Tier Installation Guides need to be followed. In some cases, interpreted for the specific use case since they were written from separate teams. See the latest FMW 11g Web-Tier Installation Guide for details within Chapters 1-4 and screen shots in the appendix.
Note:
The second approach requires additional steps during installation and configuration, but subsequently allows for easier GUI-based administration. There have been some doc bugs filed to correct and clarify the steps. The Documentation and Installer has an "Install+Configure" step which is intended to do everything. There is a problem (bug filed) in this process and the proper Enterprise Manager and Java Required Files (JRF) domain templates do not get installed by the Web-Tier configuration. This document discusses the high-level install and configuration steps for the second approach, installing for the intent of using Fusion Middleware Control to adminstrer Oracle HTTP Server and/or Oracle Web Cache. Option 1 below takes the place of the "Install+Configure". from the bugs filed, it has been made not feasible to fix the issue allowing a straight install+config. Other options are used depending on your circumstance, as described.
Important:
An Oracle Web-Tier should be installed in its own Middleware home. Many other FMW installations automatically install an OHS and you should use that OHS for your needs. It has been common to mistakenly install another Web-Tier unnecessarily. If you need a separate OHS it is only supported to install in a separate Middleware home, preferably a separate machine as is typical in a reverse-proxy scenario. The exception is in option 2, where it is documented and tested together where it is planned to maintain the same level of patching throughout the life cycle. You do not want to have error correction support end just because you cannot apply a patch set in your environment with another product which did not release a patch set. SOA and Web-Tier are two which follow the same schedule. OBIEE and Web-Tier are an example which do not. (The OBIEE installs its own OHS, too).
The second approach requires additional steps during installation and configuration, but subsequently allows for easier GUI-based administration. There have been some doc bugs filed to correct and clarify the steps. The Documentation and Installer has an "Install+Configure" step which is intended to do everything. There is a problem (bug filed) in this process and the proper Enterprise Manager and Java Required Files (JRF) domain templates do not get installed by the Web-Tier configuration. This document discusses the high-level install and configuration steps for the second approach, installing for the intent of using Fusion Middleware Control to adminstrer Oracle HTTP Server and/or Oracle Web Cache. Option 1 below takes the place of the "Install+Configure". from the bugs filed, it has been made not feasible to fix the issue allowing a straight install+config. Other options are used depending on your circumstance, as described.
Important:
An Oracle Web-Tier should be installed in its own Middleware home. Many other FMW installations automatically install an OHS and you should use that OHS for your needs. It has been common to mistakenly install another Web-Tier unnecessarily. If you need a separate OHS it is only supported to install in a separate Middleware home, preferably a separate machine as is typical in a reverse-proxy scenario. The exception is in option 2, where it is documented and tested together where it is planned to maintain the same level of patching throughout the life cycle. You do not want to have error correction support end just because you cannot apply a patch set in your environment with another product which did not release a patch set. SOA and Web-Tier are two which follow the same schedule. OBIEE and Web-Tier are an example which do not. (The OBIEE installs its own OHS, too).
Scope
The advice in this document is intended for System Administrators, Architects, Consultants and Support Engineers
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| How to Install FMW 11g Web Tier Managed by Fusion Middleware Control (EM) |
| Option 1: New Installation of FMW 11g Web-Tier With New WLS Installation |
| Option 2: Associating Existing FMW 11g Web-Tier to a New or Existing WLS Domain |
| Less Popular - |
| Option 3: New Installation of FMW 11g Web-Tier to an Existing In-Use WLS Domain |
| Option 4: New WLS Installation After Installing FMW 11g Web-Tier Standalone |
| References |