Testing your Web service with Web Services Explorer

You can test your Web service using Eclipse WDT tools and wizards before you create a client application.

Before you start this process, ensure that the ZIETrans runtime is started. You can do this by starting your server, and then, in the Servers view, choose the EAR file in which your Web service is contained, right-click, and choose Restart.

If you selected the option to Generate WSDL file into the project, see step 8 in the list under Creating a Bottom-up Web service from Integration Objects, the WSDL file that you created is located within your ZIETrans project:
  • If you are creating a Web service for an IBM® WebSphere® JAX-RPC or JAX-WS runtime, it is located in the Web Content/WEB-INF/Web Service Definitions folder.
  • If you created a Web service for an Apache Axis runtime, it is located in the Web Content/Web Service Definitions folder.
This folder contains a file called wrapper.wsdl, where wrapper is the name you gave to your wrapper class. Right-click this file and select Web Services > Test with Web Services Explorer.

In the right pane of the Web Services Explorer, you will see the io_nameProcessWS() methods for each Integration Object or EJB Access Bean included in the Web service. Click any method name to test that Integration Object. You will see a list of the input properties that you can specify for the Integration Object. This list is based on the Integration Object's io_name_Input_Properties class. The only properties that must be set are the prompts that you defined when you recorded your macro. The other properties can be left blank. Refer to the Eclipse documentation for information about using the WSDL view of Web Services Explorer to explore and test your Web service definition.

If you did not select the option to Generate WSDL file into the project, see step 8 in the list under Creating a Bottom-up Web service from Integration Objects, you can use a dynamically generated WSDL file to test your Web service from Services view of the Java™ EE perspective.