| Author |
Message
|
| kats |
 Posted: Fri Feb 23, 2007 11:10 am Post subject: MO71 GUI |
 |
|
Voyager
Joined: 20 Apr 2006
Posts: 78
|
--------------------------------------------------------------------------------
My machine: Win XP SP-2, MQ client 5.3 and MO71.
Remote Machine: SunOS, MQ 5.3 CSD 12.
Installed MO71 Pack on My machine. Chose MO71 over MQ 6.0 GUI as one of my requiremnts is to pick messages from Queue and delete.
Also apart from MQ client, I am not really sure If the eclipse part is free. Is it?
But MO71 together with MQ client are free. (So far I think)
Now problem is : I am getting error AMQ2059.
http://www-1.ibm.com/support/docview.wss?rs=856&context=SSWHKB&dc=DB520&uid=swg21166939&loc=en_US&cs=UTF-8&lang=en&rss=ct856websphere
Qmgr, CSV and listener are running on remote system.
Well, I am trying to connect Via SYSTEM.DEF.SVRCONN.
I don't have ID in MQM group in remote system. Can this problem be overridden by putting MCAUSER as MQM in SYSTEM.DEF.SVRCONN. (this is just for test sake)
Can I use dynamic CLINTCONN channel on my machine for remote admin:?
SET MQSERVER=SYSTEM.DEF.SVRCONN/TCP/Hostname(14XX)
I just tried to put message from my box thru amqputc, but met with same result.
Also Do I need to create model queue SYSTEM.MQEXPLORER.REPLY.MODEL on remote system for MO71?
Network is fine, I can ping the remote machine through my machine.
Any thoughts guys!
Last edited by kats on Mon Feb 26, 2007 2:30 pm; edited 1 time in total |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Feb 23, 2007 1:56 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Also Do I need to create model queue SYSTEM.MQEXPLORER.REPLY.MODEL on remote system for MO71? |
No |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Sat Feb 24, 2007 4:37 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
You specify the connection as documented in MO71 doc.
This means when adding new queue manager select client. and specify the wanted channel to use, in your instantance SYSTEM.DEF.SVRCONN.
Use the correct connectionname incl the port (if differ from 1414).
Then should you be able to get some usefull reason code like 2035 (MQRC_NOT_AUTH..). And yes the you could add the MCAUSER on the channel.
I CAN'T recomment this because this will open a huge security hole...
You could add SSL to help you protecting who care allowed to connect using the MCA user or a use a security exit like BlockIP2 or others.
-- Lock it or Lose it -- 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Last edited by oz1ccg on Sat Feb 24, 2007 9:36 am; edited 1 time in total |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Feb 24, 2007 8:24 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| oz1ccg wrote: |
| Another hack that a ISV presented years ago to advertize for his security solution was a client exit that are extremely usefull for penetration purposes.... Hacking etc. |
Jorgen, why this tone or am I reading more into what you are saying?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| kats |
| Posted: Mon Feb 26, 2007 12:45 pm Post subject: |
|
|
Voyager
Joined: 20 Apr 2006
Posts: 78
|
Thanks vennela for obviating this step, saved me time.
Jorgen/Masters, I've reached AMQ 2035;
Error connecting via client to 'QmgrName' RC(2035) Not authorized.
Once again I don't have my ID at remote MQ server, I'm trying by putting 'mqm' in MCAUSER id field of Sys.Def.Svrconn channel.
But, if I try to put message thru my PC, I get 2059
H:\>amqsputc SYSTEM.DEFAULT.LOCAL.QUEUE QmgrName
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
Last edited by kats on Mon Feb 26, 2007 2:15 pm; edited 1 time in total |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Feb 26, 2007 1:43 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| Michael Dag wrote: |
| oz1ccg wrote: |
| Another hack that a ISV presented years ago to advertize for his security solution was a client exit that are extremely usefull for penetration purposes.... Hacking etc. |
Jorgen, why this tone or am I reading more into what you are saying? |
| oz1ccg wrote: |
| Home of BlockIP2, the free MQ Security exit |
Jorgen, I assume that your comment is referring to my previous posting:
http://www.mqseries.net/phpBB2/viewtopic.php?t=21782
Since I am a sponsor and a regular contributor to this list, I do not appreciate reading what I interpret as derogatory comments about me personally or my business practices.
I feel that it is inappropriate and unprofessional for you to use this list to vent your personal grievances against me.
Especially in light of previous problems I have had with you in the past, I would appreciate your future cooperation in refraining from voicing your opinions about me or my business practices.
Thank you.
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| kats |
| Posted: Thu Mar 01, 2007 11:53 am Post subject: |
|
|
Voyager
Joined: 20 Apr 2006
Posts: 78
|
I don't feel like posting on same thread and end up publicising or bringing up more reader to it. I don't know if it's appropriate to start new thread and post same problem!
I'm getting an error: Error connecting via client to 'QmgrName' RC(2035) Not authorized.
Now as said before: My desktop ID does NOT exist in remote MQ Server in mqm group. But I put mqm in MCAUSER field of SVRCONN channel I am using. Is that an answer to not having my ID in mqm group?
or I have to have an ID in mqm group of remote MQ server?
Pls guide. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Mar 01, 2007 10:04 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| kats |
| Posted: Tue Mar 06, 2007 2:31 pm Post subject: |
|
|
Voyager
Joined: 20 Apr 2006
Posts: 78
|
It's working finally.
Logic was right but there was a syntax error while executing the command:
ALTER CHL(SYSTEM.DEFAULT.SVRCONN) CHLTYPE(SVRCONN) MCAUSER(mqm)
I did not put quotes on user.
According to MQ Client.pdf :
When you define a channel with runmqsc, the MCAUSER attribute is changed to uppercase unless the user ID is contained within single quotation marks.
So my user was changed to MQM and system did not recognise this user.
I admit Mistake was silly...
Thank you Jorgen for your help. I appreciate your inputs Vennela. |
|
| Back to top |
|
|
|
|
