Chris Phillips’ Blog - API, Integration and Governance

I am often asked if there is a way we can limit the range of IPs that we accept calling an API Gateway. This can be done with a GlobalPolicy and a little GatewayScript.

Amit Kumar Singh from my team built some GatewayScript that will do this check.

This article will explain how to enable Open Telemetry on API Connect 10.0.8.0 with DataPower 10.6.0.1. In order to apply these settings today, a GW extension must be used. This article will explain the steps to build the gateway extension.

Thanks to Zach Groseclose and Ben Stern for assisting with this.

For an introduction to OpenTelemetry please refer to our previous article on OpenTelemetry for AppConnect https://chrisphillips-cminion.github.io/ace/2024/04/22/ACE-Otel.html

For the last year a small team and I have been updating the API Connect WhitePaper to cover changes between 10.0.1 and 10.0.8.

The previous versions of this WhitePaper have assisted clients, IBMers and Business Partners from around the world deploying and understanding IBM API Connect.

For this release we have changed our approach to deployment patterns to ensure that we could accurately show the flexibility of the product while at the same time provide a clear cookbook of options.

Our intention is not to make our audience wait another 2.5 years for the next version, we are intending to update this every few months as new function is provided that makes sense for us to include.

To download a copy please head over to IBM Communities.

https://community.ibm.com/community/user/integration/viewdocument/ibm-api-connect-v1008x-deploymen?CommunityKey=2106cca0-a9f9-45c6-9b28-01a28f4ce947

A client asked how they can make two invokes in API Connect asynchronous. This is not possible with the invoke policies as they must always be synchronous. However it can be done with JavaScript/GatewayScript.

When using the rate limit policy on the Assembly you need to first create a rate limit in datpower in the API Gateway object. This must be done via a GatewayExtension to stop the policy being removed when a publish request is done from API Connect.

This article will show you to create the rate limit objects in DataPower using a gateway extension.

We will create a rate limit called chrisblog-ratelimit that can be referenced from a rate limit policy.

While testing disaster recovery it is advisable to take offline the primary API Manager. This instructions will cover OpenShift and Kubernetes.

Setting a downstream proxy is often a requirement when API Connect needs to make calls to the invoke downstream services on the internet.

In part 1 we discussed what a multipart API was and how it can be parsed in API Connect. In this part we will take that knowledge and apply it to a real situation.

Scenario: Upload two images, validate that the images are png and that the size is less then 1MB.

MultiPart API calls allow multiple sets of data to be sent to an API as individual items. If you have a series of images and text you need to upload you could write a curl command similar to

curl -vk -F 'name=fred' -F "name2=@image.png" https://APIURL/ -H "content-type: multipart/related"

This articles covers the key pieces of information that needs to be passed on to the load balancer team to configure the load balancer of choice.

Please Note: DataPower Self Load balancing with the AIO module is not supported with API Connect v10.