oracle application concurrent managers

How to check the running concurrent managers?

$ ps -ef|grep FNDLIBR

ICM (internal concurrent manager):-

The master manager is called the Internal Concurrent Manager (ICM) because it controls the behavior of all of the other managers, and because the ICM is the boss, it must be running before any other managers can be activated. The main functions of the ICM are to start up and shutdown the individual concurrent managers, and reset the other managers after one them has a failure.

It is a FNDLIBR process

It is used to communicate the service manager (GSM).

Located at:- $APPLCSF/$APPLLOG 

Standard Manager:—

 Another important master Concurrent Manager is called the Standard Manager (SM). The SM functions to run any reports and batch jobs that have not been defined to run in any specific product manager. Examples of specific concurrent managers include the Inventory Manager, CRP Inquiry Manager, and the Receivables Tax Manager.

used to perform the single client request processing. & used to execute the all all the concurrent managers.

If any request is not defined to run the standard manager will take care of that request.

Conflict Resolution Manager — The Conflict Resolution Manager (CRM) functions to check concurrent program definitions for incompatibility rules. However, the ICM can be configured to take over the CRM's job to resolve incompatibilities.

FNDSM:-

It is service manager. FNDSM is executable and core component in GSM ( Generic Service Management Framework discussed above). You start FNDSM services via application listener on all Nodes in Application Tier in E-Business Suite.

APPS listener:-

Combination of FNDFS & FNDSM.

FNDFS:-

FNDFS or the Report Review Agent (RRA) is the default text viewer within Oracle Applications, which allows users to view report output and log files. Report Review Agent is also referred to by the executable FNDFS. The default viewer must be configured correctly before external editors or browsers are used for viewing requests.

GSM:-  (generic service manager)

GSM stands for Generic Service Management Framework. Oracle E-Business Suite consist of various compoennts like Forms, Reports, Web Server, Workflow, Concurrent Manager ..

Service Management is an extension of Concurrent Processing, which provides a powerful framework for managing processes on multiple host machines.   Today, services such as the Oracle Forms Listener, Oracle Reports Server, Apache Web listener, and Oracle Workflow Mailer can be run under Service Management.

 With Service Management, the Internal Concurrent Manager (ICM) manages the various service processes across multiple hosts. On each host, a Service Manager acts on behalf of the ICM, allowing the ICM to monitor and control service processes on that host. System administrators can then configure, monitor, and control services though a management console which communicates with the ICM.

Service Management provides a fault tolerant system. If a service process exits unexpectedly, the ICM will automatically attempt to restart the process.  If a host fails, the ICM may start the affected service processes on a secondary host.  The ICM itself is monitored and kept alive by Internal Monitor processes located on various hosts.

OPP:- (output post processer)

OPP is an enhancement to Concurrent Processing and is designed to support XML Publisher as post-processing action for concurrent requests. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

Thread Vs Process :You can either increase process (or) threads. It depends on the load .

Reseting and altering can be done via these navigation

Concurrent -> Manager -> Define > Output Post Processor

Locating OPP log file?

whenever XML issues or other publishing problems occurs, first thing you will do is to trace the OPP logfile.Locating such logs is not a big things, just follow the steps below:

1.     logon with System Administrator

2.     Function: Concurrent --> Manager --> Administration and select the Output Post Processor

3.     Click on the Processes button

4.     Select the Concurrent Process which was active during the time that the request ran

5.     Click on the Manager Log button to open the Output Post Processor log file