Installing and configuring the Thin Client for JMS with WebSphere Application Server

To use the Thin Client for JMS with WebSphere® Application Server copy the com.ibm.ws.sib.client.thin.jms_8.5.0.jar and any other required files from the application server or application client %WAS_HOME%/runtimes directory.

About this task

The Thin Client for JMS with WebSphere Application Server can be used for default messaging provider messaging engines for WebSphere Application Server Version 6.0.2 or later. The connection to the messaging engine can be either TCP or SSL. HTTP connectivity is not supported.

Installation and configuration of the client in an OSGi environment is different and described in Installing and configuring the Thin Client for JMS with WebSphere Application Server in an OSGi environment.

You can install the client in any location and run it in any supported Java™ 2 Platform Standard Edition 1.5.0 (also known as 5.0) or newer Java Runtime Environment (JRE). The client supports the following JREs:
  • IBM® JRE 1.5.0 and newer
  • Sun JRE 1.5.0 and newer
  • HP-UX JRE 1.5.0 and newer
  • Lotus Expeditor Version 6.1 or newer with J2SE 5.0 or newer Device Runtime Environment. jclDesktop and jclDevice profiles are not supported.

The client does not require any further configuration after installation, apart from adding the jar file or files to the classpaths for your client application. You can choose either to create JMS connection factories programmatically, or use the Java Naming and Directory Interface (JNDI). If required, you can use secure connections by configuring Secure Sockets Layer (SSL) settings.

Procedure

  1. Install the client in the required location.
    The client is always installed in the /runtimes directory of a WebSphere Application Server installation, and might optionally be installed by the Application Client for WebSphere Application Server, which is a separate WebSphere Application Server deliverable. The client is shipped as three files:
    • com.ibm.ws.sib.client.thin.jms_8.5.0.jar - the regular JMS Client.
    • com.ibm.ws.sib.client_ExpeditorDRE_8.5.0.jar - the JMS Client packaged for Lotus Expeditor.
    • sibc.nls.zip - language-specific resource bundles. You can extract any combination of these files. The client jar already includes US English, so you only need the additional language files from sibc.nls.zip if you require languages other than non-US English.
  2. Include the appropriate jar file or files in the classpaths for your client application:
    1. To compile JMS code, include the client jar file in the CLASSPATH setting for the javac command.
    2. To run JMS code, include the client jar file and any required optional language files extracted from sibx.nls.zip in the CLASSPATH setting for the java command.
  3. Configure the required JMS resources.
  4. If you require secure connections, configure SSL.