Posted: Thu Apr 01, 2010 8:02 am Post subject: Connecting to MQ queue manager with WAS 6.1
Apprentice
Joined: 14 Jun 2002 Posts: 31 Location: Kansas City
When our WAS group upgraded to WAS 6.1 they decided to not install the MQ client and use the 'embedded messaging' or 'message engine' (not sure what it is called). Since there is no /var/mqm directories with the WAS install, I have no idea of where to find any client connection errors. Apparently neither do our WAS admins. One application that they moved to WAS 6.1 is attempting to connect to a queue manager and the connection appears to be timing out. As usual, they are unable to give me the return and reason codes from the connection attempt. I am seeing no errors on the MQ logs on the server with the MQ 7.0.0.1 queue manager that they are attempting to connect to. I am not seeing any MQ like error messages in the WAS System.Out.log for the application. Any help would be greatly appreciated.
Posted: Mon Apr 12, 2010 7:19 am Post subject: Different approch for WAS connecting to MQ
Novice
Joined: 19 Nov 2007 Posts: 11 Location: Canada
I think you application team changed to use SIB in the WAS 6.1, possibly the WAS admin need to setup the MQ link to connect to your QM, so likely it works as dummy qm on WAS 6.1 then to your QM. Check with you WAS admin to see whether that is the way the application using, hope it help. _________________ Mike
You first need to determine whether your resource is defined on the SIBUS (was embedded messaging) or as an MQ qmgr. (See JNDI for qcf/tcf).
If you are looking to the MQ_INSTALL directories etc... those are being setup/defaulted in the WAS management console under the different variables....
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum