Before deploying Web services-enabled modules or any enterprise
application archive (EAR) files that contain Web services-enabled module onto
an application server, you must generate deployment code for the application.
Before you begin
This article assumes you have assembled a module enabled with Web
services, added it to an application, saved the application, and verified
the application. It also assumes that you have started and configured an assembly
tool.
About this task
You can use an
assembly
tool to generate deployment code for the Web services-enabled module
or for the EAR file that contains the Web services-enabled module.
Procedure
- If you have turned automatic validation off, manually validate
any modules that use Web services with the JSR109 Web services validator before
generating deployment code for them. If validating your module results in
compilation errors or validation errors, fix the errors before generating
deployment code. However, if validating your module results in warning or
information messages, you can generate deployment code.
- In the Project Explorer view of the assembly tool, right-click
on the Web services-enabled module (WAR, enterprise bean JAR, or application
client JAR file) for which you want to generate code for deployment.
- Click Deploy. Alternatively, you can generate
deployment code for Web services-enabled modules using the deployment tool
for Web services (wsdeploy)
from a command prompt.
- If messages indicate that automatic file overwriting is not enabled,
click Yes to All so the generated files are added to the module.
- If errors such as Unbound classpath variable: WAS_50_PLUGINDIR appear
in the Tasks list, change the Java build path libraries properties to define
that variable to be the WebSphere Application Server installation directory.
Results
Code is generated into the folder where your Web services-enable module
is located. Problems with the generation of code result in a window that displays
error messages.