Edition rollout settings

Use this page to configure your edition rollout settings.

To view this administrative console page, click Applications > Edition control center > application_name > select edition > Rollout.

Java Platform, Enterprise Edition (Java EE) rollout settings

You can use the following settings for Java EE applications:

Rollout strategy

Specifies which strategy to use when rolling out an application edition. The default rollout strategy is grouped.

Use the atomic rollout option to serve all user requests with a consistent edition of the application. This option causes your cluster to run at half capacity. If your cluster is very large, group rollout might better suit your needs.

Atomic: Rolls out half of the cluster at a time. The previous edition is served until the first half of the cluster is available to serve the next edition. At that time, the old edition is taken offline and the remaining half of the cluster is rolled out. The cluster serves user requests either from one edition or the other.
Grouped: Specifies to perform the rollout across the clusters in groups of servers, n servers at a time, where 1 <= n <= size of cluster. The next edition replaces the previous edition n servers at a time. If a value of n is specified such that n >= size of cluster, the group size is internally resized to (size of cluster) -1. During this period, both the next and previous editions of the application can be available to serve user requests until the rollout completes. The default group size is 1.

Reset strategy

Specifies how to restart the application. The default reset strategy is soft reset.

Soft reset: Resets the application by restarting the application.
Hard reset: Resets the application by restarting the server.

Drainage interval

Specifies the number of seconds to wait for hypertext transfer protocol (HTTP) requests to complete before starting the reset strategy. The default is 30 seconds.

Session Initiation Protocol (SIP) rollout settings

You can use the following settings for SIP applications:

Quiesce options

Specifies how old servers or cluster members that host the current edition are removed. This setting does not affect the new edition that is being rolled out.

Quiesce server or cluster members after all active sessions or dialogs are completed: Removes the server or cluster member when all of the active sessions and dialogs for the server or cluster member complete.
Quiesce servers or cluster member after the specified interval: Removes the server or cluster member after a specified time period. Specify an amount of time, in seconds, minutes, or hours.

File name: app_edition_roll.html