Colony-by-colony upgrade: an example

For more information on a colony-by-colony upgrade, you can review the example of a sharded deployment.

About this task

In this example, the sharded deployment, Production_V1, is deployed on Sterling Order Management System Software Release 9.5, and includes the colonies CLY1, CLY2, and CLY3. The following example describes the process of upgrading CLY1 to Release 10.0:

To upgrade CLY1 to Release 10.0, perform the following tasks:


  1. Create an Upgrade Environment: Upgrade_V1.
  2. Move CLY1 to the Upgrade Environment.
  3. Upgrade Upgrade_V1 to Release 10.0.
  4. Return CLY1 to the Production Environment.


After the colony-by-colony upgrade process is completed, a new sharded production environment, Production_V2, is established. Production_V2 is your new version, active sharded runtime. Production_V2 includes CLY1 running on Release 10.0, and CLY2 and CLY3 running on Release 9.5.

Note: Later, you can upgrade the other colonies, CLY2 and CLY3, to Production_V2 by following the same tasks that you performed to upgrade CLY1 to the production environment. The only exception is that you must create a new upgrade environment every time you upgrade a colony from the sharded deployment to Production_V2. For example, if six months after upgrading CLY1 to Production_V2 you want to upgrade CLY2 to Production_V2, you must create a new upgrade environment. You cannot use Upgrade_V1.