Getting Started With IBM API Connect

2y ago
113 Views
4 Downloads
3.36 MB
72 Pages
Last View : 8d ago
Last Download : 2m ago
Upload by : Aarya Seiber
Transcription

Front coverGetting Started with IBM API ConnectConcepts and Architecture GuideBenjamin WisnewskiBhargav PerepaIlene SeelemannKurtulus YildirimRahul GuptaSoad HamdyVasfi GucerRedpaper

International Technical Support OrganizationGetting Started with IBM API Connect: Concepts andArchitecture GuideSeptember 2016REDP-5349-00

Note: Before using this information and the product it supports, read the information in “Notices” on page v.First Edition (September 2016)This edition applies to IBM API Connect Version 5.0.This document was created or updated on September 8, 2016. Copyright International Business Machines Corporation 2016. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

ContentsNotices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viIBM Redbooks promotions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixAuthors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixNow you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiStay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiChapter 1. Introduction to APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Overview of APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.1 Business drivers of APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2 Innovation with APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.3 Generic API use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Classification of APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.1 External APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.2 Partner APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.3 Internal APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Considerations before launching APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 API business monetization models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4.1 API monetization model: For free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4.2 API monetization model: Developer pays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4.3 API monetization model: Developer gets paid . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4.4 API monetization model: Indirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5 API lifecyle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.1 Creating APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.2 Running APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.3 Managing APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.4 Securing APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.6 API strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7 API economy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7.1 Key roles in the API economy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7.2 API economy supply chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.8 What makes an effective API design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.8.1 Ease of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.8.2 Version support and documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.8.3 Aligned with the audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.9 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Chapter 2. API, microservices, and API management . . . . . . . . . . . . . . . . . . . . . . . . . .2.1 API concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.1 REST API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2 Microservices concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.1 Benefits of microservices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3 API management platform concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3.1 API management components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3.2 API management platform component description . . . . . . . . . . . . . . . . . . . . . . . . Copyright IBM Corp. 2016. All rights reserved.1516171820212224iii

2.3.3 API management architectural components interaction . . . . . . . . . . . . . . . . . . . . 262.3.4 API management and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ivChapter 3. IBM API Connect overview and offerings. . . . . . . . . . . . . . . . . . . . . . . . . . .3.1 IBM API Connect overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.1 API management with API Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.2 Capabilities of API Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.3 API Connect personas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.4 Features of API Connect to enable various personas. . . . . . . . . . . . . . . . . . . . . .3.1.5 API Connect key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.6 API Connect unique differentiatiors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2 IBM API Connect architecture and strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3 API Connect offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3.1 API Connect Essentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3.2 API Connect Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3.3 API Connect Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4 API Connect deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4.1 API Connect for IBM Bluemix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4.2 API Connect for on-premises solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.5 API reference use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.5.1 Reference use case 1: European auto manufacturer . . . . . . . . . . . . . . . . . . . . . .3.5.2 Reference use case 2: Global commercial bank. . . . . . . . . . . . . . . . . . . . . . . . . .3.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2930303133343535363738394041414243434445Chapter 4. Principals of good API design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1 Introduction to designing REST APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.1 URI naming considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.2 Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.3 Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.4 Other base URI segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1.6 Case conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2 Common query parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.1 Sorting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.2 Partial responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.3 Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.4 Pagination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.5 Expanding inline resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2.6 Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47484848484949495050515152525253Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55555555Getting Started with IBM API Connect: Concepts and Architecture Guide

NoticesThis information was developed for products and services offered in the US. This material might be availablefrom IBM in other languages. However, you may be required to own a copy of the product or product version inthat language in order to access it.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility toevaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not grant you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, USINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS”WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM websites are provided for convenience only and do not in anymanner serve as an endorsement of those websites. The materials at those websites are not part of thematerials for this IBM product and use of those websites is at your own risk.IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.The performance data and client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operating conditions.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, andrepresent goals and objectives only.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to actual people or business enterprises is entirelycoincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs areprovided “AS IS”, without warranty of any kind. IBM shall not be liable for any damages arising out of your useof the sample programs. Copyright IBM Corp. 2016. All rights reserved.v

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business MachinesCorporation, registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at “Copyrightand trademark information” at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks or registered trademarks of International Business Machines Corporation,and might also be trademarks or registered trademarks in other countries.Bluemix Cloudant DataPower DB2 IBM IBM API Connect IBM Watson Rational Redbooks Redpaper Redbooks (logo)WebSphere z/OS The following terms are trademarks of other companies:LoopBack, StrongLoop, and the StrongLoop logo are trademarks of StrongLoop, Inc., an IBM Company.ITIL is a Registered Trade Mark of AXELOS Limited.Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or itsaffiliates.Other company, product, or service names may be trademarks or service marks of others.viGetting Started with IBM API Connect: Concepts and Architecture Guide

IBM REDBOOKS PROMOTIONSIBM Redbooks promotionsFind and read thousands ofIBM Redbooks publicationsSearch, bookmark, save and organize favoritesGet personalized notifications of new contentLink to the latest Redbooks blogs and videosDownloadNowAndroidiOSGet the latest version of the Redbooks Mobile AppPromote your businessin an IBM Redbookspublication Place a Sponsorship Promotion in an IBMRedbooks publication, featuring your businessor solution with a link to your web site. Qualified IBM Business Partners may place a full pagepromotion in the most popular Redbooks publications.Imagine the power of being seen by users who downloadmillions of Redbooks publications each year!ibm.com/RedbooksAbout RedbooksBusiness Partner Programs

THIS PAGE INTENTIONALLY LEFT BLANK

PrefaceApplication programming interfaces (API) act as the digital glue that links services,applications, and systems together to create compelling customer experiences. Using APIsyou can create interfaces between back-end systems and applications that can help you bringnew digital services to market, open revenue channels, and exceed customer expectations.IBM API Connect is an API management solution from IBM that offers capabilities to create,run, manage, and secure APIs and microservices, thus managing the full lifecycle of APIs forboth on-premises and cloud environments.This IBM Redpaper publication gives a broad overview of APIs and API Connect andcovers key considerations for managing the lifecycle of APIs. This paper is targeted forowners of an API Connect based API, such as, C-level executives, members of the businessdevelopment teams, product managers, and technical evangelists.For practical scenarios using API Connect, refer to the companion IBM Redbooks publication, Getting Started with IBM API Connect: Scenarios Guide, REDP-5350.AuthorsThis paper was produced by a team of specialists from around the world working at theInternational Technical Support Organization, Austin Center.Benjamin Wisnewski is a member of the IBM Watson Health Cloud Development Team. He has 5 years ofinformation technology and business experience at IBM inareas including client data analysis, project management,continual improvement, defect prevention, and quality deliverysystems integration. His areas of focus at IBM are centered insocial business, cloud product development, data analysis, andhealthcare regulation compliance. Most recently Benjamin hasbeen engaged in working with IBM Watson Health teams todevelop innovative and cognitive solutions for IBM businesspartners and clients.Bhargav Perepa has been with IBM for 22 years. He is an IBMIT Specialist/Architect, working with various US Federal Civilianand Department of Defense government agencies in the IBMFederal Software Group in the Washington, DC, area. Hereceived his M.S. in Computer Science from Illinois Institute ofTechnology, Chicago IL, and an MBA from University of Texasat Austin, TX. His current interests are in cloud, analytics,mobile, social, security, and Watson technologies. Copyright IBM Corp. 2016. All rights reserved.ix

Ilene Seelemann is a senior consultant for the IBM Bluemix Garage in Toronto, Canada, where she works with clients todevelop cloud solutions on the Bluemix platform. Shespecializes in API strategy and application security. Prior to thisrole, Ilene worked for over 20 years in software development atIBM, most recently on the API Management product. She holdsa Masters degree in Mathematics from the University ofWaterloo.Kurtulus Yildirim is a Certified and Senior IT Specialist in IBMCloud Unit, Turkey. He has 12 years of experience inapplication design, development, and consulting. He holds amaster degree in Software Management from the Middle EastTechnical University. His areas of expertise include change andconfiguration, requirement, quality, and API management. Athis current assignment, he works as an IBM Rational consultant for various clients in Middle East and Africa Region.Rahul Gupta is a Senior Software Architect in the Internet ofThings group in Austin, TX. He is a Certified SOA Architect with10 years of professional experience in IBM messagingtechnologies. Rahul has been a technical speaker formessaging-related topics at various IBM WebSphere conferences. He is a recognized inventor by the IBM innovationcommunity. He is a co-author of several IBM Redbookspublications on messaging, mobile, and cloud computing.Soad Hamdy is a Software Engineer in Cairo TechnologyDevelopment Center, IBM Egypt. She has more than 6 years ofexperience in developing web and mobile applications. Sheobtained 12 product certificates, including IBM Worklight,Oracle Java Business Component, IBM SOA Associate, andOracle Java Programmer. She also received many awards forher achievements, such as the Duke Choice Award and theManager Choice Award. She has spoken at many events indifferent countries, including the Africa Technical Academy inMorocco, Cairo, as well as South Africa and Kenya. Shepublished many technical articles, including Getting startedwith MongoDB in Node.js, MongoDB for Beginners, Overviewof IBM StrongLoop, Worklight Common errors, RPT in a nutshell, Getting started with android development, and AndroidGoogle Maps. She has BSc. degree in Computer Science.xGetting Started with IBM API Connect: Concepts and Architecture Guide

Vasfi Gucer is an IBM Redbooks Project Leader with the IBMInternational Technical Support Organization. He has morethan 18 years of experience in the areas of systemsmanagement, networking hardware, and software. He writesextensively and teaches IBM classes worldwide about IBMproducts. His focus has been on cloud computing for the last 3years. Vasfi is also an IBM Certified Senior IT Specialist,Project Management Professional (PMP), IT InfrastructureLibrary (ITIL) V2 Manager, and ITIL V3 Expert.A complete and detailed IBM Redpaper publication on a topic such as this would not bepossible without generous support and guidance from key members in the IBM APIConnect product and development organizations, as well as many other IBMers.The authors team would like to acknowledge the following people for their contributions to thisproject:Mohammed Abdula, Dennis Ashby, Roland Barcia, Vince Brunssen, Shane Clausen, GangChen, Jason Gartner, Marc E Haberkorn, Laura (Olson) Heritage, David K Hodges, PrasadImandi, David Kerr, Chris Markes, Alan Moore, Tien Nguyen, Shiu-Fun Poon, Rachel ReinitzIBM USAJohan H TholeIBM NetherlandsClaus T JensenIBM DenmarkKim ClarkIBM UKSpecial thanks to Gang Chen (Executive IT Specialist, Cloud Architecture and SolutionEngineering, IBM USA) for providing technical support and guidance throughout this project.Now you can become a published author, too!Here’s an opportunity to spotlight your skills, grow your career, and become a publishedauthor—all at the same time! Join an ITSO residency project and help write a book in yourarea of expertise, while honing your experience using leading-edge technologies. Your effortswill help to increase product acceptance and customer satisfaction, as you expand yournetwork of technical contacts and relationships. Residencies run from two to six weeks inlength, and you can participate either in person or as a remote resident working from yourhome base.Find out more about the residency program, browse the residency index, and apply online at:ibm.com/redbooks/residencies.htmlPrefacexi

Comments welcomeYour comments are important to us!We want our papers to be as helpful as possible. Send us your comments about this paper orother IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at:ibm.com/redbooks Send your comments in an email to:redbooks@us.ibm.com Mail your comments to:IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400Stay connected to IBM Redbooks Find us on Facebook:http://www.facebook.com/IBMRedbooks Follow us on Twitter:http://twitter.com/ibmredbooks Look for us on LinkedIn:http://www.linkedin.com/groups?home &gid 2130806 Explore new Redbooks publications, residencies, and workshops with the IBM Redbooksweekly sf/subscribe?OpenForm Stay current on recent Redbooks publications with RSS ng Started with IBM API Connect: Concepts and Architecture Guide

1Chapter 1.Introduction to APIsThis chapter provides an overview of application programming interfaces (APIs). It describeswhat APIs are and the business drivers and value of APIs. It also includes an in-depthdiscussion of the API value chain, API pricing models, and API lifecycle. This broad viewhelps in building the foundation and understanding the role and value APIs bring to thedynamic digital services.This chapter includes the following sections: 1.1, “Overview of APIs” on page 21.2, “Classification of APIs” on page 61.3, “Considerations before launching APIs” on page 71.4, “API business monetization models” on page 71.5, “API lifecyle” on page 91.6, “API strategy” on page 101.7, “API economy” on page 111.9, “Summary” on page 14 Copyright IBM Corp. 2016. All rights reserved.1

1.1 Overview of APIsAn API is a public persona for a company or a product, where the API exposes businesscapabilities and services. APIs form a bridge for interactions between services, such asmainframe and databases and customer-facing services. APIs enable organizations to shareinformation with external developers, business associates, and other teams within the sameorganization.APIs allow you to expose some functions of a program or service in a managed and secureenvironment. API providers can share portions of their code with developers but do not haveto release everything for new applications and services to be developed. APIs from differentproviders can be combined by developers to create new applications as well.A high-quality API facilitates the development of applications by allowing differentfunctionalities to be created independently while offering a complete set of capabilities fordevelopment.1.1.1 Business drivers of APIsThe development of the cloud, cognitive computing, mobile devices, and mobile apps alongwith the creation of the Internet of Things (IoT) is changing the way organizations plan andoperate, both internally and externally.Figure 1-1 shows how in today’s world there is a rapidly growing ecosystem of interconnecteddevices that require APIs to consume business functions. Applications in cars, appliances,smartphones, gaming consoles, and other devices all communicate with back-end businessfunctions through dAppliancesAPIsGameConsolesTrillions2016 Millions1993 - 2000I tInternett TVsTVSSmartphonest hTabletsFigure 1-1 APIs are enabling digital integration2Getting Started with IBM API Connect: Concepts and Architecture Guide 2011 IBM Corporatio

The interconnected revolution is here today. The following examples are already using API toenable this digital integration: Refrigerators can tell 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 utilitycompany.Mobile devices, sensors, and data sources are forcing organizations to continually evaluatehow and on what platforms they need to conduct business. The interconnected globaleconomy ensures a continual pressure on businesses to develop new innovations to increasethe productivity of existing assets and to differentiate themselves from their competitors in themarket. Collaborating with partner organizations and other businesses requires a quick andefficient means to collaborate. Businesses are also under pressure to expand their presenceon a range of platforms, such as websites, mobile apps, social media, connected devices,and other areas.All these developments are driving businesses to embrace APIs, which can help transformthe way digital services are created, developed, managed, and secured. APIs providebusinesses the flexibility in filtering the data and services to share and the ones to keepprivate. APIs allow sharing of business capabilities with external partners and driveinnovation. Standardized interfaces of APIs provide for access to a multitude of devices andservices and a host of different audiences. The desire of businesses for increased integrationof various business data and record systems is in part satisfied through APIs. The IoTrevolution, the explosion of mobile and social, along with the growth of the cloud have alldriven APIs to the forefront of business strategy.API-enabled mobile payments account for 21% of transactions at Starbucks1 and contributedt

run, manage, and secure APIs and microservices, thus managing the full lifecycle of APIs for both on-premises and cloud environments. This IBM Redpaper publication gives a broad overview of APIs and API Connect and covers key considerations for managing

Related Documents:

Modi ed IBM IBM Informix Client SDK 4.10 03/2019 Modi ed IBM KVM for IBM z Systems 1.1 03/2019 Modi ed IBM IBM Tivoli Application Dependency Discovery Manager 7.3 03/2019 New added IBM IBM Workspace Analyzer for Banking 6.0 03/2019 New added IBM IBM StoredIQ Suite 7.6 03/2019 New added IBM IBM Rational Performance Test Server 9.5 03/2019 New .

api 20 e rapid 20e api 20 ne api campy api nh api staph api 20 strep api coryne api listeriaapi 20 c aux api 20 a rapid id 32 a api 50 ch api 50 chb/e 50 chl reagents to be ordered. strips ref microorganisms suspension inoculum transfer medium i

Latest API exams,latest API-571 dumps,API-571 pdf,API-571 vce,API-571 dumps,API-571 exam questions,API-571 new questions,API-571 actual tests,API-571 practice tests,API-571 real exam questions Created Date

3 API Industry Guide on API Design Apiary - Apiary jump-started the modern API design movement by making API definitions more than just about API documentation, allowing API designers to define APIs in the machine-readable API definition format API blueprint, then mock, share, and publish

IBM 360 IBM 370IBM 3033 IBM ES9000 Fujitsu VP2000 IBM 3090S NTT Fujitsu M-780 IBM 3090 CDC Cyber 205 IBM 4381 IBM 3081 Fujitsu M380 IBM RY5 IBM GP IBM RY6 Apache Pulsar Merced IBM RY7

FireEye's Endpoint Security Policy API provides a rich API to allow users to explore functions within the API. The Policy API Tool allows users to add remove and list policy exceptions quickly as well as list create policies for the tool. Overview To get started with the API you will need to create an API user or API Admin to access the API.

Product Analysis for IBM Lotus Domino, IBM Lotus Notes, IBM Lotus iNotes, IBM Lotus Foundations, IBM Lotus Quickr, IBM Lotus Sametime, IBM Lotus Connections, and IBM LotusLive. This report is intended for Organizations, Vendors, and Investors who need to make informed decisions about the Email and Collaboration market. Figure 1: Worldwide IBM .

May 01, 2014 · API RP 580 API RP 580—Risk-Based Inspection API RP 581 API RP 581—Risk-Based Inspection Technology API RP 941 API RP 941—Steels for Hydrogen Service at Elevated Temperatures and Pressures in Petroleum Refineries and Petrochemical Plants API RP1 API Recommended Practices. API