| Author |
Message
|
| skopparapu |
 Posted: Wed Dec 24, 2014 12:12 pm Post subject: MQ User-id |
 |
|
Novice
Joined: 04 Mar 2014
Posts: 19
|
Hello All. I got stuck with a production issue in my project. I am actually trying to trigger the data in a queue to a shared folder in a server.
Now when data arrives into the queue, if trigger conditions are met then MQ invokes my program(specified in process definition) and trying to write the data on queue to shared folder in a server. But this is failing since I do not have access to the server where data needs to be written.
I claim for access and they ask me for user-id. Can anyone please tell me which user-id do I have to specify ? I am confused how come MQ can make use of my user-id to write data to file  |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Dec 24, 2014 12:22 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
MQ doesn't write data to your filesystem; rather, MQ puts messages to queues that it owns and manages.
MQ messages reside in queues. Your app needs authority to MQCONNect to the qmgr, and authority to MQPUT and MQGET messages to/from queues, and perhaps other authorities.
Authority to use MQ resources is different from access to the filesystem where your application and data live.
Your application is launched by the o/s only if your ID has execute authority on the filesystem where the application resides. How does your app write to the filesystem? With fwrite() call? Something else?
If your application tries to write to the filesystem, then you need write authority, too.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| skopparapu |
| Posted: Wed Dec 24, 2014 4:06 pm Post subject: |
|
|
Novice
Joined: 04 Mar 2014
Posts: 19
|
Bruce you are saying like OS invokes my application, then which user-id it uses to execute that as we have a lot of users on that server(where my application resides).
If I invoke the application manually then it would be my user-id needs to be checked whether having access or not but what would be the case when it is automatically kicked off by OS(as you said) ?
Thanks a lot for your reply...  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 24, 2014 4:54 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
If you manually execute the app, your userid will be used by the o/s to determine
1. if you have execute permissions to the filesystem where your app resides
2. if you have MQ authorizations to use MQI commands
3. if you have write permissions to the filesystem you are trying to write to
Are you saying that this works when you execute the app manually?
If the trigger monitor starts the app, then it (the trigger monitor and/or your app) have insufficient write permissions to the filesystem.
Please be specific as to the error you are seeing. Is it logged in the o/s log?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| skopparapu |
| Posted: Thu Dec 25, 2014 4:28 am Post subject: |
|
|
Novice
Joined: 04 Mar 2014
Posts: 19
|
Bruce Trigger monitor is invoking my app and fails to write data to destination.
Even if, I execute may app manually its not working since I don't have access to the server to which my app trying to write data into.
One thing here I am not getting is if " I am not executing the app manually then which user-id does the OS/MQ uses to invoke my app and write data into destination ? "
Note: As you said I have seen Event viewer logs and I could find nothing  |
|
| Back to top |
|
|
| skopparapu |
| Posted: Thu Dec 25, 2014 4:32 am Post subject: |
|
|
Novice
Joined: 04 Mar 2014
Posts: 19
|
| Bruce I was trying to say you this which u said : " If the trigger monitor starts the app, then it (the trigger monitor and/or your app) have insufficient write permissions to the file system. " |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 25, 2014 1:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| skopparapu wrote: |
Note: As you said I have seen Event viewer logs and I could find nothing |
So there is one other avenue you need to explore. Run the trigger monitor as a foreground process. Put a message on the triggered queue and see all the output the trigger monitor generates. There should be something in there to give us a clue as to what is happening. 
_________________
MQ & Broker admin
Last edited by fjb_saper on Fri Dec 26, 2014 7:37 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 25, 2014 3:04 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| skopparapu wrote: |
| Even if, I execute may app manually its not working since I don't have access to the server to which my app trying to write data into. |
What o/s? Windows or UNIX?
Please use more precise computer technical terminology.
What does "I don't have access to the server" mean?" Do you mean your userid doesn't have execute permission to the filesystem where your application resides? Or, do you mean that your userid is not known to the o/s?
What or who starts the trigger monitor? Does it start automatically when the qmgr starts?
Is this a new application? Or, is it an application that has been modified recently?
Is the first time you have attempted to trigger an application to start?
Are you a programmer? Is this your application?
Does the application produce and/or consume MQ messages successfully? Does the application actually touch the filesystem (change date/time, for example)?
What language is the application written in? Copy/paste here the command that writes to the filesystem.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
