A colleague recently was trying to figure out a way to determine what was going on with one of his soap calls, he browsed the SCN network to see what others might be doing but most referenced using SOAPui to do testing of the web service. As much as I like SOAPui I tend to use it to test my own web services I develop and not necessarily for web services I am consuming
We will assume that the developer has created his proxy using a WSDL wether local or using the URL everything is ready to go but I want to run some tests and see an immediate response. Normally here I see direction to create a quickly several line program to make the call and honestly using the proxy this is fairly simple but I want it even easier then that and I want to mimic what I am seeing in SOAPui (ok as close as possible).
- From SE80 I access my proxy
- Select Test
- Select my options
- Execute
- Populate my sample data in the template SAP has provided me
- Execute
- Wala!
We can see the payload we sent to the web service and we can see the response.
When troubleshooting scenarios such as Proxy (I am referring to a firewall type) problems or even just errors I am seeing in my programs that I cant figure out without debug running a simple test in SAP that I might use SOAPui for will save me a lot of time.
Hope that helps at least one developer from pulling his hair out.
Later…..