...
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.
The WSO2 BAM is an on-going project. It undergoes continuous improvements and enhancements with each new release, to address new business challenges and customer expectations. WSO2 invites users, developers and enthusiasts to get involved or get the assistance from our development teams at many different levels through online forums, mailing lists and support options. We are committed to ensure you a fulfilling user experience at any level of involvement with the WSO2 BAM.
What is new in this Release
The WSO2 BAM version 2.0.1 is the successor of version 2.0.0 and built on Carbon 4.0.2 base platform. It has several enhancements and defect fixes included in it. For a list of fixed defects in this release, refer to : WSO2 BAM 2.0.1 - Fixed Issues .
New Features and Enhancements:
- Performance enhancements due to refactoring the Carbon context. (Inherited from new and enhanced Carbon 4.0.2).
- Two new toolboxes added: Activity Monitoring Toolbox and Mediation Statistics Toolbox.
- Load balancing facility in Mediation and Statistics Data Agents.
Known Issues
For a list of known issues in BAM 2.0.1, please refer to the following link in WSO2 Oxygen Tank: WSO2 BAM 2.0.1 - Known Issues .
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
...
For tutorials, articles, Webinars and similar resources, visit the WSO2 Oxygen Tank and search under t he "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:
| Code Block |
|---|
$ svn checkout http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon |
...
.
...
...
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.
| Code Block |
|---|
$ 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:
| Code Block |
|---|
$ mvn clean install -Dproduct=bam |
Execute the following command to commit your changes (SVN will prompt you for password).
| Code Block |
|---|
$ 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:
| Code Block |
|---|
$ 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:
...
| Excerpt | ||
|---|---|---|
| ||
WSO2 Business Activity Monitor Documentation - Forums, support options and community. |