Assembling a Web services-enabled client WAR file into an EAR file

Assembling a Web services-enabled client WAR file into an EAR file

Now that you have generated deployment descriptors, located the Web Services Description Language (WSDL) file that was used to develop the Web services client, and generated the necessary classes for the client module, assemble these artifacts to create an enterprise archive (EAR) file that is used in the Web services application.
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:

Assembled client WAR module that contains the implementation, all of the classes generated by the WSDL2Java command-line tool, and the web.xml deployment descriptor

The WSDL file that you used to develop the client.

The templates for the ibm-webservicesclient-ext.xmi and ibm-webservicesclient-bnd.xmi deployment descriptor, if used, and the Java API for XML-based remote procedure call (JAX-RPC) mapping file.

Overview

Assemble the client code and artifacts that enable the application client to access a Web service with steps provided:

Procedure

Start an assembly tool. See "Starting WAS Toolkit" in the Application Server Toolkit documentation.

If you have not done so already, configure the assembly tool to work on J2EE modules. We need to make sure that the J2EE and Web categories are enabled. See "Configuring WebSphere Application Server 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 an assembly tool. See "Importing Web archive (WAR) files" in the Application Server Toolkit documentation.

Results
You have the artifacts required to enable the client module to use Web services are added to the module.

Example
This example of the assembly process uses the AddressBookWeb.war WAR file and the AddressBook.ear EAR file:
WEB-INF/MANIFEST.MF WEB-INF/web.xml WEB-INF/wsdl/AddressBook.wsdl WEB-INF/AddressBook_mapping.xml WEB-INF/ibm-webservicesclient-ext.xmi (optional) WEB-INF/ibm-webservicesclient-bnd.xmi  com/ibm/websphere/samples/webservices/addr/Address.class com/ibm/websphere/samples/webservices/addr/AddressBook.class com/ibm/websphere/samples/webservices/addr/AddressBookClient.class com/ibm/websphere/samples/webservices/addr/AddressBookService.class
...other generated classes...
After assembling the AddressBookWeb.war file into the AddressBook.ear file, the AddressBook.ear file contains the following files:
META-INF/MANIFEST.MF 
AddressBookWeb.war
META-INF/application.xml
What to do next
Configure the client deployment descriptor . Now that you have assembled the client module, configure the bindings so that the client can communicate with a Web service that is deployed on a server.

Web services

Related tasks

Testing Web services-enabled clients
Task overview: Implementing Web services applications
Developing and deploying Web services clients

Related Reference

Artifacts used to develop Web services