Now that you have generated your application artifacts,
you need to assemble these artifacts to create an enterprise archive
(EAR) file that is used in the Web services application.
Before you begin
You can assemble Java-based Web services modules with assembly tools provided
with WebSphere Application Server.
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.
About this task
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 WebSphere Application Server Toolkit" in the Application
Server Toolkit documentation.
- If you have not done so already, configure
the assembly tool to work on J2EE modules. You 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 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,
you need to configure
the client deployment descriptor bindings so that the client
can communicate with a Web service that is deployed on a server.