| Author |
Message
|
| bkiran2020 |
 Posted: Wed Aug 28, 2013 6:38 pm Post subject: listener |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| If we configure the mutiple listener for a queue manager any use of doing it, |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Aug 29, 2013 1:28 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
An example consideration:
Listener 1 - remote Admins
Listener 2 - Client applications
Listener 3 - remote queue managers
I'm sure others will be along with different ideas/reasons to do/not to do in a moment.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 29, 2013 3:52 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
'Edge' Queue Managers that are used to talk to business partners can benifit from having a listener per remote business partner.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Tibor |
| Posted: Thu Aug 29, 2013 4:25 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
You can create multiple listeners:
- for separating by network interfaces (considering network security)
- handling platform specific properties or protocols |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Aug 29, 2013 3:57 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
A bonus of multiple listeners is that you can control when a client or remote channel can use the qmgr by only running their port at certains times of the day.
If there is a rogue or problem app / remote qmgr on one port, it can be barred by stopping the listener, leaving all the other apps / remote qmgrs to run on other ports.
Neat features, but they are very rarely utilized.
_________________
Glenn |
|
| Back to top |
|
|
|
|
