In this blog post, I will talk about the new and changed features/things/concepts in FMW 12c. Most of us (atleast I was ) are so used to work with 11g concepts that I found it a bit confusing initially to get hang of all the changes in 12c.
So, lets start with basics.
1) What is Oracle Fusion Middleware ?
|Used in 12c||Used in 11g|
|Oracle home or ORACLE_HOME|
This term replaces Middleware Home (MW_HOME) which is being eliminated from 11g.
Oracle home is created for all the Oracle Fusion Middleware products and includes binary and library files, the Oracle common directory and the individual product directories for each Oracle Fusion Middleware product.
|Middleware home or MW_HOME
In 11g the Middleware home is a container for the Oracle WebLogic Server home, and, optionally, one Oracle Common home and one or more Oracle homes.
|Product directory or PRODUCT_DIR|
The product directories within the Middleware home are no longer Oracle homes. They are simply directories within the Oracle home that are created for all the Oracle Fusion Middleware products. Most Oracle Fusion Middleware components should be installed in the same Oracle home. The names of the product homes are predefined and can no longer be modified by the user during the installation.
|Oracle home or PRODUCT_ORACLE_HOME
In 11g, if you install SOA at $MW_HOME/Oracle_SOA1 then this location was referred as SOA_ORACLE_HOME.
|Oracle instance term is not being used in 12c.|
The installer will no longer create a separate instance directory for system components, such as Oracle HTTP Server. Instead, you can use the Fusion Middleware Configuration Wizard to configure your system components, just as you do for Java components. Instance information about each system component will be stored in the domain home.
|Oracle instance or ORACLE_INSTANCE
The installer used to create a separate instance directory for system components, such as Oracle HTTP Server.
|The term "farm" is no longer necessary for 12c.||Oracle Fusion Middleware farm
It was used in 11g to refer to a container for a WLS domain and its associated system component instances when presented in Fusion Middleware Control.
- Here as you can see above, it is recommended to create products and config directories inside your target install directory.(oracle in above case)
- Oracle Home resides in products directory. It is a read-only directory which contains binary and library files, the Oracle Common home directory, and the individual product directories for each Oracle Fusion Middleware product you install.
- Oracle_Common_Home directory contains the binary and library files that are common to all the Oracle Fusion Middleware products and features installed in the Oracle home. In addition, it includes the files required for common tools, such as Oracle Enterprise Manager Fusion Middleware Control, WLST, the Configuration Wizard, upgrade tools, and Oracle JRF. There is only one Oracle Common directory within each Oracle home.
- PROD_DIR. It is not shown in above diagram but this directory resides within the Oracle home, which contains the binary files associated with a logical product or feature set (for eg SOA). The name of each product directory within the Oracle home is predefined by the installer and cannot be changed.
- Oracle WebLogic Server home or WL_HOME is a directory for the WebLogic Server binary files. It also resides in ORACLE_HOME.
- Fusion Middleware Control or EM_DIR lso resides in ORACLE_HOME. This directory contains the binary and library files required to run Fusion Middleware Control.
- Domain home or DOMAIN_HOME is the location in which the domain information and configuration artifacts are stored. It resides under config directory.
- Application Home or APPLICATION_HOME is the directory where the applications related to the domains you configure will be created. Oracle recommends that this location reside outside of the Oracle home directory; in the event that you need to upgrade or patch your software, the files inside the Oracle home would be affected.
- Per domain With a per-domain Node Manager, the Node Manager is associated with a domain and is configured to control all servers for the domain on a machine. (A per-domain Node Manager is a Java-based Node Manager.)This is the default when you configure Node Manager with the Configuration Wizard (see above).
- Per host With a per-host Node Manager, the Node Manager process is not associated with a specific WebLogic Server domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. A per host Node Manager must run on each computer that hosts WebLogic Server instances—whether Administration Server or Managed Server—that you want to control with Node Manager. (A per-host Node Manager can be either a Java-based or script-based Node Manager.)