Doorgaan naar hoofdcontent

Lets take you through some new features of WSO2 API Management 2.0.0

WSO2 has recently released a new version of the API Manager: version 2.0.0. So what are the new features of the product?
I will take you through some new features.

Packaging

The API Manager consists of three packages to be downloaded:
  • API Manager
  • Tooling (For Eclise)
  • Analytics (Full fledged Data Analytics Server, ready to be used)

Traffic Manager

The API Manager has a new component besides the Publisher, Store and Key Manager, and that is the traffic manager. This component handles the throttling policies.


Advanced throttling

With the previous product it was possible to set throttling limits, i.e. 20 calls per minute allowed. With the new possible some more advanced policies can be configured.
Filtering based on properties.


  • IP Address and range
  • http request headers
  • JWT claims
  • Query parameters

Custom Rules

Note that this dialog is shown when logging into the admin console: https://:9443/admin
Also custom throttling policies can be configured using the scripting language Siddhi. You can use the following keys to define the policy: resourceKey, userId, apiContext, apiVersion, appTenant, apiTenant, appId 




Subscription Tiers

It will also be easier to edit the subscription tiers and to add tiers.





This adds a lot of new possible use cases to the throttling possibilities of the api manager. The Message Broker and Complex Event Processor components are used to implement the traffic manager.
The Siddhi syntax is very technical of course but it is a good step.

Log Analyzer

The log analyzer is added and is especially usefull when you are not able to login to the server yourself. This can be the case in a multi-tenant cloud environment.
You are for example able to view the number of errors and warnings of the application.



I am wondering who usefull this feature is in standalone mode.

API Store look-and-feel

The API Store has a new theme and looks better. Some screen shots are shown below.

APIs




Applications




For the applications you are able to select the possible grant types fort he token generation of that application.




Analytics

Configuring analytics with API Manager is easy when you use the analytics server package of the download page of API Manager. Then you just have to set Enable to true within the api-manager.xml configuration file. I think it will be more complex when you want to use an existing DAS or BAM server.

Batch statistics

There has been added some more statistics on the usage of the APIs.



Geolocation based statistics is also possible to be configured.

Realtime analytics

It is also possible to configure realtime analytics and to receive mails when something extraordinary happens. Note that the admin and Publisher/Store possibilities differ. There are more possible settings as admin.


Notifications

A client recently asked if he could receive mails when new api versions are available. Well WSO2 has added this feature. For now you have to configure that within some configuration files and not through a nice UI, and only a notification is sent when a new api version is available. However the first step is taken to implement more notifications (for example when an api will become obsolete or deprecated).


So this were some of the most important features added to the product. Will keep you informed in case i tried some more!

Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h...
12 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept ...
5 reacties
Meer lezen