All geek questions in one place

Standalone Java JMS client for WebSphere MQ

Can I use only WebSphere jar files with standard JMS to send messages to the WebSphere MQ server, or do I need to download their WebSphere MQ client?

+6
source share
4 answers

You can only use jar files for JMS and the native Java MQ API, but the question is whether you really want it. A full client installation includes sample programs in the form of a source and an object, utilities, tracing, etc. When you open a ticket for problems with IBM, they may request information that you will use to collect these tools. If you do not have a complete installation, you will not be able to provide the requested diagnostic information. For this reason, IBM supports full client installation. If you are just trying to learn JMS and write a toy application, this is probably good. If the application is in Production, and you can get it someday, install the client.

WMQ client installation is free and available as SupportPac MQC7 . Development on the V7 client is good, as it is compatible with V6 QMgr. This will save you some testing when the V6 crashes in September 2012.

Note that the JMS thin client mentioned in another answer is described in Infocenter as a “JMS client integration JMS client designed to run as an embedded client in Java SE applications in IBM®, Sun, and HP Java (JRE) runtime environments. The client does not support transactional and local transaction models. " As already noted, this is a SI Bus client, not an MQ client, has limited platform support and does not even have single-phase commit. The actual WMQ client is specific to WebSphere MQ, has broad platform support, and provides a single-phase transactional transaction.

UPDATE:
As of April 24, 2012, an extended transaction client fee is no longer charged for any version of WMQ on any platform. I deleted the part of the answer explaining the previous license terms.

+5
source

You need the appropriate banks to create what is called the JMS thin client . This will allow you to use standard JMS to communicate with MQ. You do not need one of the specific clients if you do not want to access a specific MQ API instead of JMS.

+2
source

I have seen application teams do this in countless cases.

Almost every time they encounter a problem at some point down the line and then request support / help from local support. Diagnosing a problem in an environment in which none of the standard mq / logging / tracing tools are practically impossible. You can’t even find out which version of MQ (dspmqver)

Different banks from different plants are mixed, sent by e-mail, etc.

I will never understand why people simply do not install a client and do not. Is it a big deal to lose as many hundreds of mega as the setup?

+2
source

To send or manage a Websphere MQ message, you can use a jms client, for example, HermesJMS +, mq series libraries, check it: http://www.hermesjms.com/confluence/display/HJMS/WebSphereMQ

Check out the demo: http://www.hermesjms.com/demos/demo_mq.html

+1
source

Source: https://habr.com/ru/post/890080/

More articles:


All Articles