This subsection describes the system configuration that does not use the scheduling functionality of the batch applications, for using a batch server.
This is a system configuration for using a batch server and not a CTM. In this case, the batch server is deployed on the Application Server. The batch server is built and operated as a Web system (j2ee-tier) of the Smart Composer functionality. Use batch execution commands to execute a batch application.
The following figure shows an example of the system configuration for deploying a batch server. In this example, HiRDB is accessed from the batch application using a resource adapter.
Figure 4-3 Example of the system configuration for deploying a batch server
For other legend items, see 3.2 Description of the system configuration..
The software and processes required on each machine are as follows:
You must install Application Server on the Application Server machine. Note that for the development environment, you must install Developer.
The following processes are to be started:
When connecting to the database, you also require the software for connecting to the database that you want to use. For details about the products required to connect 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:
For details about the products required in a database server machine, see the explanation about the machine on which the resource manager operates, in the section 3.6.1 Configuration when using a local transaction. However, you can use only the following databases as resources in a batch server: