Architect Consultant blog

One of my hobbies is photography and when I bought my first camera it was a compact camera. I soon realized and experienced that I needed a reflex camera (SLR), because the resolution, speed and quality was far more better. I did not realize it until I really used the product. Again after a few years I noticed that I did not use my camera a lot. Why was that? Because the camera was pretty big and unpractical to take with me all the time. Then I read about a system camera, which has the advantage of being small, but you still have the possibility to switch lenses. I never regretted my choices, because at the time it seemed to be the best choice. Today there are a lot of camera’s with a lot of possibilities and specifications. Which one to pick? It depends on a lot of factors and what you want todo with the camera, like portret-, landscape-, sport- and street photography. The same holds when selecting a software application, in this case an API manager. In my opinion there ...

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...

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 ...

I currently work for a customer that wants to expose its "services" to partners and other external consumers. They do not want to build websites themselves anymore, but instead have the services published and used by partners. So how can this be done? Always curious and looking for good solutions i started to think about this. I saw one of the following options: Just expose the (web)services through a web gateway and use http basic authentication over SSL for security Make REST adapters and expose those  Requirements  However soon i also discovered: Consumers have to be managed. You have to manage the client credentials. For a few consumers this is doable, but for a couple of hundred or thousands this can be cumbersome Consumers have to find the services somewhere. What is the functionality of those services? Is it soap or REST based? Consumers want to test the services within a sandbox before actually using them As a service provider you have to manage the ...