Running an unmanaged Web services JAX-RPC client

WebSphere Application Server V6.1 and the Application Client for WebSphere Application Server V6.1 provides an unmanaged client implementation that is based on the Java API for XML-based RPC (JAX-RPC) 1.1 specification. The Thin Client for JAX-RPC with WebSphere Application Server is an unmanaged and stand-alone Java client environment that allows you to run JAX-RPC Web services client applications to invoke Web services that are hosted by the application server.

Before you can set up a JAX-RPC unmanaged client execution environment you will need to obtain the Thin Client for JAX-RPC jar file. To obtain the Thin Client for JAX-RPC, either Install WebSphere Application Server or Install Application Client for WebSphere Application Server.

The Thin Client for JAX-RPC jar file, com.ibm.ws.webservices.thinclient_6.1.0.jar, is located in the app_server_root\runtimes directory. Refer to the license agreements to ensure correct usage and for limitations on copies of the Thin Client for JAX-RPC outside of the WebSphere environment. The Thin Client for JAX-RPC runs on distributed operating systems with IBM Software Development Kits (SDKs) V1.5 and Sun Java Development Kit (JDK) V1.5 that are packaged by IBM. The Thin Client for JAX-RPC is supported on non-IBM SDKs V1.5 with these limitations:

• Secure Sockets Layer (SSL) limitation on non-IBM SDKs

  The Thin Client for JAX-RPC has a dependency on the IBM Java Secure Socket Extension (JSSE2) provider. The Sun JDK prevents a vendor-acquired JSSE provider from being plugged in, which causes SSL not to be supported with the Sun JDK or other non-IBM SDKs.

• Xerces limitation on non-IBM SDKs

  If you are using a non-IBM SDK, because of dependencies with the Xerces implementation, you will need to download Xerces-J version 2.6.2 and set it in the classpath before attempting to run the Thin Client for JAX-RPC.

Overview

Procedure

1. Configure the path. You can add the Java bin directories to your path by typing:

2. Configure the classpath.

   • If you are using an SDK or JDK that is provided by IBM, you can add the thin client jar file to the classpath definition.

     export CLASSPATH=.:<your_web_services_thin_client_install_directory>/com.ibm.ws.webservices.thinclient_6.1.0.jar:<your_application_jars>;$CLASSPATH

   • If you are using a non-IBM SDK, first obtain a Xerces xml-apis.jar and xercesImpl.jar from the Xerces Web site and then configure the classpath definition.

     export CLASSPATH=.:<your_Xerces_install_directory>/xml-apis.jar:<your_Xerces_install_directory>\xercesImpl.jar:$CLASSPATH

3. Run your client application using the following Java command.

   $JAVA_HOME/bin/java <your_client_application>

Results

Related Reference

Related information