| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| remote administration through QM1 to QM2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| tso0rxp |
 Posted: Fri Jan 21, 2011 9:03 am Post subject: remote administration through QM1 to QM2 |
 |
|
Voyager
Joined: 07 Jan 2002
Posts: 85
|
Did a search but I may have not used the right terms to find my answer.
Situation:
QM1 resides inside our firewall.
QM2 resides in our DMZ
Security on MQ ports only allows a client connection (using 3rd party MQ visual edit) to QM1 but QM1 can talk to QM2 via normal sender/receiver channels.
In other words, I cannot get to QM2 from my PC.
I've read somewhere that I could use QM1 to serve as a pass through queue manager to get to QM2 from my PC. True? If so, how would that be configured?
I want to be able to administer QM2 from my client software and not have to remote into QM2 and administer locally.
_________________
Bob Perry
MQ Administrator |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jan 21, 2011 9:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| tso0rxp |
| Posted: Fri Jan 21, 2011 9:24 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2002
Posts: 85
|
thanks, this helps for remote administration using runmqsc type commands but can i get to the DMZ Queue Manager via a client on my PC? for queue managers inside our DMZ I just use the SYSTEM.DEF.SVRCONN but I can't get to that channel on the DMZ queue manager. if that is not possible then i will have to live with runmqsc.
_________________
Bob Perry
MQ Administrator |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 21, 2011 9:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
This will also allow you to send PCF messages. Your client software on your PC will use PCF messages. It specifically says it will work with PCF messages...
Depending on *why* you cna't get to the QM2 in the DMZ, there may be other options. Perhaps the *port* is open to your desktop, but the qmgr is not set up for remote administration. In that case you could configure a specific, known, channel and set up SSL and an SSLPEER and MCAUSER. This would prevent anyone who is not authorized from connecting to the qmgr using this channel, and ensure that when you do connect, that you have the needed access. |
|
| Back to top |
|
|
| tso0rxp |
| Posted: Fri Jan 21, 2011 9:40 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2002
Posts: 85
|
Perfect! Thanks.
_________________
Bob Perry
MQ Administrator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
