Invoking a call with a WSDL file

You can invoke calls to SOAP or JMS-based services that use a Web Service Description Language (WSDL) file to specify the contents of the call.

Before you begin

Ensure that you have a valid WSDL file. Ensure that the WSDL files use the correct syntax for the test environment. The generic service client might not work with some Web Services Description Language (WSDL) files.

If the service uses Secure Sockets Layer (SSL) authentication, create an SSL configuration before invoking the call. See Creating an SSL configuration for details.

If the service uses SOAP security for encryption, signature, or other security algorithms, you must first configure the environment with the correct libraries and configuration files, and then create a security profile for the WSDL. See Configuring the environment for SOAP security and Creating a SOAP security profile for a WSDL for details.

If the service sends or receives file attachments, ensure that you have configured the environment with the correct libraries and configuration files. See Configuring the environment for handling file attachments for details.

About this task

To invoke a service call based on a WSDL file:

Procedure

  1. Open the generic service client and click the Calls tab, and then, click Add a WSDL file Add a WSDL file.
  2. In the Add WSDL Files window, select an existing WSDL or import a WSDL with one of the following methods:
    • Click Import from File to import a WSDL file from the file system.
    • Click Import from URL to download and import an online WSDL from the Web.
    • Click Import from WSRR to import a WSDL from an IBM® WebSphere® Service Registry and Repository (WSRR). Enter the URL of the WSRR and click Connect. You can click Search Search to browse the contents of the repository.
    • Click Import from UDDI to import a WSDL from a Universal Description Discovery and Integration (UDDI) repository. Enter the URL of the UDDI and click Connect. You can click Filter Filter and Search Search to browse the contents of the repository.
  3. Click OK. The WSDL is added to the Call Library.
  4. In the Call Library, expand the WSDL, binding, and operation, and then select the call element. The call is automatically configured with any SOAP or JMS endpoints that are available in the WSDL. The generic service client shows 3 steps: Edit Data, Invoke and View Response. The details for the call are displayed under the Edit Data step.
  5. On the Message page, use the Form, Tree, or Source views to edit the contents of the call. Each view proposes a different display of the same data. If you want to add or remove XML elements in the Form or Tree view, you can click Schema > Validate and Assist to comply with an XML Schema Definition (XSD) specified in the Schema Catalog.
  6. On the Attachments page, specify any file attachments that will be sent with the call. You must have configured the environment with the correct libraries and configuration files to handle file attachments.
  7. On the Transport page, specify an HTTP, JMS, or WebSphere MQ transport configuration to be used by the call. You can create and edit transport and security configurations by clicking the Transport tab.
  8. On the Security for Request and Security for Response pages, specify whether you want to override the security settings for the WSDL. If you want to edit the current security settings for the WSDL, click Edit WSDL Security to open the WSDL Security Editor.
  9. When you are ready, click Invoke to invoke the service call. The generic service client sends the request and displays the message return under the View Response step.

What to do next

Successful calls are recorded and added to the Call History.

Feedback