Versions Compared

Old Version 10

changes.mady.by.user Former user

Saved on

compared with

New Version 11

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Artifact Type in BAM  

Replaced in DAS ByNoteRecommended Action
  • Input Event Adapter
  • Event Builder
Event Receiver

The Event Receiver artifact in DAS 3.0.0 embeds both the Input Event Adapter and Event Builder artifacts in BAM 2.5.0.

Identify the input event adapters and event builders used in combination in BAM 2.5.0, and redefine them as event receivers. For detailed instructions, see Configuring Event Receivers.

  • Event Stream
N/AThe Event Stream artifact in DAS is different to that in BAM since a DAS event stream can be a real time event stream or a persistent event stream, whereas BAM event streams are always defined for persistent data.

Redefine the event streams in DAS 3.0.0 using the following procedure.

  1. Log into the WSO2 BAM Management Console, and go to the Main tab.
  2. Under Registry, click Browse to open the Browse page.
  3. Navigate to <Top_Folder>/system/governance/StreamDefinitions/<relevant_event_stream>/<relevant_stream_version> as shown in the example below.
  4. Click on the stream version. This will open the Detail View tab for the event stream version you selected.
  5. Click Display as Text to view the event stream configuration as a JSON array.
     
  6. Copy the JSON array to the clipboard.
  7. Log into the DAS Management Console and go to the Main tab.
  8. Click Streams to open the Available Event Streams page.
  9. Click Add Event Streams to open the Define New Event Stream page.
  10. Click switch to source view.
  11. Clear the existing text in the source view and paste the JSON array you copied to the clipboard.
  12. Click Add Event Stream.
  13. If you want the event stream to persist events, follow the instructions in Persisting Data for Batch Analytics.

Alternatively, you can redefine the complete event stream configuration as described in Understanding Event Streams and Event Tables.

  • Output Event Adapter
  • Event Formatter
Event PublisherThe Event Publisher artifact in DAS 3.0.0 embeds both the Output Event Adapter and Event Formatter artifacts in BAM 2.5.0.

Identify the output event adapters and event formatters used in combination in BAM 2.5.0, and redefine them as event publishers. For detailed instructions, see Creating Alerts.

  • Execution Plan
N/A

The Siddhi Query Language in DAS 3.0.0 is different to that in BAM 2.5.0.
Therefore, the Siddhi queries of an execution plan directly migrated from BAM cannot function in DAS 3.0.0.

Redefine the execution plans in DAS 3.0.0.

For detailed instructions on defining execution plans, see Creating a Standalone Execution Plan and Creating a STORM Based Distributed Execution Plan.

For the modified Siddhi Query Language, see Siddhi Query Language.

Migrating

...

data

Run the <DAS_HOME>/bin/analytics-migrate.sh script to migrate events data from WSO2 BAM to WSO2 DAS. For detailed information, see Analytics Migration Tool.

...

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.

...

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 Query LanguageSQL query language.

Handling dashboards and gadgets

...

  1. 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
  2. Deploy the toolbox in DAS.
  3. Publish data to WSO2 DAS and check whether they are received by the event receivers configured in DAS.
  4. 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.
  5. Verify that all the required scenarios are working as expected. This confirms that the upgrade is successful.