Sending service requests with the generic service client
The generic service client enables you to send requests
to services for which you do not have a convenient client and to view
the responses returned by the service.
Generic service client overview
The purpose of the generic service client is to send requests
to any service that uses an HTTP, JMS, WebSphere® MQ, or Microsoft .NET transport. The generic service
client also displays the response returned by the service.
Sending service requests with WSDL files
You can send requests to services based on SOAP, Java Messaging
Service (JMS), WebSphere MQ,
and Microsoft .NET that
use a Web Service Description Language (WSDL) file to specify the
contents of the service request.
Testing all operations in a WSDL file
You can use the generic service client to rapidly send
requests to a service using all the operations in a Web Services Description
Language (WSDL) file. The calls are generated with default values
based on the type of data.
Viewing message content
The Raw Transaction Data view displays
the raw XML, text, or binary content of any service request or response
that is selected in the generic service client.
Synchronizing a remote WSDL file
For web services that make their Web Services Description
Language (WSDL) file available from a URL, you might have to ensure
that the WSDL that you work with is always up to date. By synchronizing
the WSDL, you ensure that the local copy of the WSDL in your workspace
is regularly synchronized with the remote WSDL.
Adding static XML headers to a service request
You can add static XML headers to service requests to ensure
compliance with WS-Addressing, WS-ReliableMessaging, and WS-Coordination
specifications as well as other predefined standards.
Opening file attachments
When a service sends a file attachment with the response,
you must import it as a resource to open the attachment.