Deploy the Updated Project in the Green Environment - BloomReach Experience - Open Source CMS

Deploy the Updated Project in the Green Environment

This documentation applies to Bloomreach Cloud 2 only
This Bloomreach Cloud tutorial assumes you are using Bloomreach Experience Manager 13. If you are using an earlier version, some steps may differ from what is described here.

Previous

In this step you will use Mission Control to create the green environment, use it to deploy and test the new release of your project, and switch production traffic routing from the blue to the green environment.

Upload the Distribution

Log into Mission Control.

Browse the Distributions tab on the Files screen.

To upload the distribution file you created in the previous step, click on the + icon in the bottom right corner, browse to the location of the file on your computer and select it.

Depending on the speed of your network connection the upload can take a while (the distribution file is over 100 MB).

Create the Green Environment

In Mission Control, browse to the environments overview.

Click on the red + icon in the bottom right corner to create a new environment.

Enter the name "green" and click on the Save button.

Announce a Content Freeze

Before making a backup of the blue environment's CMS data, it is important to announce a content freeze to all CMS users. This means that no content changes should be made from the moment the backup is created to the moment production traffic is routed to the green environment.

It is also important to realize that any write operations made by the website during the content freeze will be lost unless manually recovered. This includes visitor data collected by the Relevance Module. If you expect any essential data to be written during the content freeze, make a recovery plan.

Copy the Blue Environment's CMS Data to the Green Environment

Select the blue environment and open the Backups tab.

Click on the + icon in the bottom right corner to create a new backup of the blue environment.

Select the green environment, open the Backups tab, and click on Other available environments.

The available backups are grouped by the environment in which they were created. Click on 'blue' to show the backup for that environment.

Identify the backup of the blue environment you just made and click on it to restore the backup in the green environment.

In the dialog that pops up click on Restore.

This will take a few minutes.

The green environment now contains an exact copy of the blue environment's CMS data.

Deploy the Distribution in the Green Environment

Select the green environment and open the Deployment tab.

Identify the distribution file myproject-1.0.1-distribution.tar.gz and click on it to deploy it.

This will take a few minutes.

As of Bloomreach Experience Manager 13.3.0, the site will be accessible immediately after deployment thanks to the default runtime virtual hosts configuration for Bloomreach Cloud. If you are using version 13.2 or earlier, you must manually configure a virtual host for your site.

Verify the Release in the Green Environment

Verify that the release is working correctly.

Any verification performed at this stage should not contaminate the repository and databases. More extensive and longer acceptance testing should be done in a separate acceptance environment before the blue-green deployment.

If everything is working as expected you are ready to switch production traffic routing from the blue to the green environment.

Route Production Traffic to the Green Environment

In Mission Control, navigate to the environments overview and click on Set Production Environment.

Select the green environment in the Set production environment dropdown, check the Switch domain rules checkbox, and click on Set:

Open the website on the production URL (www.yourcompany.com) and verify that everything is working as expected.

You can now announce the end of the content freeze.

Previous

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?