| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ client on Google Cloud Platform (GCP) |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Mon Nov 04, 2024 5:54 am Post subject: MQ client on Google Cloud Platform (GCP) |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5859
Location: UK
|
I am interested in any experiences of hosting business applications that require MQ connectivity (back to the legacy systems) in GCP.
So assuming there are central in-house legacy systems with MQ QMs including on z/OS - how can new Java/JMS applications hosted on GCP connect to them?
Is this best done using the GCP MQ connector, or by installing MQ client or MQ JMS Jar files on GCP?
What issues were encountered and how were they overcome?
Did you connect directly back (via MQ connector/MQ client/JMS) to the central host QMs or did you install full QMs in GCP?
Our preference is to avoid full QMs hosted in GCP for support reasons.
Is "MQ on cloud" an option here?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Nov 04, 2024 11:44 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5859
Location: UK
|
No-one here interested in MQ on GCP?
Or is no-one here anymore?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Nov 05, 2024 2:03 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7719
|
If you go the route of having the IBM MQ Client connection originate in the cloud and stretch back to the On Prem queue manager, it can work. Some considerations:
That stretch client connection now relies on the skill and diligence of the app developer for building/configuring the client app to reconnect when the connection breaks. There is a lot more opportunity for breaks in the connection when its stretched across many miles and many additional components. But if you had a local QM in the cloud for that client to locally connect to, now you rely on the QM to QM channel resiliency built up by IBM over decades and tested by thousands of companies.
Having many clients connecting to the On Prem queue manager from the cloud means many connection points that need to be allowed (firewalls and the like). But having queue manager(s) up in the cloud could mean fewer connections to secure between cloud and on prem.
Latency - its gonna be the same whether its a client to a queue manager or a queue manager to a queue manager. But, if the client app is just putting messages as fast as it can and not blocking waiting for a reply message, that client will be able to complete all its puts much faster if the QM its connected to is colocated with the client.
If the client does stretch its connection whether to put or get, the latency can be significant enough for the client app to have to do something to mitigate it. That something could be running more parallel instances of the app to process the same exact number of transactions. That can cause an interesting situation - the client app migrates from On Prem to Cloud, still connecting to the same On Prem QM, still processing the same # of transactions, but the MQ Admin is dealing with more channel connections. Multiply that by many apps and maybe you are dealing with a LOT more connections. Apps are moving to the cloud, same business workload, but the MQ Admin says they need to increase their MQ capacity......
I don't have any experience or knowledge even about GCP. Seems almost everyone is AWS or Azure. But I don't think any of (the maybe obvious) points I made above would change based on the cloud provider.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Nov 08, 2024 4:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5859
Location: UK
|
Thanks. I would imagine that MQ client auto-reconnect would help with disconnects.
We have many MQ client applications and the general preference is not to have QMs sited close to each application but to use the central z/OS QMs.
Hosting a QM in GCP also presents us with support issues - we have outsourced all MQ support for LUW platforms but they don't cover GCP.
Using the GCP supplied MQ connector seems the simplest option but would like to hear from anyone that has used it.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
