34 lines
1.9 KiB
HTML
34 lines
1.9 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
|
|
|
<title>Publish Web Services Description Language files</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h3><a name="wswsdlpub"></a>Publish Web Services Description Language files</h3>
|
|
|
|
<p>The purpose of publishing the Web Services Description Language (WSDL) file is to provide clients with a description of the Web service, including the URL that identifies the location of the service.</p>
|
|
|
|
<p>After installing a Web services application and optionally modifying the endpoint information, you might need WSDL files that contain the updated endpoint information. You can obtain the updated WSDL files by publishing them 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 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.</p>
|
|
|
|
<p>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.</p>
|
|
|
|
<p>You can publish WSDL files for the deployed EAR file in one of the following ways:</p>
|
|
|
|
<ul>
|
|
<li><a href="wswsdlpubac.htm">With the administrative console</a></li>
|
|
<li><a href="wswsdlpubwsa.htm">With wsadmin</a></li>
|
|
<li><a href="wswsdlpuburl.htm">Through a URL</a></li>
|
|
</ul>
|
|
|
|
<p>For more information, see <a href="wswsdlpubbp.htm">Multipart Web Services Description Language file best practices</a>.</p>
|
|
|
|
</body>
|
|
</html>
|