Following are the few default tool boxes that are offered with WSO2 BAM 2.4.2. Out of these toolboxes, some have a more generic use, whereas the others address specific use cases.
| Toolbox | Description |
|---|---|
| HL7 | |
| HTTPD Logs | A toolbox with necessary artifacts (analytic scripts, visualization gadgets etc.), which are intended to demonstrate the capability of WSO2 BAM to analyze raw HTTD logs and produce useful analytics. For a demonstration of a sample scenario see, Analyzing HTTPD Logs. |
| JMX Stats | A toolbox with necessary artifacts which are intended to monitor JMX attributes of a required JMX enabled server and produce useful analytics. |
| KPI Phone Retail Store Toolbox | A toolbox with necessary artifacts (analytic scripts, visualization gadgets etc.), which are intended to monitor key performance indicators of a sample phone retail store. For a demonstration of a sample scenario see, Monitoring key Performance Indicators. |
| Mediation Statistics Toolbox | A toolbox with necessary artifacts (Hive scripts, data stream definitions, properties files, gadgets etc.), which are required to collect and monitor activities related to services deployed in any WSO2 service-hosting product (WSO2 Enterprise Service Bus, WSO2 Application Server, WSO2 Data Services Server etc). For more information, see Mediation Statistics Toolbox. |
| Message Tracing | |
| Mobile Web Channel Monitoring | |
| Realtime Traffic | |
| Service Statistics Toolbox | A toolbox with necessary artifacts (Hive scripts, data stream definitions, properties files, gadgets etc.), which are required to collect and monitor statistics related to services deployed in any WSO2 service-hosting product (WSO2 Application Server, WSO2 Data Services Server etc.). For more information, see Service Statistics Toolbox. |
| We Apps Stats Monitoring |
Toolboxes bundled with BAM are using embedded H2 databases to persist summarized data. These toolboxes can be configured to work with a default BAM installation. Therefore, if you change the default settings (port offset and H2 database), change the Hive script accordingly. For example: If port offset is set to 1 in the BAM server instance used, you should update the Hive script as " cassandra.port" = "9161".