Try OpenEdge Now
skip to main content
Web Services
Creating ABL Clients to Consume OpenEdge SOAP Web Services : Handling Errors in ABL Requests to OpenEdge SOAP Web Services : Debugging ABL applications that call Web services : Using ProSOAPView : Running ProSOAPView (SOAPSpy)
 
Running ProSOAPView (SOAPSpy)
You run ProSOAPView by setting it up as a proxy server for the ABL client.
To configure the ABL client and run ProSOAPView:
1. Start ProSOAPView by executing the prosoapview command in the OpenEdge environment using the following syntax:
Syntax
prosoapview [port-number]
By default the SOAPSpy executable listens on TCP/IP port 4444. You can specify the port-number value to change this port assignment.
2. To begin tracking HTTP and SOAP messages, be sure that the client application has not yet executed the Web service CONNECT( ) method, then choose Start Spying > Spy from the menu bar, as shown here, or click the spy icon in the SOAPSpy window.
3. Start up the ABL client adding the following startup parameters to the command line:
-proxyhost localhost -proxyport port-number
Set port-number to the TCP/IP listening port used by SOAPSpy (4444 by default). For more information on these startup parameters and starting up an ABL client, see OpenEdge Deployment: Startup Command and Parameter Reference.
Note: You do not have to change any connection parameters coded for the Web service CONNECT( ) method in the ABL client application to use ProSOAPView. Proxy settings handle all redirection of message traffic that is required to inspect messages sent between the ABL client and the Web service.
After the SOAPSpy window is opened and tracking messages has begun, the status bar indicates the proxy host and port as shown here, where the proxy host is name beata.