Book Image

Digital Transformation and Modernization with IBM API Connect

By : Bryon Kataoka, James Brennan, Ashish Aggarwal
Book Image

Digital Transformation and Modernization with IBM API Connect

By: Bryon Kataoka, James Brennan, Ashish Aggarwal

Overview of this book

IBM API Connect enables organizations to drive digital innovation using its scalable and robust API management capabilities across multi-cloud and hybrid environments. With API Connect's security, flexibility, and high performance, you'll be able to meet the needs of your enterprise and clients by extending your API footprint. This book provides a complete roadmap to create, manage, govern, and publish your APIs. You'll start by learning about API Connect components, such as API managers, developer portals, gateways, and analytics subsystems, as well as the management capabilities provided by CLI commands. You’ll then develop APIs using OpenAPI and discover how you can enhance them with logic policies. The book shows you how to modernize SOAP and FHIR REST services as secure APIs with authentication, OAuth2/OpenID, and JWT, and demonstrates how API Connect provides safeguards for GraphQL APIs as well as published APIs that are easy to discover and well documented. As you advance, the book guides you in generating unit tests that supplement DevOps pipelines using Git and Jenkins for improved agility, and concludes with best practices for implementing API governance and customizing API Connect components. By the end of this book, you'll have learned how to transform your business by speeding up the time-to-market of your products and increase the ROI for your enterprise.
Table of Contents (21 chapters)
1
Section 1: Digital Transformation and API Connect
5
Section 2: Agility in Development
15
Section 3: DevOps Pipelines and What's Next

Global scoped user-defined policy

As you should be aware by now, APIC uses a DataPower Gateway as its runtime for your APIs. Many API developers using APIC often have previous DataPower development experience and naturally ask the question "Why can't I use any of the robust features and functionality that the DataPower product offers?" This is a legitimate question, and many developers will take it upon themselves to create separate services on DataPower to implement this functionality, but this is not the way you should accomplish this. Much like you saw in the previous section of this chapter, APIC provides a way to package all of your DataPower-specific functionality into one shareable policy that can be shared and reused by all of your APIs by simply dragging it onto the assembly flow like any other policy. Unlike the Catalog UDP we discussed in the previous section, any global UDP created will be available to any API being developed in any Provider Organization...