Introduction to IBM API Management
http://ibmapimanagementonlinetraining.blogspot.com/2015/05/introduction-to-ibm-api-management13.html
Introduction
to IBM API Management
IBM API Management is a complete on-premises
solution enabling companies to rapidly create, socialize, and manage APIs. It
covers the following key areas through a configuration, not through coding:
Security
– Managing access, both from the front end
with application developer security, to the back-end with integration security,
to data services.
– Quota usage, tracking and monitoring
Capability
– The design, creation,
versioning of APIs
– Proxy or assembly of existing services
Caching
– Dealing with increased load on back-end
services
– Flood control and denial-of-services (DoS)
prevention
Analytics
– Technical matrix
about calls made, devices used, workload per application developer
– Business level
queries defined as needed
Community
– Publicize and promote
adoption of your APIs
– Manage the signing up
of application developers
– Provide branding for
your enterprise, plus self-service documentation and samples for your users
IBM API Management
is designed to remove barriers to the installation and configuration of a
scalable, secure, enterprise API Management solution. Installation and
configuration details are not given in this book, but the components that form
the solution are outlined. API principles and how they can be implemented is
also described.
The easy-to-use developer interface and
tooling enables developers from a company to make internal applications and
services available to a community of application developers and partners
through these APIs.
An API typically consists of a request and
a response made over HTTP. The templates for different data sources supplied by
IBM Web API Services allows a Chapter 2. IBM API Management introduction 17
company’s developers to easily identify what parts of an application or service
can be accessible through the web API.
The API Management solution provides
a robust mechanism for exposing resources and synchronizing with the back-end
data needed in those resources. This can be done through a simple proxy
mechanism to an existing service, or through the assembly of existing
applications and data to create the appropriate actions and responses.