Managing Parallel Concurrent Processing
This essay describes how to manage parallel concurrent processing from System Administration forms. It presents the following topics, each in the context of parallel concurrent processing:
Defining Concurrent Managers
You define concurrent managers using the Concurrent Managers window. When you define a manager, you specify the manager type, which may be either "Concurrent Manager", or "Internal Monitor". There is a third manager type, "Internal Concurrent Manager", that describes the Internal Concurrent Manager process that Oracle Applications predefines for you.
Attention: When using parallel concurrent processing, manager names cannot have embedded spaces in them. Name your managers using one word, or connect two words using a hyphen (manager-name) or underline (manager_name).
To each concurrent manager and each Internal Monitor Process, you may assign a primary and a secondary node. You may also assign primary and secondary system queue names, if a platform-specific queue management system is available on your platform. See: Concurrent Managers.
Administering Concurrent Managers
Using the Administer Concurrent Managers form, you can view the target node for each concurrent manager in a parallel concurrent processing environment. The target node is the node on which the processes associated with a concurrent manager should run.
When a manager's primary node and ORACLE instance are available, the target node is set to the primary node. Otherwise, the target node is set to the manager's secondary node (if that node and its ORACLE instance are available.) During process migration, processes migrate from their current node to the target node.
Control Across Nodes
Using the Administer Concurrent Managers form, you can start up, shut down, migrate, and monitor concurrent managers and Internal Monitor Processes running on multiple nodes from any node in your parallel concurrent processing environment. You do not need to log onto a node to control concurrent processing on it. You can also terminate the Internal Concurrent Manger from any node in your parallel concurrent processing environment.
Starting Up Managers
You start up parallel concurrent processing by issuing an "Activate" command against the Internal Concurrent Manager from the Administer Concurrent Managers form, or by invoking the STARTMGR command from the operating system prompt. Regardless of the node from which you activate the Internal Concurrent Manager, it starts up on its assigned node (assuming that you operate from a node whose platform supports remote process startup.)
After the Internal Concurrent Manager starts up, it starts all the Internal Monitor Processes and all the concurrent managers. It attempts to start Internal Monitor Processes and concurrent managers on their primary nodes, and resorts to a secondary node only if a primary node is unavailable.
Shutting Down Managers
You shut down parallel concurrent processing by issuing a "Deactivate" command against the Internal Concurrent Manager from the Administer Concurrent Managers form. All concurrent managers and Internal Monitor processes are shut down before the Internal Concurrent Manager shuts down.
Most process migration occurs automatically in response to the failure or subsequent availability of a primary node. However, you may migrate processes manually by changing the node assignments for a concurrent manager or Internal Monitor Process using the Concurrent Managers form. To effect your changes, you issue a "Verify" command against the Internal Concurrent Manager from the Administer Concurrent Managers form.
Terminating a Concurrent Process
You can terminate a running concurrent process on the local node or on remote nodes by issuing a "Terminate" command from the Administer Concurrent Managers form.
Administer Concurrent Managers
Controlling the Internal Manager from the Operating System