A term coined by Gartner, business activity monitoring refers to aggregating, analyzing and presenting information about business activities. This definition is paramount when designing a solution to address a business activity monitoring use case. The aggregation refers to the collection of data. The analysis refers to the manipulation of data to extract information. Presentation refers to representing this data visually or in other ways such as alerts. The WSO2 BAM architecture reflects this natural flow in its very design.
WSO2 Business Activity Monitor (BAM) is designed to address a wide range of monitoring requirements in business activities and processes. It is a flexible framework allowing to model your own key performance indicators to suit different stakeholders, may it be business users, dev ops, CxOs etc. WSO2 BAM achieves this level of flexibility, while facilitating technologies such as Big Data storage, Big Data analytics and high performance data transfer.
SOA encourages systems to expose business functions as services. It is required to start monitoring these exposed services in order to gain insight and transparency to business activities. By plugging into services, data can be harnessed as valuable information. But, the amount of information that is flowing through an organization's systems is enormous. Therefore, all this data needs to be collected and processed by a system capable of handling Big Data loads, capable of handling data volumes of TeraBytes or even PetaBytes with relative ease. WSO2 BAM is designed to be significantly scalable to sustain large amounts of corporate data loads when aggregating, analyzing and presenting data. This is another reason why WSO2 BAM is a best-fit for businesses.
Community Resources
WSO2 is willing to provide you guidance for any technical issues or questions regarding the BAM product. You can communicate with the WSO2 BAM development team directly using the relevant mailing lists mentioned here: http://wso2.org/mail
WSO2 encourages you to report issues and enhancement requests for WSO2 BAM using the publicJIRA available at https://wso2.org/jira/browse/BAM. You can also track their resolutions and comment on the progress.
Questions regarding BAM can also be raised through http://stackoverflow.com. Ensure that you tag the question with appropriate keywords such as WSO2 and Business Activity Monitor so that our team can easily find your questions and provide answers. You can also browse old threads in the WSO2 BAM Forum.
For tutorials, articles, Webinars and similar resources, visit the WSO2 Oxygen Tank and search under the Resources menu.
Support Options
WSO2 also offers a variety of development and production support programs, ranging from Web-based support during normal business hours, to premium 24x7 phone support. WSO2 is committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that support leverages the open development methodology and is provided by the very same engineers who build the products. For additional support information please refer to http://wso2.com/support.
Get Involved
WSO2 invites you to contribute by checking out the source from SVN using the following commands. This project uses Subversion to manage its source code. Instructions on Subversion can be found at http://svnbook.red-bean.com.
The WSO2 BAM release 2.0.0 is based on Carbon 4.0.0.
Anonymous Checkout
The complete source including the Carbon platform can be checked out anonymously from SVN with this command:
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon
The list of commands that can be run are as follows. If you only want to build the Application Server, you have to always use the option "-Dproduct=as".
| mvn clean install -Dproduct=bam | To create the complete release artifacts of WSO2 BAM including the binary and source distributions. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bam | To create the complete release artifacts of WSO2 BAM including the binary and source distributions, without running any of the unit tests. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=bam -o | To create the complete release artifacts of WSO2 BAM including the binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you've already built the source at least once. |
Developer Access
Everyone can access the Subversion repository via HTTPS, but Committers must checkout via HTTPS. The Carbon framework related source code can be checked out using the following commands.
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
The Carbon core project is the root project of the OSGi platform on which the Java product stack is built. The Carbon components contain all the components not just the Application Server specific ones. Therefore, you need to build just the set of components required by the Application Server, using the following command:
$ mvn clean install -Dproduct=bam
Execute the following command to commit your changes (SVN will prompt you for password).
$ svn commit --username your-username -m "A message"
Access through a Firewall
If you are behind a corporate firewall which is blocking http access to the Subversion repository, you can try the developer connection:
$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbon
Access through a Proxy
The Subversion client can be configured to access through a proxy.
1) Specify the proxy to use in the "servers" configuration file in:
- "~/.subversion" directory for Linux/Unix
- "%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")
2) There are comments in the file explaining what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.
Example : Edit the 'servers' file and add something similar to:
[global] http-proxy-host = your.proxy.name http-proxy-port = 3128