Behind the 12.2 scenes 1. - the new file structure

Behind the 12.2 scenes 1.

Now that the 12.2.2 version of Oracle EBS is publicly available we could go inside, go behind the marketing. We have already downloaded the new software and searching places for creating a new demo site from it. Until it's created I am reading the Concept, Install Guide, admin and etc documentations for searching the documented changes.

First from file directory structure - cause of why is increased the apps tier size from about 40GB to 64GB

New Application tier directory structure

As the concept documenteted there are many, many changes in the new version compared to the previous versions.

The only directory structure what is not changed is the database tier, it is still as in the earlier R12 releases - except it's main directory will be directly under "s_base" common base directory.

The first big change is that the Application Tier directories was completly redesigned, restructured. The main publicated reason is the new patching feature, the online patching. The Concept is usually writen for beginners, but now because of the new structure I recommend to read it for advanced technical consultants too. We have to learn again the structure :) So what is the main changes - it isn't same order as the concept written.

• a new base directory - for all application tier files, including runable, log, configuration and etc. files
• new dual filesystem base directories
• new non editioned base directory
• modified INST_TOP directory
• modified log file locations
• new weblogic home directories
• patch directory

New main base directory

From now we have new base directory (new context code: s_ebs_base, or s_base; there are some inconsistency between a diagram and the text) which will contain the database, the new subbase directories and the modified INST_TOP (and or a PATCH_BASE directory, there is an example in the documentation where s_base and s_patch_base is the same).

Dual file system directory

One of the effects of the online patching are the 2 new "dual file system" directory. One of them is the actual, the live filesystem, the other one is the patching one. It means that when you are doing the patching only the "patch" directory object will be patched, the actual one will not. (except using hotpach mode). When you are ready with the patching, or your maintenance window begin you should do a switch between these to directory. After switching the old live directory will be the patching and the other one will the the actual, the run directory. ("Maintenance Mode is not needed or used in Release 12.2" as the documentation said)

The dual file system directories will have very simple names: fs1 and fs2. There will also be a 2 new enviroment variable: RUN_BASE and PATCH_BASE. RUN_BASE will point to the actual live dual directory, the PATCH_BASE will point to the actual one.

A dual file system will contain:

• EBSbase subdirectory which will contain
• appl - the appl_top
• comn - common_top
• 10.1.2 - the form server OAS home
• inst - the modifief INST_TOP
• FMW_HOME - the weblogic home directory

Non editioned file system

The third main sub directory under the common base is the non editioned file system (context code: s_ne_base) . This directory will be used to store file that is needed across all file systems. Non-editioned files are not copied or moved during patching: their location remains constant across online patching cycles.

The non-editioned file system directories will have a very simple name: fs_ne. There will also be a new enviroment variable: $NE_BASE.

The document is defined this directory as "The non-editioned file system is designed to store files that contain transactional data and reference data."

What are the examples?

• Batch upload, download data
• Transactional data from/to outside, or that are needed across all file systems
• Concurrent manager log and out files
• AD administration log files
• patch admin log files (new adop tool log files)

There is a funny constraint: "The non-editioned file system is not designed to store shared files, because initially identical files can become non-identical during patching life cycles". Which is a little bit contradict the this example sentence just some rows above it: "where a third party order entry system delivers orders via order import files". If I could not use is as shared what happens when we have got multi node system. Where should I really put an order import file if I could not share them?

Modified INST_TOP directory

First new changes is e Instance Home include support for read-only file systems. In Release 12.2, the APPL_TOP and FMW_Home contain some configuration files modified by AutoConfig. Only the OracleAS 10.1.2 ORACLE_HOME configuration files are located under $INST_TOP, and so can be made read-only. I am not believe that this is really useful at most cases and I am not sure too that it will work without any bug.

Other new behaviuor is from now the HTTP, the Oracle WebLogic Server configuration files and concurrent processing files are not stored under the $INST_TOP

Modified log file locations

Is I have discussed earlier from now we could not find all log files under $LOG_HOME directory. We have to search them under HTTP, Weblogic, ne_fs directories. It's a enough big back step. So we have to surf across directories and nodes when we have to search for error messages in EBS log files.

New weblogic home directories

Some good quote from concept guide

"The Oracle Fusion Middleware (FMW) directory is another key high-level directory. It
is completely new in Oracle E-Business Suite Release 12.2, as this technology was not
used in previous releases.
Typically, the FMW directory will be located in a path such as /u01/R122_EBS/fs1,
at the same level as the inst and EBSapps directories. "

It includes subdirectories such as:

• A Weblogic domain for the EBS system
• the weblogic server files
• java files required by Oracle EBS
• the HTTP server
• the deployed J2EE applications of EBS system (oacore, forms, oafm)

patch directory

On diagram of the 4-10 page there is a strange patch directory under non edition file system. There is nothing about it near the diagram. The concept is enough big and I could not find the real purpose of this directory. When I find it I will come back to here and refresh this post.