Batch applications are Java™ Platform,
Enterprise Edition (Java EE) applications
that conform to one of the batch programming
models. By rolling out an edition, you replace an active edition with
a new edition.
Before you begin
You must have an application edition that is installed and
started, and have configurator or administrator administrative privileges
to perform this task.
避免困難: Application edition
rollout fails when two user IDs on two administrative consoles attempt
a parallel application edition rollout.
gotcha
About this task
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, you can perform a rollout
to replace the active edition without affecting existing clients.
To roll out a new edition, you must first install the application
edition with the new edition information.
Procedure
- Install the new edition. Specify your new edition
information. Use the following example to specify the new edition.
- Type 2.0 in the Application
edition field.
- Type Second edition in the Application
description field.
- Select the same deployment targets that are used for
the current edition.
- Save and synchronize your nodes.
- Start the rollout. Click OK.
This action starts an interruption-free replacement of the older edition
with your new edition.
Results
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 . 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.