Analyzing Web Services Running in the Embedded Server

The WS-I compliant analyzer correlates messages in the log file against a set of standard assertions, and in particular the <soap:address> sub element of the <service> element in the WSDL document must exactly match that specified in the wsi-log.xml messageEntry's <senderHostAndPort> or <receiverHostAndPort>, otherwise the messages won't be analyzed for WS-I compatibility.

When the web service is run in the embedded server (by choosing Run from the web service's context menu), and you create the log by running the TCP packet monitor while running a generated stub against the web service, you may need to change the web service endpoint in the WSDL or the _endPoint variable in the generated stub before creating the log file of the stub running.

To make sure the web service endpoint is the same as the _endPoint variable in the stub:

Edit the WSDL document of the web service. Either double-click the web service container in the navigator, go to the Endpoint page of the Edit Web Service dialog, and edit the Web S ervice Endpoint,
or
Select the web service container in the navigator, and double-click the WSDL document in the Structure window. Navigate to the <soap:address> sub element, and edit the endpoint.

Change the web service endpoint either to:
- <IP_address>:<embedded_port_no> (the default embedded port number is 8988)
  or
- <hostname> (in lower case)
Open the EmbeddedStub.java file by double-clicking on it and navigate to the _endpoint variable. Edit the value to exactly match the web service endpoint.

Now you can continue from step 2 of Creating and Analyzing Web Service Logs.