Wednesday, 4 September 2013

From the coal face - IBM BPM - Tracing Process Center to Process Server communication

A friend of mine was having fun and games with the installation of a BPD snapshot from his Process Center to a connected Process Server, via HTTPS.

The solution to the problem was to ensure that he had: -

<deploy-snapshot-using-https merge="replace">true</deploy-snapshot-using-https>

in 99Local.xml ( or, better still, the overriding 100Custom.xml ) on BOTH the Process Center and Process Server cells.

However, on the voyage of discovery, he realised that he could learn a LOT about the way that the process works by enabling JVM-level tracing.

The particular trace strings that made a difference were: -

com.ibm.bpm.fds.*=all:ProcessApplicationLifecycle=all:com.ibm.bpm.fds.repo.util.ContributionHelper=off

and: -

WLE.*=all

Nice :-)


No comments:

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="{...