4.6 Migrating to the environment using the scheduling functionality
This section describes how to migrate from an environment where the scheduling functionality is not used. When migrating an execution environment of batch applications, from an environment that does not use the scheduling functionality to an environment that uses the scheduling functionality, you cannot use the environment in use, as it is.
In the environment which is in use, you must edit the definition files. The following table describes the files, for which you need to edit the settings, when migrating the environment.
|
File |
Main key to be edited |
Settings |
Required or optional |
|---|---|---|---|
|
usrconf.properties (User property file for batch servers) |
ejbserver.ctm.enabled |
true |
Required |
|
vbroker.agent.enableLocator |
true# |
Optional |
|
|
ejbserver.batch.schedule.group.name |
A schedule group name |
Optional |
|
|
ejbserver.batch.queue.length |
The length of the created schedule queue |
Optional |
|
|
usrconf.cfg (option definition file for batch applications) |
batch.ctm.enabled |
true |
Required |
|
batch.schedule.group.name |
A schedule group name |
Optional |
|
|
batch.request.timeout |
A timeout between a batch execution command and a batch sever, and a timeout between a batch forced stop command or a batch list display command and CTM |
Optional |
|
|
batch.vbroker.agent.port |
A port number being used by Smart Agent |
Optional |
- Legend:
-
Required: You must specify
Optional: Specify as and when required
Note: This section describes the main keys to be edited when migrating to an environment that uses the scheduling functionality. For details on the usrconf.properties file (user property file for batch servers) and the keys, see 3.2.2 usrconf.properties (User property file for batch servers) in the uCosminexus Application Server Definition Reference Guide.
For details on the usrconf.cfg file (option definition file for batch applications) and the keys, see 3.2.5 usrconf.cfg (Option definition file for batch applications) in the uCosminexus Application Server Definition Reference Guide.
#: false is specified by default. However, when integrating with CTM, true is specified automatically.
For details on the parameters to be edited in respective files, see the uCosminexus Application Server Definition Reference Guide.