Process Commander does not work with WebSphere 220.127.116.11, due to a bug introduced into that WebSphere version by IBM.
As part of Process Commander processing, the browser sends encoded data from users’ machines (the client machine) to the Process Commander server, using industry-standard encoding. Due to the IBM bug, WebSphere 18.104.22.168 takes this data and parses it before passing it to the Process Commander system. The parsing process alters the data so that Process Commander can no longer read it.
There is no workaround that Pegasystems can apply for this issue. Instead, use either WebSphere 22.214.171.124 or 126.96.36.199, both of which do not have this problem.
IBM has identified this bug in their system as PK05760, and has released fixpacks and individual fixes to correct the problem. Excerpts from PK05760:
In 188.8.131.52, for a post request with "x-www-form-urlencoded" content-type, its post data can not be read from the InputStream, because it has been consumed by parsing parameters [within WebSphere].
The fix for this APAR is targeted for inclusion in cumulative fixes 5.02.12 and 184.108.40.206. Refer to the recommended updates page for delivery information:
IBM has a patch for this error that may be applied to WebSphere 220.127.116.11 (PK05760_fix_5114.jar). See:
NOTE: Pegasystems has not tested these fixes. As stated above, WebSphere version 18.104.22.168 or 22.214.171.124 are recommended alternatives.