Performing a rollout on an edition
When you perform a rollout on an edition, you replace an active edition with a new edition. The new edition might be a simple modification to the application, or contain a more substantial change. If the new edition is compatible with earlier versions, then you can perform a rollout to replace the active edition without impacting existing clients. To perform a rollout on a new edition, you must first install the application edition with the new edition information.
Before you begin
- Performing a rollout fails when two user IDs on two administrative consoles attempt to complete the process in parallel.
- Tune the SOAP connector properties to set the request timeout value for the deployment manager
to be greater than the total time required to perform a rollout on your system, and restart the
deployment manager. Not setting the property can cause the rollout process to fail when the
requestTimeout
value expires. The formula to estimate the value to set is number-of-groups-to-rollout * (drainage-interval + internal-quiesce-timeouts-approximately-5minutes + application-or-server-restart-times-approximately-10minutes). Alternatively, you can set the value to zero to disable the timeout.- If you are performing the rollout using the wsadmin tool, adjust the request
timeout value by setting the
com.ibm.SOAP.requestTimeout
property in the soap.client.props in the deployment manager profile. The default value is 180 seconds and should be increased adequately. - If you are performing the rollout using the administrative console, adjust the request timeout
value by clicking
For more information, read about Java™ Management Extensions connector properties.
. The default value is 600 seconds and should be increased adequately.
- If you are performing the rollout using the wsadmin tool, adjust the request
timeout value by setting the
- If you are performing a rollout within the administrative console, set the session expiration for the administrative console to a value greater than the amount of time required for the entire rollout process to end. Multiply the request timeout value by the number of groups processed during the rollout. For more information about session expiration for the administrative console, read about changing the console session expiration.
- You must define a multi-cluster routing policy for each new edition you install before you can perform a rollout. Use the administrative tasks to add multi-cluster routing policies for your new editions. For more information about multi-cluster routing policies, read about rules for ODR routing policy administrative tasks.
About this task
You can also use the application edition manager if you want to perform a rollout to batch applications. These are Java Enterprise Edition 5 (Java EE 5) applications that conform to one of the batch programming models.
Procedure
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. The routing rules are updated to begin routing to your new edition.
During the application rollout process, errors that occur in the first group of targets are handled differently than errors that occur in later groups. In atomic rollouts, the first group is the first half of the targets where the new edition is activated. In group rollouts, the first group refers to the first group of targets where the new edition is activated. If an error occurs during the rollout on the first group of targets (for example an application or a server fails to start), the rollout process fails. The current application edition remains in active state. If an error occurs after the rollout on the first group of targets, the rollout process completes successfully. The new application edition is now in active state. The old application edition moves into inactive state.
What to do next
To validate the results, click
. Your new edition is the active edition on the deployment target. The new edition automatically starts, because it replaces a running edition.When you perform a rollout on an edition in validation mode, the binding names are changed back
to the original values. For example,
/clusters/cluster1-validation/jdbc/CustomerData
is changed back to
/clusters/cluster1/jdbc/CustomerData
.