Page Comparison

...

Upgrade procedure

Follow the instructions below to upgrade the system.

...

1. Stop the current server.

2. To migrate deployment artifacts (including ESB message flow configurations):
   

   • Copy the <ESB_HOME>/repository/deployment/server directory from ESB 4.6.0 to ESB 4.7.0.

     Info
     If you do not have axis2 modules or axis2 services, you can copy the  <ESB_HOME>/repository/deployment/server/synapse-cofigs/default directory instead of all the contents in the <ESB_HOME>/repository/deployment/server directory.

   • Perform any configurations required for the server, e.g., external user stores, clustering, mounting.

3. If there are any external applications used with ESB 4.6.0 that you want to migrate, copy the following directories from ESB 4.6.0 to ESB 4.7.0:
   • ESB_HOME/repository/components/lib 
   • ESB_HOME/repository/components/dropins
4. If you have multiple tenants defined in ESB 4.6.0, copy the ESB_HOME/repository/tenants directory from ESB 4.6.0 to ESB 4.7.0.
5. If you have not mounted the registry space to an external database you should manually copy the registry entries in ESB 4.6.0 to ESB 4.7.0. However. note that it is recommended to mount the registry entries to an external database. See Sharing Registry Space Among Multiple Products.
6. Start the server.

Going into production

The following are a few recommended tests you may carry out to test whether the upgrade has been successfully performed.

...

Once the above tests are run successfully, it is safe to consider that the upgrade is ready for production.  However, you should also test any features that are being used in production.

Downtime

The downtime is limited to the time taken for switching databases.