Sunday, 26 March 2017

IBM BPM Advanced 8.5.7 - "Unable to establish a connection to the server" seen when attempting to access Health Management

I saw this: -


within the BPM Advanced 8.5.7 Process Admin console.

What was interesting was that nothing obvious was popping up within the WAS logs ( for the Node Agent, SupCluster, AppCluster etc. ).

This was the URL that I was using to access Process Admin: -


I'm not sure what made me think this, but I then realised that the hostname - bpm857.uk.ibm.com - was actually an alias to the real hostname - bpm857.novalocal - as the server is running on an openStack PaaS platform.

When I switched the URL to: -


the Health Management console burst into life: -


which is nice.

at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...