In the first release of IBM Integration Bus V10, we introduced support for building REST APIs from a Swagger document. We have continued to build on this capability in V10 fix packs – fix pack 2 introduced toolkit support for pushing REST API definitions into IBM API Management, and fix pack 4 introduced toolkit support for developing REST APIs from scratch using graphical tooling in the toolkit.
We have been continuing to extend our REST API support, and in fix pack 5 we have introduced support for pushing REST API definitions into IBM API Connect from the web UI and the command line.
IBM API Connect 5.0 is the latest version of IBM’s API management solution (formally called IBM API Management), which provides a full set of features for managing the life cycle of your REST APIs. The most important features of this solution for IBM Integration Bus users are:
REST APIs pushed in IBM API Connect can be published to your wider organization via customizable portals that allows developers to quickly discover and consume those REST APIs. Those developers can register their applications using these portals, and sign up to plans that define which operations they are permitted to access and what usage/rate limits their applications are subject to.
Monitoring and analytics
REST APIs pushed into IBM API Connect can be monitored and their usage analyzed using graphical tooling built into the web console. The IBM API Connect tooling allows you to monitor a wide range of metrics, such as the most active APIs, the number of API calls, and response times/latency.
IBM API Connect offers fine grained control over security for REST APIs. You can secure a REST API using HTTP Basic Authentication, an API key (a secret key generated for an individual application), and OAuth 2.0. Security options can be specified for the whole REST API, or individual operations within that REST API. It also offers control over who is permitted to see and subscribe for REST APIs.
(see PDF attached below for full article)
You may also be interested in: