This topic explains how to use the wsdeploy command-line tool with Web services that are based on the Web Services for J2EE specification. The wsdeploy command adds WebSphere product-specific deployment classes to a Web services compatible enterprise application enterprise archive (EAR) file or an application client Java archive (JAR) file. These classes include:
For Version 5.0.2, you can download the Assembly Toolkit
from the Web site
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q=ASTK&uid=swg24005125&loc= en_US&cs=utf-8&lang=en+en
The wsdeploy command operates as follows:
When the generated files are compiled, they can reference application-specific classes outside the EAR or JAR file, if the EAR or JAR file is not self-contained. In this case, use either the -jardir or -cp option to specify additional JAR or zip files to be added to CLASSPATH when the generated files are compiled.
wsdeploy command syntax
The command syntax is as follows:
wsdeploy Input_filename Output_filename [options]
Required options:
Specifies the path to the EAR or JAR file to be deployed.
Specifies the path of the deployed EAR or JAR file. If output_filename already exists, it is silently overwritten. The output_filename can be the same as the input_filename.
Other options:
Specifies a directory containing JAR or zip files. All JAR and 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.
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.
Specifies that deployment code is to be generated, but not compiled. This option implicitly specifies the -keep option.
Includes debugging information when compiling, that is, use javac -g to compile.
Displays a help message and exit.
Do not stop deployment if validation or compilation errors are encountered.
Do not delete working directories containing generated classes. A message is displayed indicating the name of the working directory that is retained.
Do not validate the Web services deployment descriptors in the input file.
Displays processing information, including the names of the generated files.
Example
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.
Messages
Option f was not recognized as being a valid option.
Options may be abbreviated, but the abbreviation must be unique. In this case, the wsdeploy command can not determine which option was intended.
A required parameter for an option was omitted.
A required option was omitted.