102 lines
5.3 KiB
HTML
102 lines
5.3 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>The wsdeploy script</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h3><a name="qshwsdeploy"></a>The wsdeploy script</h3>
|
|
|
|
<p>The wsdeploy command line tool adds Websphere Application Server - Express product-specific Web services deployment classes to a Web services enterprise archive (EAR) file. These classes include:</p>
|
|
|
|
<ul>
|
|
<li>Stubs</li>
|
|
<li>Serializers and deserializers</li>
|
|
<li>Implementations of service interfaces</li>
|
|
</ul>
|
|
|
|
<p>This deployment step must be performed at least once, and can be performed more than once. Deployment can be performed separately using the wsdeploy command or when the application is installed. When using the wsadmin command for installation, specify the -deployws option. When using the administrative console for installation, select the Deploy Web services check box.</p>
|
|
|
|
<p>The wsdeploy command operates as follows:</p>
|
|
|
|
<ol>
|
|
<li>Each module in the enterprise application is examined.</li>
|
|
<li>If the module contains Web services implementations, indicated by the presence of the webservices.xml deployment descriptor, the associated Web Services Description Language (WSDL) files are located and the WSDL2Java command is run with the role deploy-server.</li>
|
|
<li>If the module contains Web services clients, indicated by the presence of the webservicesclient.xml deployment descriptor, the associated WSDL files are located and the WSDL2Java command is run with the role deploy-client.</li>
|
|
<li>The files generated by the WSDL2Java command are compiled and repackaged.</li>
|
|
</ol>
|
|
<p>See WSDL2Java command for more information about the files that are generated for deployment.</p>
|
|
|
|
<p>When the generated files are compiled, they can reference application-specific classes outside the EAR if the EAR is not self-contained. In this case, use -cp option to specify additional zip files to be added to CLASSPATH when the generated files are compiled.</p>
|
|
|
|
<p><strong>Authority</strong></p>
|
|
<p>To run this script, your user profile must have *RX authority.</p>
|
|
|
|
<p><strong>Syntax</strong></p>
|
|
<p>The syntax of the script is:</p>
|
|
|
|
<pre>wsdeploy <em>Input_filename</em> <em>Output_filename</em> [options]</pre>
|
|
|
|
<p><strong>Parameters</strong></p>
|
|
<p>The parameters of the script are:</p>
|
|
|
|
<ul>
|
|
<li><p><strong><em>Input_filename</em></strong>
|
|
<br>Specifies the path to the EAR to be deployed.</p></li>
|
|
|
|
<li><p><strong><em>Output_filename</em></strong>
|
|
<br>Specifies the path of the deployed EAR file. If output_filename already exists, it is silently overwritten. The output_filename can be the same as the input_filename.</p></li>
|
|
|
|
<li><p><strong>-jardir</strong>
|
|
<br>This is an optional parameter. The value <em>directory</em> specifies a directory containing zip files. All zip files in this directory are added to the CLASSPATH used to compile the generated files. This option can be specified zero or more times.</p></li>
|
|
|
|
<li><p><strong>-cp</strong>
|
|
<br>This is an optional parameter. The value <em>entries</em> specifies entries to be added to CLASSPATH when the generated classes are compiled. Multiple entries are separated the same as they would be in the CLASSPATH environment variable, with a semicolon on Windows platforms and a colon for UNIX platforms.</p></li>
|
|
|
|
<li><p><strong>-codegen</strong>
|
|
<br>This is an optional parameter. Specifies that deployment code is to be generated, but not compiled. This option implicitly specifies the -keep option.</p></li>
|
|
|
|
<li><p><strong>-debug</strong>
|
|
<br>Includes debugging information when compiling, that is, use javac -g to compile.</p></li>
|
|
|
|
<li><p><strong>-help</strong>
|
|
<br>Displays a help message and exit.</p></li>
|
|
|
|
<li><p><strong>-ignoreerrors</strong>
|
|
<br>Do not stop deployment if validation or compilation errors are encountered.</p></li>
|
|
|
|
<li><p><strong>-keep</strong>
|
|
<br>Do not delete working directories containing generated classes. A message is displayed indicating the name of the working directory that is retained.</p></li>
|
|
|
|
<li><p><strong>-novalidate</strong>
|
|
<br>Do not validate the Web services deployment descriptors in the input file.</p></li>
|
|
|
|
<li><p><strong>-trace</strong>
|
|
<br>Displays processing information, including the names of the generated files.</p></li>
|
|
</ul>
|
|
|
|
<p><strong>Example</strong></p>
|
|
|
|
<pre>wsdeploy x.ear x_deployed.ear -trace -keep
|
|
Processing web service module x_client.jar.
|
|
Keeping directory: f:\temp\Base53383.tmp for module: x_client.jar.
|
|
Parsing XML file:f:\temp\Base53383.tmp\WarDeploy.wsdl
|
|
Generating f:\temp\Base53383.tmp\generatedSource\com\test\WarDeploy.java
|
|
Generating f:\temp\Base53383.tmp\generatedSource\com\test\WarDeployLocator.java
|
|
Generating f:\temp\Base53383.tmp\generatedSource\com\test\HelloWsBindingStub.java
|
|
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\WarDeploy.java.
|
|
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\WarDeployLocator.java.
|
|
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\HelloWsBindingStub.java.
|
|
Done processing module x_client.jar.</pre>
|
|
|
|
<p><strong>Note:</strong> The wsdeploy always displays messages in English, regardless of the locale setting.</p>
|
|
|
|
</body>
|
|
</html>
|