A significantly reduced footprint JMS Client that allows a JMS application running in a J2SE environment to connect to an IBM WebSphere Application Server service integration bus.
The IBM Client for Java™ Message Service (JMS) on Java 2, Standard Edition (J2SE) with WebSphere Application Server is an embeddable technology that provides JMS V1.1 connections to a service integration bus messaging engine in WebSphere Application Server V6.0.2 (or above) or any IBM product that incorporates the service integration bus. The connection to the service integration bus messaging engine can be either TCP or SSL. HTTP connectivity is not supported.
The functionality provided by the IBM Client for JMS on J2SE with IBM WebSphere Application Server is now superseded by the stand-alone thin clients supplied in the runtimes directory of a WebSphere Application Server Version 7.0 installation. See the Migration to the Thin Client for JMS with WebSphere Application Server topic of the WebSphere Application Server Version 7.0 information center for further information.
You can install the client in any location.
The client supports the following Java Runtime Environments (JREs):
IBM JRE 1.4.2 and 1.5.0
Sun JRE 1.4.2 and 1.5.0
- March 2009
- Fix for PK76300 Cannot establish JMS connections in an OSGi environment with boot delegation disabled
- March 2008:
- Fix for PK56272 An application may periodically delay for periods of time while sending messages
- Fix for PK56464 ArrayIndexOutOfBoundsException from SocketIOBaseRequestContext.run()
- Fix for PK58698 Custom property to configure the TCP connect timeout
- Added OEM re-distributable downloadable file
- October 2007:
- Fix for PK54957 NullPointerException from SibTr.getMEName() when trace is enabled.
- July 2007:
- Fix for PK48875 Client creates multiple connections when redirected from bootstrap server
- November 2006:
- Fix for PK34488 iSeries ClassNotFoundException
- Limited Support for WebSphere Application Server V5.1
- August 2006:
- Initial release
WebSphere Application Server V6.0.2 (or above) or any IBM product that incorporates the service integration bus is required.
See the Getting Started guide to select the correct dowloadable file.
The download installation file supports multiple install options. To perform an install of the client enter:
- -text install using a command-line interface
- -silent install using silent license acceptance
- -xpd install Lotus Expeditor v6.1 Device Runtime Environment J2SE 5.0 ready executables
- The install option, one of jms, jms_jndi_ibm, jms_jndi_sun, nls (see below)
- The installation directory.
The following install options are available:
- jms - JMS only
Choose this option if you require JMS v1.1 function only. All connection factories must be programmatically created, since no Java Naming and Directory Interface (JNDI) function is available. This option has the smallest installed footprint.
- jms_jndi_ibm - JMS + JNDI for IBM JREs
Choose this option if you require JMS v1.1 with basic JNDI function to run under an IBM JRE.
- jms_jndi_sun - JMS + JNDI for Sun JREs
Choose this option if you require JMS v1.1 with basic JNDI function to run under a Sun JRE.
- nls - optional National Language Support (NLS) files
Choose this option if you require support for languages other than English.
For example, to install JMS + JNDI for IBM JREs into c:\jms use:
|Getting Started||US English||81499|
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options
What is DD?
|JMS Client||3/10/2009||US English||3443428||FTP DD|
|JMS Client (OEM)||3/10/2009||US English||3447895||FTP DD|
|Application Servers||Runtimes for Java Technology||Java SDK|
|Application Servers||WebSphere Application Server for z/OS||z/OS||6.0|