Migrating BAM 2.0.x to BAM 2.2.0/2.3.0

If you are using WSO2 BAM 2.0.x and want to migrate to WSO2 BAM 2.2.0/2.3.0, you need to migrate the data in Cassandra used by BAM. The reason is because we have made the following improvements to Cassandra and added some metadata regarding column families such as Validator type, and these improvements cannot be achieved to the Cassandra column families already existing in your system.

• When saving events and event streams, you can now view a created column family in Cassandra explorer without any formatting issues in data types such as integer and long.
• We have also changed the stream ID format of a stream definition.

Run the following migration steps in order to upgrade your existing Cassandra database to be compatible with BAM.

1. If you are using embedded Cassandra that comes with BAM, start the BAM server. If you are connecting to an external Cassandra server, start it separately.

2. Edit the properties of the Cassandra configuration in <BAM_HOME>/migration/conf/cassandra-config.xml file according to your setup. By default, the embedded Cassandra server starts on port 9160. If you have started BAM with a port offset value, the embedded Cassandra server's port should be 9160+<port-offset>.
   
   Given below is the dafault configuration of embedded cassandra in BAM.

   <Cassandra-Cluster>
       <clusterName>TestCluster</clusterName>
       <nodes>localhost:9160</nodes>
       <username>admin</username>
       <password>admin</password>
   </Cassandra-Cluster>

3. After you complete editing and verifying the Cassandra cluster information, go to <BAM_HOME>/migration/scripts directory via the terminal and execute the bam_migration.sh file. For example, ./bam_migration.sh.

4. Restart the BAM server and external data agents that you are using to publish data to BAM.

5. You have now successfully migrated your system from BAM 2.0.x to 2.2.0/2.3.0.