Before you begin
Before testing your Java client, confirm that the server endpoint specified in the client Web Services Description Language (WSDL) file is running and available.The following steps and examples assume that you are testing a system that has WebSphere Application Server installed, and that you have configured your environment as described in Setting up a Web services development and unmanaged client execution environment.
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.
Why and when to perform this task
To test Web services-enabled clients:Steps for this task
"%JAVA_HOME%\bin\java" "-Xbootclasspath/p:%WAS_BOOTCLASSPATH%" -Djava.security.auth.login.config="%WAS_HOME%\properties\wsjaas_client.conf" -Djava.ext.dirs="%WAS_EXT_DIRS%" -classpath "%WAS_CLASSPATH%;<list your application JAR files and classes>" <fully qualified class name to run><your application parameters>On UNIX:
"$JAVA_HOME/bin/java" "-Xbootclasspath/p:$WAS_BOOTCLASSPATH" -Djava.security.auth.login.config="$WAS_HOME/properties/wsjaas_client.conf" -Djava.ext.dirs="$WAS_EXT_DIRS" -classpath "$WAS_CLASSPATH;<list of your application JAR files and classes> <fully qualified class name to run><your application parameters>
launchClient clientEar
Results
Web services-enabled clients that have been tested.What to do next
Troubleshoot your Web services application.