37 lines
2.5 KiB
HTML
37 lines
2.5 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>WSIF usage scenarios</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h5><A NAME="wswsifuse">WSIF usage scenarios</A></h5>
|
|
<p>This topic describes two brief scenarios that illustrate the role that Web Services Invocation Framework (WSIF) plays in the emerging Web services environment.</p>
|
|
|
|
<p><strong>Scenario: Redevelopment and redeployment</strong></p>
|
|
|
|
<p>If you are implementing Web services today, you are probably working with simple prototypes. As your Web services move into production, you need to reimplement and redeploy them. WSIF uses the same API calls with different underlying technologies. If you use WSIF you can reimplement and redeploy your services without changing the client code, and you can use existing highly reliable and high-performance infrastructures like RMI-IIOP without sacrificing the location-independence that the Web service model offers.</p>
|
|
|
|
<p><strong>Scenario: Service Flow composition</strong></p>
|
|
|
|
<p>A service flow typically invokes a Web service, then passes the response from one Web service into the next Web service, perhaps performing some transformation in the middle.</p>
|
|
|
|
<p>There are two key aspects to this that WSIF provides:</p>
|
|
<ul>
|
|
<li>A representation of the service invocation based on the metadata in WSDL. </li>
|
|
<li>The ability to build invocations based on the portType only, which can be used on any implementation. </li></ul>
|
|
<p>For example, imagine that you build a meta-service that uses a number of services to build a process. Initially several of those services are simple JavaBean prototypes that are written and exposed through Simple Object Access Protocol (SOAP), but you plan to reimplement some of them as EJB components, and to out-source others.</p>
|
|
|
|
<p>If you use SOAP, it ties up multiple threads for every onward invocation, as they pass through the webserver and servlet engine into the SOAP router. If you use WSIF to call the beans directly, you get much better performance compared to SOAP, and you don't lose access or location transparency. Using WSIF, you can move some of the Web services from local implementations to external SOAP services you just update the WSDL.</p>
|
|
|
|
|
|
|
|
</body>
|
|
</html>
|