Chris Phillips’ Blog - API, Integration and Governance

When installing gateway sub component this can fail if stale webhooks are not cleaned up first.

Deleting an entire namespace to clean up a failed installed is not an uncommon action.

When deploying API Connect it is possible that the postgres does not start due to user error. (Most commonly due to invalid image registry url).

When using the image-tool to load images into your docker registry with a self signed certificate you will see the following error.

When installing OpenShift 4.3+ there is no default route created for the image registry. Therefore we are unable to load in images from outside of the cluster.

Lars Fanebost put together this awesome guide on calling DB2 from inside of API connect. This is taken from https://github.com/lfanebost/api-connect-exposing-db-data-pub/

From API Connect V5 and onwards users have been able to customise the Client ID and Client Secret values on applications. But this is a rarely known gem. This article will explains the API calls required to do this.

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.