52 lines
2.8 KiB
HTML
52 lines
2.8 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>Web Services Description Language (WSDL)</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><a name="wswsdl"></a>Web Services Description Language (WSDL)</h2>
|
||
|
|
|
||
|
|
<p><em>Web Services Description Language (WSDL)</em> is an Extensible
|
||
|
|
Markup Language (XML)-based description language that has been submitted to
|
||
|
|
the World Wide Web Consortium (W3C) as the industry standard for describing
|
||
|
|
Web services. The power of WSDL is derived from two main architectural principles:
|
||
|
|
the ability to describe a set of business operations and the ability to separate
|
||
|
|
the description into two basic units, a description of the operations and
|
||
|
|
the details of how the operation and the information associated with it are
|
||
|
|
packaged.</p>
|
||
|
|
|
||
|
|
<p>The WSDL document is the engine of a Java<sup>(TM)</sup> 2 platform, Enterprise Edition (J2EE) Web service; without it, there is no service. The information within a WSDL file maps to the Java application to create a Web service. WebSphere Application Server - Express
|
||
|
|
Versions 5.0.2, 5.1 and 5.1.1 use standards based on WSDL 1.1.</p>
|
||
|
|
|
||
|
|
<p>A WSDL document allows a service provider to specify the name and address
|
||
|
|
of the Web service; protocol and encoding style used when accessing the public
|
||
|
|
operations of the Web service; and the type information, including name, operations,
|
||
|
|
parameters and data comprising the interface of the Web service.</p>
|
||
|
|
|
||
|
|
<p>A WSDL document defines services as collections of network endpoints, or
|
||
|
|
ports. In WSDL, the abstract definition of endpoints and messages is separated
|
||
|
|
from their concrete network deployment or data format bindings. This allows
|
||
|
|
the reuse of abstract definitions: messages, which are abstract descriptions
|
||
|
|
of the data being exchanged, and port types which are abstract collections
|
||
|
|
of operations. The concrete protocol and data format specifications for a
|
||
|
|
particular port type constitutes a reusable binding. A port is defined by
|
||
|
|
associating a network address with a reusable binding, and a collection of
|
||
|
|
ports define a service. Therefore, a WSDL document is composed of several
|
||
|
|
elements. See <a href="wswsdlelements.htm">WSDL architecture</a> for
|
||
|
|
more information and examples of the WSDL elements.</p>
|
||
|
|
|
||
|
|
<p>When creating a Web service for WebSphere Application Server, you must
|
||
|
|
first have an implementation bean that includes a Service Endpoint Interface.
|
||
|
|
Then, you use <a href="qshjava2wsdl.htm">the Java2WSDL script</a> to create a WSDL that defines the Web service. To learn more about how
|
||
|
|
the WSDL file is used in the development process, see <a href="wsdev.htm">Develop Web services</a>.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|