Canvas® API Manager™
An API (Application Programming Interface) at its most basic level, allows your product or service to talk to other products or services. In this way, an API allows you to open up data and functionality to other developers and to other businesses. It is increasingly the way in which companies exchange data and services, both internally and externally.
Organizations have no choice but to adapt or risk getting left behind as markets enter the era of the Web application programming interface (API). By providing a framework that developers can use to quickly build http services or create an application from multiple services, a Web API provides a public persona for the enterprise. Web APIs may use traditional service-oriented architecture (SOA) services or may be created from various data sources, including databases and legacy systems, or just about anything in the enterprise, to extend key assets beyond traditional boundaries.
Web APIs rely on XML or JSON formats to provide internal and external developers with a foundation for easily creating Web 2.0 applications that are readily accessible through Web browsers, mobile devices and other mechanisms. API management is the process of publishing, promoting and overseeing application programming interfaces (APIs) in a secure, scalable environment. It also includes the creation of end user support resources that define and document the API. The goal of API management is to allow an organization that publishes an API to monitor the interface’s lifecycle and make sure the needs of developers and applications using the API are being met.
Publishing APIs to an external developer community, be it partner or public, introduces a number of challenges and risks for the enterprise. How do you protect the information assets you are exposing from abuse or attack? How do you deliver your APIs as reliable services with no downtime that can impact your API users? How do you govern access and usage of your APIs in a consistent, policy driven way? How do you make money from your APIs? How do you help developers discover your APIs and self-manage their access? While these questions are relevant to start-up and enterprise alike, they are more acute and urgent for enterprise IT organizations. Enterprises cannot afford the reputation damage that may result from a rushed API Management strategy. They have deliberate IT processes and safeguards that need to be upheld. But no matter what type of API an enterprise wants to expose, it will need an API Management solution.
Organizations have no choice but to adapt or risk getting left behind as markets enter the era of the Web application programming interface (API). By providing a framework that developers can use to quickly build http services or create an application from multiple services, a Web API provides a public persona for the enterprise. Web APIs may use traditional service-oriented architecture (SOA) services or may be created from various data sources, including databases and legacy systems, or just about anything in the enterprise, to extend key assets beyond traditional boundaries.
Publishing APIs to an external developer community, be it partner or public, introduces a number of challenges and risks for the enterprise. How do you protect the information assets you are exposing from abuse or attack? How do you deliver your APIs as reliable services with no downtime that can impact your API users? How do you govern access and usage of your APIs in a consistent, policy driven way? How do you make money from your APIs? How do you help developers discover your APIs and self-manage their access? While these questions are relevant to start-up and enterprise alike, they are more acute and urgent for enterprise IT organizations. Enterprises cannot afford the reputation damage that may result from a rushed API Management strategy. They have deliberate IT processes and safeguards that need to be upheld. But no matter what type of API an enterprise wants to expose, it will need an API Management solution.
Canvas® API Manager™ offers following features:
Access Control – Access control includes authorization, authentication, access approval, and audit.
Security – Like website development, API security revolves around three stages—planning the API, testing the API, and monitoring the API after it has launched.
Transformation – Format transformation
Routing and Orchestration – Routing, mashups, caching
Lifecycle – API Lifecycle Management and versioning
Charging and Billing – Prepaid and Postpaid management
Monitoring – Monitoring security, traffic, developers, applications, platform health, backends, revenue
Reporting – Detailed reporting capabilities
KEY FEATURES
Common Provisioning
Unified Operations and Administration
Simplified Integration
Flexible Licensing
NFV/SDN Ready Architecture
BENEFITS
Optimum Usage Of Resources
Decrease OPEX and CAPEX costs
Reduced Hardware Footprint
Optimize Daily Operations
Reduced Number Integration Points
Optimum Usage Of Resources
Decrease OPEX and CAPEX costs
Reduced Hardware Footprint
Optimize Daily Operations
Reduced Number Integration Points
REFERENCES
Airtel / India
Ooredoo / Qatar
0 Comments