Chris Phillips’ Blog - API, Integration and Governance

This article builds on top of the API Connect WhitePaper, this may be included in the WhitePaper in a future revision

API Connect supports that each component running in its own cloud. The most common use of this is the Gateway Service (DataPower) running in AWS, IBM Cloud, Azure, GCP or any cloud that provides a Kubernetes Runtime.

Your company has just bought DataPower X2 appliances. The datacenter that they will be installed in is remote and you have been asked to put together a plan to remotely do their setup. This article will provide instructions and guidance on what is needed for a minimal setup to get the appliance on your network and accessible via the DataPower WebGUI.

Image taken from ibm.com

Your company has just bought DataPower X2 appliances and you have been assigned to lead the effort to migrate from the current appliances to the new X2s and you are looking for some direction on how to put together a high-level plan. This article will give you an overview on how to plan and execute the migration with some key pointers on what to look for and possible gotchas. It will not be a detailed step by step on how to do the migration.

On the 15th of July, I updated the API Connect WhitePaper to 1.0.8. This can be downloaded from the same location as before, https://www.ibm.com/downloads/cas/30YERA2R

Frequently I get asked “What is the best strategy to enable access to the logs of container pods without giving access to Kubernetes?”. The obvious answer is log forwarding to a central location e.g. Splunk. However because of the cost of platforms like Splunk many organisations choose not to use it in Dev, or at least not straight away.

Kubernetes is a container orchestration system that provides many advantages. In this article I am going to describe how DataPower or any pod can be scaled out with a simple request. There are ways to solve this.

DataPower provides the facility to proxy WebSocket connections. This article is part three of a three part guide consisting of

• Part 1 - How to create a WebSocket Proxy in DataPower
• Part 2 - How you can use API Connect to secure your implementation
• Part 3 - How to socialise it via the Developer Portal
• Part 3.1 - How to socialise it via the Developer Portal giving your consumers the easiest way to use your websocket

#This article has been replaced with

DataPower provides the facility to proxy WebSocket connections. This article is part three of a three part guide consisting of

• Part 1 - How to create a WebSocket Proxy in DataPower
• Part 2 - How you can use API Connect to secure your implementation
• Part 3 - How to socialise it via the Developer Portal giving your consumers the easiest
• Part 3.1 - How to socialise it via the Developer Portal giving your consumers the easiest way to use your websocket