4.2.2 System configuration of a system that uses the scheduling functionality of batch applications

This subsection describes the system configuration that uses the scheduling functionality of the batch applications, for using a batch server.

Organization of this subsection
(1) Features of system configuration
(2) Processes and software required on each machine

(1) Features of system configuration

This is a system configuration for using a batch server and CTM. In this case, the batch server and CTM are deployed on the Application Server. The batch server and CTM is built and operated as a Web system (ctm-tier) of the Smart Composer functionality. You use batch execution commands for executing batch applications. A batch application executed by directly by command is scheduled using a CTM, and then distributed to the batch servers.

The following figure shows an example of the system configuration for using a CTM. In this example, two batch servers are deployed and the execution request of the batch application is scheduled using a CTM.

Figure 4-4 Example of system configuration for using CTM

[Figure]

For other legend items, see 3.2 Description of the system configuration..

Features
You can execute multiple batch execution commands concurrently by scheduling the execution requests of a batch application using a CTM. Moreover, you must not use batch execution commands for specifying a batch server. Therefore, you can change the number of concurrent executions of the batch server without changing the job definition.
Note that even in this system configuration, you can integrate the system with Batch Job Execution Server or JP1/Advanced Shell.
Flow of the process
A batch application executed by directly by the batch execution command is registered as an execution request of the batch application in the schedule queue of CTM. The execution request of the batch application in the schedule queue is distributed to an appropriate batch server using CTM. Note that the execution request of the batch application is retained (standby) in the schedule queue when the batch server, where the execution request is to be distributed, does not exist.

(2) Processes and software required on each machine

The software and processes required on each machine are as follows:

(a) Application server machine

You must install Application Server on an Application Server machine. Note that for the development environment, you must install Developer.

Additionally, you must also install the following products to execute the batch applications using JP1/AJS, and control the jobs integrated with Batch Job Execution Server or JP1/Advanced Shell:

Products required for integration with JP1/AJS
  • JP1/Base
  • JP1/AJS - Agent
  • JP1/AJS - Manager
  • JP1/AJS - View
Products required for integration with Batch Job Execution Server
  • Batch Job Execution Server
  • Products required for integration with JP1/AJS
Products required for integration with JP1/Advanced Shell
  • JP1/Advanced Shell
  • Products required for integration with JP1/AJS (for executing JP1/Advanced Shell via JP1/AJS)

The following processes are to be started:

When connecting to the database, you also require the software for connecting to the database to be used. For details about the products required for connecting to the database, see 3.6.1 Configuration when using a local transaction. However, you can use only the following databases as resources in a batch server:

(b) Database server machine

For details about the products required in a database server machine, see the description about the machine on which the resource manager operates, in the subsection 3.6.1 Configuration when using a local transaction. However, you can use only the following databases as resources in a batch server: