Upgrading from a Previous Release

This page takes you through the steps for upgrading from ELB 2.1.0 to ELB 2.1.1. For more information on release versions, see the Release Matrix.

Upgrading ELB 2.1.0 to ELB 2.1.1 does not require any database upgrade and mainly involves configuration changes.

The following are the specific prerequisites you must complete before you upgrade ELB 2.1.0 to ELB 2.1.1.

Stop all the WSO2 Carbon-based servers connected to the production environment.

Note that the upgrade should be done during a period when there is low traffic on the system.

The downtime is limited to the time taken for the configurations to be done before the ELB is updated in the production environment.

To upgrade the configurations to the new ELB:

Download ELB 2.1.1.
Redo the configurations you made for ELB 2.1.0 in ELB 2.1.1.

Note that configurations should not be copied directly between servers. These configuration changes to be done are the same ones you did for ELB 2.1.0. These are typically the changes made to the <ELB_HOME>/repository/conf/loadbalancer.conf file and the <ELB_HOME>/repository/conf/axis2/axis2.xml file. This connects ELB 2.1.1 to your cluster/deployment.
Remove ELB 2.1.0 completely from your production environment. This step is necessary as it ensures that ELB 2.1.1 is the version of the WSO2 ELB connected to your cluster/deployment.
Start the ELB and restart all other WSO2 Carbon-based servers. See Running the Product for more information on starting the ELB.