Publishing WSDL files using the administrative console

You can publish a Web Services Description Language (WSDL) file using the WebSphere® Application Server administrative console.

Before you begin

Before completing this task, you need to install or deploy the web service. After deployment, configure the URL endpoint tasks for your transport:
  • Configure endpoint URL information for HTTP bindings
  • Configure endpoint URL information for JMS bindings
  • Configure endpoint URL information to directly access enterprise beans

About this task

By publishing a WSDL file, you are providing clients with a description of the web service, including the URL identifying the location of the service.

The WSDL files in each web services-enabled module are published to the file system location you specify. You can provide these WSDL files in the development and configuration process of the web service clients so they can invoke your web services.

This task applies for Java™ API for XML-Based Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) web services.

To learn about more ways to publish WSDL files, see the making deployed web services applications available to clients information.

To publish an application's WSDL file with the administrative console:

Procedure

  1. Open the administrative console.
  2. Click Applications > Application Types > WebSphere enterprise applications > application_name.
  3. Under Web Services Properties, click Publish WSDL files. This takes you to the Publish WSDL zip files page.
  4. Click the WSDL compression file to download.
    The compression file contains the application's published WSDL files. The compression file ExtendedWDLFiles.zip contains EJB binding information. It can also contain JMS or HTTP binding information. The compression file WSDLFiles.zip only contains JMS or HTTP binding information.

    [z/OS]The compression file ExtendedWDLFiles.zip can contain HTTP binding information. The compression file WSDLFiles.zip only contains HTTP binding information.

What to do next

Apply security to your web services. To learn more, see the securing web services applications using message level security information.