132 lines
4.8 KiB
HTML
132 lines
4.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>SoapEarEnabler tool</title>
|
||
|
</head>
|
||
|
|
||
|
<BODY>
|
||
|
<!-- Java sync-link -->
|
||
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
||
|
<h6><A NAME="wsspseet">SoapEarEnabler tool</A></h6>
|
||
|
|
||
|
<p>The SoapEarEnabler tool is a Java application that enables a set of SOAP services within an
|
||
|
Enterprise Application Archive (EAR) file. The SoapEarEnabler guides you through the required steps to
|
||
|
enable one or more services within an application. It makes a backup copy of your original EAR file in
|
||
|
case you later need to remove or add services.</p>
|
||
|
|
||
|
<p><strong>Note:</strong> Start with an existing EAR file. The SoapEarEnabler tool does not
|
||
|
accept a SOAP enabled EAR file as input.</p>
|
||
|
|
||
|
<p>You are prompted as to whether you want to add the administration client to the EAR file. This is a
|
||
|
Web-based client that allows you to list all active services for a specific context from a browser
|
||
|
window. With this interface, you can stop and start existing services. You can choose to not add this
|
||
|
interface for security reasons, or you can secure the interface before making a service available.</p>
|
||
|
|
||
|
<p>Perform these steps to invoke and use the SOAPEarEnabler tool:</p>
|
||
|
|
||
|
<ol>
|
||
|
<li>Create an Apache SOAP deployment descriptor for each service to be enabled.</li>
|
||
|
|
||
|
<li>You can invoke the SOAPEarEnabler tool from QShell on iSeries.</li>
|
||
|
|
||
|
|
||
|
<li>If running in interactive mode, enter the required information when prompted by the tool.</li>
|
||
|
</ol>
|
||
|
|
||
|
|
||
|
<p><strong>Silent mode</strong></p>
|
||
|
|
||
|
<p>If you use the SOAPEarEnabler in silent mode, you must supply all the required parameters as command
|
||
|
line arguments. These include:</p>
|
||
|
|
||
|
<ul>
|
||
|
<li><strong><em>ear-file-name</em></strong><br>
|
||
|
This is the name of the EAR file to which you want to add SOAP services. Note that you can type a
|
||
|
path relative to the bin directory.</li>
|
||
|
|
||
|
<li><strong><em>number-of-services</em></strong><br>
|
||
|
This is the number of services you want to enable for the EAR file. If you want to enable more
|
||
|
than one service, you must specify that number of each of these parameters:
|
||
|
<ul>
|
||
|
<li><em>deployment-descriptor-file-name</em><br>
|
||
|
This is the name of the deployment descriptor file you are using to describe the SOAP service
|
||
|
you are enabling for this EAR file.
|
||
|
</li>
|
||
|
|
||
|
<li>Specify whether the service is an enterprise bean.<br>
|
||
|
Type <tt>n</tt> to indicate that the service you are adding is not an enterprise bean.
|
||
|
WebSphere Application Server - Express does not support enterprise beans.</li>
|
||
|
|
||
|
<li>Specify whether this service should be secured.<br>
|
||
|
Type <tt>y</tt> to secure this SOAP service; type <tt>n</tt> if you do not want to enable
|
||
|
security.
|
||
|
<ul>
|
||
|
<li>If you typed <tt>y</tt>, type the context root for the secured service. Example:
|
||
|
<tt>/soapsec</tt>.</li>
|
||
|
<li>If you typed <tt>n</tt>, type the context root for the nonsecured service. Example:
|
||
|
<tt>/soap</tt>.</li>
|
||
|
</ul>
|
||
|
</li>
|
||
|
</ul>
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
<p><strong>Silent mode examples</strong></p>
|
||
|
|
||
|
<p>When invoking the SOAPEarEnabler tool in silent mode, type the command and its parameters as a
|
||
|
single, continuous line.</p>
|
||
|
|
||
|
<p><strong>Note:</strong>The text for the following commands have been wrapped for better
|
||
|
readability. If you are using the command from iSeries, use '/' in the pathnames instead of '\'.</p>
|
||
|
|
||
|
|
||
|
|
||
|
<p>This is an example of deploying 2 java classes as nonsecured services:</p>
|
||
|
|
||
|
<pre> soapearenabler soap.ear 2 xml-soap\java\samples\stockquote\deploymentdescriptor.xml
|
||
|
n 1 samples.jar n xml-soap\java\samples\addressbook\deploymentdescriptor.xml
|
||
|
n 1 samples.jar n /soap</pre>
|
||
|
|
||
|
<p><strong>Interactive mode</strong></p>
|
||
|
<p>In interactive mode, the SoapEarEnabler tool prompts you for all required information. For
|
||
|
example:</p>
|
||
|
|
||
|
<pre>
|
||
|
Please enter the name of your ear file:
|
||
|
..\work\stockquote.ear
|
||
|
How many services would you like your application to contain (1...n)?
|
||
|
1
|
||
|
|
||
|
Now prompting for info for service #1:
|
||
|
|
||
|
Please enter the file name of the deployment descriptor xml file:
|
||
|
..\work\Stockading.xml
|
||
|
Is this service an EJB (y/n)?
|
||
|
n
|
||
|
How many jar files are required for this service (0...n)?
|
||
|
1
|
||
|
Classpath requirement #1: Please choose a file ([1] samples.jar, [2] stockquote.war):
|
||
|
1
|
||
|
Should this service be secured (y/n)?
|
||
|
n
|
||
|
|
||
|
Please enter a context root for your nonsecured services (Example: /soap):
|
||
|
/soapsamples
|
||
|
Do you wish to install the administration client?
|
||
|
|
||
|
Warning! You should not install this client in a production ear
|
||
|
unless you intend to secure the URI to it.
|
||
|
|
||
|
Install the administration client (y= yes/n= no)?
|
||
|
y
|
||
|
</pre>
|
||
|
|
||
|
<p><strong>Note: </strong>Examples may be wrapped for display purposes.</p>
|
||
|
|
||
|
</body>
|
||
|
</html>
|