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.
Related
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.
I have installed a IBM MQ Developer version on a server, and I need to configure Rest requests, to be more specific it must be able to put message in the queue using a Rest request.
Unfortunately I didn't find any good source of information about this...
You need to run the MQ web server. Use the command strmqweb.
See https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q127860_.html
Does Open Liberty support network deployment?
Are we able to buy IBM Support for Open Liberty? and How?
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment? e.g Having Load balancer (hardware) received request from web application and auto distribute received request to 2 or more standalone Open Liberty installed in separate VM/Machine?
Thanks
Your question is a bit vague, so I'll try my best.
Does Open Liberty support network deployment?
Depends what you mean by that support. You can install multiple Open Liberty on multiple VM/machines that will serve your applications and use LB/or IHS to route to them.
You cannot centrally manage via single console, for that you need WebSphere Liberty ND version that supports collectives.
However most recent deployments will use more 'farm' like or container orchestration approaches rather than central management via dedicated manager (as Dmgr in WAS v9).
Are we able to buy IBM Support for Open Liberty? and How?
Yes you can. See Get IBM or Red Hat support for Open Liberty page for general info and contact IBM sales representative for best option for your needs.
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment?
Depends on your application and non-functional requirements. You can setup LB or IHS with plugin (for more intelligent balancing) to route requests to multiple VM/machines with Open Liberty.
Check for example this Configuring IBM HTTP Server for Liberty and here Open Liberty Plugin Configuration. Few manual steps will be needed to edit generated config file to support many servers.
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 am designing a new file transfer infrastructure using WebSphere MQ v7.5 FTE product and like to know for creating an FTE agent in a Windows box, what is the basic minimum requirement? Does it require the MQ v7.5 server edition installed or will it work with the MQ v7.5 client libraries?
You need at least one WMQ queue manager to act as the queuing hub for all the agents. The regular FTE agents can be client-based. Typically, these are placed local to the file endpoints and access the underlying filesystem directly. For most agents a client connection to a central queue manager works great. The exception is a node where the transfer volume is very high, in which case it might warrant having a local queue manager.
The exception is the "Protocol Bridge" agents which are the ones that talk to remote FTP, SFTP and FTPS servers. These must reside on the same host as the queue manager.
Short answer: on your Windows box a client agent is the minimal requirement. Just point its configuration to a queue manager somewhere on the network.