IBM API Management Online Training

live IBM API Management class

noreply@blogger.com (Anonymous) — Sat, 16 May 2015 19:08:00 +0000

hello
our virtualnuggets institute glad to announce ibm api management online program starts on 20/05/2015......

Deployment topologies

noreply@blogger.com (Anonymous) — Fri, 15 May 2015 06:24:00 +0000

Deployment topologies

An API Management solution is deployed to facilitate the development of applications (apps). The apps may be created by one or more of the following developers:

Internal developers behind the firewall
Third-party trusted developers, for example business partners or mobile app agencies
Unknown public developers

If the apps are developed internally, then the APIs need not be exposed to external developers, such as the partners or public. An API Management layer is effective in providing a uniform integration layer for internal app developers who wants the straightforward REST/JSON based data access and it complements a SOA strategy.

Mobile enterprise application platforms

Where mobile apps are developed, a mobile enterprise application platform (MEAP) might be used. The MEAP, such as IBM Worklight, might contain mechanisms and adapters for integration to data services and include accessing HTTP resources such as APIs. The MEAP is typically placed inside the enterprise and protected by a secure gateway.

Using an externally exposed API through the MEAP integration, adapters add latency to the call and thus the mobile application calls the API directly. For internally exposed APIs using the MEAP integration, adapters are used.

Internal API exposure

In this topology, APIs are exposed only to internal app developers.

The topology of exposing the internal APIs is shown in below Figure . Here, the mobile application makes calls to a MEAP adapter (shown as IBM Mobile platform), which then makes the call to the API Management layer or other integration middleware such as an enterprise service bus(ESB).

Fig:Internal API exposure for mobile applications

External API exposure

Socializing and exposing the APIs is a common approach and requires that the API Management solution is fully secure. The gateway tier within IBM API Management is implemented with IBM DataPower and provides security functionality inherent within that solution

Control over app developer usage is still possible through approval processes, and only registered developers and their registered applications can gain entitlement to the API resources. The topology for exposing APIs externally for mobile applications is shown in below Figure. This differs from above Figure in that the mobile application makes a call directly to the API management layer which then provides the integration service to cloud or back-end data sources.

Fig: Exposing APIs externall

Overview of API

noreply@blogger.com (Anonymous) — Thu, 30 Apr 2015 07:05:00 +0000

What is API ?

The API means APPLICATION PROGRAMMING INTERFACE, provides a comparison of APIs with the traditional web sites, and describes the values and benefits of using APIs.

With an API, developers can exploit functions of existing computer programs in other applications. APIs have existed for a long time, since computer programming first started.

Over the years, APIs have evolved based on advances in technology (such as network speed, security, and dynamic integration), and also maturation in business that allows for thinking of business functions as discreet, consumable entities. Competition is now possible for business functions based on business value as opposed to technology foundations.

API architecture has also evolved over the years, most recently with the advent of service-oriented architecture (SOA). SOA provides for an architectural model to manage consumer and provider relationships in a dynamic environment. This paved the way for producing and exposing APIs with better business enablement capabilities including request access, entitlement, identification, authorization, management, monitoring, and analytics.

Today, progressive companies are exposing APIs to allow others to consume their business functions, for a profit. Where Windows and Linux have been traditional development platforms of the past, Google, Facebook, Twitter and other companies are becoming the development platforms of the future. All of these companies built a functional platform of business capabilities and extended their business models by exposing APIs so that developers can exploit their functionality. Google Maps is a great example. Many developers write mashups on top of Google Maps for various reasons, for example retail store locator, traffic reports, road conditions, and so forth.

The way we work and reach customers is evolving. Below fig. shows a fundamental shift from websites as being the information technology access mechanism for the majority of businesses, to the rapidly growing ecosystem of internconnected devices that require APIs to consume business function. Today, we have applications in cars, appliances, smartphones, game consoles, and other devices, that communicate with back-end business functions through APIs. APIs are enabling more and more devices to connect

This “interconnected revolution” is here today, as in the following examples:

Refrigerators can tell their manufacturer services systems when maintenance is required.
Cars can do the same with routine maintenance notification.
Smart electric meters can provide usage and consumption information to the utility company.

All of this is possible through APIs.

Introduction to IBM API Management

noreply@blogger.com (Anonymous) — Thu, 23 Apr 2015 12:36:00 +0000

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.