Upgrading from WSO2 CEP 4.0.0

This section explains how to upgrade to CEP 4.1.0 from CEP 4.0.0. For more information on release versions, see the Release Matrix.

Preparing to upgrade

The following prerequisites should be completed  before upgrading.

• Make a backup of the CEP 4.0.0 database and copy the <CEP_HOME_4.0.0> directory in order to backup the product configurations.
• Download CEP 4.1.0 from http://wso2.com/products/complex-event-processor/.

Upgrading the databases

The instructions in this section describe how you can perform a data migration to upgrade the 4.0.0 database for use in CEP 4.1.0.

1. Before you upgrade to CEP 4.1.0, create a new database and restore the backup of the CEP 4.0.0 database in this new database.

   Note

   You should NOT connect a new version of WSO2 CEP to an older database that has not been upgraded.

2. Select the relevant script for the upgrade from here and run it on the new database. Running this script will ensure that the new database is upgraded to have the additional tables and schemas that are required for CEP 4.1.0.

   Note

   There are three migration scripts available:  migration-service-provider.sql , migration-identity.sql and  migration.sql. However, only the  migration.sql script is required to be executed for the CEP database upgrade.

Migrating configurations

Follow the procedure below to migrate configurations from CEP 4.0.0 to CEP 4.1.0.

1. Check the configurations in the following files in <CEP_HOME>/repository/conf/data-bridge directory for CEP 4.0.0, and apply the same changes in CEP 4.1.0 manually.
   • data-agent-config.xml
     
   • data-bridge-config.xml

2. Check the configurations in the following files in CEP 4.0.0, and apply same configurations in CEP 4.1.0 manually. 

   Configuration File	Location
   axis2.xml	<CEP_HOME>/repository/conf/axis2
   axis2_client.xml	<CEP_HOME>/repository/conf/axis2
   carbon.xml	<CEP_HOME>/repository/conf
   master-datasources.xml	<CEP_HOME>/repository/conf/datasources
   identity.xml	<CEP_HOME>/repository/conf
   log4j.properties	<CEP_HOME>/repository/conf
   registry.xml	<CEP_HOME>/repository/conf
   catalina-server.xml	<CEP_HOME>/repository/conf/tomcat
   web.xml	<CEP_HOME>/repository/conf/tomcat

3. If the Cipher tool was configured for CEP 4.0.0, check the configurations in the following files and apply the same changes in CEP 4.1.0 manually.

   Configuration File	Location
   cipher-text.properties	<CEP_HOME>/repository/conf/security
   cipher-tool.properties	<CEP_HOME>/repository/conf/security

4. Check the configurations in the other files located in the <CEP 4.0.0_HOME>/repository/conf directory and apply the same changes to CEP 4.1.0 manually.
5. If there are any third party libraries used with CEP 4.0.0 that you want to migrate, copy the following directories as applicable from CEP 4.0.0 to CEP 4.1.0: 
   
   • If you have used JMS libraries, JDBC libraries etc, copy <CEP_HOME>/repository/components/lib.
   • If you have used OSGi bundles such as SVN kit etc, copy <CEP_HOME>/repository/components/dropins.
6. Start the CEP 4.1.0 server. For more information, see Running the Product.

Migrating artifacts

You should manually deploy Composite Application Archive (CAR) files that you have in CEP 4.0.0 to CEP 4.1.0. For more information, see Packaging Artifacts as C-App Archive .

Testing the upgrade

1. When the database upgrade scripts are executed, the following are some of the new tables that will be created in the database:
   • UM_DOMAIN
   • UM_SYSTEM_USER
   • UM_SYSTEM_ROLE
   • UM_SYSTEM_USER_ROLE
2. Verify that all the required scenarios are working as expected. This confirms that the upgrade is successful.