WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Making deployed Web services application available to clients

You can publish WSDL files to the file system. If you are a client developer or a system administrator, you can use WSDL files to enable clients to connect to a Web service.

Before you begin

New or updated for this feature pack Important: The WebSphere Application Server Version 6.1 Feature Pack for Web Services extends the capabilities of this product to introduce support for the Java API for XML-Based Web Services (JAX-WS) 2.0 programming model. JAX-WS is the next generation Web services programming model complimenting the foundation provided by the Java API for XML-based RPC (JAX-RPC) programming model. Using the strategic JAX-WS programming model, development of Web services and clients is simplified through support of a standards-based annotations model. Although the JAX-RPC programming model and applications are still supported, take advantage of the easy-to-implement JAX-WS programming model to develop new Web services applications and clients.
New or updated for this feature pack Supported configurations: The Feature Pack for Web Services does not support Java Message Service (JMS) transports or enterprise beans. This product only supports an HTTP transport and hosting JavaBeans endpoints within the Web container for JAX-WS Web services applications. To develop enterprise beans hosted as Web services, you must use the JAX-RPC programming model. This product does allow JAX-WS clients to issue requests from any of the Java Platform, Enterprise Edition (Java EE) containers along with the client Java 2 Standard Edition (J2SE) environment.

The publish WSDL administrative console panel, however, supports both JAX-RPC and JAX-WS services in the Feature Pack for Web Services. The publish WSDL panel generates a zip file that contains WSDL files for all modules in an application that contain a JAX-WS or JAX-RPC Web service. Read about providing the HTTP endpoint URL information to learn how the URL information affects the content of the published WSDL.

sptcfg
To publish a Web Services Description Language (WSDL) file you need an enterprise application, also known as an enterprise archive (EAR) file, that contains a Web services-enabled module and has been deployed into WebSphere Application Server. See Deploying Web services based on Web Services for Java 2 platform, Enterprise Edition (J2EE).

About this task

The purpose of publishing the WSDL file is to provide clients with a description of the Web service, including the URL identifying the location of the service.

After installing a Web services application, and optionally modifying the endpoint information, you might need WSDL files containing the updated endpoint informations to make deployed Web services application to be available to clients.

Before you publish a WSDL file, you can configure Web services to specify endpoint information in the form of URL fragments to enable full URL specification of WSDL ports. Refer to the tasks describing configuring endpoint URL information.

The WSDL files for each Web services-enabled module are published to the file system location you specify. You can provide these WSDL files to clients that want to invoke your Web services.

You can specify endpoint information for HTTP ports, Java Message Service (JMS) ports or directly access Enterprise JavaBeans (EJB) that are acting as Web services.

To publish a WSDL file:

Procedure

  1. Configure the URL endpoint information for HTTP bindings.
  2. Externalize or publish the WSDL file out of the application. You can complete this task in the following ways:

What to do next

Apply security to the Web service.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twbs_publishwsdl.html