Chris Phillips’ Blog - API, Integration and Governance

API Connect v2018 has the ability to configure vanity Urls for the API Endpoints . Vanity URLs allow the api developer/administrator to change how the endpoint is rendered in the API Connect Developer portal. This is useful if you wish to go via a CDN or there is a requirement for each catalog having a different URL subdomain.

When making calls from ACE to https endpoints the trust store must contain the certificate for the target endpoint. In ACE this is done by creating a secret and reference it in the help chart. This article provides instructions on how to do this.

User Defined Policies (aka Custom Policies) allow a customer to provide a bespoke piece of function as a policy in the API Designer Pallet. In this example I will explain the different pieces that need to be constructed to build an MQ Invoke Policy.

Ways to handle the DataPower quorum when there is only enough Licenses for two DataPowers.

THIS HAS BEEN UPDATED - https://chrisphillips-cminion.github.io/apiconnect/2022/10/19/APIC-DataPowerQuorum2Node0.html

Chatbots have been a current fashionable project to work on right now. An API Gateway is critical to help take the load off the main business application as well as providing a way to implement multiple Chatbot intermediaries without rewriting the business logic.

In the event that a DataPower quorum is lost the remaining DataPowers can be forced into a working quorum.

API Connect has four components, there is a requirement to deploy the DataPower Gateway to their own worker nodes in Kubernetes.

I’m often asked whether IBM API Connect supports GraphQL APIs. The short answer is “yes” but let’s have a deeper look at the topic.

This article explains how in API Connect 2018.4.1.8 you can persist additional configuration to DataPower.

This article explains the basics of error handling in APIs in API Connect 2018.