Connection differences

The way you program for WebSphere MQ classes for Java has some dependencies on the connection modes you want to use.

Client connections

When WebSphere MQ classes for Java is used as a client, it is similar to the WebSphere(R) MQ C client, but has the following differences:

When used in client mode, WebSphere MQ classes for Java does not support the MQBEGIN call or fast path bindings.

For general information on WebSphere MQ clients, see the WebSphere MQ Clients book.

Bindings mode

The bindings mode of WebSphere MQ classes for Java differs from the client modes in the following ways:

Note:
WebSphere MQ for iSeries and WebSphere MQ for z/OS do not support the use of MQBEGIN to initiate global units of work that are coordinated by the queue manager.

Defining which connection to use

The connection is determined by the setting of variables in the MQEnvironment class.

MQEnvironment.properties
This can contain the following key/value pairs:
MQEnvironment.hostname
Set the value of this variable follows: