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.
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'm looking to setup a Queue Manager Using WebSphere MQ V7 MQ Explorer.
After Creating my Queue Manager, normally I expect that some sub directories are automatically generated under it, "Queues", "Topics", "Channels" .. as illustrated in the photo below.
In my case, no sub directories are generated, as illustrated below in the second snapshot.
PS: the status of my Queue manager is : Running but disconnected from WebSphere MQ Explorer.
When I right-click on the QMgr Name and choose Connect, I get "An unexpected error (2063) has occurred (AMQ4999)"
Could you advise please about a possible cause of this behavior ?
Administrative tools -> Local Security Policy -> Local Policies -> User Rights Assignment -> Log on as a service -> Properties -> add your user here
Same problem with MQ v9 and i solved it this way.
Go to control panel – Administrative tools
Control Panel\All Control Panel Items\Administrative Tools
Local
Inside Local Security Policy
Enter your domain user name then click check names – finalize by clicking ok. Then apply.
Now the domain user can log on as a service – Now open the services running on your machine.
Double click on the MQ service – then go on log on tab
Then apply click okay button – from the restart your machine for the changes to take effect
Finally open WebSphere MQ Explorer as admin - queue manager should be able to connect
Same issue with MQ 9.0 installed on Windows 10 EE.
(Run as Administrator) secpol.msc /s
(open) Local Policies > User Rights Assignment > Log on as a service
then add your User. Same user should be used for "IBM MQ (Installation1)" (Properties> Log On), installation default (when you do not setup the Domain Policy during installation) is MUSR_MQADMIN.
(Maybe you can try to run "MQ Explorer" as MUSR_MQADMIN user, but it's password is automatically generated during the installation. It's possible to change it, but it doesn't seem to be a safer against the using local account to run the MQ service)
I encountered a really wired problem. I have successfully install Websphere MQ on my windows machine and want to create QManager and Queue to connect to a remote Qmanager server. I have already created a QManager as you can see in the picture below. However, when I tried to create a queue for this QManager, I could not find any expand button as the IBM tutorial mentioned.
I have already tried to create a queue with MQSC but when I run runmqsc in the command prompt with administrator user, it shows AMQ8135: Not Authorized error!
Check your error logs (AMQERR01.LOG) for an explanation of why AMQ8135 was returned to the client - for security reasons clients aren't given more information and so you have to go to the logs to get the detail.
I suspect the user you're running MQ Explorer and runmqsc as isn't in the 'mqm' group, or is otherwise not authorised to connect to the queue manager.
Run your IBM MQ Explorer as administrator and it will solve most of the issues.
I have some stopped QMGRs. When I try to start them or delete them from MQ Explorer, I encounter this error:
AMQ7077: You are not authorized to perform the requested operation.
exitvalue=119
How can I change or remove the restrictions on this object?
You can start or delete a queue manager via the MQ Explorer too, so long as the queue manager and MQ Explorer are running on the same machine/installation. You must ensure that the MQ Explorer is running under an mqm user ID, just as you needed to do run the strmqm or dltmqm commands.
I figured it out that I can do this by command STRMQM 'qmName' or DLTMQM 'qmName' as an alternative to using MQ Explorer.
I am using the WebSphere 7.1. I am following the below steps :
Creating the queue manager using WebSphere MQ Explorer
Procedure:
Start WebSphere MQ Explorer.
In the Navigator view, right-click the Queue Managers folder, then
click New > Queue Manager.The Create Queue Manager wizard opens.
In the Queue Manager name field, type QM_APPLE.
Click Next twice.
Ensure that Automatic is selected from the Select type of queue
manager startup option.
Click Next.
Ensure that the Create listener configured for TCP/IP check box is
selected.
If the Finish button is not available, type another port number in
the Listen on port number field. If the current value is 1414, try
using a different port number, for example: 1415 or 1416. If the
default port number of 1414 is not used at this stage, make a note of
the port number used because you will need it in later stages of this
tutorial when QM_APPLE serves as a receiving queue manager.
Click Finish.
The Problem is, I am stuck in the Step 2. When i right Click I cannot find "NEW" option to create the Queue. Can anyone tell me Why I am not getting it?
Do you have a Websphere MQ Server properly installed locally?
I saw such behavior when only Websphere MQ Explorer is installed.
In this case the only point on step 2 is to add a remote Queue Manager.
START The MQ Explorer in Administrator mode.
Got the Bin folder of MQ Installation and right click on the mqexpolrer image and select as "Run as administrator"
Right click > My computer
Select and open > manage
Expand > local users and groups
Select USerS
Right side you user MUSR_MQADMIN and Properties.
Uncheck the TickBox > Account is Disabled.
Click apply and ok.
Now restart your MQ .
Try to open MQ explorer with the user which we installed MQ. For example it should be mqm and group mqm. Else add your user into mqm group. Then reopen MQ and check.
You should have local admin rights to find New option at Queue managers.
To do this get local admin rights and follow the steps below:
Right click my computer
Select and open manage
Expand local users and groups
Select groups at left side
Right side you can see all the groups.
Double click on mqm group and add your user id.
Click apply and ok.
Now restart your MQ. You can see the new option after restarting the
MQ.