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.
You must configure the assembly tool before you can use
it.
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.
The Eclipse assembly tools provide a graphical interface for
developing code artifacts, assembling the code artifacts into various
archives or modules and configuring related J2EE Version 1.2, 1.3
or 1.4 compliant deployment descriptors.
- If you have not done so already,
configure the assembly tool for work on J2EE modules. Ensure
that J2EE and Web capabilities are enabled.
- Click File > Import to
import the WAR file into the assembly tool.
- Open the J2EE perspective by clicking
Windows >Open Perspective > Other >J2EE.
- Switch to the Navigator pane
by clicking the Navigator tab.
- Locate the project for the file
that you just imported in the Navigator pane.
- Expand the webContent entry
so the WEB-INF directory is displayed. Expand the WEB-INF directory.
- Right-click the WEB-INF directory
and click New > Folder. Create a subfolder named wsdl in
the WEB-INF directory.
- Copy the WSDL file to the WEB-INF\wsdl directory
by right-clicking the wsdl directory and click Import > File
system. Browse the WSDL file for this Web service and click Finish.
- Copy the web.xml file. If the WAR
module already contains a web.xml file, manually merge the <service-ref>
elements in the web.xml file with the original web.xml file
that is generated by the WSDL2Java command.
- Copy the JAX-RPC mapping file in the WEB-INF subdirectory
in the same manner in which you copied the WSDL file. The
JAX-RPC mapping file is indicated by the element in the web.xml file.
- (Optional) Place the ibm-webservicesclient-ext.xmi file
and the ibm-webservicesclient-bnd.xmi file in the WEB-INF subdirectory,
if used. If these files are already contained in the WAR
module, manually merge the ibm-webservicesclient-ext.xmi and
the ibm-webservicesclient-bnd.xmi files that are generated
by the WSDL2Java command with the existing files.
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
Configure the client deployment
descriptor . Now that you have assembled the client module,
you need to configure the bindings so that the client can communicate
with a Web service that is deployed on a server.