I've just installed the demo version of this but fail to connect to the default queue manager. The error in the logs shows me that configuration is not correct for the mq dlls
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: Error: MQJE001: Completion Code '2', Reason '2495'.
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: getCause()=com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
I've tried everything I can to set the path and java.library.path correctly but it all fails. They appear in the visual edit logs as being set but it makes no difference to the outcome.
Visual edit log also tells me that it should have the mq jars in its install directory:
C:\Capitalware\MQVE3\com.ibm.mq.commonservices.jar;
but these are not there and are nowhere to be seen. So, I'm mystified as to what version of the client it's using and therefore what help I can give it. I'm wondering if it's using a different version of the client from the one I have installed and so the dll and mq java lib have a mismatch? Or, if it's using the client I have installed then how is it finding it - because it's not in the paths that I've got in the visual edit logs !
Any thoughts anyone? What can I do to investigate further?
thank you !
Background: There are 2 ways an MQ client application can connect to a queue manager:
(1) Bindings mode means that the MQ client application is connecting to a local (i.e. on the same server) queue manager
(2) Client mode means that the MQ client application will connect to a remote queue manager by specifying the hostname/IP address, port # and channel name
CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
This error mean that you are trying to connect to a local queue manager (in bindings mode) but there is no local queue manager. MQ client library uses the 'mqjbnd64' DLL to handle the connection to the local queue manager. But clearly, the queue manager is remote to where MQ Visual Edit is running.
Go back to the Queue Manager Access Profile, click on the Remote icon, then fill in the channel name, hostname/IP address and port # of the remote queue manager, save the information then you should be able to the remote queue manager.
Related
I am trying to create the Client Channel Definition Table using IBM MQ Explorer 7.5.0.2. I have found several articles here which go through the steps of creating the options using the graphical UI in MQ Explorer but when I click 'Finish' nothing is created in the qmgrs folder. i.e. I run MQ Explorer as an Administrator and I have created a Channel definition and then a new Client Connection which I can see in the list of Client Connections but when I click on OK in the dialogue with the options, nothing is created in the Qmgrs folder.
Am I missing a step somewhere?
I found the files. The problem is that all the documentation I read says that the qmgrs directory is created in the application directory for MQ (where it was installed). This is not correct. It is created in the MQ data folder which can be different. Whoever first installed our MQ environment set this to a different location. Easy when you find the problem!
Thanks to everyone for their help.
I am testing a deployment of MQ 9.0.1 using Docker, and trying to administer this instance using the Web console. However I am receiving a warning when attaching widgets stating the "Queue manager unavailable".
Warning messages
In the console I can see my Queues are running and have created local queues and can run commands against them.
Also if I try to modify the Queue security records I get another error:
Failed to get authority recordsWMQWB0003E: The request could not be completed due to an internal web application server error.
Any thoughts or suggestions around this issue?
There is no definitive fix for MQ9.0.1 but upgrading to use MQ9.0.2 will resolve issues with hosting MQ Console on linux.
I have been using WebSphere MQ lately to send message from local machine to the WebSphere MQ present on same (local) machine. Which works fine as expected.
I dont know how to install WebSphere MQ in other/remote Machine so that I can send message form my local machine to that remote machine.
Thanks,
There are a number of ways to do this but the most likely is that you will need to install an Websphere MQ Client onto the remote machine. I am not sure what version you want to use but the WMQ 7.5 client is available here MQC75 You can google for other versions by changing the number (MQC7, MQC71, MQC8 etc).
You haven't said what language your application is written in, if it is Java then the WMQ Client provides everything you need, if it is C/C++ or .NET then the page I linked to has more information about what you need for these languages.
I've got a question with the MQ client configuration file mqclient.ini.
If i have one MQ JAVA application which put msg to queue of remote MQ server in another box through TCP， does that java application search mqclient.ini locally when connectting to MQ Server? Or will it even go find that mqclient.ini file in remote MQ Server? since there is one default such file under MQ sever data directory, like /var/mqm
thanks in advance
MQ Client libraries use the mqclient.ini file located on the local server. They don't use the one on the remote server. The mqclient.ini file on the remote server will be used by MQ applications running on there.
I am trying file transfer between two windows servers connected over network in the same domain. I have successfully connected with remote agent through Explorer but when try to browse the destination directory in remote system I find it is not enabled. I do not see any specific error in agent logs.
I do not see any specific error in MQ or Agent logs as I am actually not able to do anything.
Is this because the user I use does not have write access in the remote server. If that is the case How can I make sure the user has write access in the remote server?. The user I use has write access on remote server on direct login. Please find attached screenshot.
When I run in command mode I get 2087 reason code
C:\>fteCreateTransfer -sa AGENT1 -sm hubQM -da AGENT3 -dm hubQ
M -w -dd "D:\MQFTE\Destination" "D:\MQFTE\Source\sample.txt"
5724-H72 Copyright IBM Corp. 2008, 2012. ALL RIGHTS RESERVED
BFGCL0003E: A messaging problem prevented the command from completing successful
ly, for queue SYSTEM.FTE.COMMAND.AGENT1 on queue manager hubQM. The WebSphere MQ
completion code was 2, and the reason code was 2087.
The 2087 means MQRC_UNKNOWN_REMOTE_Q_MGR. This indicates that the QMgr that your WMQ Explorer is connected to cannot resolve the QMgr where the remote agent is connected. You'll need to look at your FTE Command QMgr to make sure it has a path to the QMgr where the remote agent lives.