+

Search Tips   |   Advanced Search

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


Configure JAX-RPC Web services client deployment descriptor with an assembly tool.

Configure deployment descriptors with assembly tools provided with WAS. Also, we need an enterprise Java Beans(EJB) JAR file, WAR file or an application client file that we 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.

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

 

  1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.

  2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. we 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.

  3. Migrate the WAR or JAR files that are created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to assembly tools.

    To migrate files, import the WAR or JAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer documentation.

  4. Set the client deployment descriptor. Read about the configuring the client deployment descriptor in the Rational Application Developer documentation.

 

Results

we have a client deployment descriptor configured.

 

Next steps

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


Assembly tools

 

Related tasks


Implementing JAX-RPC Web services clients
Assembling a Web services-enabled client JAR file into an EAR file
Assembling a Web services-enabled client WAR file into an EAR file