ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » remote MQ administration for Windows

Post new topic  Reply to topic
 remote MQ administration for Windows « View previous topic :: View next topic » 
Author Message
eleanora
PostPosted: Sat Jan 17, 2004 11:29 pm    Post subject: remote MQ administration for Windows Reply with quote

Novice

Joined: 18 Nov 2002
Posts: 16
Location: Melbourne, Australia

I'm trying to find a document that suggests IBM's preferred way to administer MQ remotely on Windows. We all know terminal services does not do a very good job, I've seen some messages suggesting VNC and PCAnywhere, but is there a document produced by IBM, that clearly states what would work and what would not?
Something we can show to our customers as well as put in our standards...
What happens now is that we are told by customers what kind of remote control software the box has, most of the time it does not allow us to administer MQ.
Thanks,
Eleanora.
Back to top
View user's profile Send private message
JasonE
PostPosted: Sun Jan 18, 2004 3:49 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

No, you will find IBM will not (should not?!) recommend one vendors method to another, they should only point out what is known not to work.

Pre 5.3 fixpack 3, you cannot use Windows terminal services or anything based around it, as each signed on user has their own desktop, and MQ requires shared data segments and named events etc. All of these were fixed in Fixpack 3 (except one bug to do with tracing whose fix went into Fixpack 4) so from then onwards, WTS is (should be!) fine.

Anything which gives you control over the whole desktop without giving you a second 'session' should be fine for earlier releases, as well as continuing to work. Ie VNC, PcAnywhere, NetMeeting, etc etc etc
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Jan 18, 2004 6:49 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Quote:
VNC, PCAnywhere,TerminalServices
But really, these are products for remote desktop access (and on Windows only), not for remote MQSeries administration.

If you configure your MQSeries for remote administration - i.e. set up the necessary admin queues and start a command server - then you can use all sorts of things to do remote MQSeries Administration, including MQExplorer, without having to access the remote desktop at all. Or you could enable an ssh server on the box, and use runmqsc.

Plus, any of the various monitoring products (Candle, contact admin, Tivoli, QPasa, etc.) will allow you to do remote MQSeries Administration without having to access the remote desktop.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
zpat
PostPosted: Sun Jan 18, 2004 9:04 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Is it still the case that there is no command server for the OS/390 version of MQSeries?

If so, it's about time that IBM provided this.
Back to top
View user's profile Send private message
EddieA
PostPosted: Sun Jan 18, 2004 10:24 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

There has always been a Command Server for z/OS.

Perhaps you meant support for PCF messages, which is sadly lacking.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
eleanora
PostPosted: Tue Jan 20, 2004 8:52 pm    Post subject: Reply with quote

Novice

Joined: 18 Nov 2002
Posts: 16
Location: Melbourne, Australia

guys,
Given we need to provide MQ support for a remote W2K server box running MQ 5.2, what I need to know is: if we only able to telnet to it and/or use terminal services, can we do all required tasks like check if listener running and on what port, check/start command server, channel init running .... etc.
I realise I can view/administer MQ object via MQ explorer, runmqsc etc, but it's not the only task we do when called after-hours. Also if QM is not running, is text based telnet enough to determine the problem and fix it?
The issue we have is that the customer thinks telnet/terminal services is ALL we need to support MQ remotely on the box.
thanks,
eleanora.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jan 21, 2004 5:19 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

eleanora wrote:
guys,
Given we need to provide MQ support for a remote W2K server box running MQ 5.2, what I need to know is: if we only able to telnet to it and/or use terminal services, can we do all required tasks like check if listener running and on what port, check/start command server, channel init running .... etc.
I realise I can view/administer MQ object via MQ explorer, runmqsc etc, but it's not the only task we do when called after-hours. Also if QM is not running, is text based telnet enough to determine the problem and fix it?
The issue we have is that the customer thinks telnet/terminal services is ALL we need to support MQ remotely on the box.
thanks,
eleanora.


I don't think terminal services is supported with 5.2. If it is, it's only supported as a remote queue manager from within the terminal services session. So, it's no better (and probably worse) than trying to work from your desktop. This should be a reasonably compelling reason for using something else (like PCAnywhere or RealVNC (which is free!)) to get access to the remote desktop.

You can also use the MQServices mmc to control remote MQServcies. You have to add another instance of the Snap-In to your window, from the Console menu "Add/Remove Snap-In", choose 'Add'. Select WebSphere MQ Services, and chose "Another Computer", and add the machine name. This will probably (likely!) only work with Windows servers.

If the QM isn't running, if you really have telnet access, then you should be able to do anything you need. Except, possibly, you might not be abel to see some of the needed log entries. Since Windows puts stuff in the Event Viewer, and there might be NON MQSeries events that you need to see. I don't, off the top of my head, know of anything to dump Event items from a command shell.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » remote MQ administration for Windows
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.