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

Chapter 8: Message Transformations

You have now learned how API Connect (APIC) can quickly and easily be configured to organize, socialize, analyze, and provide a secure gateway to your existing APIs. Hopefully, you have seen the tremendous value in using it to expose your existing APIs where the request and response messages are simply passed to/from the backend API that is being proxied. There may be times, however, that the request and/or response messages will not be what the consumer is passing and the backend API is expecting. Or perhaps you wish to modernize an existing backend service by exposing it as a RESTful API. Take, for example, an existing SOAP Web service that you wish to expose as a RESTful API to your consumers. Or maybe you will just need to enrich or redact certain data within the request/response messages. There are many reasons why you might to alter the request and response data as it passes through your API. This is where API Connect provides many options depending...