Test the Web services-enabled client application

Before testing your Java client, confirm that the server endpoint specified in the client WSDL file is running and available.

The following steps and examples assume that you are testing a system that has WAS installed, and that the WAS_HOME environment variable is set in the WAS installation directory.

Tests are run differently depending on whether the client module has client container deployment information, which consists of the application-client.xml and webservicesclient.xml files, as well as the JAX-RPC mapping file and WSDL file. The client enterprise archive (EAR) files discussed in this topic are referred to as managed because they contain the deployment information. The client Java archive (JAR) files discussed are referred to as unmanaged because they that do not contain the deployment information.

To test Web services-enabled clients, follow these steps:

1. Test an unmanaged client JAR file.

   1. Set your CLASSPATH when you Set up a Web services development environment.
   2. Add your client JAR file to CLASSPATH.
   3. Run your application with the java command.

2. Test a managed client EAR file.
   Run your client application with the launchClient command. For example, if the client application is named clientEar, run this command:

   launchClient clientEar