This assumes you have done the following:

• Created a new edition of an application 
• Setup routing rules
• Validated the edition
• Activated the edition

Rolling out an application is a way to replace an active edition with a new edition. In Editon Control Center, select the higher version of the application and select Rollout. You will be prompted to select a rollout strategy, a reset strategy, and a drainage interval.

Rollout strategy

There are two possible rollout strategies:

• group rollout
• atomic rollout

A group rollout pushes the new edition to every application server in the cluster, whereas an atomic rollout pushes the new edition to each application server in the cluster, one at a time. Atomic means "one at a time". An atomic rollout guarantee's that all requests will be sent to the new edition of the application. If requests are submitted while the new application is being rolled out, the requests will be queued until the rollout is completed, and then the requests will be served by the new edition of the application.

Reset strategy

There are two possible rollout strategies:

• soft reset
• hard reset

Both a soft and hard reset will restart the application servers the application is being rolled out to. With a soft reset, process memory and any native libraries used by the application will not be refreshed. With a hard reset, process memory and any native libraries used by the application will be reset.

Drainage Interval

The drainage interval is the number of seconds to wait before the reset strategy is kicked off, to give time for HTTP sessions to complete. By default, the drainage interval is 30 seconds.