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.
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.|
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.
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.
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
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.
|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 are defined using the Work Shifts form. See: Work Shifts.
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.
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.
Select from the poplist whether or not to include or exclude those requests that are based on the rule to run.
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:
Life cycle of a concurrent request
Defining Managers and their Work Shifts
Overview of Parallel Concurrent Processing
Administer Concurrent Managers field help
Work Shifts field help
Combined Specialization Rule field help
Concurrent Request Types field help
Nodes field help