You probably remember my posting from July this year on the HTTP 302 in Process Designer when creating a managed asset. If not, here is a reminder.
Now, last week one of my customers reported the same issue, but on the BPM Pattern on an IBM Pure Application System.
Of course the first thing we checked was the cluster-bpm.xml config. We found the useHTTPSURLPrefixes set to true already, but saw in a fiddler trace that the redirect from http to https was still done (for details please see the link above).
Today I thought I would share a fairly common issue that I have come across quite frequently in the past weeks.
When creating a new managed asset in the BPM Process Designer, you may receive an error like the following:
Now, what can we do to debug this? We'll use fiddler!
For those of you who do not yet know fiddler, below a short explanation.
Fiddler will act as an HTTP proxy and will need to be installed on the client.
If all goes well it should capture ALL HTTP traffic on the client, which should include the HTTP communication between ProcessDesigner and ProcessCenter.
I will try my best in ASCII-Art:
This is how the communication usually works
| Process Center Repository | <----------http(s)----------> | Process Designer |
When you run fiddler, it will looks like this:
| Process Center Repository | <----------http(s)----------> | Fiddler | <----------http(s)----------> | Process Designer |
This will allow us to look into all the details of the communication between ProcessCenter and Process Designer. Header Information, Cookies, response codes etc.
There are actually 2 versions of fiddler that you could use. A very light weight version named "fiddlercap" (www.fiddlercap.com), which basically only provides a small UI with a few buttons and options. This should be sufficient for just capturing data.
Please find below an IBM Support TV video with instructions on how to use fiddlercap (starting at 2:40):
However, instead of recreating the problem in your browser you would simply recreate it in PD. Please remember to select the option "decrypt HTTPs traffic".
The second version is the full version of fiddler, with which you can (http://www.telerik.com/download/fiddler). This provides a lot of more options, but for recording we would also just need the "Decrypt HTTPs traffic" option to be enabled. For fiddler, we have another IBM Support TV video with instructions on how to record traffic:
Once you recorded the error, open fiddler and review the frames. You may see an HTTP call to the /assetServlet URI. This is the one to look at!