Skip to main content

WSO2 APIManager integration with WSO2 BAM


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.


[1] Once a user trying to invoke a published API,the request will go through the engaged API handlers for that specific API as explained in here.

[2] The request will hit APIUsageHandler implementation class and once you configured AM server with enabling BAM monitoring support.

[3] From this handler implementation,it'll direct to Usage Publisher implementation in order to create an event from the request and  push that event to BAM side.Note that from AM side,three types of events will be  push in to BAM server as listed below.
  • An event with successful API invocation request
  • An event with fault API invocation request
  • An event with API response
[4] Once such event received from BAM side,first it check the sent event matched with defined stream definition in AM stats toolbox deployed in BAM server.There are three pre-defined stream definitions can be found from AM Stats toolbox as mentioned below.
  • requestStreamDefn
  • faultStreamDefn
  • responseStreamDefn
If the event matches,that event will stored in local Cassandra data store and else an error will thrown.

[5] Then with BAM inbuilt analyzer engine support,by using the relevant analyzer script [hive script],which can be found from AM Stats toolbox,the data in local Cassandra space will be analyzed and populate to relational database tables.

[6] Next with Usage Client implementation of WSO2 APIManager,that created BAM side relational database will be directly accessed and retrieve data from the db tables,by querying them.

[7] Then from API Publisher UI,those queried data will be pulled out and shown them in pre-defined graphs.

[8] Once an API Creator logged into publisher UI,he can view the statitics related to his created API.

[9] Additionally since the graphs defined in publisher UI is limited,a user can directly use the BAM node to show stats from gadgets in BAM dashboard as explained in here or either generate pre-defined/custom reports from the stored data as explained here.

 References

 [1] http://docs.wso2.org/wiki/display/BAM200/Introduction+to+BAM+Toolbox

Comments

Post a Comment

Popular posts from this blog

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html
2 comments
Read more

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources  on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src >  request for a different domain as 'domain-b.com' to get an image via an API request.  For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as  XMLHttpRequest  or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to  note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers from which these resources getting need to handl
Post a Comment
Read more

[WSO2 AM] APIStore User Signup as an approval process

In previous versions of WSO2 APIManager before 1.6.0, it was allowed any user who's accessible the running APIStore come and register to the app.But there will be requirement like,without allowing any user to signup by him/her self alone,first get an approve by a privileged user and then allow to complete app registration.Same requirement can be apply to application creation and subscription creation as well.To fulfill that,we have introduced workflow extension support for  WSO2 APIManager  and you can find the introductory post on this feature from my previous blog post on " workflow-extentions-with-wso2-am-160 " . From this blog-post,I'll explain how to achieve simple workflow integration with default shipped resources with  WSO2 APIManager 1.6.0 and WSO2 Business Process Server 3.1.0 with targeting "user-signup" process. Steps First download the WSO2 APIManager 1.6.0[AM] binary pack from product download page . Extract it and navigate to
Post a Comment
Read more