| Author |
Message
|
| sandios |
 Posted: Thu Jun 16, 2016 10:47 pm Post subject: access data in config folder |
 |
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
Hi, elements deployed in broker on windows OS is:
C:\ProgramData\Application Data\IBM\MQSI\components\XXXXX\3550ec49-5501-0000-0080-b52a822a3e59\config
My question is... in linux¿¿¿?¿? where?
Greetings and thanks. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jun 17, 2016 4:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why?
You shouldn't be messing with these.
Also, there are only a small number of "top level" directories that IIB uses on linux. So it can't be under one of a very large number of different places.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 17, 2016 4:51 am Post subject: Re: access data in config folder |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sandios wrote: |
| My question is... in linux¿¿¿?¿? where? |
Wherever you told broker to store them. Exactly the same as on Windows.
The path you quote is the default value. That information could be stored in C:\IBM\Stuff if you so desired.
And wherever you store it, either on Windows or on Linux, you should make sure there's enough space and then ignore it. Modifying that data outside the supported commands is a one-way road to misery. Even looking at it is a very hard way of determining something the supported commands can tell you easily.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sandios |
| Posted: Sun Jun 19, 2016 11:48 pm Post subject: ok |
|
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
OK thanks. I do not want to modify these files, just consult them.
I understand that it is not recommended to consult these files, I know.
Thank you. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 20, 2016 4:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What are you trying to find out by consulting these files?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 21, 2016 2:39 am Post subject: Re: ok |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sandios wrote: |
| I understand that it is not recommended to consult these files, I know. |
So you're doing it why? Getting in touch with your inner lemming?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sandios |
| Posted: Thu Jun 23, 2016 3:53 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
| Is it advisable to access files in folders deployed broker (XML, JAR ...) of each execution group? ... for read files... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 23, 2016 4:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sandios wrote: |
| Is it advisable to access files in folders deployed broker (XML, JAR ...) of each execution group? ... for read files... |
No, and why would you ever want or need to?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sandios |
| Posted: Thu Jun 23, 2016 4:02 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
| Deployed information files. information can not be obtained with UDP. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 23, 2016 4:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What does that mean "deployed information file" ?
Are you including some additional configuration file in your bars?
If you don't know exactly what version of your code - including any configuration files - are deployed to your environment, then you have to fix that problem before you do anything else.
If you are trying to make some kind of configuration used by your internal code available for dynamic updates, then you should use a UDP to specify the location of that file. OUTSIDE the broker's internal directories.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| sandios |
| Posted: Thu Jun 23, 2016 4:21 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
| I'm sure you're right. But ... what consequences can be deployed reading these files ?, I could give examples of malfunction by this cause? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 23, 2016 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If nothing else, you'd have to give anything that wanted to read these files the necessary permissions on the file system.
Which is likely done by adding it to the mqbrokers group - or making enough of the broker private file store publicly readable to get to these files.
Which makes too much else very very vulnerable.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| sandios |
| Posted: Thu Jun 23, 2016 4:34 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2016
Posts: 27
|
Yes, you are right. But now in my system the user has permission to read in those folders.
I will look for alternatives, but did not want to host the files elsewhere.
Thank you. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 23, 2016 4:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's not a matter of "elsewhere".
It's a matter of "in some more sensible location on the same machine's file system".
Even as simple as the broker user's home directory.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 24, 2016 7:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sandios wrote: |
| Deployed information files. information can not be obtained with UDP. |
Flows should not be reading information files. IIB is not WAS and it's not intended that flows read "config.xml" or similar.
If you don't want to or can't use UDPs, there are a number of other, better mechanisms to get dynamically variable information into a flow.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
