| Author |
Message
|
| Imran |
 Posted: Wed Jan 07, 2004 4:10 am Post subject: CHAD Exit - Determine Partner QM |
 |
|
Newbie
Joined: 12 Dec 2003
Posts: 1
Location: W Yorks, UK
|
As part of a Clustering solution I am creating a CHAD exit which will modify properties of the Cluster sender and receiver channels depending on the initiating partner queue manger.
The problem I have at the moment is that to determine the Partner Queue Manager I am interrogating the PartnerName field in the MQCXP. Whilst this works for the Cluster Sender Channel, the Cluster Receiver's PartnerName field is blank, hence I am unable to determine the Queue manager initiating the request. IBM say that this works as is expected, and as the CHAD exit is called early in the initiation process many fields in the MQCD and MQCXP will be blank.
Has anyone else come across this problem and found a solution. Or can anyone suggest a way of determining where the initiating channel originates from.
Thanks[/i] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 07, 2004 5:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I haven't worked with CHAD exits, or really any exits, but I wonder if you can get the IP address of the sending side?
Of course this would require maintaining a map between IP address and QM names. But it seems like you're going to be maintaining a map based on QM names anyway.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 07, 2004 10:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
What properties are you going to change? And why?
If you really have a valid reason for different settings between different QMs, wouldn't it be a LOT eaisier just to create another set of channels?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| missing_link |
| Posted: Thu Jan 08, 2004 4:27 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
We are in the proceess of implementing a fairly simple CHAD Exit/Security Exit routine. Within the CHAD exit all we do is to reset the security exit that this queue manager runs - obv this is OS dependant. However you can retrieve the other queue manager name ie PartnerQMGR from the security exit.
ash. |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Jan 09, 2004 12:00 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| The ReplyToQMgr field have the Original QMgr sender. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Sun Jan 11, 2004 12:16 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hmm, how can the ReplyToQmgr field be present in CHAD exit ??
Anyway typicly CHAD exits works together with the security exit.
My way of doing this is use CHAD for modifying desired parameters e.g. security exit, and other parameteres especialy on connections defined from the other end. The parmeters for CHAD normally comws from the channel models: SYSTEM.xxxx
One of mine CHAD's just adjusts the SCYEXIT parms, to my customers qmregs can do clustering on a large variaty of platforms.
And when QMGR is trying to establish connection let the security exit deside if connection should be alloved or not. And if MCAUSER and other things should be modifyed in regard to the connection. the MQCD is available to the security exit also.
Typicly Security exits works in pairs, so both ends uses a defined security protocol, who sends what and when.
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 |
|
|
| LuisFer |
| Posted: Tue Jan 13, 2004 11:56 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
I'm confuse,  what's is a CHAD Exit? , i'm understood that is a Channel Message Exit.
We have implemented a Message Chl Exit to validate the Partner QMgr.
At the beginning we validate the PartnerQMgr field, but sometimes the msg went with Blanks .
Finally, we validate the Partner with the ReplyToQMgr field, & works fine. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Jan 13, 2004 12:40 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
CHannel AutoDefinition exit. It's invoked when the Queue Manager is going to dynamically create a Receiver channel in response to a connection from a Sender channel that doesn't have a corresponding Receiver. This feature is enabled/disabled at the Queue Manager level.
It's a 'kinda' reduced administration thing. But can lead to security problems.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| LuisFer |
| Posted: Wed Jan 14, 2004 9:14 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed Jan 14, 2004 10:19 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
I can only say welcome to the club. 
Anyway, when the channel is established between different platforms/companies etc. it's a good idea to have a CHAD exit to fix such "small" details. especially when dealing with Z/OS vs. all other platforms, because of the way of specifying the security exits...
The CHAR can just overload the parameters that your site don't like, so you'll allways get the right exits, timeout etc.
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 |
|
|
|
|
