| Author |
Message
|
| Sacha |
 Posted: Sun Dec 05, 2004 11:55 am Post subject: Problems installing remote administration |
 |
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
Hi,
I installed a MQ Demo 5.3 version on my linux and windows box.
I started using Quick Beginnings for Linux and got a running
server-to-server installation. Happy about that i tried to install
channels and transmissions queues for remote administration.
I would like to see the linux queues and channels inside the windows explorer.
For some reason message send from windows using cmd
"runmqsc -w 30 venus.queue.manager" are sent to the linux DLQ 
Here what i defined and started:
Windows:
DEFINE CHANNEL ('QM_qube.to.venus') CHLTYPE(SDR) +
CONNAME ('192.168.0.2(1416)') XMIT ('venus.queue.manager') TRPTYPE(TCP)
DEFINE CHANNEL ('venus.to.QM_qube') CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE QLOCAL ('venus.queue.manager') USAGE (XMITQ)
runmqlsr -p 1417 -t TCP -m QM_qube&
I activated the channel using the MQ Explorer.
Linux:
DEFINE CHANNEL ('venus.to.QM_qube') CHLTYPE (SDR) +
CONNAME ('192.168.0.3(1417)') XMITQ ('QM_qube') TRPTYPE(TCP)
DEFINE CHANNEL ('QM_qube.to.venus') CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE CHANNEL ('QM_qube.to.venus') CHLTYPE(RCVR) TRPTYPE(TCP)
runmqlsr -p 1416 -t TCP -m venus.queue.manager&
runmqchl -c venus.to.QM_qube -m venus.queue.manager
strmqcsv venus.queue.manager
SYSTEM.ADMIN.COMMAND.QUEUE is defined.
I used amqsbcg on my linux box to trigger out the Reason for this behavior but couldn't find any reason code as described in the IBM web page.
Here the output of amqsbcg:
AMQSBCG0 - starts here
**********************
MQOPEN - 'venus.dead.letter'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 16777216 MsgType : 1
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 923
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D512076656E75732E71756575652E9713B34102040020'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : 'AMQ.41B3106B010D0020 '
ReplyToQMgr : 'QM_qube '
** Identity Context
UserIdentifier : 'sacha '
AccountingToken :
X'1601051500000093E3624807E9942D07E53B2BEF03000000000000000000000B'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : 'amqpcsea '
PutDate : '20041205' PutTime : '18420069'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 280 bytes
00000000: 444C 4820 0100 0000 F307 0000 414D 512E 'DLH ....ó...AMQ.'
00000010: 3431 4233 3130 3642 3031 3044 3030 3230 '41B3106B010D0020'
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 514D 5F71 ' QM_q'
00000040: 7562 6520 2020 2020 2020 2020 2020 2020 'ube '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: 9B03 0000 4D51 4144 4D49 4E20 0B00 0000 '....MQADMIN ....'
00000080: 5765 6253 7068 6572 6520 4D51 5C62 696E 'WebSphere MQ\bin'
00000090: 5C72 756E 6D71 7363 2E65 7865 3230 3034 '\runmqsc.exe2004'
000000A0: 3132 3035 3138 3432 3030 3639 0100 0000 '120518420069....'
000000B0: 2400 0000 0100 0000 2600 0000 0100 0000 '$.......&.......'
000000C0: 0100 0000 0000 0000 0000 0000 0200 0000 '................'
000000D0: 0300 0000 1000 0000 F903 0000 0100 0000 '........ù.......'
000000E0: 0400 0000 3800 0000 C60B 0000 9B03 0000 '....8...Æ.......'
000000F0: 2400 0000 4449 5350 4C41 5920 4348 414E '$...DISPLAY CHAN'
00000100: 4E45 4C20 2827 514D 5F71 7562 652E 746F 'NEL ('QM_qube.to'
00000110: 2E76 656E 7573 2729 '.venus') '
No more messages
MQCLOSE
MQDISC
Any help will be appreciated. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Sun Dec 05, 2004 1:14 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I would like to see the linux queues and channels inside the windows explorer |
To do that, all you need is a ServerConn Channel called SYSTEM.ADMIN.SVRCONN defined on the Linux side, make sure the Command Server is running, and then "Show a Queue Manager", by right clicking on Queue Managers in the GUI and fill in the blanks.
The DLQ Reason code is x'7f3' (2035). Not Authorised. Try searching the site for 2035 and Report messages. You should find all the information you need.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Sacha |
| Posted: Sun Dec 05, 2004 3:05 pm Post subject: Problem installing remote administration |
|
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
| EddieA wrote: |
To do that, all you need is a ServerConn Channel called SYSTEM.ADMIN.SVRCONN defined on the Linux side, make sure the Command Server is running, and then "Show a Queue Manager", by right clicking on Queue Managers in the GUI and fill in the blanks.
The DLQ Reason code is x'7f3' (2035). Not Authorised. Try searching the site for 2035 and Report messages. You should find all the information you need.
Cheers, |
Thx Eddie for your reply
I defined SYSTEM.ADMIN.SVRCONN on the linux side:
DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
than i tried "Show Queue Manager" in the GUI and filled:
WS-Manager: venus.queue.manager
Name: 192.168.0.2
and got again Error AMQ4043?
BTW: I made a mistake in my previous post. In the Linux box i did not
define the channel twice instead i made:
DEFINE QLOCAL ('QM_qube') USAGE (XMITQ)
Copy paste error.
Your hint about the (2035). Not Authorised was great. I dont know how you found this out looking into the amqsbcg output?
I defined:
- Local unix user sacha:
- i called: setmqmaut -m venus.queue.manager -t mqr -p sacha +connect +inq
- i called: setmqmaut -m venus.queue.manager -t queue -p sacha -n QM_qube.** +allmqi
then i tried again command "runmqsc -w 30 venus.queue.manager".
Still does nit work.
Got a strange message inside the linux error log describing problems sending the reply back to Windows (193.168.0.3:1417) with error code: 111 (X'6F'). Then i realised that the listener stopped on windows (don't know why the process like channels and listeners are stopping always).
I restarded the listener and tried again. Now it looks like the Messages
are queued on the XMIT queue venus.queue.manager on windows?
I tried again to add the QM inside the GUI after setting the permissions and got again AMQ4043.
hmm, i think i'm to tired to continue. I will make some more tests tomorrow.
Thx
Sacha |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Dec 05, 2004 6:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Sacha,
| Quote: |
| To do that, all you need is a ServerConn Channel called SYSTEM.ADMIN.SVRCONN defined on the Linux side, make sure the Command Server is running, and then "Show a Queue Manager", by right clicking on Queue Managers in the GUI and fill in the blanks |
You must as well make sure that the user running the MQExplorer has all the authorizations.
Looking at your earlier attempt using runmqsc:
a) the queue manager used to connect to must be the default qmgr.
b) the remote qmgr must have a default path to the default qmgr your are using. (interconnection manual)
Enjoy  |
|
| Back to top |
|
|
| Sacha |
| Posted: Sun Dec 05, 2004 10:55 pm Post subject: |
|
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
Just made the test again this morning before to go for real work.
"runmqsc -w 30 venus.queue.manager" works! 
I can display all the remote queues and channels.
I tried again "Show Queue Manager" in the GUI and filled:
WS-Manager: venus.queue.manager
Name: 192.168.0.2
and got again Error AMQ4043 
runmqsc for the remote QM works but i still
can't display it in the explorer GUI?
Thx
Sacha |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Dec 06, 2004 4:57 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Here is a complete description of how to set up authorities to enable remote administration via MQExplorer:
.
| Quote: |
The requirement is for userID MYUSER on a Windows machine to be able to perform remote admin on a qmgr called MYQMGR hosted on a remote UNIX machine called tenpin listening on port 1444.
Actions on tenpin
1. Create the required user on the remote machine
Use the O/S facilities to create the user, e.g. on AIX smit, HPUX sam or useradd, Solaris useradd.
The user name must be in lower case, e.g. for user MYUSER on Windows create user myuser on UNIX.
2. Ensure that the listener is setup and running.
If using inetd, put this entry in /etc/services
MQ_MYQMGR 1444/tcp
and this entry in /etc/inetd.conf
MQ_MYQMGR stream tcp nowait root /usr/lpp/mqm/bin/amqcrsta amqcrsta -m MYQMGR
Request inetd to refresh its cache from the files by finding the PID of inetd and sending a SIGHUP signal to the process.
tenpin:/scratch/nigelg $ su
root's Password:
# ps -ef | grep inetd
root 4450 8010 0 27 Oct - 0:01 /usr/sbin/inetd
root 14706 1 0 27 Oct - 0:00 /etc/inetd.afs /etc/inetd.conf.afs
root 30596 44986 0 09:16:34 pts/0 0:00 grep inetd
# kill -1 4450
If using runmqlsr, start the listener:
runmqlsr -m MYQMGR -t TCP -p 1444
3. Ensure the command server is running
The command server's process name is amqpcsea.
tenpin:/scratch/nigelg $ ps -fe | grep amqpcsea
nigelg 35272 51086 0 09:21:53 pts/0 0:00 grep amqpcsea
tenpin:/scratch/nigelg $ strmqcsv MYQMGR
WebSphere MQ command server started.
tenpin:/scratch/nigelg $ ps -ef | grep amqpcsea
nigelg 29248 1 0 09:22:00 - 0:00 amqpcsea MYQMGR
nigelg 44990 51086 1 09:22:08 pts/0 0:00 grep amqpcsea
4. Create the SVRCONN channel for the command server to use
The channel name is SYSTEM.ADMIN.SRVCONN
tenpin:/scratch/nigelg $ runmqsc MYQMGR
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager MYQMGR.
def chl(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) replace
1 : def chl(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) replace
AMQ8014: WebSphere MQ channel created.
end
2 : end
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
There are several options at this point
1. If the customer wants the required userID to have full privileges over all MQ objects, add the userID to the mqm group on the UNIX machine, again using the O/S facilities to do so. In this case there is no further action required.
2. An alternative method of giving full privileges is to set the MCAUSER attribute on the SVRCONN channel created at step 4 above to mqm. Do this by adding MCAUSER('mqm') to the above runmqsc command. Again, no further action is required.
3. If restricted access to MQ objects is required, further commands are necessary as below
5. Grant specific authority over MQ objects to the required userID
Issue these setmqaut commands to grant minimal authority to the userID:
tenpin:/scratch/nigelg $ setmqaut -m MYQMGR -t qmgr -p myuser +connect +inq +dsp
tenpin:/scratch/nigelg $ setmqaut -m MYQMGR -t q -n SYSTEM.DEFAULT.MODEL.QUEUE -p myuser +inq +browse +get
tenpin:/scratch/nigelg $ setmqaut -m MYQMGR -t q -n SYSTEM.ADMIN.COMMAND.QUEUE -p myuser +inq +put
The purpose of these commands is:
1. Grant authority to access the qmgr
2. Grant authority to the client channel to get the command server reply messages
3. Grant authority to put messages onto the command server input queue
Administration setmqaut commands, +chg +clr +dlt +dsp, will be required on each object in the qmgr to be administered remotely.
For example, to allow dsp authority on a particular queue QL1:
tenpin:/scratch/nigelg $ setmqaut -m MYQMGR -t q -n QL1 -p myuser +dsp
Actions on Windows
1. Show the qmgr in the Explorer window
Right-click the Queue Managers folder and select Show Queue Manager...
Select the Show a remote queue manager radio button
Enter the Queue Manager Name, e.g. MYQMGR
and Connection Name, e.g. tenpin(1444)
Click OK
|
|
|
| Back to top |
|
|
| Heinz57 |
| Posted: Mon Dec 06, 2004 8:22 am Post subject: |
|
|
Apprentice
Joined: 21 Jan 2004
Posts: 26
Location: Syracuse, NY
|
| I'm not 100% sure about this but I thought MQExplorer could only access Windows based qmgrs. Correct me if I'm wrong.... |
|
| Back to top |
|
|
| JT |
| Posted: Mon Dec 06, 2004 8:25 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| No, that's not quite correct. The MQExplorer console can also access/adminsiter UNIX based qmgrs. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Dec 06, 2004 8:49 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| Sacha |
| Posted: Mon Dec 06, 2004 11:03 am Post subject: |
|
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
Hi
Many helps to all. I'm really surprised about the good feedback.
Ok, finally i found the reason and as usual it is a stupid thing
that i did not know.
In the MQ explorer GUI you define the remote QM and the
remote host and of course you have to add the port number
where the listener is waiting if it's not the default port (1414) 
I typed:
Queue Manager: venus.queue.manager
Host: 192.168.0.2(1416)
bingo 
Anyway here my change request for IBM for the next MQ explorer version. Ask pls for Host(Port)
Many thx
Sacha |
|
| Back to top |
|
|
| confusedmq |
| Posted: Wed Jun 22, 2005 9:05 am Post subject: |
|
|
Newbie
Joined: 22 Jun 2005
Posts: 4
|
| bower5932 wrote: |
| http://www.developer.ibm.com/tech/faq/individual?oid=2:25984 gives some details on setting up the explorer to administer a remote unix machine. |
I've followed the instructions on the above page but am still having trouble connecting to a remote QM on an AIX box.
I think I may not be defining the correct port. The command 'ps -ef | grep runmqlsr' gives me the port for the default QM on the box but I am trying to connect to a separate QM (QM2). How do I check I am trying to connect to the right port for QM2? |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Jun 22, 2005 9:29 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| How do I check I am trying to connect to the right port for QM2? |
Ask the MQ Administrator for that box.
Or run the command on it.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 22, 2005 10:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
if you do not find an entry for the qmgr running
| Code: |
| ps -ef | grep runmqlsr |
you need to check /etc/inetd.conf
if there is an entry there you need to check the symbolic port against the entries in /etc/services
If there is no runmqlsr running and the listener is not running through inetd then just create a listener... remember the user should be part of mqm group...or have the right permissions on the qmgr.
| Code: |
| runmqlsr -m qmgr -t tcp -p portnum & |
Enjoy  |
|
| Back to top |
|
|
|
|
