Slashdot Mirror

← Back to Stories (view on slashdot.org)

MQSeries to COM - What's Best?

Posted by Cliff on from the working-with-the-middleware dept.

King Of Chat asks: "We have a project underway which involves Suns, A/S400s, 390s and the jewel in the crown, a COM application on NT. Given all these different platforms, the powers that be have decided the MQSeries is to be the middleware. The problem is the NT server app which some executive decided was going to be a strategic purchase. The NT app is all COM components so the question is: how do we get MQSeries to talk to them?"

"Options as we see it are:

  • Use an off-the-shelf MQSeries/MSMQ bridge. Problem here is that this is a high(ish) volume web app so extra latency == bad.
  • Write a bit of C++ which picks the messages out the queue and then services them from a thread pool (my favourite but will generate fear and loathing from our VB coders).
  • Use the triggering to start apps to service the messages. I don't see this working under heavy load due to limits in NT.
  • Anything else?
Has anyone out there any experience in trying to do such a thing? I don't like the look of it much as the NT app looks like the weakest link."

1 of 24 comments (clear)

  1. Why not use VB? by Anonymous Coward · · Score: 0, Funny

    Apart from the obvious problems with memory leaks and some bugginess, why not use VB instead of C++? Sounds like you already have some VB coders there. I've written a few apps that move messages between the mobile phone network (SMS) and two MQSeries message queues, and I've found using VB with MQSeries is a cinch, provided you look at their examples.