4.1.2 Procedure for designing the system configuration
Design the system configuration according to the following procedure:
- Organization of this subsection
(1) Determining the format for starting the application
Determine the format for starting batch applications. Choose from the following two types:
-
Starting on batch servers
This is the format for starting Java applications on batch servers. You can reduce overhead involved in starting JavaVM using a batch server that is a resident-type JavaVM process. Also, you can use CTM to schedule the execution of the batch applications running on the batch server.
When applications run on batch servers, you can also use DB Connector as the resource adapter.
-
Starting individually using the cjclstartap command
This is the format for starting Java applications in the same way as Java commands. For this format, you must start JavaVM each time batch applications are executed.
If you choose to start the application on batch servers, it will lead to the following items to be determined. If you choose to use the cjclstartap command, the following items to be determined will not be applicable:
(2) Determining the method of using a transaction
For connecting to resources, determine the method of using a transaction. Choose from the following two types:
-
Using a DB Connector
In this method, a DB Connector is used that is a resource adapter provided in the Application Server. You can use connection pooling and statement pooling as the functionality of the DB Connector. You can also use the functionality to control the occurrence of full garbage collection. Note that you can manage a local transaction on batch servers.
-
Directly using a JDBC driver
In this method, the processing required for managing the transaction is implemented using APIs provided in a JDBC driver.
For details about the configuration of the resource adapter and resources if you are using DB Connectors, see 3.3.2 Resource types and resource adapters. However, for a batch server, you can connect only to the database, as a resource.
(3) Checking the security settings
Start the batch server after disabling security protection with SecurityManager.
(4) Deploying a process to output the performance analysis trace file
Check if the PRF daemon (performance tracer) that is a process to output the performance analysis trace file is deployed. Deploy a PRF daemon on each batch server.
(5) Determining the methodology for operating management and operation monitoring
Check if the Management Server that is a process for executing operating management and operation monitoring is deployed. For a batch application execution platform, the Management Server is deployed on the same machine as the batch server (use the host unit management model).
(6) For using other functionality
Determine the following configurations according to the functionality to be used:
-
Configuration in which servers are integrated
Determine this configuration when you want to invoke an Enterprise Bean running on the J2EE server from the batch application. See 3.5 Determining integration between servers.
-
Configuration for node switching using cluster software when a failure occurs
Determine this configuration for node switching on batch servers.
See the following explanation:
When reading the description provided in the above references, please substitute J2EE server for batch server.