Rolling out batch application editions

Batch applications are Java EE applications that conform to one of the batch programming models. By rolling out an edition, we replace an active edition with a new edition.

We must have an application edition installed and started, and have configurator or administrator privileges to perform this task.

Application edition rollout fails when two user IDs on two administrative consoles attempt a parallel application edition rollout.

The new edition might be a simple modification to the application, such as a bug fix, or a more substantial change. As long as the new edition is compatible with earlier versions, we can perform a rollout to replace the active edition without affecting existing clients. To roll out a new edition, first install the application edition with the new edition information.

Tasks

1. Install the new edition. Specify the new edition information. Use the following example to specify the new edition.

   1. Type 2.0 in the Application edition field.

   2. Type Second edition in the Application description field.

   3. Select the same deployment targets used for the current edition.

2. Save and synchronize the nodes.

3. Start the rollout. Click OK. This action starts an interruption-free replacement of the older edition with the new edition.

For an edition that is not in validation mode, the new edition replaces the current edition after the rollout completes. An edition that is in validation rolls out on the original deployment target and the cloned environment is deleted. If the jobs of the batch rollout application are running on the quiesced endpoint, the job scheduler will cancel the jobs after the drainage time.

What to do next

To validate the results, select...

Applications > Edition Control Center > application_name

Your new edition is the active edition on the deployment target. The new edition automatically starts, because it replaces a running edition.

When an application edition in validation mode is rolled out, the binding names must be changed back to the original values. For example: /clusters/cluster1-validation/jdbc/CustomerData must be changed back to /clusters/cluster1/jdbc/CustomerData.

Related:

Batch jobs and their environment