Instructions on how to migrate from WSO2 Business Activity Monitor 2.x to WSO2 DAS are as follows.
Migrating analytics data
The analytics data migration tool can be used to migrate the column family data of a WSO2 BAM 2.x server to WSO2 Data Analytics Server (DAS) 3.0.0. The <DAS_HOME>/bin/analytics-migrate.sh script serves as the analytics migration tool.
Sample command
wso2das-3.0.0-SNAPSHOT/bin$ ./analytics-migrate.sh -analyticTable <ANALYTICS_TABLE_NAME> -columnFamily <COLUMN_FAMILY-NAME> -port <PORT> -serverUrl <SERVER_URL> -tenantId <TENANT_ID>
Parameters
The parameters that can be used with the command are described below.
| Parameter | Description | Default Value | Example |
|---|---|---|---|
-analyticTable | Destination name of the table which will have the migrated data. | None | testTable |
-columnFamily | Name of the columnFamily to which analytics data will be migrated. | None | jmx_agent_toolbox |
-port | Cassandra server port. | 9042 | 9042 |
-serverUrl | Cassandra server URL. | localhost | 192.168.200.130 |
-tenantId | Tenant ID of the considered tenant. | super tenant | -1234 |
Example
wso2das-3.0.0-SNAPSHOT/bin$ ./analytics-migrate.sh -analyticTable -columnFamily jmx_agent_toolbox -port 9042 -serverUrl 192.168.200.130 -tenantId -1234
Migrating WSO2 BAM toolboxes
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.