Author |
Message
|
Pavan Kumar PNV |
Posted: Fri Jun 29, 2007 9:51 am Post subject: Clustering across VPN |
|
|
 Acolyte
Joined: 03 Feb 2007 Posts: 66
|
Is it possible to cluster end points, when they are out of the company VPN and therefore cannot use hostnames but must use ip address resolution for the connection name parameter? |
|
Back to top |
|
 |
EddieA |
Posted: Fri Jun 29, 2007 10:52 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
You can use either Hostnames or IPs for connection names.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
Vitor |
Posted: Fri Jun 29, 2007 10:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
So long as the channel can find it's destination you can use anything you like _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jun 29, 2007 11:00 am Post subject: Re: Clustering across VPN |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Pavan Kumar PNV wrote: |
Is it possible to cluster end points, when they are out of the company VPN and therefore cannot use hostnames but must use ip address resolution for the connection name parameter? |
You are right it is particularly challenging when trying to get a cluster to work accross firewalls and different networks.
No I would not advise the use of IP's.
And No you do not need the IP.
You can use the hostname even when it is not in the DNS as long as it is at least in the /etc/hosts file or equivalent of your machine.
This way your cluster receiver can still reference a name but the resolution of that name might point to a different IP depending on which side of the network you are on.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
thindk00 |
Posted: Fri Jun 29, 2007 11:37 am Post subject: Firewall rules |
|
|
Voyager
Joined: 16 May 2001 Posts: 75 Location: UK
|
So I guess the external application (APP_EXT_QM) that is to be clustered with the applications inside the company VPN (APP1_INT_QM and APP2_INT_QM) and any cluster repositories (CR1_INT_QM and CR2_INT_QM) inside the company VPN needs to be be able to connect with the firewall allowing connectivity.
When joining APP_EXT_QM to CR1_INT_QM we'll use IP addresses (or host name if in the hosts file) to connect to the cluster. When APP_EXT_QM tries to send messages to APP1_INT_QM or APP2_INT_QM it will automatically define cluster sender channels. What would the cluster sender channel use as the connection name? IP address or hostname?
I guess we just need to make sure that all possible IP's that the external app can talk to or receive from, just need to be in the firewall rules. Right? |
|
Back to top |
|
 |
|