To publish a Web Services Description Language (WSDL) file you need an enterprise application (*.ear) that contains 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, 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: