WSO2 ESB includes a data agent that can capture data events and send them to WSO2 Business Activity Monitor (BAM) or WSO2 Complex Event Processor (CEP) using their Thrift API. To enable this integration, you take the following steps:
- Install and configure WSO2 BAM or CEP as described in the BAM documentation or CEP documentation. If you are installing BAM or CEP on the same server as the ESB, be sure to configure the ports as described below.
- Configuring a BAM Server Profile (the same steps apply for configuring a CEP server profile) and one or more streams in the ESB Management Console.
- Add the BAM mediator to your sequence and connect it to the server profile you created step 2.
Configuring the BAM/CEP ports
If you are running BAM or CEP on the same server as the ESB, be sure to set the
<BAM/CEP_HOME>/repository/conf/carbon.xml so there won't be a conflict with the ESB's HTTPS port. For example, if you set BAM's offset to 1, its HTTPS port will be 9444 instead of 9443. You must also increment the Cassandra URL port by the same amount in
<BAM/CEP_HOME>/repository/conf/datasources/master-datasources.xml. For example, if your port offset is 1, change
<url>jdbc:cassandra://localhost:9161/EVENT_KS</url> in both the WSO2BAM_CASSANDRA_DATASOURCE and WSO2BAM_UTIL_DATASOURCE data sources. Additionally, when you set up the BAM server profile in the ESB Management Console, increment the authentication port by the same amount as the offset (such as 7712 instead of the default 7711 if the port offset is 1).