Before installing, configuring, and using the adapter, you must understand its environmental requirements:
The adapter framework that an adapter uses must be compatible with the version of the integration broker (or brokers) with which the adapter is communicating. The 2.6 version of the adapter for JMS is supported on the following adapter framework and integration brokers:
See the Release Notes for any exceptions.
The adapter is written to the JMS 1.0.2 standard. Support for other versions of the standard has not been verified although there are currently no known issues that would preclude this.
The adapter supports both the point-to-point (PTP) messaging and publish-and-subscribe (Pub/Sub) messaging interfaces defined by the JMS standard; these styles are also commonly referred to as queue-based and topic-based messaging, respectively. A single instance of the adapter supports only one messaging style at a time (i.e. topics and queues cannot be mixed in the configuration); however, both messaging styles can be supported by running multiple instances of the adapter in parallel with instances configured for either PTP or Pub/Sub.
The adapter is supported on the following platforms:
The adapter does not use or depend upon any database. All client libraries required by the JMS provider and the JNDI provider must be included in the adapter classpath. These libraries differ by provider.
The connector has been internationalized so that it can support double-byte character sets, and deliver message text in the specified language. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserves the meaning of the data.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encoding for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.
To log error and informational messages in the appropriate language and for the appropriate country or territory, configure the Locale standard configuration property for your environment. For more information on configuration properties, see Appendix A, Standard configuration properties for connectors.