57 lines
3.4 KiB
HTML
57 lines
3.4 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>Deploy a programming component as a SOAP accessible Web service</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="wssoapdc">Deploy a programming component as a SOAP accessible Web service</A></h5>
|
||
|
|
|
||
|
|
<p>Complete these steps to deploy a SOAP-accessible Web service on WebSphere Application Server - Express:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><strong>Create or locate the software resource to be published as a service</strong><br>
|
||
|
|
To deploy a service, create one or more of the supported programming components (beans, DB2 stored procedure, or BSF script), or locate an existing piece of code of the supported type.</li>
|
||
|
|
|
||
|
|
<li><strong>Assemble an Enterprise Archive (EAR) file</strong><br>
|
||
|
|
Package the component into an Enterprise Archive (EAR) file. This step is a deployment packaging requirement of WebSphere Application Server - Express. Create the EAR file.</li>
|
||
|
|
|
||
|
|
<li><strong>Create the SOAP deployment descriptor for the desired service</strong><br>
|
||
|
|
In order to deploy a component as a SOAP service, create an Apache SOAP deployment descriptor that describes the service you are creating. This step designates the programming component as a <strong>service</strong>. The descriptor describes and defines the parts of the code that are invoked through SOAP calls.
|
||
|
|
|
||
|
|
<p>The information contained in the deployment descriptor varies, depending on the type of artifact you are publishing. For example, this deployment descriptor could be used with the StockQuoteSample:</p>
|
||
|
|
|
||
|
|
<pre>
|
||
|
|
<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
|
||
|
|
id="urn:service-urn" [type="message"]>
|
||
|
|
<isd:provider type="java" scope="Request | Session | Application" methods="exposed-methods">
|
||
|
|
<isd:java class="implementing-class" [static="true|false"]/>
|
||
|
|
</isd:provider>
|
||
|
|
<isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
|
||
|
|
</isd:service>
|
||
|
|
</pre>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li><strong>Run the SoapEarEnabler tool to enable your Web service</strong><br>
|
||
|
|
You must first package your component into an Enterprise Archive (EAR) file. Next, using the deployment descriptor as input data, add the necessary pieces to the EAR file to enable the component as a Web service. To facilitate this process, use the Java<sup>(TM)</sup>-based tool, SoapEarEnabler. Depending on whether you secure the Web service, this tool adds two Web modules: soap.war and soap-sec.war to the EAR file. These Web modules include the SOAP deployment descriptors plus the necessary parts to deploy the service into the WebSphere Application Server - Express run time.
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> The service does not become available until you install the SOAP enabled EAR file and restart the application server.</p>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li><strong>Install the modified EAR file into your WebSphere Application Server - Express instance</strong><br>
|
||
|
|
Install the modified EAR file into your WebSphere Application Server - Express instance.</li>
|
||
|
|
|
||
|
|
<li><strong>Restart your WebSphere Application Server - Express instance.</strong></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|