Making deployed web services applications available to clients
We can publish WSDL files to the file system. If we are a client developer or a system administrator, we can use WSDL files to enable clients to connect to web services.
The publish WSDL administrative console panel supports both JAX-RPC and JAX-WS services. The publish WSDL panel generates a compression file containing WSDL files for all modules in an application containing JAX-WS or JAX-RPC web services.
To publish a WSDL file we need an enterprise application, also known as an EAR file, containing a Web services-enabled module and has been deployed into WebSphere Application Server.
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, we might need WSDL files containing the updated endpoint informations to make deployed web services application to be available to clients.
Before publishing a WSDL file, we can configure web services to specify endpoint information in the form of URL fragments to enable full URL specification of WSDL ports.
The WSDL files for each web services-enabled module are published to the file system location we specify. We can provide these WSDL files to clients that want to invoke your Web services.
We can specify endpoint information for HTTP ports, for Java Message Service (JMS) ports, or we can directly access enterprise beans that are acting as web services.
- Configure the web services client bindings.
- Configure the URL endpoint information for HTTP bindings. Do one of the following depending on what kind of bindings we are using:
- Configure the URL endpoint information for HTTP bindings.
- Configure the URL endpoint information for JMS bindings.
- Configure the URL endpoint information to directly access enterprise beans.
- Externalize or publish the WSDL file out of the application. We can complete this task in the following ways:
- Publish a WSDL file with the administrative console
- Publish a WSDL file using a URL.
- Publish a WSDL file with the wsadmin tool.
What to do next
Apply security to the web services.
- Configure web services client bindings
- Configure endpoint URL information for HTTP bindings
- Configure endpoint URL information for JMS bindings
- Configure endpoint URL information to directly access enterprise beans
- Publishing WSDL files
- Publishing WSDL files using a URL
WSDL Overview of standards and programming models for web services message-level security Publishing WSDL files Developing a WSDL file for JAX-RPC applications Deploy web services applications onto application servers