| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Series Configuration |
« View previous topic :: View next topic » |
| Author |
Message
|
| kris |
 Posted: Mon Apr 12, 2004 3:03 pm Post subject: MQ Series Configuration |
 |
|
Newbie
Joined: 12 Apr 2004
Posts: 7
|
Hi Experts,
I am trying to set up a MQ Configuration for exchanging messages between two applications over the internet that are in different TCP/IP domains. My understanding is that if both the applications's Q Managers are in the same TCP/IP domain, I can cluster them. But in this situation what do you guys suggest? I am thinking of using remote queues for this solution. What are the implications? can you guys point me to some examples?
Regards,
Kris |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 12, 2004 4:14 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What's a TCP/IP domain?
A subnet? A registered-with-the-Internic domain?
MQSeries doesn't care about those things. If there's a viable network path between two queue managers and a viable addressing scheme (a resolvable DNS name or a regular IP address), then MQSeries can build a channel across that path.
The big thing you really need to do before you even think about making an MQ connection to another company is MQSeries security. And it sounds like you don't really understand MQSeries connectivity very well - so it's likely you don't really understand the security implications very well either.
Start by reading the Security manual, and the security sections of the System Administration guide. Then read the recent thread in the Cluster forum here about clustering with 3rd parties. And look for the redbook on Websphere MQ Security in the Enterprise.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kman |
| Posted: Mon Apr 12, 2004 7:53 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
|
| Back to top |
|
|
| kris |
| Posted: Mon Apr 12, 2004 8:30 pm Post subject: |
|
|
Newbie
Joined: 12 Apr 2004
Posts: 7
|
Hi Jeff, Thanks for your reply. There is security already set-up between these two companies (thats what their sys admin told me, but I need to double check) that we are trying to integrate. So do you think that the approach I am looking into is the right approach?
Here are all the details on what I am tring to do:
I have two computes, A and B
A has a Q Manager called a.queue.manager
B has a Q Manager called b.queue.manager
A is part of a workgroup
B is part of a domain called xyz
A and B can ping each other
Now I would like to send a message from application running on A to an application running on B.
On A, I have created a Local Queue, a transmit queue and a local definition of a remote queue on computer B. I have also created a sender channel on A and a receiver channel on B. But I am searching for a place where I can put B's IP address. Your help will be much appreciated.
Kris |
|
| Back to top |
|
|
| kman |
| Posted: Mon Apr 12, 2004 10:29 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Had you read the Intercommunication guide, you would know where to put the ip address.
fyi, it's in the connection name field of the sender channel.
You did not mention if you had setup the listener. I would imagine you haven't done so. The listener service should be started at the B side, and should listen on a port number. That same port number, if not the default 1414, must be specified in the connection name field. |
|
| Back to top |
|
|
| kris |
| Posted: Tue Apr 13, 2004 9:15 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2004
Posts: 7
|
| Thanks. I found that last night. There is a great example in the Intercommunications guide. Thanks for your help. |
|
| 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
|
|
|
|
