Kbase P120871: How to view SOAP messages between an OpenEdge Web Service client and a Web Service ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/16/2010 |
|
Status: Unverified
GOAL:
How to view SOAP messages between an OpenEdge Web Service client and a Web Service ?
GOAL:
How to trace SOAP messages between an OpenEdge Web Service client and a Web Service ?
GOAL:
How to troubleshoot issues with SOAP messages between an OpenEdge Web Service client and a Web Service ?
FACT(s) (Environment):
OpenEdge 10.x
Windows
FIX:
In order to troubleshoot a Web Service from the 4GL client side you will need to use, what is a called a SOAP message viewer. Progress provides two SOAP messages viewers: WSAViewer and ProSOAPView (also known as SOAP Spy). ProSOAPView provides more information and thus will be the only one discussed in this Solution. Refer to the "OpenEdge Development: Web Services" for further details on the WSAViewer. The general way to use ProSOAPView is as follows:
Open a Proenv window.
Start ProSOAPView from the command-line: start prosoapview
Go to the "Spy" menu and choose "Start Spying" (default listen port is 4444).
Now configure your OpenEdge 4GL client startup parameters to communicate through the ProSOAPView message viewer, e.g.: prowin32 ?proxyhost localhost ?proxyport 4444
There is no need to change the 4GL code. All Web Service communication will now go through the ProSOAPView. It will show you the SOAP Request and Response, as well as the HTTP Request and Response messages. This allows you to debug whether there is a problem with the SOAP messages between the 4GL client and the Web Service.