Dr. Debug's Advice
G'day my friends,
Today I'd like to share with you an excellent piece of work that will make your debugging life so much easier.
This IBM Support TV video hosted on our youtube channel will show you various ways to record HTTP traffic using your browser:
This becomes quite handy in cases where IBM Support asks your for HTTP traffic captures or Fiddler traces, but your company policy does not allow you to install fiddler.
I would suggest to bookmark this video. We will need this as a basis for future debugging.
And if neither this video, nor fiddler helps...
Take two of these and call me in the morning,
Dr.Debug 3100008NWU Tags:  ibm decrypt fiddler https youtube video tv trace tutorial dr.debug debug support traffic http ibmsupporttv recording 32,519 Views
Good morning my dearest debuggers,
Today, I would like to share a new IBMSupportTV video with you. It shows, how to capture HTTP traffic using Fiddler and can become quite handy if IBM Support asks you for a fiddler trace.
You will find it on the IBMSupportTV youtube channel.
And if this does not help you gathering the trace, take two of these and call me in the morning.
Dr.Debug 3100008NWU Tags:  bad pd http troubleshooting bpm 302 process_designer fiddler error 8.5.6 dr.debug redirect debug troubleshoot request managed_assets http_302 15,548 Views
Dear friends of the debugging fun,
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.
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!
What you may see is something like this:
Now this indicates that you may not have set the "useHTTPSURLPrefixes" parameter to 'true' in your cluster-bpm.xml file.
The entry would usually look like this:
Once you have set the useHTTPSURLPrefixes to true, try again.
What this will do is it will prevent the redirect to the SSL port as the HTTPS URL will be used from the beginning. This will avoid the 302 redirect and the error.
And if this does not help, take two of these and call me in the morning.
Your Dr. Debug