| Author |
Message
|
| hilltops |
 Posted: Fri Nov 22, 2013 12:14 pm Post subject: Specifying MQSI_WORKPATH at Installation of IIB 9.0.0.0 |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
Hello,
Help required please. I am installing IBM Integration Bus Version 9 on a Linux server and am wondering whether it is possible to specify the location work direction at installation. The default location is /var/mqsi, and is given by the environment variable MQSI_WORKPATH after installation. But I want to be able to specify a different location. If this is possible, given that with IIB9, it is possible to have multiple installations of the product on the same server, I want each installation to have its own work directory. If this is not possible to do at installation time, it looks like one is stuck with having multiple installations sharing the same work directory (ie /var/mqsi ) - pretty ugly state of affairs, methink. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Nov 22, 2013 12:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'm confused - a broker's workpath is specific to a given broker not a specific installation (and is specified on the create command) by the -w parameter.
So why not just create different brokers that use different installations with different workpaths? What am I missing?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hilltops |
| Posted: Fri Nov 22, 2013 1:17 pm Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
Yes, it is possible to specify the work directory at Broker creation time with the -w option, which is optional. But if you don't specify it, the broker's work directory defaults to that of the installation (which is /var/mqsi).
I have just done an installation and without creating any brokers yet, the env variable MQSI_WORKPATH has a value of /var/mqsi, and it is here that a lot of stuff has been deposited.
Now, imagine if I were to install another version of IIB on the same server, say version 9.5.0.1 (some time in the future). If there is no way of giving this installation a different work directory, it will end up sharing the same work directory as the first installation which is at 9.0.0.0. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 22, 2013 1:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hilltops wrote: |
| Now, imagine if I were to install another version of IIB on the same server, say version 9.5.0.1 (some time in the future). If there is no way of giving this installation a different work directory, it will end up sharing the same work directory as the first installation which is at 9.0.0.0. |
Fair point. Sounds like either a PMR or an RFE.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 22, 2013 4:10 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'm confused.
I currently have three versions of broker installed and sharing the same workpath without issue.
What's the concern? |
|
| Back to top |
|
|
| hilltops |
| Posted: Fri Nov 22, 2013 5:25 pm Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
Ah - the question is whether there is any potential problem in store in having multiple installation share the same work directory.
If an earlier installation is removed, uninstalled - is there a potential that it might remove resources that are required by the other installations?
If it were possible to specify the work directory at installation time, one could put each installation in its own work path, thus eliminating this issue completely. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Nov 22, 2013 11:37 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
by installation, do you mean a particular version of Broker (say 7.0.0.5) or do you mean a broker itself with 'mqsideletebroker'
The MQSI_WORKPATH setting or /var/mqsi is the default root for brokers created without the -w option.
The broker software can handle multiple brokers on your systems but if you doubt me then why not try the following:-
1) Backup all of /var/mqsi with something like tar.
2) Create a new broker with mqsicreatebroker
3) Delete the broker with mqsideletebroker
4) extract the backup into somewhere like /var/tmp/mqsi
5) compare the trees of the existing brokers to see if a) any files are missing or b) any files have been updated between the time of 1) and 5).
Obviously, the existing frokers should be stopped for the purposes of the test.
If there are actual differences between the trees then it would be time to raise a PMR (IMHO). Note, just a timestamp difference on a directory file is not enough to trigger a PMR.
You could even write a simple script that traverses the directory tree in 1) that does an md5sum on each and every file and writes the results to an output file.
Run it before and after creating/deleting of the test broker and you will have your answer when you do a 'diff' of the two files.
As you can see, there are many ways to actually test this out. Go for it and let us know what you find. We are always eager to improve our understanding of the product.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| hilltops |
| Posted: Sat Nov 23, 2013 2:55 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
Thanks guys.
I just wanted to know if it was possible to decide on the work directory at installation time and check if I had not missed some steps from the installation process. From your contribution is seems that:
1) One cannot select the work directory at installation time
2) All installations will share the same default work directory
3) A broker can be given a different work directory at broker creation time with the -w option. That way it will not use the default which is shared by all the installation on the server.
If I have multiple installation on the same server, I will not let the brokers share the same work directory for fear of unforeseen effects. I will create the brokers with -w to keep each installation, something like /var/mqsi/<broker>. That way each broker has its own work directory within the shared work directory. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Nov 23, 2013 8:44 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You premise that ALL the files relating to a particular broker can be stored in a tree specificed by the -w option may well be flawed.
I have an IIB V9.0.0.0 system on an RHEL VM.
I created a directory /var/mqsi/DEVBRKR
Then I created a broker using the following command
| Code: |
mqsicreatebroker DEVBRKR -q DEVBRKR -i broker -u Ummagumma -w /var/mqsi/DEVBRKR
|
A tree containing the
common
components
config
shared-classes
was created in the directory specificed by the -w option.
However, there is still a directory in the /var/mqsi/registry called surprisingly enough called DEVBRKR
What you really need to do is to carry out the tests I suggested and satisfy yourself that using the default MQSI_FILEPATH won't cause you any problems.
Remember that where bits for different brokers are included in the same directory the software conviently uses the brokerhame either as a directoryname and all the bits specific to that broker are contained within that directory tree OR the files use the Broker Name in the filename itself
for example
| Code: |
DEVBRKR.mqsifindmqpath.userTrace.bin.0
|
It is not that difficult to test this out. I really do think you are worrying about nothing.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| hilltops |
| Posted: Sat Nov 23, 2013 9:43 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
| Thanks - Looks like am worrying too much. Will try the suggested experiment at work on Monday. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Nov 23, 2013 9:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Note that the behavior of the -e <SharedWorkPath> may be different than the behavior of the -w <WorkPath>.
For good and solid reasons.
Although overly and unnecessarily clunky having to know you have to use different flags in different use cases. |
|
| Back to top |
|
|
|
|
