| Author |
Message
|
| dblack9 |
 Posted: Fri Jun 13, 2003 5:59 am Post subject: How to force the userid in a message put from a flow |
 |
|
Newbie
Joined: 13 Jun 2003
Posts: 3
Location: Boulder, CO USA
|
I have a customer who wants to insure the a message output from his flow ALWAYS has the same userid (mqsiadm).
Currently this is somehow happening with no special coding in his WMQI test and development environments. I created a new WMQI environment called UAT and it puts the message with the userid of the application which put the original message on the input queue to the flow.
I have compared WMQI and MQSeries in all three environments and can find no special coding nor any differenced between them, yet the message output in the UAT environment remains that of the putting application and is not always mqsiadm.
The reason for this is that the putting application is resides on remote qmgrs and there is no guarrantee that this app is running under the mqsiadm id.
I am looking both for a legitimate way to force the is to mqsiadm and as to how the customer is doing this under the covers illegitimately. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jun 13, 2003 6:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Have you looked at the properties of the MQOutput node? They're documented in the Control Center help. |
|
| Back to top |
|
|
| mehedi |
| Posted: Mon Jun 16, 2003 5:22 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
"Currently this is somehow happening with no special coding in his WMQI test and development environments"
This happen because the service user id for the broker is "mqsiadm".
This was specified on the mqsicreatebroker command service userid option.
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
|
| whiting |
| Posted: Mon Jun 16, 2003 6:45 am Post subject: |
|
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
In the UAT environment the MQOutput nodes are probably configured to pass all context. However it doesn't matter from an MQ perspective what user name is attached to a message, unless the receiving application is coded to filter messages by user name.
//Bill |
|
| Back to top |
|
|
| dblack9 |
| Posted: Mon Jun 16, 2003 8:56 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2003
Posts: 3
Location: Boulder, CO USA
|
Thanks Guys for your replies. Yes you are both correct in what you say. I created the Broker with a domain id instead of a local id, thus the id issue.
The problem with a message being sent without the userid mqsiadm in it is that it is being sent to a mainframe and RACF, (the security manager) is only setup to allow the message to be read if it has the userid mqsiadm.
And yes, If I were coding it I would force the userid to be mqsiadm in the mqoutput node of the flow, but the customer does not want to change his code.
Thanks for the input between it and studying the manuals I have learned alot. |
|
| Back to top |
|
|
|
|
