Managing batch instances

Each running batch process is referred to as a batch processor instance. Each time you start a batch job, a batch processor instance picks up the job and processes it.

Each batch processor instance has a name that is defined in the instanceName property of the Batch.properties file. To define the instance name to be batch01, edit the property as follows:

instanceName=batch01

The batch processor uses instance names to identify each runtime instance. If you attempt to run a batch processor instance when it is already running, the console provides the message Another copy of the bulk processing instance is running: <instance name>.

When a batch processor job begins, its batch processor instance is locked until the process is completed or terminated. A lock file (<instanceName>.lock)) is created in the $home folder. When the batch job is stopped or completed, the lock file is deleted. If the instance crashes, then the lock file remains in the $home folder, but it will not prevent the same batch instance from being started.

When a runtime instance of the batch processor is running:

• You cannot start any other runtime instances of the batch processor using the same instance name.
• You can only start a new batch job on a single batch processor instance after any running batch instances have ended.