WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging provider > Use JMS from stand-alone clients to interoperate with service integration resources > Use JMS to connect to a WAS default messaging provider messaging engine

Install and configure the Thin Client for JMS with WAS

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.

The Thin Client for JMS with WAS can be used for default messaging provider messaging engines for WAS v6.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 Install and configure the Thin Client for JMS with WAS in an OSGi environment.

We 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 above Java Runtime Environment (JRE). The client supports the following JREs:

• IBM JRE 1.5.0 and above
• Sun JRE 1.5.0 and above
• HP-UX JRE 1.5.0 and above
• Lotus Expeditor v6.1 or above with J2SE 5.0 or above 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 the client application. Choose either to create JMS connection factories programmatically, or use the JNDI. If required, we can use secure connections by configuring SSL settings.

1. Install the client in the required location. The client is always installed in the /runtimes directory of a WAS installation, and might optionally be installed by the Application Client for WAS, which is a separate WAS 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. We 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 the 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 as described in Use JMS resources with the Thin Client for JMS with WAS.

4. If you require secure connections, configure SSL as described in Secure JMS client and JMS resource adapter connections.

Subtopics

• Migration to the Thin Client for JMS with WAS
  There are a number of differences to consider when migrating to the Thin Client for JMS with WAS from an earlier version of the client.
• Install and configure the Thin Client for JMS with WAS in an OSGi environment
  Use this information to install and configure the Thin Client for JMS with WAS in an OSGi environment.

Related

Add tracing and logging for stand-alone clients
Use JMS to connect to a WAS default messaging provider messaging engine

+

Search Tips   |   Advanced Search