Updating MWARE ESB¶
MWARE introduces ESB Updates, which is a command-line utility that allows you to get the latest updates that are available for a particular product release. These updates include the latest bug fixes and security fixes that are released by MWARE after a particular product version is released. Therefore, you do not need to wait and upgrade to the next product release to get these bug fixes.
ESB in-place updates¶
The ESB in-place updates tool allows you to update your currently used product by fetching updates from the server and merging all configurations and files. The tool also gives backup and restore capability.
ESB Updates 2.0¶
You should manually merge the updated configuration files or use a tool like Puppet. You should store backups with the custom configurations in your system, in case you have to restore later.
Warning
Tip
Before you discard the old ESB instance,
You must take a backup of the <API-M_HOME>/repository/data directory and copy it to the ESB binary pack in the <API-M_HOME>/repository/data directory that is updated.
Persisting WSO2CarbonDB
To avoid conflicts that can be occurred in the update process, it is recommended to persist the local H2 databases as well.
Tip
Before you discard the old ESB instance,
Take a backup of <API-M_HOME>/repository/database/WSO2CARBON_DB.h2.db and replace it to the ESB binary pack in the <API-M_HOME>/repository/database directory that is updated.
If you are using the existing local H2 database for WSO2MetricsDB as well,
Take a backup of <API-M_HOME>/repository/database/WSO2METRICS_DB.h2.db and replace it to the ESB binary pack in the <API-M_HOME>/repository/database directory that is updated.
For more information on run time and configuration artifact directories of ESB refer Common Runtime and Configuration Artifacts .