Skip to main content

Posts

Showing posts from 2013

Workflow Extentions with WSO2 AM 1.6.0

This is a major requirement raised by many WSO2 API Manager users many times and finally it was introduced with latest WSO2 APIManager 1.6.0 release.It's the ability of plugin workflow extensions in to APIManager major functionalities. As the first cut,we have introduced workflow extension support for below three major functionalities; User Signup API Subscription  Application Creation By default,APIM binary pack is shipped with a java workflow executor and a web service executor to trigger workflow processes on above three functions and that executor can be defined and configurable via api-manager.xml file.If you wish to add your own workflow executor on each above three processes,that also possible.What you have to do is write your own custom executor and integrate it to WSO2 APIM pack via a configuration change in api-manager.xml file.For more information,please refer  http://docs.wso2.org/display/AM160/Adding+Workflow+Extensions . Addition to providing abil...

Digging to WSO2 BAM

From this blog-post,I'm going to explain how to setup WSO2 BAM 2.3.0 clustered setup with getting data from mediation agents[WSO2 ESB] and service agents[WSO2 AS]. Components of the setup 1. ESB Cluster 2. AS Cluster 3. BAM Cluster     --- Two DR nodes     --- Four cassandra nodes     --- Two DA nodes     --- Two zoo-keeper nodes     --- One dashboard node WSO2 BAM is used to aggregate ,analyze and visualize the data events coming from different agents. By default WSO2 BAM contains data agents for --Collecting mediation statistics --Collecting service statistics  and more.To get more information on it,please refer [ 1 ]. Once different data agents send different stat events to BAM side,first those row data will be stored to BAM integrated No-SQL cassandra data store . Note - In WSO2 BAM,primary default data-store would be No-SQL cassandra and secondary data store is H2 based RDBMS databa...