This section will describe how to create a Transport to
access a Java Message Service (JMS) based target queue
implemented by any of the following JMS Servers:
- IBM WebSphere Application Server (WAS) 6.0 or
later.
- WebSphere - SIB (SIB is WebSphere Service Integration Bus)
- WebSphere - SIB Direct
- BM WebSphere MQ 6.x or later
- SAP NetWeaver Application Server 7.1 or later. The SAP NetWeaver JMS transport is available with a Limited Release status. For more information on the release status of enterprise transports, see Enterprise transports Feature Matrix.
The JMS transport provides the mechanism to put a JMS text message (ASCII, XML or FreeForm) or Map message payload on a queue destination.
The following is assumed for a Websphere - SIB Direct transport:
- The WebSphere Application Server administrator has created a Service Integration Bus (SIB) and one or more SIB queues.
The following is assumed for a WebSphere - SIB transport or SAP NetWeaver transport:
- The Application Server administrator has created a JMS Queue Connection Factory, a JMS queue for requests, and optionally a JMS queue for replies.
- The Application Server administrator has registered the Queue Connection Factory and the queue in the WebSphere Application Server JNDI namespace and has given you those registration names.
- The computer which hosts the JMS Server has a valid hostname that is resolvable by a DNS server.
- The node is configured to access a valid DNS server for resolving host names. For some products, the DNS server is defined using the node's operating system tools. For other products, the DNS server is defined using the System Administration > Network Configuration tab.
What's Inside