WAS v8.5 > Deploy applications > Deploy web servicesTest web services-enabled clients
Before testing a web services Java client, verify the server endpoint specified in the client Web Services Description Language (WSDL) file is running and available.
Tests are run differently depending on whether the client module is in a Java EE container or if the client is running in the Thin Client for JAX-RPC with WAS application environment or the Thin Client for JAX-WS with WAS application environment.
- Test an unmanaged client JAR file by running the application with the java command.
For JAX-WS applications:
"%JAVA_HOME%\bin\java" -Djava.endorsed.dirs=<your_jax-ws_thin_client_install_directory>/endorsed_apis_8.5.0.jar -classpath "<your_JAX-WS_thin_client_install_directory>\runtimes\com.ibm.jaxws.thinclient_8.5.0.jar; <list_of_your_application_jars_and_classes>" <fully_qualified_class_name_to_run> <your_application_parameters>For JAX-RPC applications:
"%JAVA_HOME%\bin\java" -classpath "<your_JAX-RPC_thin_client_install_directory>\runtimes\com.ibm.ws.webservices.thinclient_8.5.0.jar; <list_of_your_application_jars_and_classes>" <fully_qualified_class_name_to_run> <your_application_parameters>For JAX-WS applications:
"$JAVA_HOME/bin/java" -Djava.endorsed.dirs=<your_jax-ws_thin_client_install_directory>/endorsed_apis_8.5.0.jar -classpath "<your_JAX-WS_thin_client_install_directory>/runtimes/com.ibm.jaxws.thinclient_8.5.0.jar: <list_of_your_application_jars_and_classes>" <fully_qualified_class_name_to_run> <your_application_parameters>For JAX-RPC applications:
"$JAVA_HOME/bin/java" -classpath "<your_JAX-RPC_thin_client_install_directory>/runtimes/com.ibm.ws.webservices.thinclient_8.5.0.jar: <list_of_your_application_jars_and_classes>" <fully_qualified_class_name_to_run> <your_application_parameters>The unmanaged client application runs.
- Test a managed JAX-RPC client EAR file or an unmanaged JAX-WS client EAR file.
- Run your client application with the launchClient command. The following example illustrates the use of this command:
launchClient clientEar
Results
You have a web services-enabled client that is tested. Now we can add security measures to the web service. Security measures are optional.
Related concepts:
Secure web services
Programming models for web services message-level security
Related
Secure web services applications using the WSS APIs at the message level
Set up a development environment for web services
Implement static JAX-WS web services clients
Implement JAX-RPC web services clients
Troubleshooting web services