| Author |
Message
|
| boingjoe |
 Posted: Wed Feb 05, 2014 3:19 am Post subject: Virtual IP for a multi instance Queue Manager |
 |
|
Newbie
Joined: 05 Feb 2014
Posts: 6
|
We are in the process of installing WMB in our production environment. As part of it we have entitlement for Active/standby set up recommended by IBM.
This is recommended to be set up in a Multi Instance mode.
Just a few of questions on this , if an expert can validate it would be great
a) As i understand switch over from an active to a passive instance causes the IP to failover from IP1 on the active node to IP2 on the standby node. Please correct.
b) To avoid this IP switch is it possible that a Virtual IP be set up so that the physical IP's of the MI cluster can be transparently switched over ?
Or
c) Will this V-IP require HA/CMP like cluster to be set up ? Will a Loadbalancer help ?
d) Many of the publishers into our ESB are MQTT enabled devices / RTU's not many have a facility to reconnect and republish to multiple IP's.
For other publishers we have on SOAP/HTTP we could i believe have a APACHE WebServer that can then provide the message to the right node in the MI Broker ? Is that a right statement.
Cheers , Appreciate help ! |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Feb 05, 2014 5:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You don't say what platform you are trying to build on
Assuming Windows
1) You assign a Virtual IP to the Cluster Service that runs WMQ & Broker.
2) It is this that moves between systems.
3) Broker has a builtin WebServer. Use the Virtual IP in your webservice URL's.
4) Probably the same applies to MQTT clients.
5) Load balancers only help if you are in situation where you are running more than one broker at once. They can distribute HTTP traffic to the available brokers using their real IP addresses.
This is a very different to an Active-Passive setup.
I guess that something like Veritas and other cluster methods can provide the same sort of environment in a Unix/Linux platform. I've not clustered Broker on an *ix platform for a long time.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 05, 2014 5:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You haven't said anything about how you connect MQTT to your ESB.
Obviously this makes a large difference in how they will deal with the fact that a multi-instance broker/qmgr uses more than one IP address.
One easy solution to this problem is to install a MessageSight appliance, and use that to bridge from MQTT to the broker's queue manager. |
|
| Back to top |
|
|
| boingjoe |
| Posted: Wed Feb 05, 2014 6:22 am Post subject: |
|
|
Newbie
Joined: 05 Feb 2014
Posts: 6
|
Thanks folks.
My bad , didnt provide the context did I 
The production servers are on RHEL (Linux) on PSeries
Will the answer remain remain same for Q1. Will it be possible for a Virtual IP that can map to any one Physical IP where WMB is installed. Do we need VERITAS for this or it is managed by any OS/H.W configuration.
I did some ground work on the WS URL part. Is the MB Proxy Servlet that will be used as a WebServer. I was thinking of having a Apache HTTP server that would do this for me. Are there any drawbacks , Wrong here am i ?
So then is it right to conclude that a Virtual IP be setup during H/W set up that can then point to the active WMB-IP (WMB-IP1 or WMB-IP2) based on which node is up..
We have RTU's attached to concentrators that publish events. I am told that these will directly publish to the WMQ Advanced infrastructure. Due to limited MQTT clients , this is planned as a Telemetry service on the Broker QM itself. We do not have a MQ node seperately or a Bridge based set up (only subscribed to events). Sadly no IBM message sight as well.
Will a Virtual IP solve the connectivity problem for Active/Passive. I assume the embedded concentrator uses a url tcp://server:1833/ to publish.
Thanks guys ! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 05, 2014 6:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Just be aware that MI does not provide the virtual IP.
However you provide that from withing your infrastructure is up to you.. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| boingjoe |
| Posted: Wed Feb 05, 2014 6:55 am Post subject: |
|
|
Newbie
Joined: 05 Feb 2014
Posts: 6
|
Hmm Okay.
I will talk to the H/W administrators to see if this can be done. But generally how does everyone do it in Production on a *NIX system
Though i understand that topologies are never alike , I am sure we are not the first to hit this roadblock with Active/Passive IP set up 
How do you guys manage application re-connection with constraints such as only 1 IP is supported say..
Is there any case where a hardware based Virtual IP mapping to an Active WMB IP fail /not work in any case (MQ or MQTT or HTTP endpoints ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 05, 2014 6:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
WMQ MI provides for this by allowing you to enter both endpoints into the channel definition. So no need for a VIP. This is not the case when your connection is HTTP or SOAP over HTTP....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 05, 2014 7:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| boingjoe wrote: |
I will talk to the H/W administrators to see if this can be done. But generally how does everyone do it in Production on a *NIX system
Though i understand that topologies are never alike , I am sure we are not the first to hit this roadblock with Active/Passive IP set up |
No, failing IP addresses over in an active/passive setup supported on Unix is a problem as old as TCP/IP 
| boingjoe wrote: |
| How do you guys manage application re-connection with constraints such as only 1 IP is supported say.. |
You either front the active/passive servers (which could be WMB, WAS, Apache, etc) with a network appliance (like an F5), or use something which can project & swap the id (like Veritas, HACMP, etc), etc. Reconnection logic is as simple as the application retrying in the event of failure.
| boingjoe wrote: |
| Is there any case where a hardware based Virtual IP mapping to an Active WMB IP fail /not work in any case (MQ or MQTT or HTTP endpoints ) |
Note that a WMQ MI doesn't switch IP addresses and leverages the reconnection facilities of a WMQ client
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
