Programmable options allow WebSphere MQ Java to connect to WebSphere(R) MQ in either of the following ways:
shows which of these connection modes can be used for each platform.
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 |
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.
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.
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.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq77g1 |