Sunday, June 7, 2009

CM Basics

The ICM (Internal Concurrent Manager) controls all of the other
concurrent managers.

The Standard Manager accepts any and all requests. It has no
predefined specialization rules and is active all the time. It is not
recommended to add specialization rules to the standard manager as it
can cause problems.

The Conflict Resolution Manager resolves conflicts, such as request
incompatibilities.

STARTING THE CONCURRENT MANAGERS

There are two ways to determine if the concurrent managers are up and
running:

1.  Log in to applications as System Administrator responsibility and
navigate to the concurrent manager administration page (Concurrent,
Manager, Administrator) and under the processes column if the
target and actual column equal the same number (above 0) this means
the managers are up and running.

2. You can also go into SQL*PLUS as APPS and run the following script:

SQL> @$FND_TOP/sql/afimchk.sql

This script will return output similar to the below:

Status Since Method
-------------------------------------- --------- ----------- ------
Internal Conc Manager is running on - colapp03 05-MAR-99 06:41:32 PM LOCK

Use this syntax to start the concurrent managers from the command line:
adcmctl.sh apps/password start

STOPPING THE CONCURRENT MANAGERS

You stop the concurrent managers from the command line:

CONCSUB apps/apps SYSADMIN 'System Administrator' SYSADMIN CONCURRENT FND
DEACTIVATE or ABORT

DEACTIVATE tells the managers to complete processing of any running
requests before terminating. This is a cleaner way of bringing down the
managers.

ABORT tells the managers to terminate the managers immediately.
When the concurrent managers are terminated through the abort command,
the jobs that they were running will be returned to pending status.

adcmctl.sh apps/password stop







No comments:

Post a Comment