Instructions on how to migrate from WSO2 Business Activity Monitor 2.x to WSO2 DAS are as follows.
...
| Parameter | Description | Default Value | Example | |
|---|---|---|---|---|
| Destination name of the table which will have the migrated data. | None | testTable | |
| Name of the columnFamily to which analytics data will be migrated. | None | jmx_agent_toolbox | |
| Tenant ID of the considered tenant. | super tenant | -1234 | |
-serverUrl | The URL of the DAS server URL. | localhost | 10.100.5.73 | |
-serverPort | DAS server The Cassandra CQL port | 944390429443 | 9042 | |
-cassandra_URLcassandraUrl | The URL to access the Cassandra server. | 9160 | 9160localhost | 10.100.5.73 |
-cassandraPort | The thrift port for the Cassandra server port. | 904291609042 | 9160 | |
-batchSize | Cassandra data is migrated from BAM to DAS in batches. This property specifies the size of a batch of data transferred at a given time. | 1000 | 1000 | |
-username | The username to access the Cassandra server. | None | admin | |
-passwords | The password to access the Cassandra server. | None | admin | |
-clusterName | The name of the cluster to which the data should be migrated. | None | cluster001 |
...
Toolboxes concept of WSO2 Business Activity Monitor is replaced in WSO2 DAS by a CAR file based deployment approach. Since you need to map Hive queries to the Apache Spark syntax that is supported by WSO2 DAS, you cannot directly upload WSO2 BAM (2.x versions) toolboxes to WSO2 DAS. Thereby, you need to wrap all the artifacts (stream definitions, event receivers, event stores, event publishers, Spark scripts etc.) in a .car file and upload it to WSO2 DAS. For instructions on how to create a Carbon application with the CAR extension, see Carbon Application Deployment for DAS. However, you can use the analytics migration tool to migrate the data from Cassandra to the DAS datasource.