2.12.2 Settings of the execution environment (Setting batch servers)
When you want to migrate Java applications to batch applications, you might need to change the settings of batch servers. This section describes the cases where you need to change setting of the batch servers.
You can use the following two files, which are used in the execution environment of Java applications until now, as it is in the execution environment of a batch server:
-
usrconf.cfg (option definition file for Java applications)
-
usrconf.properties (user property file for Java applications)
However, you must migrate the files, if corresponding to the following conditions:
-
If you set up a storage location of usrconf.cfg (option definition file for Java applications) and usrconf.properties (user property file for Java applications) in the CJCLUSRCONFDIR environment variable
- How to migrate
-
Specify a storage location of usrconf.cfg (option definition file for batch applications) and usrconf.properties (user property file for batch applications) in the CJBATCHUSRCONFDIR environment variable with an absolute path.
-
If you specify an option other than -cp, -classpath, and -D in add.jvm.arg of usrconf.cfg (option definition file for Java applications)
- How to migrate
-
Describe the option settings in usrconf.cfg (option definition file for batch applications). When you want to execute multiple batch applications in a sequence, on one batch server, you must adjust the definition settings. An example is given below. In the example, the value of application 2, for which a greater value is specified, is set up on a batch server.
For example: If add.jvm.arg=-Xmx512m is set up in application 1 and add.jvm.arg=-Xmx768m is set up in application 2,
specify add.jvm.arg=-Xmx768m on the batch server.
-
If ejb.client.log.directory is specified in usrconf.cfg (option definition file for Java applications) and the log output location is changed from the default value
- How to migrate
-
Specify batch.log.directory in usrconf.cfg (option definition file for batch applications) and set up an output location for logs other than the default location.
-
If ejb.client.ejb.log or ejb.client.log.appid is specified in usrconf.cfg (option definition file for Java applications) and the log output location is changed from the default value
- How to migrate
-
There is no method for migration. In the case of a batch server, you cannot specify a log output location that is specified by using ejb.client.ejb.log and ejb.client.log.appid.
-
If ejb.client.directory.shareable=true is specified in usrconf.cfg (option definition file for Java applications) and multiple applications are executing concurrently
- How to migrate
-
You cannot concurrently execute multiple batch applications on one batch server. Therefore, prepare the same number of batch servers as the maximum number of batch applications that will be concurrently executing. Change the server name specified in the cjexecjob command in such a way so that the batch applications operate on the respective batch servers.
-
If the unsupported properties are defined in usrconf.properties (user property file for batch applications)
In usrconf.properties (user property file for Java applications), if you have defined the properties not supported by usrconf.properties (user property file for batch applications)#, you must modify usrconf.properties (user property file for Java applications).
- How to migrate
-
Delete the definition of the properties, not supported by usrconf.properties (user property file for batch applications), from usrconf.properties (user property file for Java applications).
- #
-
This excludes the user-defined property. For details on the properties that are supported by usrconf.properties (user property file for batch applications), see 3.2.6 usrconf.properties (User property file for batch applications) in the uCosminexus Application Server Definition Reference Guide.