MO71 is run by a number of our customers in a shared environment, that is any setup where multiple users in a department want to ensure they are using the same version of the executable, similar queue manager configuration, and share any resources that would make their lives easier. Over the years we have added a number of features to make this kind of collaboration easier.
- MO71 executable size
It is probably worth saying right up front, that the MO71 executable is small enough that loading it from a network drive is not onerous. We have many of our customers successfully doing this without any problems. It is only around 3MB in size, and thus small enough to easily run from a USB key if you wanted to.
- Location of the MQMON.CFG file
The MQMON.CFG contains all your hardened configuration from the details of where your queue managers are, to the colour scheme you want to see on all your dialogs. By default the MQMON.CFG file will be written in the same directory as your executable. If the executable is stored in a shared directory, you may not want your MQMON.CFG file to be stored there too. You can choose a different location by starting the mqmonntp.exe with the -f parameter to give a different directory name for your configuration to be stored in.
While it is possible to have numerous users all running from one MQMON.CFG file, you would have to put up with a consensus on colour schemes, column arrangements, dialog screen positions, fonts, histories and more, and of course everyone’s changes would be applied to the same file. Instead we recommend having your own version of the MQMON.CFG file. There is some data that is useful to have centralised, and for that we suggest using a Master Config file – more in a moment.
- MQGem Licence File
All the MQGem Software products are licensed by means of an mqgem.lic file, which by default is located in the same directory as the executable (even if you have used the -f parameter to change where your configuration is stored). If your department has purchased a Diamond or Enterprise licence, then it makes sense for that licence file to also be stored centrally with the executable. However, if you have an individual Emerald licence, then you have a choice; you could either store it locally, and you can change the location MO71 will search by setting the MQGEML environment variable to point to a different directory, or you could combine all the Emerald licences together into one mqgem.lic file, and store that centrally. This would have the advantage that updating the licences could be done centrally without the individual users being aware.
- Renewal and reminders
When using central licence management (see above) it may not be appropriate for every single user to be notified when the licence is running out. By default MO71 will start reminding you when there are 30 days left on your licence. One model might be to have most users tune down these notifications by setting the MQGEMLR environment variable to a small number of days, say 7. Then one or two system administrators, perhaps the ones with control over the shared drives where the executable and licence files are kept, are responsible for renewing the licences and they keep the notifications on, and perhaps even set it to a longer time frame such as 90 days. Remember, you don’t have to wait until there is only 30 days left before renewing your licence. You can renew at any time, and you don’t lose any time, your new licence file will simply extend the current licence by whatever period has been purchased. In fact we would recommend that you renew your licences well before the expiry period to avoid any unexpected outage as a result of a sluggish Purchasing Department 😉
- Licence Command
When using licences that are renewed on your behalf, you may prefer to have a local copy, and MO71 provides a licence command, configured on the General tab of the Preferences dialog, where you can add a command to copy a new version of your licence file from a central location once MO71 detects you have MQGEMLR days left. This means that you don’t have to personally remember to go a take a new copy, since MO71 does this automatically for you.
- Master Configuration File
One of the reasons some MO71 users previously chose to have a centralised (and thus shared) MQMON.CFG file, was because they wanted the details of the queue managers to be centralised. This led us to add a feature to MO71 where you can provide a master configuration file which contains the common queue manager details, but you still have your own configuration for all the personalised things we mentioned earlier. Each time MO71 starts up, it compares the queue managers configured in your setup against those in the master configuration file, and adds, or changes, any locations in the master file to bring your configuration up-to-date. Note that you can still have your own queue manager definitions in addition to those in the master file. To specify a master configuration file to use, you point to the file with the -j parameter.
- Shared Filters
MO71 has a very powerful filtering language, and many of our users have written very useful, and often complex filters. Using the Filter Manager makes it easier to create filters when they start to be complex, and beyond what can be seen on a single line. Each filter is given a name in the Filter Manager. You can share these filters with all your colleagues with a Shared Filter file which they can import in a similar manner to the Master Config file above. At startup of MO71 the filters in the file are merged into the local configuration to ensure you have the latest set of definitions.
I hope these points help you when thinking about using MO71 in a shared environment. If you have any questions, or extra points to consider, please don’t hesitate to get in touch, either with a comment below, or through any of the usual channels.
If you don’t have a licence and would like to try out MO71 then send an email to firstname.lastname@example.org and a 1-month trial licence will be sent to you.