Open Space

From this blog-post,I'm going to dig into the implementation of monitoring support provide by WSO2 API Manager with WSO2 BAM integration.First you need to know how to configure WSO2 AM with BAM to start with.You can find about the related configuration details from our product documentation .  However,before continue with this post,I think its better if I explain one step of above configuration.It's the AM Stats toolbox[API_Manager_Analytics.tbox] deployment in BAM server.This toolbox can be found from {AM_Home}/Statistics folder.A toolbox can be defined as an installable archive in BAM[1].This AM Stats toolbox contains below artifacts. Stream Definitions -These are the  descriptions of streams of data to be sent to WSO2 BAM in order to perform analytics. Analytics- Analytics include the hive scripts to be deployed in WSO2 BAM. Below diagram shows the main flow of the integration between WSO2 API Manager and WSO2 BAM.I will go through each step by step. ...

As the starting blog-post for 2013,I thought of summarizing about the implementation of key features of WSO2 API Manager as security,throttling,monitoring aspects by explaining a bit of API template.In WSO2 API Manager,once a API creator create the API from publisher app UI and change its status as 'PUBLISHED' ,a template xml for that API will be generated with its input attributes of name,version,context,endpoint,etc. You can find that generated template from '{AM_Home}/repository/deployment/server/synapse-configs/default/api'.Below is such a generated sample API template. When you observe that API,you'll notice for each API resource there's a separate in sequence and an out sequence created.And additionally apart from the input data added by the creator,you'll notice for an API ,four handlers have been engaged to each published API. Each of the above handlers contain the implementation of key providing features of WSO2 API Manager.Y...