The followings steps describe how to upgrade from an older version of WSO2 ESB to the current version. E.g., Product versions based on Carbon 4.0.0 to newer versions based on Carbon 4.1.0 or 4.2.0. For more information on release versions, see the Release Matrix.
Preparing to
...
upgrade
Before starting the migrationupgrade, complete the following prerequisites must be followed on the database.
- A separate staging database should run as the production database server. As a result, once the migration process is completed, the database server should have the configurations required for a production server.
- Take backups Make a backup of the database and system prior to migrating the database. The system backup can be taken by copying the Carbon server home folder.Shut down all the Carbon servers the <ESB_HOME> directory.
- Stop all Carbon servers that are connected to the database before running the migration scripts.
- Since a separate database (staging database) is used for the migration instead of the actual production database, the data that is collected in the actual production system while the migration is in progress should later be added to the migrated database using a script.
- The database administrator should collect the data portion that is added to the production database, while the migration is in progress. Generally, the WSO2 support team will provide help in these types of situations.
If any files/folders are changing in the product pack to which you are migrating, you need to make a backup of the relevant files/folders prior to changes.
Note New product (e.g. IS 4.5.0) must not be connected to the old database (e.g. IS 4.0.0) without executing the migration script provided in the old database.
...