This section explains how you can to upgrade to WSO2 DAS 3.0.1 from WSO2 BAM 2.5.0 and WSO2 DAS 3.0.0. For more information on release versions, see the Release Matrix.
Note | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
You cannot roll back the upgrade process. However, it is possible to restore a backup of the previous database so that you can restart the upgrade progress. | |||||||||||||||||||||||||||||||||||||||
Localtabgroup |
Localtab | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
This section provides information on how you can upgrade from WSO2 BAM 2.5.0 to WSO2 DAS 3.0.1. For more information on release versions, see the Release Matrix.
Preparing to upgradeThe following prerequisites should be completed before upgrading.
Upgrading the databaseThe instructions in this section describe how you can perform a data migration to upgrade the BAM 2.5.0 database for use in DAS 3.0.1.
Migrating the configurationsHandling event flow related configurationsConfigurable objects used for realtime processing in WSO2 DAS are different to those in WSO2 BAM as explained in the table below. Therefore, they need to be manually reconfigured instead of migrated.
Migrating dataRun the
Handling indexesThe indexing mechanism in WSO2 DAS is different to that in WSO2 BAM. Therefore, the Cassandra custom and secondary indexes cannot be directly migrated to WSO2 DAS. Recommended actionWSO2 DAS uses Apache Lucene for indexing. To use the Lucene indexing functionality, select the required stream attributes as index columns as described in Configuring Indexes. Handling scriptsScripts that analyze data in WSO2 BAM are written in the Apache Hive query language whereas the scripts in WSO2 DAS are written in the Apache Spark SQL query language. Therefore, the syntax of the scripts differ in WSO2 BAM and WSO2 DAS. Due to this, scripts cannot be directly migrated from WSO2 BAM to WSO2 DAS. Recommended actionRedefine the required scripts in WSO2 DAS in the Spark query language. For detailed information on writing queries in the Spark SQL query language, see Spark SQL query language. Handling dashboards and gadgetsThe BAM Dashboard in WSO2 BAM is replaced with the Analytics Dashboard in WSO2 DAS. Since the two dashboards and their gadgets are configured differently, dashboards and gadgets cannot be directly migrated from WSO2 BAM to WSO2 DAS. Recommended actionRedefine the required dashboards and gadgets in the Analytics Dashboard. Handling reportsThe reporting feature is WSO2 BAM is deprecated in WSO2 DAS. Therefore, reports cannot be migrated from BAM to DAS. Migrating artifactsBAM toolbox functionality is not available in DAS. Therefore, it is not possible to migrate a toolbox from BAM to DAS. If you need the artifacts in a BAM toolbox for a particular user case, you need to create a corresponding C-App and deploy it in DAS. For more information on creating and deploying C-Apps, see Packaging Artifacts as a C-App Archive.
Testing the upgrade
|
title | Upgrading from DAS 3.0.0 |
---|
Table of Contents | ||||
---|---|---|---|---|
|
Preparing to upgrade
The following prerequisites should be completed before upgrading.
- Make a backup of the DAS 3.0.0 database and copy the
<DAS_HOME_3.0.0>
directory in order to backup the product configurations. - Download WSO2 DAS 3.0.1 from http://wso2.com/products/data-analytics-server/.
Reindexing data
DAS versions 3.0.0 and 3.0.1 use the same databases. Therefore, you are able to use the same data by connecting to the same databases as DAS 3.0.0 via configuration files. Once DAS 3.0.1 is connected to the same databases as DAS 3.0.0, you need to reindex the data using the Analytics Data Backup / Restore Tool.
Migrating artifacts
To migrate event streams, event receivers, event publishers, execution plans, scripts, dashboard and gadgets, pack them into a C-App and deploy the C-App in DAS 3.0.1. For more information, see Packaging Artifacts as a C-App Archive.