WebSphere MQ using JMS

I have an application that uses the WebSphere MQ Java API along with a configuration file (xml) to access MQ. I would like to migrate to the WebSphere JMS API. To do this, I try to create 1) WebSphere MQ Queue Connection factory and 2) WebSphere MQ Queue Assignment from my local WAS. When I configure the addresses of my queues and try to set the MQ Config parameters, I get an error message like "WMSG0316E: you tried to view a queue that was not a local queue. Only local queue administration is supported."

The message is correct in the sense that I am trying to connect to a remote queue. Now, can I configure my WAS as an MQ client trying to connect to a remote queue? The MQ client has the necessary MQ JMS banks in the path to the server classes.

It would be nice if anyone could shed light on this.

+3
source share
3 answers

I am working on the same problem - I found articles in which the authors confirm that WebSphere should say that the client in remote queue mode is desirable, but I still have to find detailed information on how to do this, except that one author mentions an environment variable.

... , .

+4

Google. here IBM . , ?

, ? , WebSphere, , ? , , -, , .

UPDATE: , , , - , , , .

+1

- . , "" factory WAS. , ?

, , , JNDI. - , JMS , - MQ. JMS, .

+1

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


All Articles