| Author |
Message
|
| mderbich |
 Posted: Wed Mar 02, 2011 6:04 am Post subject: Setting up MQSeries |
 |
|
Newbie
Joined: 02 Mar 2011
Posts: 4
|
Hi,
I need some help to get the connection to MQSeries right, please.
I have an MQ Manager located at a third party service provider (ASP1) that communicates with SWIFT. The connection with the Manager is done via an MQ Client located on my network.
There are two systems on my side that send and get messages via MQSeries to/from SWIFT. Messages are converted into files (in case of traffic in both directions) and placed on a server on my network. There are two scripts taking care of that which are called MQPut and MQGet, but I’m not sure if they are standard MQSeries elements. There was some work done on them.
The situation needs to be kept primarily as is for one of the systems (S1). For the other system (S2) I need a solution.
System S2 will be moved and outsourced yet to another third party (ASP2). I’d like S2 to use the existing MQ Manager/Client. I wouldn’t necessarily need files on my network though. I’d like S2 (at ASP2) to connect to the MQ Manager (at ASP1) via my network. The S2 as part of the standard product includes also an MQ Client, by the way.
Who should I turn to for advice? How should I connect S2 at ASP2 to the MQ Manager at ASP1 via my network? Is it possible?
Best regards,
MQSeries novice |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Mar 02, 2011 6:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Well.
One solution would be to set up MQ Internet Passthrough (MQIPT) to act as a relay point. Then you would configure the S2 to connect to your MQIPT and the MQIPT to connect to the remote qmgr. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Mar 02, 2011 6:41 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's a shame files are used. Applications should consume and produce MQ messages directly. If files are used then most of the MQ transactional integrity is compromised.
However you may find the open source product file move from capitalware will provide a good file to message service. Better than most home-grown solutions. http://www.capitalware.biz/mqfm_overview.html
Connecting a MQ client is simply a matter of network connectivity between the client and the queue manager (e.g. using a VPN).
It's probably simpler to connect the external MQ client to a queue manager on your site and then connect that QM to the third-party QM. |
|
| Back to top |
|
|
| mderbich |
| Posted: Wed Mar 02, 2011 8:20 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2011
Posts: 4
|
Thank you so much!
MQ Internet Passthrough (MQIPT) would sound like a solution for me. Will this be secure? Will it go over the Internet?
Regarding files, that's what I'm aiming for indeed - not to have them any more. So for SP2 I wouldn't want files. But I need to keep them for SP1 for now.
Could you please explain a bit more: 'connect the external MQ client to a queue manager on your site and then connect that QM to the third-party QM'? Do you mean I connect MQ Client of SP2 to my queue manager and then that queue manager to MQ Manager at ASP1? Should I be able to access my queue manager from my MQ Client and make the connections? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Mar 02, 2011 10:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| mderbich wrote: |
| Will this be secure? |
If you set it up to be, yes.
| mderbich wrote: |
Will it go over the Internet?
|
If you set it up that way. MQIPT over the Internet is one of its uses.
| mderbich wrote: |
Could you please explain a bit more: 'connect the external MQ client to a queue manager on your site and then connect that QM to the third-party QM'? Do you mean I connect MQ Client of SP2 to my queue manager and then that queue manager to MQ Manager at ASP1? Should I be able to access my queue manager from my MQ Client and make the connections? |
Correct. QM to QM connections between companies are much preferred to have an MQ Client on Company A connect to a QM in Company B.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mderbich |
| Posted: Thu Mar 03, 2011 12:00 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2011
Posts: 4
|
| Quote: |
| Correct. QM to QM connections between companies are much preferred to have an MQ Client on Company A connect to a QM in Company B. |
That's what we are doing too. We - Company A - have an MQ Client and we connect to a QM in Company B (ASP1). But now I want Company C (ASP2) to connect to the QM at Company B. Company C have their own MQ Client but I don't want to connect it directly to the QM at Company B. I want to connect it via my Company A. I guess I would need to have a QM in my Company A for that. Is that right? |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 03, 2011 12:19 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Peter was saying that all external connections are better as QM to QM rather than as MQ client to QM, which I would agree with. However if an external company has no MQ skills then having their own QM may complicate matters, unless you can manage it for them.
I don't know if MQIPT works for client channels, but these days the use of a VPN is more common and you don't need MQIPT for that.
So the easiest way is to get a VPN (over the internet) set up between your firewall and their firewall. This is a job for network people. Once in place you can use standard MQ channels as you would normally.
It's probably a good idea to use SSL certificates to authenticate the third-party as well, but get the channel working without these first.
"Making connections" means defining channels - if you are struggling with this concept then you need to start with basics - set up some queue managers at your site and get familar with MQ connectivity.
Getting MQ working over external links is always difficult (for network reasons) and you need to know exactly what you are doing in MQ terms - getting an expert to help with this you would be a wise investment. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 03, 2011 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
MQIPT does work with client channels, afaik.
VPN is certainly another option. In fact it's the more obvious solution - just provide Company C with connectivity information that directs things to Company A, and reroute it at the network level to point to the address at Company C. |
|
| Back to top |
|
|
| mderbich |
| Posted: Thu Mar 03, 2011 8:26 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2011
Posts: 4
|
|
| Back to top |
|
|
|
|
