| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message validation in a channel exit on Windows 2000 |
« View previous topic :: View next topic » |
| Author |
Message
|
| dbalaam |
 Posted: Wed Apr 14, 2004 10:27 pm Post subject: Message validation in a channel exit on Windows 2000 |
 |
|
Newbie
Joined: 13 Apr 2004
Posts: 2
|
I'm considering using a channel exit to validate messages before they are placed on the destination queue. The queue manager is running in a Windows 2000 environment. I think that a message exit would be the right one to use to perform the checks. Messages that don't pass some relatively simple validation are to be rejected.
Has anyone had any experiences, good or bad, with this sort of exit in a Windows environment? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Apr 15, 2004 3:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why go to the trouble to write a message exit to do this?
Why not create a simple MQSeries application, and route messages to this app for validation before they go to the "real" app?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Thu Apr 15, 2004 6:35 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Why moving application logic into mq ??
This will require taht the MQ-sysprog. have to change the exit whenever the application developers changes just a tiny part.....
I don't like to add business logic to MQ, it's a application area !
Stick to Jeffs proposal 
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| dbalaam |
| Posted: Thu Apr 15, 2004 2:11 pm Post subject: |
|
|
Newbie
Joined: 13 Apr 2004
Posts: 2
|
Two buts:
1. My client doesn't want any suspect messages to arrive on any queue.
2. The validation is generalised and would be metadata driven, with the metadata managed by application owners, rather than MQ admins |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 15, 2004 4:37 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| dbalaam wrote: |
| 1. My client doesn't want any suspect messages to arrive on any queue. |
Then your client should spend their time making sure their applications are correct and do not produce invalid data.
Ask them how they expect a channel exit, that will only affect messages that flow over a channel, to fix data before it shows up on a transmission queue.
| dbalaam wrote: |
| 2. The validation is generalised and would be metadata driven, with the metadata managed by application owners, rather than MQ admins |
Because, of course, the application owners will always get the metadata correct, and never do anything to cause an issue with MQSeries because of a mistake on their part. 
The point is still this: If your client has an issue with application level data, the correct place to fix that issue is at the application level.
If the data is coming in from an external party, then it should be validated by a gateway application running on the gateway queue manager. If it fails validation, it should go back to the sender's queue manager.
If it's coming from an internal application, that they have the source code for, they should fix the internal application so that it is incapable of putting bad data on a queue.
If it's coming from an internal application that your client does not have the source code for, then they should still have a regular application developer spend time writting a regular MQSeries application, rather than having an MQSeries systems programmer (not an MQ Admin) write a channel exit that will only validate data that crosses queue manager boundaries.
Or at least, have an MQSeries systems programmer write an API exit that will interecept the application calls, and return bad codes if the application programmer tries to write invalid data to a queue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 15, 2004 5:16 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Or stick MQ Intergrator in the mix, and let it look at the messages, and route them accordingly, or even "fix" them before passing them on.
A channel Exit can technically do this. But its not the right way in the long run.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
