To check the operation of the Web service, the Web service application must be deployed to the execution environment, then executed. Perform these operations in the Servers view.
For details on operations, refer to "6.2.6 Checking Application Behavior".
In addition, the following support functions are available for checking operation:
Web Service Explorer
If the arguments of the method published as a Web server and the return values are the primitive type or other simple type, rather than creating a client for invoking the Web service, the Web service can be invoked from the Web service explorer and the results can be checked.
For details, refer to "5.3.7.1 Using the Web Service Explorer as a Web Service Client".
TCP/IP Monitor
A TCP/IP Monitor can be used to monitor the exchange of SOAP data between the Web service client and the Web service.
For details, refer to "5.3.7.2 Using the TCP/IP Monitor to check Web Service Messages".
If the arguments of the method published as a Web server and the return values are the primitive type or other simple type, the Web service can be invoked from the Web service explorer and the results can be checked.
Launching the Web Service Explorer
To launch the Web service explorer, select [Run] > [Launch the Web Services Explorer] from the menu.
Displaying the WSDL Page
The Web service explorer has UDDI, WSIL, and WSDL pages, and users can switch between these pages using the right icon button. Click the [WSDL Page] button to display the WSDL page.
Invoking the Web Service
Use the following procedures to invoke the Web service from the WSDL page of the Web service explorer:
Select WSDL Main from the Navigator on the left side.
Specify the URL of the WSDL in the Actions at upper-right, then click the [Go] button.
The WSDL structure is displayed in the Navigator on the left side. Select the operation that you want to check.
Enter the operation argument in the Actions at upper-right, then click the [Go] button.
The result of invoking the Web service is displayed in the Status at lower-right.
Point
Web service messages can be checked directly by selecting the source in the Actions at upper-right or the Status at lower-right.
Note
The UDDI registry can be referred to on the UDDI page of the Web service explorer. However, this is not normally used because the registry function is not supported by Interstage Application Server.
The TCP/IP monitor is placed between the Web service and the Web service client, and can be used to monitor SOAP data exchanges.
TCP/IP Monitor Setup
TCP/IP monitor setup is performed from [Run/Debug] > [TCP/IP Monitor] on the Preferences page.
Refer to the following for the settings:
Local monitoring port
Specify the port number used for access to the TCP/IP monitor from the client.
Host name
Specify the name of the host operating on the server.
Port
Specify the port number operating on the server.
Launching the TCP/IP Monitor
To launch the TCP/IP monitor, select the monitor on the [TCP/IP Monitor] preferences page, then click the start button.
Changing the Client Side Connection URL
Since the client side needs to access the Web service via the TCP/IP monitor, the connection URL may need to be changed.
If the @WebServiceRef annotation is being used, use wsdlLocation as shown below to specify the TCP/IP monitor URL.
Example of using the WebServiceRef Annotation
@WebServiceRef(wsdlLocation="http://localhost:8888/websv/CalculateService") private CalcService service; |
Using the TCP/IP Monitor to Check Messages
When messages are sent from the client to the TCP/IP monitor while the TCP/IP monitor is in the started state, these request messages and the corresponding response messages are displayed on the TCP/IP monitor.
To clear the messages, click the clear button on the right of the TCP/IP monitor.
Validating the WS-I Message Log File
The following procedures can be used to check whether or not the messages monitored by the TCP/IP monitor are valid as WS-I Basic Profile messages:
Select send request at the TCP/IP monitor.
Click the Validate WS-I Message Log File button on the right of the TCP/IP monitor.
Specify the message save destination in the displayed wizard.
If required, specify include for the WSDL document.
Use the WS-I message validator to check the validity of the messages.
For validator details, refer to "6.2.5.2 Validation".
