ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » The order in whcih exits are called

Post new topic  Reply to topic
 The order in whcih exits are called « View previous topic :: View next topic » 
Author Message
Anuradha Bose
PostPosted: Thu Jan 08, 2004 9:36 pm    Post subject: The order in whcih exits are called Reply with quote

Newbie

Joined: 08 Jan 2004
Posts: 7

Hello

If I have security, message & send exits, then
I know they are called in that order. But does anyone know what order API exit (e.g MQPUT exit) will be called in reference to all these exits?

Also is there a problem running any of these channel exits and API exits together?

a. bose
Back to top
View user's profile Send private message Send e-mail
JasonE
PostPosted: Fri Jan 09, 2004 2:33 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

The api exits get called very early on in the processing of an MQ message so I would guess they get called first. Note they also get called as a result of API's within MQ when passing the messages around etc.

There should be no problem mixing exits - they are all independant, but of course this may depend on what you code the exit to do!
Back to top
View user's profile Send private message
Anuradha Bose
PostPosted: Fri Jan 09, 2004 8:01 am    Post subject: Reply with quote

Newbie

Joined: 08 Jan 2004
Posts: 7

Thanks for the reply


I am planing to change message payload in MQPUT exits. Was wondering if that will mess up other exits running on the system.
Also, on the same lines, I was wondering what happens if I change the message payload of a REFERENCE message.B'cos the doc. says that reference messages are used in conjunction with message exits, if I change mesasge payload (i.e. add something in front of it as a header) then reference messages will not work correctly? Presumably in mesasge exit the user is expecting the *original* message, ya?

Should I assume, this is the order the exits get called:

On sending side:
API exit - security-message-send

On receiving side:
receive exit-message-security-API exit

thanks again
Back to top
View user's profile Send private message Send e-mail
EddieA
PostPosted: Fri Jan 09, 2004 9:33 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Taking your 2 questions from the 1st paragraph.

If you change the payload in the MQPUT exit, then this is what all the other exits will see, as this exit would (should ) be called ahead of the others. Just as if your application wrote the 'modified' payload. They won't know any different.

For a reference message, when you actually do the PUT, there is NO payload. All you write is the header. It's the responsibility of the Message exit on the Channel to actually add the payload to the message for transmission. So, if you want to add some extra data, then that might work, as long as your Message exits know of it.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ API Support » The order in whcih exits are called
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.