44 lines
1.8 KiB
HTML
44 lines
1.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 architecture</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h3><A NAME="wsarch">Web services architecture</A></h3>
|
|
|
|
<p>The Web services architecture includes three roles:</p>
|
|
<ul>
|
|
<li><strong>Service provider</strong><br>
|
|
Web service providers create components, then publish them to a repository. On the WebSphere Application Server - Express platform, these components include:
|
|
<ul>
|
|
<li>Java beans</li>
|
|
<li>DB2 Universal Database stored procedures</li>
|
|
<li>Server-side scripts that implement the Bean Scripting Framework (BSF)</li>
|
|
</ul>
|
|
<!--<p>For more information on accessing enterprise beans, see <a href="wssoapeb.htm">Enterprise beans</a>.</p>-->
|
|
<p>Web service providers can also unpublish components (remove them from the repository) when they are no longer needed.</p>
|
|
</li>
|
|
|
|
<li><strong>Service broker</strong><br>
|
|
Web service brokers categorize Web services as they are published, and search for them as service requests are received. Web brokers are roughly analagous to Internet search engines, except that they locate components instead of Web pages.</li>
|
|
|
|
|
|
<li><strong>Service requester</strong><br>
|
|
Web service requesters look up, or locate and invoke components as services. They act as the client for published Web services.
|
|
</li>
|
|
</ul>
|
|
|
|
<p>This diagram illustrates how client and server roles can interact to provide Web services.</p>
|
|
<p><img src="rzaiz524.gif" width="301" height="223" alt="Web services architecture" border="0"></p>
|
|
|
|
|
|
</body>
|
|
</html>
|