Scribd
Upload
6 views2 pages

5-Custome Manager

The document outlines the steps to create custom Concurrent Managers in an application, including defining combined rules, work shifts, and attaching them to a manager. It also describes the activation process and how to exclude combined rules from the Standard Manager. Additionally, it provides information on various tables related to concurrent requests and their management in Oracle Applications.

Uploaded by

saddamshaikhdba0401
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
6 views2 pages

5-Custome Manager

The document outlines the steps to create custom Concurrent Managers in an application, including defining combined rules, work shifts, and attaching them to a manager. It also describes the activation process and how to exclude combined rules from the Standard Manager. Additionally, it provides information on various tables related to concurrent requests and their management in Oracle Applications.

Uploaded by

saddamshaikhdba0401
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

----------------------------------------> Creating Custom

ConcurrentManagers:>------------------------------
|

--------- | ------------
|
|
|

- Define Combined Rule |


nav: Concurrent:Manager:Rule
name=cuntom rule
application=hyd application
specialixation rule=
include type=program application (AOL)
name=active user
include type=program hyd application name=hyd
user

- Define workshift
nav: Concurrent:Manager:Workshifts
name =hyd workshift
from=09.00
to=18.00
from=mon
to=sat

- Define Manager & attach combined rule + workshift

nav: Concurrent:Manager:Define

manager-hyd manager
short name=hyd
application=hyd application
type= concurrent manager
cache size =3
program library=fndlibr application=aol
(save)
===specialization rules
name=include type=combined rules application =custom application name=hyd
name
work sift
hyd work shift processess =3 (at a time 3 job run)
Note:

Cache Size=1 for long running jobs

Cache Size=4/5 for short running jobs

- Activate the manager


nav: Concurrent:Manager:Administer
hyd manager
(activate)

(bounce the cms)

- Exclude the combined rule from "Standard Manager"

nav: Concurrent:Manager:Define

Query the "Standard Manager"


specialization rule (name=active user)
exclude combinedrule hyd custome hyd ule
- Submit any conc program that is part of combined rule

and check whether Custom Manager is Picking the request or not.

nav: Concurrent:Manager:Administer

FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests.

FND_RUN_REQUESTS
When a user submits a report set, this table stores information about the reports
in the report set and the parameter values for each report.

FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program it
starts running.

FND_DUAL
This table records when requests do not update database tables.

FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system
processes.

FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.

FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by the
Purge Concurrent Request and/or Manager Data program. The Purge Concurrent Request
and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these
statistics.

-> adcmctl.sh stop apps/appspwd

-> adcmctl.sh status apps/appspwd

-> ps -ef grep FNDLIBR grep applmgr

sql>select phase_code from fnd_concurrent_requests;


sql> delete from fnd_concurrent_request where phase_code='c';
sql>commit
sql>select concurrent_queue_name from fnd_concurrent_queues where
concurrent_queue_name like'FNDSM%';

You might also like