communicating between two queue managers through and ISP - is it possi

[kjcamp]

I am trying to set up two queue managers using MQSeries on Windows 2000 server.

The problem that I have is that one of the servers is most likely to be offline most of the time. It will queue up messages locally, then use RAS to connect to the internet through an ISP. Since it will be dynamically assigned IP addresses each time it connects, is this possible through MQSeries. How does the fixed queue manager (one of the servers has a static IP address) communicate back to the other server with the dynamic IP address. Any thoughts?

 

[smeridew]

Hmmm..a couple of things. First, you should always define your channels using the fully qualified domain name (FQDN) rather than a static IP address. Having said that, MQSeries does not like dynamic IP addressing.

You can try creating a requester/server channel pair - these channels are started by the requester (your non-fixed QMgr). The server channel does not need to have a CONN defined (which would typically define the address of the requester). You can then define the static IP of the fixed QMgr in your requester channel definition.

You should also look at MQSeries Internet passthru as an option for Internet proxy connections (MS81 service pac available on the MQSeries web site).

Let me know how this goes...

Scott Meridew
MQ Squared Inc.

 

[kjcamp]

I was checking this out on the MQSeries Information Center.
It looks like I would have to create both a requester-server channel for receiving information, and a requestor-sender channel to allow the static IP server to pull information back (callback). Is that the direction you were thinking? I am going to have to try this out.

Thanks.

 

[smeridew]

Yes - but you raise an interesting concern now. I thought you were just trying to send to the fixed QMgr. If you need to send messages back to the non-fixed QMgr you have another problem. The problem is, you have to define a sender channel back to the non-fixed QMgr, and you must provide a CONN name.

Here's a trick I just though up..(oh, this is sneaky).

1) Inlcude the IP address of your non-fixed QMgr as part of the message you send.

2) Define your fixed QMgr's sender channel using a CONN name of something like "DYNAMIC.host.domain(1414)"

3) Make your fixed QMgr's receiving application update it's local routing table (i.e. the C:\Winnt\system32\drivers\etc\hosts file on WindowsNT) with the new IP address you just received in #1

4) Make sure the sender channel is defined as a triggered channel, and that the disconnect interval is very short - this will ensure it doesn't stay alive and connected to the wrong IP address.

I think I should bottle this solution and sell it...

Let me know how it goes

Scott Meridew
MQ Squared Inc.

 

[kjcamp]

I'm working through this right now. It could do the trick.
I will let you know the results.

Thanks for all your help. (I'll take a bottle)