Assembling a WAR file that is enabled for Web services from Java code
This topic explains how to assemble a WAR file that is enabled for Web services from Java code with an assembly tool.
You can assemble Java-based Web services modules with assembly tools provided with WAS. We need the following artifacts that are generated by the WSDL2Java command-line tool to complete this task:
- An assembled WAR file that contains the web.xml file, but is not enabled for Web services.
- The Java class for the service endpoint interface
- A Web Services Description Language (WSDL) file
- The complete webservices.xml,ibm-webservices-bnd.xmi, and ibm-webservices-ext.xmi deployment descriptors, and the Java API for XML-based remote procedure call (JAX-RPC) mapping file classes that are generated by the WSDL2Java command.
Overview
Assemble a Web services-enabled WAR file from Java code by following the actions in the steps for this task section.
Procedure
- Start an assembly tool. See "Starting WAS Toolkit" in the Application Server Toolkit documentation for more information.
- If you have not done so already, configure the assembly tool so that it works on J2EE modules. We need to make sure that the J2EE and Web categories are enabled. See "Configuring WAS Toolkit" in the Application Server Toolkit documentation for more information.
- Migrate WAR files created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to an Application Server Toolkit or Rational Application Developer assembly tool. To migrate files, import your WAR files to the assembly tool. See "Migrating code artifacts to an assembly tool" in the Application Server Toolkit documentation.
Results
The artifacts required to enable the Web module for Web services are added to the WAR file.
What to do next
Now you can assemble the WAR file that is enabled for Web services into an EAR file.
Assembling a Web services-enabled WAR into an EAR file
Assembling a Web services-enabled WAR file from a WSDL file