Architect Consultant blog

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 conf

Introduction Testability is one of the underestimated qualities of software. This is also the case for WSO2 ESB projects. However it is important to design the integrations for testability and this starts with the way you setup the proxies. This blog gives some guidelines which you can use to design for testability. Sequences Sequences are a way in WSO2 to group Mediators. A proxy has by default an in-Sequence, out-sequence and optionally an error-sequence. These sequences can be split up in sub-sequences and this is a good way for reuse, but also a way to split up the design. A proxy usually contains the following functional parts: Validation Transformation Sending to an endpoint   These parts can be put in separate sequences. This has the advantage that the part scan be reused in other proxies. This is also the way to enable testing for these parts.  Design for testability The sequences are the basis for the testability of WSO2 ESB proxies. Th

One of the features i missed within the WSO2 Developer Studio was a data mapper. We had to write our own XSLT or PayloadFactory within the product. But everything is going to change with the release of ESB 5.0.0 ! Or is it ? .... There is a first blog item on the datamapper that i read and tried: https://nuwanpallewela.wordpress.com/2016/04/10/how-to-use-wso2-data-mapping-mediator-in-esb/ A very good blog indeed. However when i tried the new developer studio, i was somehow disappointed. I am positive about the fact that the Mapper is a real resource (even project) now. But i miss a lot of features (like for example XPath functions, if-then-else-construct, constraints) within the mapper. As you can see from the picture below, only the following operators are supported: Concat Split LowerCase UpperCase And when you investigate the generated project files, you will notice that JScript? is generated to do the actual mapping. So my first impression is disappoin

Using the WSO2 API Manager in a DTAP environment is slightly different than for example the ESB product. Nadeesha has written a good article about it:  http://wso2.com/library/articles/2016/03/article-architecting-a-multi-environment-api-manager-deployment-with-wso2-api-manager/ My conclusion of the article and some take aways: API Manager does not use Carbon Archive files because API Manager artifacts are both stored on file system and database Use import/export facility to migrate APIs There is also a bulk tool available to import/export a bulk of APIs Environment specific attributes must be given as parameters The downside of that last point is that each time new parameters are added, you must restart the API server. Each backend will have its own endpoints, so this will require new parameters. I would recommend a seperate file that must be imported within the  wso2server.bat file.

Introduction Unfortunately i did not went to the WSO2 Conference in Asia  but i went through the presentations and this blog item describes some interesting topics i came accross. There were a lot of different tracks: API Management  Cloud Strategy Integration' Security Governance Architecture Analytics DevOps Internet of Things (IoT) API API (Management) is a hot topic. Almost all reference architectures use APIs to expose functionality, either to mobile apps or other apps. It is used within Microservices as contracts, it is used in connected enterprises that want to expose their APIs into the API economy system and it is used internally to manage and govern services. IoT Internet of Things is a also a big thing, so also at the WSO2 conference. The WSO2 IoT Server was announced in 2016 Q2. Features of this product: Implementation of WSO2 IoT Reference Architecture Device Management Device Analytics Device adapters Suppo