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. Read about providing the HTTP endpoint URL information to learn how the URL information affects the content of the published WSDL.
To publish a WSDL file we need an EAR file, containing a Web services-enabled module and has been deployed into WebSphere Application Server. To learn how to deploy web services, see the deploying web services applications onto application servers information.
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 you publish 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. 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 specified. We can provide these WSDL files to clients that want to invoke the 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 you are using:
- (dist)(zos) Configure the URL endpoint information for HTTP bindings.
- Configure the URL endpoint information for JMS bindings.
- (dist)(zos) 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:
- (dist)(zos) Publish a WSDL file with the administrative console
- (dist)(zos) Publish a WSDL file using a URL.
- Publish a WSDL file with wsadmin.sh.
What to do next
Apply security to the web services. To learn more, see the securing web services applications using message level security information.
Subtopics
- Configure web services client bindings
When a web services application is deployed into WebSphere Application Server, an instance is created for each application or module. The instance contains deployment information for the web module or EJB module, including client bindings.
- Configure endpoint URL information for HTTP bindings
Configuring a service endpoint is necessary to connect JAX-WS and JAX-RPC web services clients to any web services among the components being assembled or to any external web services.
- Configure endpoint URL information for JMS bindings
WebSphere Application Server supports the use of the Java Message Service (JMS) API to transport web services requests, as an alternative to using HTTP.
- Configure endpoint URL information to directly access enterprise beans
WebSphere Application Server supports directly accessing an enterprise bean as a web service, as an alternative to using HTTP or Java Message Service (JMS) to transport requests between the server and the client. The EJB module used as a web service contains a Web Services Description Language (WSDL) file containing EJB bindings.
- Publish WSDL files using the administrative console
We can publish a WSDL file using the WAS administrative console.
- Publish WSDL files using a URL
We can publish a WSDL file using a URL.
Related concepts
WSDL Overview of standards and programming models for web services message-level security
Related tasks
Publish WSDL files Develop a WSDL file for JAX-RPC applications Deploy web services applications onto application servers