Installing into Eclipse environments

Install WebSphere® MQ Explorer into your own Eclipse environment or Eclipse-based product to help with developing Java™ applications or to develop your own extensions.

Before you begin

If you are using a version of Windows with User Account Control (UAC) such as Windows 7, UAC is enabled, and your Eclipse-based product is installed into a directory under UAC such as C:\Program Files, then you must run the Eclipse-based product with elevated authority (Run as Administrator) before installing the IBM® WebSphere MQ Explorer feature into it. Once installed the product can then be run without elevated authority.
Note: If you have placed the IBM WebSphere MQ Explorer plugins in another Eclipse environment, in order to use CipherSpecs TLS_RSA_WITH_AES_128_CBC_SHA256 and TLS_RSA_WITH_AES_256_CBC_SHA256 when in FIPS mode, you must have IBM JREs 6.0 SR13 FP2, 7.0 SR4 FP2 or later.

About this task

IBM WebSphere MQ Explorer is Built on Eclipse as a stand-alone application using the Eclipse Rich Client Platform. You can also install IBM WebSphere MQ Explorer into your own Eclipse environment or an Eclipse-based product, to aid with developing Java applications with IBM WebSphere MQ, or developing your own extensions to IBM WebSphere MQ Explorer. To do this you need an environment based on Eclipse 3.6.2 that includes the Graphical Editing Framework (GEF) tools. For details of which Eclipse-based products are supported, see the system requirements page for IBM WebSphere MQ at https://www.ibm.com/software/integration/wmq/requirements/.

Procedure

To install into a compatible Eclipse-based environment:

  1. Click Help and then click Install New Software in the Eclipse environment.
  2. Click Add and then click Archive, and then browse to the mqexplorer/eclipse directory inside the MQ installation directory. Select the file MQExplorerSDK.zip.
  3. Click OK after optionally typing a name for the local site.
  4. A category of IBM WebSphere MQ Explorer is displayed. Expand this category and select WebSphere MQ Explorer and optionally, the translations.
  5. Click Next and follow the instructions. Then click the button to restart Eclipse (or the Eclipse-based product).
  6. MQ Explorer is available as a separate perspective. To view, click Open perspective, and then click Other.

What to do next

Local queue managers

This procedure is sufficient if IBM WebSphere MQ Explorer is being used to administer remote queue managers. If there are local queue managers to administer, you must run the Eclipse-based product with the required environment settings for your operating system. In addition, the Eclipse-based product must be a 32 bit application on Windows and Linux® x86 platforms, and it must be a 64 bit application on Linux x86_64 platforms.

On Windows:

Set the PATH environment variable to include the bin and java/lib directories of your IBM WebSphere MQ installation before running the Eclipse-based product. You can use the setmqenv command with the '-x 32' option to do this because IBM WebSphere MQ Explorer is a 32 bit application on all Windows platforms. For example, if IBM WebSphere MQ is installed in directory C:\Program Files\IBM\WebSphere MQ, enter the following command: 
C:\Program Files\IBM\WebSphere MQ\bin\setmqenv -s -x 32

On Linux x86:

Set the LD_LIBRARY_PATH environment variable to include the java/lib and lib directories of your IBM WebSphere MQ installation before running the Eclipse-based product. For example, if IBM WebSphere MQ is installed in /opt/mqm: 
export LD_LIBRARY_PATH=/opt/mqm/java/lib:/opt/mqm/lib:$LD_LIBRARY_PATH

On Linux x86_64:

Set the LD_LIBRARY_PATH environment variable to include the java/lib64 and lib64 directories of your IBM WebSphere MQ installation before running the Eclipse-based product. For example, if IBM WebSphere MQ is installed in /opt/mqm: 
export LD_LIBRARY_PATH=/opt/mqm/java/lib64:/opt/mqm/lib64:$LD_LIBRARY_PATH