Skip to main content

Dig in to generated API Template from WSO2 API Manager

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.You can find each of the implementations of these handlers from  here.
An API Handler provides QoS features like security,throttling,monitoring for an API.
If I explained a bit of each of these;

  1. APIAuthenticationHandler -This provides the API Authentication support with OAuth2.0.All the API resource level authentication schemes handling through this handler.
  2. APIMgtUsageHandler- This provides API monitoring support with WSO2 BAM integration.
  3. APIMgtGoogleAnalyticsTrackingHandler-This provides API monitoring support with Google Analytics support.
  4. APIThrottleHandler-This provides API throttling handling support with pre-defined throttling policies.
  5. APIManagerExtentionHandler-This is a extention handler,looking for a in/out sequence with a pre-defined name pattern to be invoked if exits such named sequence.This handler first looks for a sequence named WSO2AM--Ext--[Dir], where [Dir] could be either In or Out, depending on the direction of the message. If such a sequence is found, it is invoked.Additionally below more API specific extension sequence is  also looked up by using the name pattern apiName--[Dir]. If such an API specific sequence is found, that is also invoked. The above searching sequences can be in global level or at the per API level.
Same-way,if you want to add a custom feature to support from API level,you can achieve it by writing a custom handler and engage it to the generated API template.To write such a custom handler ,you can find more information from here.
When an API invocation request comes to API Manager,first the request will process through the engaged handlers of the API element in sequential order.And if the request pass through each security,monitoring, throttling handling layers,it will direct to the relevant API resource.



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