Versions Compared

Old Version 6

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

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

Message Tracing is used to trace, track and visualize a message's body in each intermediate stage of its transmission. This is useful for a number of reasons, including auditing and debugging. You use the Activity Dashboard of WSO2 BAM to trace messages going through WSO2 ESB. It allows you to track and trace messages in real-time within Cassandra, without having to write Hive scripts.

...

  1. Download and set up WSO2 ESB.
  2. Log in to ESB management console and select Features under the Configure menu.
  3. In the Repository Management tab click Add Repository.
  4. Enter a name for the new repository and its URL as http://product-dist.wso2.com/p2/carbon/releases/turing/, and click Add.
    add new repository
  5. Go to the Available Features tab and select the newly added repository from the Repository drop-down list. Under Filter by feature name field, enter BAM Message Tracer Handler Aggregate, select Show only the latest versions checkbox, and deselect Group features by category checkbox. 
  6. Click Find Features.
  7. Select BAM Message Tracer Handler Aggregate feature 4.2.2 version from the available features list and click Install. 
    select the feature from the repository
  8. Click Finish to complete the installation and click Shutdown/Restart on the left navigation menu to restart the server.

...

Publishing data to WSO2 BAM

  1. After message tracing is configured, invoke a deployed service on WSO2 ESB (for example: echo service) for data publishing.
     

    Tip

    You need to first enable the relevant message tracer feature in WSO2 ESB before deploying the proxy service.

  2. Log in to BAM management console to check whether data is being published to BAM. 
  3. On the Tools menu, click Cassandra Explorer and then click Explore Cluster.
  4. Enter the default values as localhost:9160, admin and admin respectively for Connection URL, Username and Password and click Connect.
  5. In Keyspaces, check for the published contents in the BAM_MESSAGE_TRACE column family, which is located in the EVENT_KS keyspace.

  6. As soon as data is published and available, on the Main menu select Activity Dashboard to track and trace messages.
  7. In the Connect to Cluster window, enter the same details as entered in step 11 above and click Login.
  8. In the Search Activities window, enter the query details related to your search and click Search. For example:

  9. You view the resulting activities of the search query you entered in the previous step as below:

...