...
Run the <DAS_HOME>/bin/analytics-migrate.sh script to migrate data from WSO2 BAM to WSO2 DAS. For detailed information, see Analytics Migration Tool.
| Info |
|---|
WSO2 BAM uses Cassandra as the event store. In WSO2 DAS, you can select either Cassandra, RDBMS or HBase as the event store. The |
Handling indexes
The 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 action
WSO2 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 scripts
Scripts 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 action
Redefine 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.
...
The 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 action
Redefine the required dashboards and gadgets in the Analytics Dashboard.
Handling reports
The reporting feature is WSO2 BAM is deprecated in WSO2 DAS. Therefore, reports cannot be migrated from BAM to DAS.
Migrating artifacts
BAM 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.
| Info |
|---|
The artifacts deployed in the C-App should be DAS artifacts and not BAM artifacts. e.g., The scripts included should be Spark scripts instead of Hive scripts. |
Testing the upgrade
- 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
- Deploy the toolbox in DASthe C-Apps you created to correspond with the relevant BAM toolboxes and check whether all the required artifacts are successfully created in your DAS environment.
- Publish data to WSO2 DAS and check whether they are received by the event receivers configured in DAS.
- Execute the scripts you redefined in the Spark SQL query language, and use the Data Explorer and/or the Analytics Dashboard to view the results.
- Verify that all the required scenarios are working as expected. This confirms that the upgrade is successful.