| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Putting messages into MQ series queue - enterprise solution |
« View previous topic :: View next topic » |
| Author |
Message
|
| neq1337 |
 Posted: Wed Jan 21, 2015 12:57 am Post subject: Putting messages into MQ series queue - enterprise solution |
 |
|
Newbie
Joined: 21 Jan 2015
Posts: 1
|
Hi everyone,
For the starters, please forgive me my lack of expert knowledge and but I am just starting with MQs  . I was trying to find some info on this topic on the forum but I couldn't find any that specifically answered my question.
We are trying to somehow standardize the way messages are put into the queues to have more control over it, possibly implement some monitoring of the scripts and be able to support MQs globally (I am working in an internal service centre that now will also support MQ flows in local business units of our company).
Most of the MQ series servers run on Windows Server and the messages are put and extracted using batches (simple f2m/m2f, sometimes they are also zipping the files).
I am wondering if this is a common way of putting messages into the queues? We hundreds of different business applications, so batches seem to be quite simple to adjust, but difficult to monitor, edit etc. Is there any enterprise solution that we could use instead of it that would be simple to adjust to any application? |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Wed Jan 21, 2015 1:30 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
I guess it depends on why you want to do this kind of thing. However, I think the short answer is 'no' there isn't a 'common' way of doing this. Each persons requirements, budget and expertise tends to be slightly different so there are lots of different solutions which give you different capabilities. For example, you could just implement wrappers around the MQI. This would allow you to control/monitor what you applications do. You could implement an API crossing exit which does a similar thing. You could use MQ Message Broker and mandate that all messages flow through the appropriate input/output nodes. This would allow you to control who does what to who. Plus many more solutions.
There are, of course, advantages and disadvantages with each approach.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jan 21, 2015 3:05 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Sounds like you are more concerned with managing data movement than with the details of MQI programming.
If you want F2M and related functions, this not part of base MQ. You can easily develop these using WMB or IIB or you can use the optional MQ feature of (chargeable) managed file transfer component which is an alternative. This has centralized monitoring.
MQ FTE (MFT) would probably be a good place to start looking. If you wanted something much less expensive - look at Capitalware's UFM.
If you really are interested in managing MQI programming then the vendor product Cressida InQuestâ„¢ for WebSphere MQ might be worth a look.
_________________
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
|
|
|
|
