Transport Type - BINDINGS or CLIENT

 

This setting determines the method the MQ JMS classes use to communicate with the queue manager.

JMS Provider:	WebSphere MQ JMS
Component:	QCF or TCF
Applies to specific messaging topologies:	Yes
Requires specific usage of JMS in application:	No
Location of setting:	Resources | WebSphere MQ JMS Provider | WebSphere MQ Queue Connection Factories | Your_QCF | Transport Type

If the queue manager is running on the same physical machine as the WAS then it is possible to set the transport type to BINDINGS. If the queue manager is on a remote machine then CLIENT has to be used. This could also affect whether transaction support is provided to MQ. To enable XA support the queue manager must either be accessed using BINDINGS (and therefore local) or accessed using CLIENT and the specific XA enabled MQ client must be installed on the appserver machine.

Using the BINDINGS transport type removes some of the overhead of remote access and is generally faster as it does not have to perform as many actions to access the queue manager.

 Prev | Next

 

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.