General Information:
E-Business Suite is formed of 3 tiers These are database, application and client. Database tier holds the database services while Application tier holds the Fusion Middleware and Concurrent Processing part. Client has the java virutal machine which enables it to access and communicate with Application tier. Application tier acts like the middleman between Database and client.
In Fusion Middleware, Forms,Oacore,Oafm servers. The $WEBAPPS_TOP shows us the location of these servers.
Oracle Homes in EBS 12.2:
There are two homes under the run files system. For example under the run file system we have our Oracle home as /u01/install/APPS/fs1/EBSapps/10.1.2 other than that /u01/install/APPS/fs1/FMW_HOME is the other Oracle home for Fusion Middleware. Third home that is seen is $APPL_TOP which has the modules. It is beside the 10.1.2 under /u01/install/APPS/fs1/EBSapps/appl
Web Services:
Web services control the HTTP requests that are coming to the application.
Concurrent Processing Server:
As well as HTML applications and forms , there are also data reporting and data updating programs that need to be run randomly or in scheduled way. They run in the background. The requests that are needed to run are written to a table, then it is read by the concurrent managers and run accordingly.
Concurrent Managers spawn their own processes which is called as target processes.Every target process can run only one concurrent request at a time.
The frequency or the amount of work that is to be done can be arranged by the work shifts
Specialized Concurrent Managers:
Specailized concurrent managers dont exactly run concurrent requests but manages other stuff.
ICM(Internal Concurrent Manager) controls all the other concurrent managers. It administers the startup and shutdown of managers. ICM is important because it has lots of configuration settings that should not be modified but can be modified manually. ICM must be run before any other concurrent manager in order to start other concurrent managers. It creates log files (std.mgr and wnnn.mgr) in $APPLCSF/$APPLLOG.
These are sleep time (number of seconds the ICM waits between checking for new concurrent requests), PMON (process monitor) cycle time (number of sleep cycles the ICM waits between checking for failed workers), and queue size (duration between checks for number of active workers, measured in PMON cycles).
Standard Manager is the default concurrent manager that comes with the installation. However special concurrent managers can be created in order to form special environments for programs.
Concurrent Manager Architecture and Related Tables:
FNDLIBR is the Oracle application object library program which has the concurrent programs that can be called by a concurrent manager.
FND_CONCURRENT_REQUESTS :Details of user requests, including status, start
date, and completion date
FND_CONCURRENT_PROGRAMS: Details of concurrent programs, including
execution method, whether the program is
constrained, and whether it must be run alone.
FND_CONCURRENT_PROCESSES: Cross-references between concurrent requests
and queues, and a history of concurrent
manager processes
FND_CONCURRENT_QUEUES: Information about each of the concurrent
manager queues
How to see the Concurrent Manager Processes?
In order to see the processes we need to be searching for processes with the name of FNDLIBR
ps -ef | grep FNDLIBR
FNDLIBR runs for every concurrent manger and Internal Concurrent Manager.
applmgr 17100 17095 0 Feb19 ? 00:09:37 FNDLIBR -- ICM
applmgr 18326 18252 0 Feb19 ? 00:00:11 FNDLIBR
applmgr 18329 18252 0 Feb19 ? 00:00:11 FNDLIBR
applmgr 18330 18252 0 Feb19 ? 00:00:29 FNDLIBR
applmgr 18331 18252 0 Feb19 ? 00:00:27 FNDLIBR
applmgr 18332 18252 0 Feb19 ? 00:00:29 FNDLIBR
applmgr 18333 18252 0 Feb19 ? 00:00:14 FNDLIBR
In fact, ICM starts up a Service Manager that instructs the concurrent manager to startup. Therefore if we look at the mother process of all, we can search for
ps -ef | grep FNDSM
For example FNDSM process is 18252
Managing Concurrent Processing:
To start ICM, we can start adcmctl.sh which is found under $ADMIN_SCRIPT_HOME to find the status of ICM or to either startup or shutdown the ICM in order to run it again so that other concurrent managers could start.
adcmctl.sh status| shutdown | startup
The EBS Technology Layers:
We have a number of utiliy that runs in between the application and the modules.
• Oracle Applications DBA (AD)
• Oracle Application Object Library (FND)
• Oracle Applications Utilities (AU)
• Oracle Common Modules (AK)
• Oracle Workflow (WF)
• Oracle Web Applications Desktop Integrator (BNE)
• Oracle Alert (ALR)
• Oracle Application Framework (FWK)
• Oracle BI Publisher (XDO)
Use application diagnostics to capture a problem that might exist.
Oracle Alert (ALR):
Oracle Alert allows us to email system notification when an exception occurs. The reason could be any event or database related.
File Structures
The APPL Directory:
Appl_top which is under the EBSapps/appl has the main context files, products and modules.
Admin directory under the common_top has the concurrent manager logs and output directiories. However the correct location is under non editioned file system which is
/u01/install/APPS/fs_ne/inst/SID_HOSTNAME/logs/appl/conc/log/
File Systems of EBS:
There are 2 file systems in EBS 12.2 in additon to non
References:
1-
