Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services > Assembling web services applications > Assembling web services-enabled clients
Assembling a web services-enabled client WAR file into an EAR file
Now that we have generated the application artifacts, you need to assemble these artifacts to create an enterprise archive (EAR) file used in the web services application.
We can assemble Java-based web services modules with assembly tools provided with WAS.
Restriction: Do not include a pound sign (#) in the name of files that are packaged within an application archive. Due to internal processing, the application server fails to correctly deploy the application when a pound sign is included in a file name within the application archive. When this failure occurs, an exception might occur when the application is being processed. Also, parts of the application might be missing after the application is deployed. To address this issue, rename any file names within the application archive so that they do not contain a pound sign.
Assemble the client code and artifacts that enable the application client to access a web service with steps provided:
Procedure
- Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.
- If we have not done so already, configure the assembly tool so that it works on Java EE modules. You need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.
- Migrate WAR files created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool.
To migrate files, import your WAR files to an assembly tool. Read about importing WAR files using an assembly tool in the Rational Application Developer documentation.
Results
You have assembled the artifacts required to enable the client application for web services into an EAR file.
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
For Java API for XML-Based Web Services (JAX-WS) applications, you are ready to deploy the web services client application.
For Java API for XML-based RPC (JAX-RPC) applications, configure the client deployment descriptor bindings with an assembly tool so that the client can communicate with a web service that is deployed on a server.
Web services
Assembly tools
Test web services-enabled clients
Task overview: Implementing web services applications
Implement static JAX-WS web services clients
Implement JAX-RPC web services clients
Deploy web services client applications
Configure the JAX-RPC web services client deployment descriptor with an assembly tool
Related
Artifacts used to develop web services
wsimport command for JAX-WS applications
WSDL2Java command for JAX-RPC applications