Concurrent Managers Window In Oracle apps

Concurrent Managers Window

Use this window to define your concurrent managers. You can determine when a manager runs and how many programs a manager can start simultaneously when you assign workshifts to the manager. Determine which programs a manager can start by defining specialization rules.

Concurrent Managers Block

The combination of an application and the name you define for your manager uniquely identifies the manager.
Application
The application name does not prevent a manager from starting programs associated with other applications. To restrict a manager to only running programs associated with certain applications, go to the Specialization Rules window.
Type
Once you define a concurrent manager, you cannot update this field. There are several types of managers:

Concurrent Manager	Concurrent Managers start concurrent programs running.
Internal Monitor	Internal Monitors monitor the Internal concurrent manager in a parallel concurrent processing environment. If the Internal Concurrent Manager exits abnormally (for example, because its node or its database instance goes down), an Internal Monitor restarts it on another node.
Transaction Manager	Transaction managers handle synchronous requests from client machines.

Transaction Managers
Requesting Transaction Managers
Cache Size (Concurrent Manager only)
Enter the number of requests your manager remembers each time it reads which requests to run. For example, if a manager's workshift has 1 target process and a cache value of 3, it will read three requests, and try to run those three requests before reading any new requests.

Suggestion: Enter a value of 1 when defining a manager that runs long, time-consuming jobs, and a value of 3 or 4 for managers that run small, quick jobs.

Data Group (Transaction Manager only)
The data group the transaction manager uses to connect to the database. Transaction managers only run programs submitted from responsibilities that use the same data group as the transaction manager.
Node
If you are operating in a parallel concurrent processing environment and you want your manager to operate on a specific node, select the name of the node.
The primary node, if available, is the node your concurrent manager operates on. If the primary node or the database instance on it goes down, your concurrent manager migrates to its secondary node. Your concurrent manager migrates back to its primary node when that node becomes available.
Nodes must be previously registered with Oracle Applications, using the Nodes form. See: Nodes.
System Queue
If you are operating in a parallel concurrent processing environment and you want your manager to use a platform-specific queue management system instead of generic concurrent processing queue management, specify the queue or class name of that system. For example, you may choose a system queue name from a platform-specific queue management system like NQS or IBM Load Leveler.
The primary system queue is the queue you associate with the primary node. The secondary system queue is the queue you associate with the secondary node.

Attention: To ensure that your manager uses your platform-specific queue management system, you should start the concurrent managers in the proper mode (set APPLDCP = OSQ). Refer to platform-specific documentation to determine if your platform supports interfacing with system queues. For Unix platforms, refer to the appropriate Oracle Applications Installation Update. For all other platforms, refer to the appropriate Oracle Applications Installation Guide.

Immediate concurrent programs must be registered in a program library by an applications developer using Oracle Application Object Library.
See: Developing Custom Extensions to Oracle Applications
Program Library
Concurrent managers can run only those immediate concurrent programs listed in their program library. They can also run concurrent programs that use only other type of concurrent program executable.
Transaction Managers can only run programs listed in their program library.

Defining Manager Operations

The two buttons near the bottom of the window display additional windows for defining when your manager operates, and, if you wish, specializing your manager to run only certain kinds of programs.

Work Shifts	You define when the manager operates by assigning one or more work shifts to your manager. With each work shift, you can vary the number of programs the manager can run simultaneously.
Specialization Rules	You define what kinds of requests the manager reads by defining specialization rules for your manager.

Work Shifts Window

Assign work shifts to a concurrent manager. A work shift defines the dates and times the manager is enabled. For each work shift you define the number of processes the manager starts running.
Work shifts are defined using the Work Shifts form. See: Work Shifts.
Processes
Enter the number of operating system processes you want your work shift to run simultaneously. Each process can run a concurrent request.
For example, if a work shift is defined with three (3) target processes, the manager can run up to three requests simultaneously.
Sleep Seconds
Enter the sleep time for your manager during this work shift. Sleep time is the number of seconds your manager waits between checking the list of pending concurrent requests (concurrent requests waiting to be started).

Suggestion: Set the sleep time to be very brief during periods when the number of requests submitted is expected to be high.

Specialization Rules Window

Specialize your manager to run only certain kinds of requests. Without specialization rules, a manager accepts requests to start any concurrent program.
Include/Exclude
Select from the poplist whether or not to include or exclude those requests that are based on the rule to run.
Type
Select the type of specialization rule you want to assign to your manager. Based on the rule's action you selected, allow or disallow, requests can be run by your manager according to a:

• Combined Rule

For example, only requests that satisfy the combined rule you select are allowed to be run by your manager. Or conversely, requests that satisfy a certain combined rule are excluded from running.

Combined specialization rules, which combine more than one logical statement, are defined using the Combined Specialization Rules form. See: Combined Specialization Rules.

• ORACLE ID

For example, programs with a certain ORACLE ID are excluded from running. Or conversely, a concurrent manager only includes programs with a specific ORACLE ID.

• Program

For example, only the program you select is excluded from running. Or conversely, a concurrent manager only includes the programs you select. You can also include or exclude all programs belonging to a specific application using the Program type by entering the application in the Application field and leaving the Name field empty.

• Request Type (of the program)

For example, programs of a certain request type are excluded from running. Or conversely, a concurrent manager only includes programs with the request type you select.

• User (application username at sign on)

For example, all programs submitted by a certain user are excluded from running. Or conversely, a concurrent manager includes only programs submitted by the user you select.