I would like to see this document expanded to include the IBM WebSphere MQ Explorer plugin as well. We are considering rolling IBM Explorer for z/OS (with the CICS and MQ plugins) across the enterprise, and this document seems to only cover the CICS plugin.
Additional information from the MQ side would be valuable.
Posted by Dave Nice on 25 November 2013 at 2:12
Because of the difficulties currently with MQ Explorer not providing an Installation Manager plug-in I've avoided going into too much detail about it.
From a deployment perspective, MQ Explorer is just the same as any other Eclipse plug-in that you could install into any other Eclipse environment.
Could you give me a bit more of an idea about what kind of additional information would be useful? I'm sure it would be relevant to other plug-ins, too!
Posted by Kevin Wick on 25 November 2013 at 13:34
As far as MQ Explorer is concerned, I'd like to see each section that refers to IBM Installation Manager and the ability to control remote system connections revised to specifically exclude MQ Explorer. It needs to be made clear that MQ Explorer does not support IBM Installation Manager (and the silent install option), as well as the ability to have users load connection information from a global location.
Posted by Kevin Wick on 25 November 2013 at 13:35
There's a good number of sentences in these sections that refer to the IBM Explorer products in general terms ("There are many ways of deploying the Explorer..", "Installation Manager also provides silent installation and upgrade..", "Using silent installation, you can push the Explorer products down to a user's workstation.."), which implies all Explorer products have the these features. However, this is not the case. It should be made clear that MQ Explorer does not have these capabilities.
Posted by Kevin Wick on 5 December 2013 at 7:13
It appears that Appendix B, "Using plugin_customization.ini to customize users' workspaces", is missing a step. After customizing one of the delivered plugin_customization.ini files (or creating your own), you must edit eclipse.ini to point at the plugin_customization.ini you want Eclipse to read. Per IBM Level 3 Support, Eclipse is not reading any of the delivered plugin_customization.ini files by default. See PMR 02604,122,000 for details.
Posted by Dave Nice on 6 December 2013 at 9:03
A couple of weeks ago I asked for this to be added:
z/OS Explorer and plain Eclipse do not come with the convenience of a plugin_customization.ini provided by default. To use the technique in these environments, you must add your own. Create a blank file called plugin_customization.ini in the same directory as the installation's eclipse.ini file. In your eclipse.ini file, before any -vmargs lines, add the following lines which will enable the pluginCustomization technique: