Chris Phillips’ Blog - API, Integration and Governance

DataPower provides the facility to proxy WebSocket connections. This article is part two 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

DataPower provides the facility to proxy WebSocket connections. This article is part one 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

I was wanting to hide sample code in my posts so the meat of the information could be more easily seen.

I went to W3Schools and they provided me with the sample I needed. However it does not work in Jekyll because of how it generates html from markdown.

Just a note to say that I have released the API Connect Profiler tool.

This tool was created to extract non runtime statistics from an API Connect 2018 system and as a sample for how to call API Connects provider APIs. It is a self contained Go Application so once the binary is downloaded no additional files are needed. This must be run from a windows/linux/macos system that has https connectivity to the API Manager node.

Nearly every organisation in the world has two data centres for a given solution or region. In order for Quorums to work they require one or three plus DataCenters. This article covers the complexities of quorums running over two sites.

As I spent about an hour this issue I imagine I will not be the only one.

When trying to go to the OpenShift console on a remote machine with http://<IP or hostname>:8443/console it redirects you to 127.0.0.1.

This article explains the basics for publishing a Node JS application to the IBM Cloud (Formally Bluemix). It assumes that you are already have an IBM ID that is used on IBM Cloud.

This post is just a rehash of https://jekyllrb.com/docs/pagination/, but as it took me a few attempts I thought I would try and post a consise list of instructions.