Saturday, March 16, 2013

Concurrent Manager Overview

Concurrent Manager:
When a user runs a report, a request to run the report is generated. The command to run the report is a concurrent request.  The program that generates the report is a concurrent program. Concurrent programs are started by a concurrent manager.
Concurrent managers are fundamental to concurrent processing. A concurrent manger is an executable that is registered as a program library within Oracle Applications, and which runs in its own operating system process
Types of Concurrent Manager:
There are many pre-configured Concurrent Managers are there in Oracle E-business Suite. The most important managers are is as follows.
Internal Concurrent Manager (ICM):
ICM controls all other concurrent managers. It administers the startup and shutdown of managers as defined by their work shift, monitors for process failure, and cleans up if a failure occurs
Standard Manager:
Standard Manager as shipped with Oracle Applications will accept and run any concurrent requests, as it has no specialization rules that would restrict its activities.
Conflict Resolution Manager:
Conflict Resolution Manager enforces rules designed to ensure that incompatible concurrent requests do not run in the same conflict domain
Transaction Manager:
Transaction Managers support synchronous request processing, whereby a pool of server processes responds to requests from client programs. Instead of polling the concurrent requests table to obtain instructions, a transaction manager waits to be signaled by a client. An example is approval of an order, where execution of the request must take place quickly
Concurrent Manager - Tables
Table Content
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
Concurrent Request Life Cycle
Phase Activity
Pending / Normal The request is waiting to be run
Pending / Standby The request is waiting at CRM.
Running / Normal The request is running
Completed / Normal The request has finished
Inactive / No Manager The request cannot be run; No
manager available to process
There are many pre-configured Concurrent ManagersWhen a user runs a report, a request to run the report is generated. The command to run the report is a concurrent request.  The program that generates the report is a concurrent program. Concurrent programs are started by a concurrent manager.
Concurrent managers are fundamental to concurrent processing. A concurrent manger is an executable that is registered as a program library within Oracle Applications, and which runs in its own operating system process
Types of Concurrent Manager:
There are many pre-configured Concurrent Managers are there in Oracle E-business Suite. The most important managers are is as follows.
Internal Concurrent Manager (ICM):
ICM controls all other concurrent managers. It administers the startup and shutdown of managers as defined by their work shift, monitors for process failure, and cleans up if a failure occurs
Standard Manager:
Standard Manager as shipped with Oracle Applications will accept and run any concurrent requests, as it has no specialization rules that would restrict its activities.
Conflict Resolution Manager:
Conflict Resolution Manager enforces rules designed to ensure that incompatible concurrent requests do not run in the same conflict domain
Transaction Manager:
Transaction Managers support synchronous request processing, whereby a pool of server processes responds to requests from client programs. Instead of polling the concurrent requests table to obtain instructions, a transaction manager waits to be signaled by a client. An example is approval of an order, where execution of the request must take place quickly
Concurrent Manager - Tables
Table Content
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
Concurrent Request Life Cycle
Phase Activity
Pending / Normal The request is waiting to be run
Pending / Standby The request is waiting at CRM.
Running / Normal The request is running
Completed / Normal The request has finished
Inactive / No Manager The request cannot be run; No
manager available to process
There are many pre-configured Concurrent Managers

No comments:

Post a Comment