DIRECT or QUEUED transport type for TCF
There is an option to change the communication type when setting up access to a publish/subscribe broker. For the Embedded JMS server and a subset of the WebSphere Business Integration products, it is possible to set the transport to DIRECT.
Component: TCF Applies to specific messaging topologies: Yes Requires specific usage of JMS in application: Yes Location of setting: Resources | MQ JMS Provider | MQ Topic Connection Factories | Your_TCF | Transport Type Resources | WebSphere JMS Provider | WebSphere MQ Topic Connection Factories | Your_TCF | Port
The WebSphere MQ Real-Time transport (DIRECT) is a protocol which allows client applications to communicate directly with the broker via TCP/IP instead of via intermediate queues. This direct communication and the small overhead of the TCP/IP flows used by the Real-Time Transport, offers potentially higher levels of performance than communicating via message queues.
The DIRECT transport only supports non-durable subscriptions, with non-transactional and non-persistent messaging.
For the embedded messaging there are no other configuration settings needed to change the transport type other than on the TCF.
If you are using WebSphere Business Integration Event Broker or Message Broker version 5 then there is more setup needed and more configuration options available. This is covered in chapter 19 of the redbook Migration to WebSphere Business Integration Message Broker V5, SG24-6995.
DIRECT cannot be used with MDBs running in the message listener service. This is because the DIRECT method of communication does not support the Application Server Facilities (ASF) used by the message listener service. ASF is used to provide concurrency and transactional support.
It is possible to make the message listener service run in a Non-ASF fashion. It would be possible to use MDBs and the DIRECT communication method with non-durable, non-persistent, non-transactional MDBs and the non-ASF support in the message listener service. Information about the non-ASF support can be found in the WebSphere InfoCenter. There are further restrictions in functionality if the message listener service is used in non-ASF mode, not least that it affects the whole message listener service for one appserver, not just one listener port.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.