You must perform batch server settings, if you want to use batch application execution functionality. Implement the batch server settings in the Easy Setup definition file.

Note

By default, the scheduling functionality is not used (set to false). When not using the scheduling functionality, do not change settings of the following parameter and key.

• ejbserver.ctm.enabled parameter of a logical J2EE server (j2ee-server) in the Easy Setup definition file.
• batch.ctm.enabled key in usrconf.cfg (object definition file for batch application)

You specify the definition of batch application execution functionality in the <configuration> tag of the logical J2EE server (j2ee-server) of the Easy Setup definition file.

The following table describes the definition of batch application execution functionality in the Easy Setup definition file.

Table 2-9 Definition of batch application execution functionality in the Easy Setup definition file

Field	Parameter to be specified	Specification contents	Required or Optional
Setting for building a server as a batch server	batch.service.enabled	To build a server as a batch server, make sure to specify true.	Required
Setting for not using SecurityManager	use.security	SecurityManager is not used. Make sure to specify false in parameter value.	Required
Setting for enabling light transaction functionality	ejbserver.distributedtx.XATransaction.enabled	You cannot use global transactions. You use local transactions#1. Make sure to specify false in parameter value. Because false is set up by default, do not change this parameter	Required
Setting of not using the Explicit Memory Management functionality	add.jvm.arg	If the Explicit Memory Management functionality is not implemented in batch application, we recommend disabling the Explicit Memory Management functionality. To disable the Explicit Memory Management functionality, specify -XX:-HitachiUseExplicitMemory as a value of parameter. In case of default settings, the Explicit Memory Management functionality is enabled (-XX:+HitachiUseExplicitMemory).	Optional
Setting of real server name	realservername	Specify real server name of the batch server. If real server name is omitted, logical server name is specified.	Optional
Setting of JavaVM operation when invoking JavaVM end method	ejbserver.batch.application.exit.enabled	If you invoke the following JavaVM end methods in a batch application, specify whether JavaVM is to be ended. java.lang.System.exit(int) java.lang.Runtime.exit(int) java.lang.Runtime.halt(int) Default value is true (end the thread of batch application without ending JavaVM). If you specify true or omit the setting, when you invoke JavaVM end method, thread of the batch application (thread belonging to batchThreadGroup) is ended and JavaVM is not ended. If you specify false, when you invoke JavaVM end method, JavaVM is ended for each batch server. As a result, you cannot use JavaVM end method and shut down hook in the batch application. #2	Optional

Legend:

Required: Must be specified

Optional: Specify as and when required

# For details on the Easy Setup definition file and parameters, see uCosminexus Application Server Definition Reference Guide.

#1 In the case of a batch server, you use the light transaction functionality that provides the optimized environment in a local transaction. The light transaction functionality is enabled, if false is specified in the ejbserver.distributedtx.XATransaction.enabled parameter.

#2 If false is specified in the ejbserver.batch.application.exit.enabled parameter, you cannot use the JavaVM end method and shutdown hook. Take actions as followings:

• Actions for the JavaVM end method
  You code the batch processing contents in the public static int main(String[]) method. When returning end code, you use return end-code. However, if you use return, the finally block is executed.
  
• Actions for shutdown hook
  If you want to implement processing, when closing a batch application, code the processing in the finally block of the main method.