4.3.2 Processes required for the scheduling functionality
This subsection describes the processes required for the scheduling functionality.
When using the scheduling functionality, you use CTM. The following figure shows an example of the process configuration of Application Server using the scheduling functionality.
|
|
![[Figure]](GRAPHICS/ZU040500.GIF)
The following table gives an overview of the processes used in CTM.
|
Process |
Explanation |
|---|---|
|
CTM daemon |
This process manages the schedule queues for controlling the batch application execution requests. |
|
CTM regulator |
This process distributes and consolidates the batch application execution requests accumulated in a CTM daemon. |
|
CTM domain manager |
This process manages the information of CTM daemons in the same CTM domain. |
|
Global CORBA Naming Service |
This Naming Service shares and manages the batch application information on the hosts that are included in the same CTM domain. |
|
Smart Agent |
This process provides the dynamically distributed directory services that are provided with Cosminexus TPBroker. This process is used when distributing the information to CTM daemons in different network segments. For details, see the Borland(R) Enterprise Server VisiBroker(R) Developers Guide. |
For details on the guidelines to arrange the processes and for the respective processes, see 3. Scheduling and Load Balancing of Requests Using CTM.
The PRF daemon (performance tracer) is also used in CTM as an I/O process to output the performance analysis information, which is output by the CTM daemon. For details, see 7.2.1 Overview of the trace based performance analysis of Application Server in the uCosminexus Application Server Maintenance and Migration Guide.