Chris Phillips’ Blog - API, Integration and Governance

API Connect has four core components.

• API Manager
• API Gateway (DataPower)
• Developer Portal
• Analytics

Notes shamelessly stolen from Mark Tayler for installing Mini Shift

Avoiding losing Plans and Subscriptions of Published APIs when Updating an API: Staging a Product

Part of Four of the API Development Series. In this part we will show how to create simple definitions in API Connect and use the Mapping Policy to map between them.

Part of Three of the API Development Series. In this part we will show how to add debug messages and how to retrieve them in the DataPower Logs.

Part of Two of the API Development on API Connect Series. In this part we will show how to specify parameters for an API call. This builds on from the artefact and knowledge created in part 1.

Part of One of the API Development Series. In this part we will show screenshot by screenshot how to create a very basic API.

When using the API Connect REST interface you need to identify yourself with a bearer token. See this earlier post for steps to get a bearer token.

A common problem area is the SSL communication between the API Connect components. Often, this is due to SSL Passthrough not being correctly configured on the F5s or the ingress. In API Connect, the SSL communication between the API Manager and the other components must be terminated before the pods.

API Connect Local Test Environment was releaed in beta in August 2019.

The purpose of the Local Test Environment is to allow developers to build and test APIs on their laptops without depending on a server instance.