Connection options

Programmable options allow WebSphere MQ Java to connect to WebSphere(R) MQ in either of the following ways:

Table 1

shows which of these connection modes can be used for each platform.

Table 1. Platforms and connection modes
Application platform Can an application connect in client mode? Can an application connect in bindings mode?
AIX(R) Yes Yes
HP-UX Yes Yes1
i5/OS Yes Yes
Linux(R) (POWER(TM) platform) Yes Yes
Linux (x86 platform) Yes Yes
Linux (zSeries(R) platform) Yes No2
Solaris Yes Yes
Windows(R) 2000 Yes Yes
Windows Server 2003 Yes Yes
Windows XP Yes Yes
z/OS No3 Yes
Notes:
  1. HP-UX Java(TM) bindings support is available only for HP-UXv11 systems running the POSIX draft 10 pthreaded version of WebSphere MQ.
  2. On Linux (zSeries platform), only TCP/IP client connectivity is supported.
  3. However, a WebSphere MQ JMS application running under WebSphere Application Server on z/OS can connect in client mode.

In addition, WebSphere MQ JMS publish/subscribe applications can connect directly across TCP/IP to a broker of any of the following products:

The following sections describe the client mode and bindings mode connection options in more detail.

Client connection

To use WebSphere MQ Java as a WebSphere MQ client, you can install it either on the WebSphere MQ server machine, which may also contain a Web server, or on a separate machine. If you install WebSphere MQ Java on the same machine as a Web server, you can download and run WebSphere MQ client applications on machines that do not have WebSphere MQ Java installed locally.

Bindings connection

When used in bindings mode, WebSphere MQ Java uses the Java Native Interface (JNI) to call directly into the existing queue manager API, rather than communicating through a network. In some environments, connecting in bindings mode can provide better performance for WebSphere MQ Java applications than connecting in client mode.