Configuring the JAX-RPC Web services client deployment descriptor with an assembly tool

You can configure JAX-RPC Web services client deployment descriptor with an assembly tool.

Before you begin

You can configure deployment descriptors with assembly tools provided with WebSphere Application Server.

Also, you need an enterprise JavaBeans (EJB) Java archive (JAR) file, Web archive (WAR) file or an application client file that you can import into the assembly tool.

Assemble the client JAR file into an EAR file or assemble the client WAR file into an EAR file.

About this task

Complete this task if you are developing a managed client that runs in the J2EE client container. This task is done after you assemble the EJB or Web module.

Configure the client deployment descriptor with an assembly tool by following the steps provided:

Procedure

  1. Start an assembly tool. The Eclipse assembly tools, Application Server Toolkit and assembly tools , provide a graphical interface for developing code artifacts, assembling the code artifacts into various archives (modules) and configuring related Java 2 Platform, Enterprise Edition (J2EE) Version 1.2, 1.3 or 1.4 compliant deployment descriptors.
  2. Click File > Import to import the EJB JAR file, WAR file or application client file into the assembly tool.
  3. Open the J2EE perspective by clicking Windows >Open Perspective >J2EE.
  4. Switch to the Navigator pane by clicking the Navigator tab.
  5. Locate the project containing the client file in the Navigator pane.
  6. Expand the directories under the project until the META-INF or WEB-INF directory and its contents appear.
  7. Right-click the client deployment descriptor file. The client deployment descriptor information is located in the web.xml file for web clients; the ejb-jar.xml file for EJB clients; or in the application-client.xml file for application clients.
  8. Select Open. The Deployment Descriptor editor is opened.

    You can also use the Project Explorer to open the Deployment Descriptor editor. The alternative step is to double-click on the Deployment Descriptor list item for the module and open the Deployment Descriptor editor.

  9. Click the References tab at the bottom of the editor window.
  10. Select the service_reference that you want to configure.
  11. Type the name that the Java Naming Directory Interface (JNDI) uses to locate the service in the Name field. The JNDI lookup string for this service is java:comp/env/service-ref-name. By convention, the service reference name always begins with service/.
  12. Type the name of the service that the client accesses in the Description field.
  13. Type the class name, including package, of the Java interface that is the service interface for this Web service in the Service interface name field.
  14. Type the Web Services Description Language (WSDL) file name used by the client, relative to the root of the module, in the WSDL file field.
  15. Type the file name of the Java mapping file, relative to the root of the module, in the JAX RPC mapping file field.
  16. Click ctrl-s to save the changes.

Results

You have a client deployment descriptor that is configured.

What to do next

Test the Web services client. This task explains how to test an unmanaged client Java archive (JAR) file and an unmanaged client application.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=twbs_atkclientdd
File name: twbs_atkclientdd.html