52 lines
2.9 KiB
HTML
52 lines
2.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>Web services overview</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><A NAME="wsovr">Web services overview</A></h2>
|
||
|
|
|
||
|
|
<p>A typical Web services scenario is a business application requesting a service from a given URL using Simple Object Access Protocol (SOAP) over a HyperText Transport Protocol (HTTP) transport. The service receives the request, processes it, and returns a response. Examples of a simple Web service include weather reports and stock quotes. The method call is synchronous, that is, it waits until the result is available. Transaction Web services, supporting quotes, business-to-business (B2B) or business-to-client (B2C) operations include airline reservations or purchase orders.</p>
|
||
|
|
|
||
|
|
<p>The key components of a Web service are:</p>
|
||
|
|
<ul>
|
||
|
|
<li>Simple Object Access Protocol (SOAP)</li>
|
||
|
|
<li><a href="wswsdl.htm">Web Services Description Language (WSDL)</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express Version 5.1 and later follows these standards:</p>
|
||
|
|
<ul>
|
||
|
|
<li>SOAP Version 1.1</li>
|
||
|
|
<li>WSDL Version 1.1</li>
|
||
|
|
<li>Web Services for J2EE (JSR-109) Version 1.0</li>
|
||
|
|
<li>Java API for XML-based remote procedure call (JAX-RPC) Version 1.0</li>
|
||
|
|
<li><a href="wssaaj.htm">SOAP with Attachments API for Java (SAAJ)</a> Version 1.1</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>You can review the Web services client programming model in the Web services for J2EE specification available in the <a href="wsrefs.htm">Web services resources</a> topic. The programming model is similar to the EJB client programming model. There is a remote interface that the client uses to interact with the service. A Java Naming and Directory Interface (JNDI) lookup method can locate the service for a client running in a Web container or client container. The client obtains a stub that implements the remote interface and makes calls to invoke operations on the remote service.</p>
|
||
|
|
|
||
|
|
<p>A WebSphere Application Server - Express Java Web service client can exist as one of the following entities:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>As an unmanaged stand-alone Java application.</li>
|
||
|
|
<li>As a Java bean or a servlet running in a Web container that is acting as a client.</li>
|
||
|
|
</ul>
|
||
|
|
<p>These topics describe further concepts of Web services:</p>
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="wsarch.htm">Web services architecture</a></strong>
|
||
|
|
<br>This topic discusses how Web service providers, brokers, and requesters interact to provide and run Web services.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsops.htm">Web services operations</a></strong>
|
||
|
|
<br>This topic discusses the life cycle of a Web service, and the roles played by providers, brokers, and requesters in that cycle.</p>
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|