You can test a service after it has been packaged and deployed. Testing the service verifies the functionality before using the service in a composite service or publishing the service. Because you are testing the public interface of the service, you should be aware of the anticipated WSDL structure for your service.
Prerequisites:
The service must have been successfully deployed.
You can test services one of three ways. All three methods require a WSDL document that has a SOAP binding. To verify that the WSDL for your service has a SOAP binding, view the structure in Example WSDL with a SOAP Binding.
For a service from a UDDI registry, you must have a UDDI Registry Connection Profile.
A service that contains a WSDL file with output parameters of the type anyType can be tested only by the SOAP Request/Response Service Test wizard. The Dialog Service Test Wizard and Web Service Client wizard do not work with WSDL files that have output parameters of anyType.
To test a service that has been deployed to EAServer 5.x, you can create a Web Service Client or you can connect to the service in the Enterprise Explorer view, find the service, right click on an individual operation and Invoke.
You can test a service using these methods:
The Generate Empty Request Message button on the SOAP Request/Response Service Test wizard genererates a sample XML instance document that matches the body of the SOAP request. Once populated, the instance document can be used for invoking the specific service. The Dialog Service Test wizard automatically and transparently generates the correct SOAP request. In both cases, you can employ the SOAP Inspector view to examine the full SOAP request and SOAP response messages.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com