The wsdeploy script

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:

• Stubs
• Serializers and deserializers
• Implementations of service interfaces

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.

The wsdeploy command operates as follows:

1. Each module in the enterprise application is examined.
2. 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.
3. 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.
4. The files generated by the WSDL2Java command are compiled and repackaged.

See WSDL2Java command for more information about the files that are generated for deployment.

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.

Authority

To run this script, your user profile must have *RX authority.

Syntax

The syntax of the script is:

wsdeploy Input_filename Output_filename [options]

Parameters

The parameters of the script are:

• Input_filename
  Specifies the path to the EAR to be deployed.

• Output_filename
  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.

• -jardir
  This is an optional parameter. The value directory 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.

• -cp
  This is an optional parameter. The value entries 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.

• -codegen
  This is an optional parameter. Specifies that deployment code is to be generated, but not compiled. This option implicitly specifies the -keep option.

• -debug
  Includes debugging information when compiling, that is, use javac -g to compile.

• -help
  Displays a help message and exit.

• -ignoreerrors
  Do not stop deployment if validation or compilation errors are encountered.

• -keep
  Do not delete working directories containing generated classes. A message is displayed indicating the name of the working directory that is retained.

• -novalidate
  Do not validate the Web services deployment descriptors in the input file.

• -trace
  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.

Note: The wsdeploy always displays messages in English, regardless of the locale setting.