+

Search Tips   |   Advanced Search


Install - WebSphere MQ v7.5

  1. Quick installation
  2. Choose an installation name
  3. Multiple installations
  4. Choose a primary installation
  5. External library and control command links to primary installation
  6. Features that can be used only with the primary installation on Windows
  7. Uninstall, upgrading, and maintaining the primary installation
  8. Choose an installation location
  9. Choose what to install
  10. Plan the installation on Windows systems
  11. Plan the installation on HP Integrity NonStop Server
  12. Checking requirements
  13. Preparing the system
  14. Install WebSphere MQ
  15. Modify your installation
  16. Post installation tasks
  17. Install a WebSphere MQ client
  18. Install a WebSphere MQ client on AIX systems
  19. Install WebSphere MQ client on HP Integrity NonStop Server systems
  20. Install a WebSphere MQ client on HP-UX systems
  21. Install WebSphere MQ client on Linux
  22. Install a WebSphere MQ client on Solaris
  23. Install a WebSphere MQ client on Windows systems
  24. Modify the client installation on Windows
  25. Install WebSphere MQ Advanced Message Security
  26. Verify a WebSphere MQ installation
  27. Set up the server using the command line
  28. Connecting a WebSphere MQ MQI client to a queue manager, using the MQSERVER environment variable
  29. Verify a client installation using WebSphere MQ Explorer
  30. Set up the server using WebSphere MQ Explorer
  31. Set up the client using WebSphere MQ Explorer
  32. Test communication between a client and a server
  33. Verify the installation of WebSphere MQ Telemetry
  34. Uninstall WebSphere MQ components
  35. Uninstall


Quick install example

  1. Review readmes

  2. Create file system

  3. Copy MQ install media to target host

      scp -r /path/to/MQ/media myhost:/usr/mqm

  4. Optional: Choose installation name

    To get name from an existing install...

      ssh MyMQHost
      /usr/mqm/bin/dspmqinst

  5. Log on to target host as user root and...

      cd /usr/mqm//path/to/MQ/media/server/

  6. Use smit to create mqm user and group

    Add user mqm to group mqm

  7. Increase number of file descriptors and system resource limits

  8. Install MQ

  9. Verify installation

    Create and start queue manager

  10. Start listener

      runmqlsr -t tcp -p 1416 -m MyQmgr &


Choose an installation name

Each installation of WebSphere MQ on UNIX, Linux, and Windows, has a unique identifier known as an installation name. The installation name is used to associate things such as queue managers and configuration files with an installation.

You can choose the installation name and make it meaningful to you. For example, you might call a test system testMQ.

If you do not specify an installation name when the product is installed, a default installation name is automatically assigned. For the first installation, this name is Installation1. For the second installation, the name is Installation2, and so on. The installation name Installation0 is reserved for an installation of WebSphere MQ version 7.0.1. The installation name cannot be changed after the product is installed.

On UNIX and Linux systems, the first WebSphere MQ installation is automatically given an installation name of Installation1. For subsequent installations, you can use the crtmqinst command to set the installation name before installing the product.

On Windows systems, you can choose the installation name during the installation process.

The installation name can be up to 16 bytes and must be a combination of alphabetic and numeric characters in the ranges a-z, A-Z, and 0-9. You cannot use blank characters. The installation name must be unique, regardless of whether uppercase or lowercase characters are used. For example, the names INSTALLATIONNAME and InstallationName are not unique.

You can find out what installation name is assigned to an installation in a particular location using the dspmqinst command.


Installation descriptions

Each installation can also have an installation description. This description can give more detailed information about an installation in cases where the installation name cannot provide enough information. These descriptions can be up to 64 single-byte characters, or 32 double-byte characters. The default installation description is blank. You can set the installation description using the setmqinst command.


Multiple installations

On UNIX, Linux, and Windows, it is possible to have more than one copy of WebSphere MQ on a system.

You can choose where each copy of WebSphere MQ is installed, but each copy must be in a separate installation location. A maximum of 128 installations of WebSphere MQ can exist on a single machine at a time. One installation can be an installation of WebSphere MQ version 7.0.1 at fix pack 6, or later. You now have a choice:

Before you install multiple copies of WebSphere MQ, you must make several decisions:

When you have answered these questions, you can install WebSphere MQ using the steps provided in Installing WebSphere MQ .

If you have existing installations of WebSphere MQ and you want to use the multiple installation capability to migrate from one version of WebSphere MQ to another version, see Multi-installation queue manager coexistence on UNIX, Linux, and Windows .


The IBM message service client for .NET support pack and multiple installations

For multiple version support, the Java and .NET Messaging and Web Services feature must be installed with the WebSphere MQ product. This feature contains all the functionality included in the IBM Message Service Client for .NET support pack (IA9H). If the support pack is installed on the system, multiple versions are not supported. You must uninstall the support pack before installing WebSphere MQ. For more information about installing the .NET feature, see Installing WebSphere MQ classes for .NET .


Choose a primary installation

On systems that support multiple installations of WebSphere MQ (UNIX, Linux, and Windows), the primary installation is the one to which WebSphere MQ system-wide locations refer.

Before WebSphere MQ version 7.1, only one instance of the product could be installed at any time. On Windows systems, several global environment variables were set to point to that installation. On UNIX and Linux systems, symbolic links were added to /usr/lib, /usr/bin, and /usr/include, also pointing at that single installation.

From version 7.1, you can install multiple versions of WebSphere MQ on UNIX, Linux, and Windows. It is possible to have more than one installation of WebSphere MQ on one of these systems at any time. Environment variables and symbolic links pointing to a single installation are less meaningful when multiple versions exist. However, some functions require these system-wide locations to work. For example, custom user scripts for administering WebSphere MQ, and third party products. These functions work only on the primary installation.

On UNIX and Linux systems, if you set an installation as the primary installation, symbolic links to the external libraries and control commands of that installation are added into /usr/lib, and /usr/bin. If you do not have a primary installation, the symbolic links are not created. For a list of the symbolic links that are made to the primary installation, see External library and control command links to primary installation on UNIX and Linux .

On Windows systems, the global environmental variables point to the directories into which the primary installation was installed. These environment variables are used to locate WebSphere MQ libraries, control commands, and header files. Additionally, on Windows systems, some features of the operating system require the central registration of interface libraries that are then loaded into a single process. With multiple versions of WebSphere MQ, there would be conflicting sets of WebSphere MQ libraries. The features would try to load these conflicting sets of libraries into a single process. Therefore, such features can be used only with the primary installation. For details about some of the features that are limited to use with the primary installation, see Features that can be used only with the primary installation on Windows .

If you have an installation of WebSphere MQ version 7.0.1 on the system, this installation is automatically the primary installation. The primary installation cannot be changed while version 7.0.1 is installed. If all the installations on the system are at version 7.1, or later, you can choose whether to have a primary installation.

This table shows the valid installation configurations for primary installations. With a single version 7.1, or later, it can be either primary, or non-primary. With multiple installations, one at version 7.0.1 and one or more at version 7.1, or later,version 7.0.1 must be the primary, and the other installations must be non-primary. With multiple installations at version 7.1, or later, one installation can be primary, or all installations can be non-primary.


External library and control command links to primary installation on UNIX and Linux

On UNIX and Linux platforms the primary installation is the one to which links from the /usr file system are made. However, only a subset of those links created with previous releases are now made.

No links are created from /usr/include to any installation and only links to external libraries and documented control commands are made from /usr/lib (external libraries) and /usr/bin (control commands).

In order to run these commands you must complete the following steps:

  1. provide a full path to the command in an available WebSphere MQ installation,

  2. Use the setmqenv script to update your shell environment,

  3. manually add the bin directory from a WebSphere MQ installation directory to your PATH,

  4. run the setmqinst command as root to make one of your existing WebSphere MQ installations the primary installation.


External libraries

Links are made to the following external libraries, both 32-bit and 64-bit:

The following 64-bit only libraries are also linked to:


Control commands

The following control commands are linked to from /usr/bin:


Features that can be used only with the primary installation on Windows

Some Windows operating-system features can be used only with the primary installation. This restriction is due to the central registration of interface libraries, which might conflict as a result of multiple versions of WebSphere MQ being installed.


The .NET monitor

The WebSphere MQ .NET monitor can run in two different modes: transactional and non-transactional. The transactional mode uses MSDTC transaction coordination and requires that the .NET monitor is registered with COM+. The .NET monitor from the primary installation is the only .NET monitor that is registered with COM+.

Any attempt to run the .NET monitor in transactional mode with a non-primary installation results in the failure of the .NET monitor to enlist with MSDTC. The .NET monitor receives an MQRC_INSTALLATION_MISMATCH error, which in turn results in an AMQ8377 error message on the console.


COM/ActiveX interface classes

The COM/ActiveX interface classes are registered only for the primary installation. If there is an installation of WebSphere MQ version 7.0.1 on the system, the COM/ActiveX interface classes registered are not capable of connecting to queue managers running under other installations. If the primary installation is an installation of WebSphere MQ version 7.1 or later, the interface classes can connect to queue managers associated with any installation. Server COM/ActiveX applications are limited by this restriction, but client applications can connect to any queue manager.

Any attempt to start a COM/ActiveX application that uses libraries from installations other than the primary installation results in failure with an MQRC_Q_MGR_NOT_AVAILABLE error.


Uninstall, upgrading, and maintaining the primary installation

On all platforms, if you uninstall the primary installation, it ceases to be the primary installation. You must run the setmqinst command to select a new primary installation. On Windows, if you update the primary installation, it continues to be the primary installation. If you apply a fix pack to the primary installation, it continues to be the primary installation.

Be cautious about the effect uninstalling or upgrading the primary installation has on applications. Applications might be using the linkage library of the primary installation to switch to the linkage library of another installation. If such an application is running, you might not be able to uninstall the primary installation. The operating system might have locked the link library of the primary installation on behalf of the application. If the primary installation has been uninstalled, an application that loads the WebSphere MQ libraries it requires by linking to the primary installation is not able to start.

The solution is to switch the primary installation to another installation before uninstalling. Stop, and restart applications that are linked through the previous primary installation before uninstalling it.


Windows

If you update the primary installation, it stops being the primary installation at the beginning of the update procedure. If, by the end of the update procedure, you have not made another installation primary, the upgraded installation is made primary again.


Maintenance

If you apply a fix pack to the primary installation, it stops being the primary installation at the beginning of the maintenance procedure. If, by the end of the maintenance procedure, you have not made another installation primary, the upgraded installation is made primary again.


Choose an installation location

You can install WebSphere MQ to a custom location during the installation process. Alternatively, you can install to the default location. The location where WebSphere MQ is installed is known as the MQ_INSTALLATION_PATH.

The default location for the WebSphere MQ product code is shown in the following table:

Platform Installation Location
Linux, HP-UX, and Solaris /opt/mqm
AIX /usr/mqm
Windows 32-bit C:\Program Files\IBM\WebSphere MQ
Windows 64-bit C:\Program Files (x86)\IBM\WebSphere MQ

On UNIX and Linux systems, working data is stored in /var/mqm, but you cannot change this location; for more information about the directory structure of UNIX and Linux systems, see Directory structure on UNIX and Linux systems .


Custom location installation

For an installation into a custom location, the path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes. On UNIX and Linux systems, the path must not contain spaces.

For each installation, all of the WebSphere MQ components that you require must be installed in the same location.

For more information about how to install to a custom location, see the installation topics for the appropriate platform.


Choose what to install

You can select the components or features that you require when you install WebSphere MQ.

WebSphere MQ can be installed as a server or a client. The installation images can be downloaded, or WebSphere MQ can be installed from a DVD.

A WebSphere MQ server is an installation of one or more queue managers that provide queueing services to one or more clients. All the WebSphere MQ objects, for example queues, exist only on the queue manager machine (the WebSphere MQ server machine), and not the client. A WebSphere MQ server can also support local WebSphere MQ applications. To install a WebSphere MQ server see, Installing a WebSphere MQ server .

A WebSphere MQ MQI client is a component that allows an application running on one system to communicate with a queue manager running on another system. The output from the call is sent back to the client, which passes it back to the application. To install a WebSphere MQ MQI client see, Installing a WebSphere MQ client .

It is possible to have both a server and a client installation on the same system. See, Installing a WebSphere MQ client .

WebSphere MQ Advanced Message Security is a separately installed and licensed component of WebSphere MQ and is another option on the WebSphere MQ installer. To install WebSphere MQ Advanced Message Security, see Installing WebSphere MQ Advanced Message Security .


WebSphere MQ components for AIX systems

You can select the components that you require when you install WebSphere MQ.

WebSphere MQ components for AIX systems

Component Description Server DVD Client DVD Hypervisor Component name
Runtime Contains files that are common to both server and client installations. This component must be installed. X X X mqm.base.runtime
Server You can use the server to run queue managers on your system and connect to other systems over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. X   X mqm.server
Standard Client The WebSphere MQ MQI client is a small subset of WebSphere MQ, without a queue manager, that uses the queue manager and queues on other (server) systems. It can be used only when the system it is on is connected to another system that is running a full server version of WebSphere MQ. The client and the server can be on the same system if required. X X X mqm.client.rte
SDK Required for compiling applications. It includes sample source files, and the bindings (files .H, .LIB, .DLL, and others), that you need to develop applications to run on WebSphere MQ. X X X mqm.base.sdk
Sample programs Required to check WebSphere MQ installation using the verification procedures. X X X mqm.base.samples
Java messaging Includes Java Messaging Service) X X X mqm.java.rte
Man pages UNIX man pages, in U.S. English, for: control commands, MQI commands, MQSC commands X X X mqm.man.en_US.data
Java JRE A Java Runtime Environment, Version 6.0, that is used by those parts of WebSphere MQ that are written in Java. X X X mqm.jre.rte
Message Catalogs For available languages, see the table of message catalogs that follows. X X X  
IBM Global Security Kit IBM Global Security Kit V8 Certificate and SSL Base Runtime. X X X mqm.gskit.rte
Telemetry Clients   X X X mqm.xr.clients
Telemetry (MQXR) Service   X   X mqm.xr.service
Managed File Transfer MQ Managed File Transfer transfers files between systems in a managed and auditable way, regardless of file size or the operating systems used. X   X

mqm.ft.agent
mqm.ft.base
mqm.ft.logger
mqm.ft.service
mqm.ft.tools

Advanced Message Security Provides a high level of protection for sensitive data flowing through the WebSphere MQ network, while not impacting the end applications. You must install this component on all WebSphere MQ installations that host queues you want to protect. You must install the IBM Global Security Kit component on any WebSphere MQ installation that is used by a program that puts or gets messages to or from a protected queue, unless you are using only Java client connections. X   X mqm.ams.rte

WebSphere MQ message catalogs for AIX systems.

Message catalog language Component name
Brazilian Portuguese mqm.msg.pt_BR
Czech mqm.msg.cs_CZ
French mqm.msg.fr_FR
German mqm.msg.de_DE
Hungarian mqm.msg.hu_HU
Italian mqm.msg.it_IT
Japanese mqm.msg.ja_JP, mqm.msg.Ja_JP
Korean mqm.msg.ko_KR
Polish mqm.msg.pl_PL
Russian mqm.msg.ru_RU
Spanish mqm.msg.es_ES
Simplified Chinese mqm.msg.zh_CN, mqm.msg.Zh.CN
Traditional Chinese mqm.msg.zh_TW, mqm.msg.Zh_TW
U.S. English mqm.msg.en_US


WebSphere MQ client components for HP Integrity NonStop Server

There are no optional components within the client installer when you install the WebSphere MQ client for HP Integrity NonStop Server.

An installation of the WebSphere MQ client for HP Integrity NonStop Server contains product binary files, command utilities, and samples.


WebSphere MQ components for HP-UX systems

You can select the components that you require when you install WebSphere MQ.

Table 1 shows the components that are available when installing a WebSphere MQ server or client on an HP-UX system:

Component Description Server DVD Client DVD Hypervisor Component name
Runtime Contains files that are common to both server and client installations. This component must be installed. X X   MQSERIES.MQM-RUNTIME
Server You can use the server to run queue managers on your system and connect to other systems over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. X     MQSERIES.MQM-SERVER
Standard Client The WebSphere MQ MQI client is a small subset of WebSphere MQ, without a queue manager, that uses the queue manager and queues on other (server) systems. It can be used only when the system it is on is connected to another system that is running a full server version of WebSphere MQ. The client and the server can be on the same system if required. X X   MQSERIES.MQM-CL-HPUX
SDK The SDK is required for compiling applications. It includes sample source files, and the bindings (files .H, .LIB, .DLL, and others), that you need to develop applications to run on WebSphere MQ. X X   MQSERIES.MQM-BASE
Sample programs The sample application programs are needed if you want to check your WebSphere MQ installation using the verification procedures. X X   MQSERIES.MQM-SAMPLES
Java™ messaging The files needed for messaging using Java (includes Java Messaging Service). X X   MQSERIES.MQM-JAVA
Man pages UNIX man pages, in U.S. English, for:

control commands
MQI commands
MQSC commands

X X   MQSERIES.MQM-MAN
Java JRE A Java Runtime Environment, Version 6.0, that is used by those parts of WebSphere MQ that are written in Java. X X   MQSERIES.MQM-JAVAJRE
Message Catalogs For available languages, see the table of message catalogs that follows. X X    
IBM Global Security Kit IBM Global Security Kit V8 Certificate and SSL Base Runtime. X X   MQSERIES.MQM-GSKIT
Managed File Transfer MQ Managed File Transfer transfers files between systems in a managed and auditable way, regardless of file size or the operating systems used. X    

MQSERIES.MQM-FTAGENT
MQSERIES.MQM-FTBASE
MQSERIES.MQM-FTLOGGER
MQSERIES.MQM-FTSERVICE
MQSERIES.MQM-FTTOOLS

Advanced Message Security Provides a high level of protection for sensitive data flowing through the WebSphere MQ network, while not impacting the end applications. You must install this component on all WebSphere MQ installations that host queues you want to protect.

You must install the IBM Global Security Kit component on any WebSphere MQ installation that is used by a program that puts or gets messages to or from a protected queue, unless you are using only Java client connections.

X     MQSERIES.MQM-AMS

WebSphere MQ message catalogs for HP-UX systems.

Message catalog language Component name
Brazilian Portuguese MQSERIES.MQM-MC-PORT
Czech MQSERIES.MQM-MC-CZECH
French MQSERIES.MQM-MC-FRENCH
German MQSERIES.MQM-MC-GERMAN
Hungarian MQSERIES.MQM-MC-HUNGARIAN
Italian MQSERIES.MQM-MC-ITALIAN
Japanese MQSERIES.MQM-MC-JAPAN
Korean MQSERIES.MQM-MC-KOREAN
Polish MQSERIES.MQM-MC-POLISH
Russian MQSERIES.MQM-MC-RUSSIAN
Spanish MQSERIES.MQM-MC-SPANISH
Simplified Chinese MQSERIES.MQM-MC-CHINES
Traditional Chinese MQSERIES.MQM-MC-CHINET
U.S. English not applicable


WebSphere MQ components for Linux systems

You can select the components that you require when you install WebSphere MQ.

Table 1 shows the components that are available when installing a WebSphere MQ server or client on a Linux system:

Component Description Server DVD Client DVD Hypervisor Component name
Runtime Contains files that are common to both server and client installations. This component must be installed. X X X

MQSeriesRuntime

Server You can use the server to run queue managers on your system and connect to other systems over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. X   X

MQSeriesServer

Standard Client The WebSphere MQ MQI client is a small subset of WebSphere MQ, without a queue manager, that uses the queue manager and queues on other (server) systems. It can be used only when the system it is on is connected to another system that is running a full server version of WebSphere MQ. The client and the server can be on the same system if required. X X X

MQSeriesClient

SDK The SDK is required for compiling applications. It includes sample source files, and the bindings (files .H, .LIB, .DLL, and others), that you need to develop applications to run on WebSphere MQ. X X X

MQSeriesSDK

Sample programs The sample application programs are needed if you want to check your WebSphere MQ installation using the verification procedures. X X X

MQSeriesSamples

Java™ messaging The files needed for messaging using Java (includes Java Messaging Service). X X X

MQSeriesJava

Man pages UNIX man pages, in U.S. English, for:

control commands
MQI commands
MQSC commands

X X X

MQSeriesMan

Java JRE A Java Runtime Environment, Version 6.0, that is used by those parts of WebSphere MQ that are written in Java. X X X

MQSeriesJRE

Message Catalogs For available languages, see the table of message catalogs that follows. X X X  
IBM Global Security Kit IBM Global Security Kit V8 Certificate and SSL Base Runtime. X X X

MQSeriesGSKit

Telemetry Clients (64-bit Linux only) X X X

MQSeriesXRClients

Telemetry (MQXR) Service (64-bit Linux only) X   X

MQSeriesXRService

MQ Explorer Use WebSphere MQ MQ Explorer to administer and monitor resources on Linux x86 and x86-64 systems. X   X

MQSeriesExplorer

Managed File Transfer MQ Managed File Transfer transfers files between systems in a managed and auditable way, regardless of file size or the operating systems used. X   X

MQSeriesFTAgent
MQSeriesFTBase
MQSeriesFTLogger
MQSeriesFTService
MQSeriesFTTools

Advanced Message Security Provides a high level of protection for sensitive data flowing through the WebSphere MQ network, while not impacting the end applications. You must install this component on all WebSphere MQ installations that host queues you want to protect.

You must install the IBM Global Security Kit component on any WebSphere MQ installation that is used by a program that puts or gets messages to or from a protected queue, unless you are using only Java client connections.

X   X

MQSeriesAMS

WebSphere MQ message catalogs for Linux systems.

Message catalog language Component name
Brazilian Portuguese MQSeriesMsg_pt
Czech MQSeriesMsg_cs
French MQSeriesMsg_fr
German MQSeriesMsg_de
Hungarian MQSeriesMsg_hu
Italian MQSeriesMsg_it
Japanese MQSeriesMsg_ja
Korean MQSeriesMsg_ko
Polish MQSeriesMsg_pl
Russian MQSeriesMsg_ru
Spanish MQSeriesMsg_es
Simplified Chinese MQSeriesMsg_Zh_CN
Traditional Chinese MQSeriesMsg_Zh_TW
U.S. English not applicable


WebSphere MQ components for Solaris systems

You can select the components that you require when you install WebSphere MQ.

Table 1 shows the components that are available when installing a WebSphere MQ server or client on a Solaris system. When you install interactively on Solaris systems, the options that are available install various combinations of the components listed in this table. Details are given in the Interactive installation section.

Component Description Server DVD Client DVD Hypervisor Component name
Runtime Contains files that are common to both server and client installations. This component must be installed. X X   runtime
Server You can use the server to run queue managers on your system and connect to other systems over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. X     server
Standard Client The WebSphere MQ MQI client is a small subset of WebSphere MQ, without a queue manager, that uses the queue manager and queues on other (server) systems. It can be used only when the system it is on is connected to another system that is running a full server version of WebSphere MQ. The client and the server can be on the same system if required. X X   sol_client
SDK The SDK is required for compiling applications. It includes sample source files, and the bindings (files .H, .LIB, .DLL, and others), that you need to develop applications to run on WebSphere MQ. X X   base
Sample programs The sample application programs are needed if you want to check your WebSphere MQ installation using the verification procedures. X X   samples
Java™ messaging The files needed for messaging using Java (includes Java Messaging Service). X X   java
Man pages UNIX man pages, in U.S. English, for:

control commands
MQI commands
MQSC commands

X X   man
Java JRE A Java Runtime Environment, Version 6.0, that is used by those parts of WebSphere MQ that are written in Java. X X   jre
Message Catalogs For available languages, see the table of message catalogs that follows. X X    
IBM Global Security Kit IBM Global Security Kit V8 Certificate and SSL Base Runtime. X X   gskit
Managed File Transfer MQ Managed File Transfer transfers files between systems in a managed and auditable way, regardless of file size or the operating systems used. X    

ftagent
ftbase
ftlogger
ftservice
fttools

Advanced Message Security Provides a high level of protection for sensitive data flowing through the WebSphere MQ network, while not impacting the end applications. You must install this component on all WebSphere MQ installations that host queues you want to protect.

You must install the IBM Global Security Kit component on any WebSphere MQ installation that is used by a program that puts or gets messages to or from a protected queue, unless you are using only Java client connections.

X     mqams

WebSphere MQ message catalogs for Solaris systems.

Message catalog language Component name
Brazilian Portuguese Pt_BR
Czech Cs_CZ
French Fr_FR
German De_DE
Hungarian Hu_HU
Italian It_IT
Japanese Ja_JP
Korean Ko_KR
Polish Pl_PL
Russian Ru_RU
Spanish Es_ES
Simplified Chinese Zh_CN
Traditional Chinese Zh_TW
U.S. English not applicable


Interactive installation

The options available with interactive installation install various combinations of the product components described in the previous tables. The following table shows you what will be installed for each option, together with the option number on the server and client DVDs:

WebSphere MQ interactive installation options for Solaris systems.

Interactive installation option Components installed Server DVD option number Client DVD option number
WebSphere MQ Server base
runtime
server
java
gskit 		1  
Man pages runtime
man 		2 1
Sample programs base
runtime
samples 		3 2
WebSphere MQ MQI client libraries (including Java, JMS, and Web Services support) base
runtime
sol_client
java
gskit 		4 3
IBM Java runtime for Solaris, Java 2 Technology Edition, Version 6 jre
runtime 		5  
IBM Global Security Kit for WebSphere MQ gskit
jre
runtime 		6  
WebSphere MQ Managed File Transfer Service ftservice
ftbase
jre
java
runtime
ftagent 		7  
WebSphere MQ Managed File Transfer Tools fttools
ftbase
jre
java
runtime 		8  
WebSphere MQ Managed File Transfer Agent ftagent
ftbase
jre
java
runtime 		9  
WebSphere MQ Managed File Transfer Logger ftlogger
ftbase
jre
java
runtime
server 		10  
WebSphere MQ Advanced Message Security runtime
mqams 		11  
Spanish message catalog runtime
Es_ES 		12 4
French message catalog runtime
Fr_FR 		13 5
German message catalog runtime
De_DE 		14 6
Japanese message catalog

runtime
Ja_JP

15 7
Italian message catalog

runtime
It_IT

16 8
Brazilian Portuguese message catalog

runtime
Pt_BR

17 9
Traditional Chinese message catalog

runtime
Zh_TW

18 10
Simplified Chinese message catalog

runtime
Zh_CN

19 11
Korean message catalog

runtime
Ko_KR

20 12
Russian message catalog

runtime
Ru_RU

21 13
Hungarian message catalog

runtime
Hu_HU

22 14
Polish message catalog

runtime
Pl_PL

23 15
Czech message catalog

runtime
Cs_CZ

24 16


WebSphere MQ features for Windows systems

You can select the features that you require when you install WebSphere MQ.

The following table shows the features that are available when installing a WebSphere MQ server or client on a Windows system.
Interactive displayed name Non-interactive displayed name Description Server DVD Client DVD
Server Server You can use the server to run queue managers on your system and connect to other systems over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. X  
MQ Explorer Explorer WebSphere MQ Explorer allows you to administer and monitor resources in WebSphere MQ. X  
Managed File Transfer Service MFT_Service The WebSphere MQ Managed File Transfer Service install option installs a file transfer agent that has additional capabilities beyond those provided by the file transfer agent installed via the WebSphere MQ Managed File Transfer Agent install option. These additional capabilities are:-

  • Create protocol bridge agents which are used to send and receive files with legacy FTP, FTPS or SFTP servers

  • Deploy the Web Gateway feature which provides RESTful interfaces for building web applications that transfer files

The WebSphere MQ Managed File Transfer Service install option must be installed on systems where the WebSphere MQ Server install option is already installed.

X  
Managed File Transfer Logger MFT_Logger The WebSphere MQ Managed File Transfer Logger install option installs a file transfer logger which connects to a WebSphere MQ queue manager, often the queue manager designated as the coordination queue manager. It logs file transfer audit related data to either a database or a file. It must be installed on systems where the WebSphere MQ Server install option is already installed. X  
Managed File Transfer Agent MFT_Agent The WebSphere MQ Managed File Transfer Agent install option installs a file transfer agent which connects to a WebSphere MQ queue manager and transfers file data, as messages, to other file transfer agents. These must be installed either as part of the WebSphere MQ Managed File Transfer Agent or WebSphere MQ Managed File Transfer Service install options. X  
Managed File Transfer Tools MFT_Tools The WebSphere MQ Managed File Transfer Tools install option installs command line tools that are used to interact with file transfer agents. You can use these tools to start file transfers, schedule file transfers and create resource monitors from the command line. The WebSphere MQ Managed File Transfer Tools can be installed and used on either a system where file transfer agents are installed, or on a system where no file transfer agents are installed. X  
Windows Client Client The WebSphere MQ client is a small subset of WebSphere MQ, without a queue manager, that uses the queue manager and queues on other (server) systems. It can be used only when the system it is on is connected to another system that is running a full server version of WebSphere MQ. The client and server can be on the same system if required. X X
Java and .NET Messaging and Web Services JavaMsg The files needed for messaging using Java (includes Java Message Service support) and WebSphere MQ Web Services. X X
Development Toolkit Toolkit This feature includes sample source files, and the bindings (files .H, .LIB, .DLL, and others), that you need to develop applications to run on WebSphere MQ . Bindings and samples are provided for the following languages: C, C++, Visual Basic, ActiveX, Cobol, and .NET (including C#). Java™ and Java Message Service support is included and samples are provided for MTS (COM+), and MQSC. X X
Telemetry Clients XR_Clients Basic and advanced clients for WebSphere MQ Telemetry. X X
Telemetry (MQXR) Service XR_Service Server component of WebSphere MQ Telemetry. X  
Advanced Message Security AMS Provides a high level of protection for sensitive data flowing through the WebSphere MQ network, while not impacting the end applications. You must install this component on all WebSphere MQ installations that host queues you want to protect.

You must install the IBM Global Security Kit component on any WebSphere MQ installation that is used by a program that puts or gets messages to or from a protected queue, unless you are using only Java client connections.

X  


Install WebSphere MQ Telemetry

From WebSphere MQ version 7.1, WebSphere MQ Telemetry is a component of the main WebSphere MQ product, and is no longer a separate plug-in. There are two main methods of installing WebSphere MQ Telemetry: selecting WebSphere MQ Telemetry in a custom installation when installing WebSphere MQ, or modifying an existing WebSphere MQ installation and selecting WebSphere MQ Telemetry.

If WebSphere MQ version 7.0.1 is installed with the WebSphere MQ Telemetry plug-in, you must migrate the installation to WebSphere MQ version 7.5. See Migrating WebSphere MQ Telemetry from version 7.0.1 to version 7.5 for information and instructions about this process.

WebSphere MQ Telemetry clients

Two WebSphere MQ Telemetry clients, called basic and advanced, are automatically installed within the mqxr subfolder of the main WebSphere MQ installation. The WebSphere MQ Telemetry installer creates a directory called mqxr in which all WebSphere MQ Telemetry components are installed. By default, for example, the clients are installed in Program Files\IBM\WebSphere MQ\mqxr\SDK on Windows systems, and in /opt/mqm/mqxr/SDK on Linux systems.

WebSphere MQ Telemetry runtime

WebSphere MQ Telemetry runtime is an extension to theWebSphere MQ queue manager. The WebSphere MQ Telemetry feature supports the connection of telemetry devices from the edge of a network to WebSphere MQ. This connection is made possible by the WebSphere MQ Telemetry Transport (MQTT) protocol.

WebSphere MQ Telemetry runtime can be configured using the WebSphere MQ Explorer. For a queue manager to accept connections from a telemetry device, one or more telemetry channels are needed. To enable MQTT there is a define sample configuration wizard that can be run from WebSphere MQ Explorer. The wizard runs through a series of steps including defining and starting the telemetry (MQXR) service, setting up the default transmission queue, and configuring a telemetry channel. For more information about using the define sample configuration wizard, and any implications, see Verifying the installation of WebSphere MQ Telemetry by using WebSphere MQ Explorer .

Support for WebSphere MQ Explorer

You can use WebSphere MQ Explorer to configure and manage the WebSphere MQ Telemetry runtime component. The extension provides the following capabilities:

  • Telemetry node and content panel - providing welcome information, define sample configuration wizard, run MQTT client utility, Help on WebSphere MQ Telemetry, and status information about the WebSphere MQ Telemetry Service.

  • Define sample configuration wizard - quickly configures a queue manager to support MQTT.

  • New Telemetry Channel wizard - gathers information required to create a telemetry channel object.

  • Telemetry Channels node and content panel - displays telemetry channels in the WebSphere MQ Explorer Content view.

  • Telemetry Channel Status node and content panel - displays telemetry channel status in the WebSphere MQ Explorer Content view.

  • MQTT Client Utility - provides a simple GUI for publishing and subscribing to topics.

  • Help on WebSphere MQ Telemetry.

You can administer WebSphere MQ Telemetry Version 7.0.1 only from the version 7.0.1 WebSphere MQ Explorer. If you connect the version 7.5 explorer remotely to a version 7.0.1 queue manager, no telemetry resources are displayed. You cannot connect a version 7.5 WebSphere MQ Explorer locally to a version 7.0.1 queue manager on the same server.

WebSphere MQ Telemetry client libraries and SDK

You can develop your applications using the WebSphere MQ Telemetry client libraries and the development SDK. The client libraries and the development SDK can be imported into a development environment (for example WebSphere Eclipse Platform). After relevant applications are developed, these applications, and client libraries can then be deployed together to the appropriate system. The SDK includes the following features:

  • Client documentation.

  • MQTT client libraries

    • Java™ MQTT libraries

    • Native C MQTT libraries

  • Advanced function components

    • MQ Telemetry Daemon for Devices

Two copies of the com.ibm.micro.client.mqttv3.jar JAR file are installed. One copy has a version number as part of the file name. For example: com.ibm.micro.client.mqttv3_3.0.2.0-20100723.jar. Use the versioned copy in OSGi applications. The content of the JAR files is the same.

The WebSphere MQ Telemetry Server and Client components can be installed together, or you can install each component on a separate system. You can install the WebSphere MQ Telemetry runtime component on one system and configure and manage it using the WebSphere MQ Explorer installed on another system. However, the components can be installed only on systems with the appropriate prerequisites. If you have the prerequisites for the WebSphere MQ Telemetry runtime on your system, then both components are installed. There is an option to select not to install the WebSphere MQ Telemetry client libraries and SDK.


Plan the installation on Windows systems

This topic describes the different methods available to install WebSphere MQ on Windows systems and the different installation types .

If you are migrating from an earlier version of WebSphere MQ, see Windows: Planning for migration from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.5 . To modify an existing installation, see Modifying your installation .


Interactive or Non-Interactive installation

WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). You can use the Installation Launchpad to invoke MSI, this process is called an attended or interactive installation. Or, you can invoke MSI directly for a silent installation, without using the WebSphere MQ Installation Launchpad. This means that you can install WebSphere MQ on a system without interaction. This process is called unattended, silent, or non-interactive installation, and is useful for installing WebSphere MQ over a network on a remote system.

For a list of interactive and non-interactive features, see WebSphere MQ features for Windows systems .


Interactive installation

If you choose an interactive installation, before you install, you must decide what type of installation you require. Table 1 shows the installation types available, and the features that are installed with each option. For the prerequisites required for each feature, see WebSphere MQ requirements .

The installation types are:

You can also:

See Choosing a primary installation for important information about these features, including whether to designate your installation as the primary installation.

Features installed with each type of interactive installation

Installation type Server Features installed Client Features installed Comments
Typical

  • Server

  • WebSphere MQ Explorer

  • Development Toolkit

  • Java™ and .NET Messaging and Web Services

  • Windows client

  • Development Toolkit

  • Java and .NET Messaging

The default option. Features are installed to default locations with a default installation name.

Java and .NET Messaging and Web Services includes WebSphere MQ classes for .NET and support for the Microsoft Windows Communication Foundation (WCF) for use with Microsoft .NET 3.

Compact

  • Server only

  • Windows client only

The feature is installed to the default location with a default installation name.
Custom By default, the following features are preselected:

  • Server

  • WebSphere MQ Explorer

  • Development Toolkit

  • Java and .NET Messaging and Web Services

A custom installation can also install:

  • Windows client

  • Client Extended Transaction Support

  • Java Extended Transaction Support

  • Telemetry (MQXR) Service

  • Telemetry Clients

By default, the following features are preselected:

  • Windows client

  • Development Toolkit

  • Java and .NET Messaging and Web Services

A custom installation can also install:

  • Telemetry Clients

A server custom installation can be used if you want to install the Windows client from within the server image.

All the available features are listed and you can select which ones to install, and where to install them. You can also name and provide a description for the installation.

Use a custom installation when you want to specify that the installation is primary.

Java and .NET Messaging and Web Services includes WebSphere MQ classes for .NET and support for the Microsoft Windows Communication Foundation (WCF) for use with Microsoft .NET 3 or later.

If Microsoft .NET is not installed before WebSphere MQ and you add it, rerun setmqinst -i -n Installationname if this is a primary installation.

The following table describes which level of .NET is required for which function:

Required levels of Microsoft .NET

WebSphere MQ function .NET version required
WebSphere MQ classes for .NET. For more information, see: Getting started with WebSphere MQ classes for .NET 2 .NET 2
The WebSphere MQ custom channel for WCF. For more information, see: WebSphere MQ custom channel for WCF

To build the sample solution files, either the Microsoft .NET 3.5 SDK, or Microsoft Visual Studio 2008 is needed. For more information, see: Software requirements for the WCF custom channel for WebSphere MQ

.NET 3.0 or later

For instructions on how to install WebSphere MQ on Windows systems, see Installing WebSphere MQ Server on Windows systems and Installing a WebSphere MQ client on Windows systems .


Non-interactive installation

If you choose a non-interactive installation the system on which you want to install must be able to access the WebSphere MQ image, or a copy of the files, and you must be able to access the system.

If you are running WebSphere MQ version 7.5 or later, with User Account Control (UAC) enabled, you must invoke the non-interactive installation from an elevated command prompt. Elevate a command prompt by using a right-click to start the command prompt and choose Run as administrator. If you try to silently install from a non-elevated command prompt, the installation fails with an error of AMQ4353 in the installation log.

There are several ways to invoke MSI:

If you need to create a special domain ID for the WebSphere MQ service, see Security considerations when installing WebSphere MQ server on a Windows system .


Security considerations when installing WebSphere MQ server on a Windows system

Use this information to learn about the security considerations when installing WebSphere MQ server on a Windows system.


Additional restrictions for installing on Windows

There are some additional points to consider when installing WebSphere MQ version 7.5 or later on Windows. First, Windows has some rules regarding the naming of objects created and used by WebSphere MQ . Second, you can set up logging during installation which assists you in troubleshooting any problems you might have with the installation.


Naming considerations


Logging

Logging is enabled by default from the Launchpad. You can also enable complete logging, for more information, see How to enable Windows Installer logging


Plan the installation on HP Integrity NonStop Server

This section describes what to do to prepare your system for installing WebSphere MQ client for HP Integrity NonStop Server.


Understanding multiple installations

WebSphere MQ client for HP Integrity NonStop Server can be installed more than once on an HP Integrity NonStop Server system. In addition, multiple different versions of WebSphere MQ can be installed on a single HP Integrity NonStop Server system, and be maintained independently. Each installation can be of any supported version of WebSphere MQ. There are no requirements for installations to be either the same, or different versions.

To install WebSphere MQ, you must specify two locations; one in the OSS file system, and one in the Guardian file system, which is used by the installer to store the results of the installation. These locations must not contain or overlap with any other WebSphere MQ installation. The locations must also be free of other files.

Each installation is independent and self-contained, with all data, such as configuration logs, or trace and program files located within the installation directory hierarchy. All commands and libraries use an embedded runtime search path (RPath) to ensure that they load their dependencies from the same installation.

As several installations might be present, each application must locate and load the WebSphere MQ client libraries from the correct installation.


Product packaging and delivery

WebSphere MQ client for HP Integrity NonStop Server is downloaded to the OSS file system as a single file.

The WebSphere MQ client for HP Integrity NonStop Server package file is a self-extracting archive (SFX) that contains an installer and all files that are required to create installations.

The SFX for WebSphere MQ client for HP Integrity NonStop Server has a file extension of .run. There is no concept of placed files. When run, the SFX creates a single installation, directly from the archive, into the OSS and Guardian file systems.

The SFX can be used to create as many installations of the WebSphere MQ client for HP Integrity NonStop Server as you require. No information about installations is retained in the SFX, and no tools are provided for extracting individual files from the SFX.


File system

Before you install the WebSphere MQ client for HP Integrity NonStop Server, make sure that the file system is set up correctly.

Review Hardware, software, and file system requirements to make sure that you understand the approximate amount of disk space in the OSS and Guardian file systems that is required for an installation. The OSS file set that is used for the installation requires enough free space for the installation files and the files you create in the installation. The Guardian volume that you use for installation does not require auditing.

Work with your systems administrator to verify the OSS file set and Guardian file system storage requirements, at least for an initial estimate of the storage. The best way to determine more precisely how much storage you would eventually need in production is to produce a prototype configuration and model the message storage requirements, scaling up as necessary for your production system.


OSS file system objects

For the OSS file system objects, this section concentrates on the differences between the HP Integrity NonStop Server installation, and the standard UNIX installation. Multiple independent installations are supported.

The opt and var trees must be present in a common root directory, which is selected at installation time. The opt tree contains files that do not change. For example, this tree contains program, library, dll, header files, and "static" data files. The var tree contains files that might change, and do hold status about the installation itself. Examples of files that this tree holds are configuration files, and log files.

Both the opt and var directories contain a single directory named mqm. The content of both trees is rooted in the opt/mqm and var/mqm directories.

This table shows a summary of the contents at the top level of opt/mqm:

Directory Purpose Contents
bin Contains the OSS programs and libraries for an installation

  • G is a symbolic link file that locates the Guardian installation subvolume

  • amq* files, containing the product executables for the client

  • lib* files, containing product dll files

  • Files containing control commands, and other utilities and scripts

inc Contains the header files for building WebSphere MQ applications

  • .h files, which are C language header files

  • .tal files which are pTAL header files

  • .cpy files which are COBOL copy file

  • cobcpy32 and cobcpy64 directories for the individual COBOL copy files

lib Contains the import libraries needed to link applications

  • G is a symbolic link file that locates the Guardian installation subvolume

  • amq* files, containing product dll files

  • iconv is a directory that contains data conversion tables

  • lib* files, which are product dll files

  • mqicb used for supplying to a CONSULT directive for compiling COBOL programs

license Contains text versions of the IBM License for the WebSphere MQ client for HP Integrity NonStop Server product, which is translated into each supported national language

  • Lic_.txt files, which are the individual national language translations of the license.

  • notices.txt is a file that contains any additional license terms from non-IBM software that is included with WebSphere MQ, if any

mq.id Single file that contains information about the build level and install package All contents in this directory might be used by IBM Support personnel.
msg Contains globalization files for use by WebSphere MQ, in logging and displaying output in the supported national language translations

The contents include:

  • amq.cat globalization message catalog currently in use by the installation, created by the OSS utility "gencat"

  • amq.msg unprocessed globalization data that is used as input by gencat to create the catalog

  • Other minor files and directories that support the different translations

samp Contains sample code and executables to illustrate the use of WebSphere MQ

  • *.cbl sample COBOL language source files

  • *.c sample 'C' language source files

  • *.tal sample pTAL language source files

  • ccsid.new backup file of ccsid.tbl

  • ccsid.tbl file that contains a table of supported CCSIDs

  • *.ini sample configuration files

  • java directory that contains source for sample Java applications

  • jms directory that contains source for sample JMS applications

  • bin directory that contains executable versions of the samples

  • dlq directory that contains a source for the sample Dead Letter Queue Handler

  • preconnect directory that contains source for preconnect exit

For more information about the samples that are provided with WebSphere MQ client for HP Integrity NonStop Server, see Samples for WebSphere MQ client for HP Integrity NonStop Server .

This table shows a summary of the contents at the top level of var/mqm:

Directory Purpose Contents
conv Contains data conversion files Binary data that supports the data conversion function for WebSphere MQ
errors Contains installation-wide error logs and FDC files

Standard content, for example:

  • AMQERR01.LOG - current system-wide error log file

  • AMQERR02.LOG - previous system-wide error log file

  • AMQERR03.LOG - oldest system-wide error log file

  • *.FDC FFST™ files

exits Stores DLLs containing exit code that is loaded by the queue managers in the installation This file is empty at installation
log Contains log files for recording and controlling units of work Standard content
mqs.ini The installation configuration file Standard content
qmgrs Directory beneath the location where all of the queue manager directories are created Standard content
sockets Directory tree that contains various queue manager control files Standard content
trace Defined location to which trace data is written by WebSphere MQ Standard content


Guardian installation subvolume

The Guardian single installation subvolume contains both the programs and libraries needed at runtime.

This table shows the contents of the Guardian installation subvolume:

File Description
AMQINST Internal file that describes installation configuration
AMQS* Samples that are built for Guardian
B*SAMP Sample build files for the various supported languages
CMQ* Header files for the various supported languages, where files ending in:

  • h are C headers

  • T are pTAL headers

  • L are COBOL headers

MQ* Product libraries
MQS*C Sample C language source files
MQS*T Sample pTAL language source files
MQS*L Sample COBOL language source files

Control commands are also included, for a list, see HP Integrity NonStop Server client commands .


Checking requirements

Before you install WebSphere MQ, you must check for the latest information and system requirements. A summary of the tasks that you must complete to check system requirements are listed here with links to further information.


Procedure

  1. Check that you have the latest information, including information on hardware and software requirements. See Finding the latest information .

  2. Check that your systems meet the initial hardware and software requirements on your platform

    • Hardware and software requirements on UNIX and Linux systems

    • Hardware and software requirements on Windows systems

    The supported hardware and software environments are occasionally updated. See the WebSphere MQ requirements website for the latest information.

  3. Check that your systems have sufficient disk space for the installation. See Disk space requirements .

  4. Check that you have the correct license requirements. See License requirements .


What to do next

When you have completed these tasks, you are ready to start preparing your systems for installation. For the next steps in installing WebSphere MQ, see Preparing the system .


Finding the latest information

Access the latest information for WebSphere MQ.

Requirements website

For the latest details of hardware and software requirements on all supported platforms, see the WebSphere MQ requirements website.

readme.html

The product readme file is frequently updated and includes information about last minute changes and known problems and workarounds. The file is included on the product media and is installed when you install product components. The latest version is always on the product readmes web page. Always check to see that you have the latest copy.

Support information

The WebSphere MQ support web page is regularly updated with the latest product support information. For example, if you are migrating from an earlier version, look under the heading Solve a problem for the document Problems and solutions when migrating .


Hardware and software requirements on UNIX and Linux systems

Before you install WebSphere MQ, check that your system meets the hardware and operating system software requirements for the particular components you intend to install.

Hardware and software requirements are set out at the WebSphere MQ system requirements page.

WebSphere MQ does not support host names that contain spaces. If you install WebSphere MQ on a system with a host name that contains spaces, you are unable to create any queue managers.


Java Message Service and SOAP transport

To use Java™ Message Service and SOAP support, you need an IBM Java 2 SDK and Runtime Environment Version 5.0 or later.

On Linux: Apache Axis V1.4 provides support for SOAP and is shipped on the server DVD, but not installed.

For a list of supported JDKs, see the WebSphere MQ system requirements page at http://www.ibm.com/software/integration/wmq/requirements/ .

For further information about using Java with WebSphere MQ, see Using WebSphere MQ classes for Java .

For further information about SOAP with WebSphere MQ, see WebSphere MQ transport for SOAP .

If you use a JDK that is not in the list of supported JDKs be aware that:

On HP-UX: To run a 64-bit or 32-bit JVM use the -d64 or -d32 parameters on the command line when running a Java application to ensure the correct JVM is used.

On Linux: On the Power platform, the 32-bit and 64-bit JDKs are typically installed to different locations, for example, the 32-bit JDK is located in /opt/IBMJava2-ppc-50 and the 64-bit JDK is located in /opt/IBMJava2-ppc64-50. Ensure that the PATH variable is correctly set for your applications that use Java. To use the Postcard application described in Verify the installation using the Postcard application , you must use a 32-bit JDK.

On Solaris: The 32-bit and 64-bit JDKs are typically installed to the same directory. To run a 64-bit JVM use the -d64 or -d32 parameters on the command line when running a Java application to ensure the correct JVM is used.

You can check the version installed using the following command: 

java -version


Secure Sockets Layer (SSL)

To use the SSL support, you need the IBM Global Security Kit (GSKit) V8 package. This package is supplied with WebSphere MQ as one of the components available for installation.

HP-UX

To use SSL, WebSphere MQ clients on HP-UX must be built using POSIX threads.

Linux

Install the g++ version runtime support

If you intend to run SSL channels then you must have the g++ runtime libraries installed. The GNU g++ libraries are called libgcc_s.so and libstdc++.so.6 and, on a Red Hat system with libgcc and libstdc++ RPMs installed, are found in the directory /usr/lib. Check that the release level of the libraries meets WebSphere MQ requirements, found at http://www.ibm.com/software/integration/wmq/requirements/ .

If you have a distribution that does not install libgcc_s.so and libstdc++.so.6 into /usr/lib, then you must do one of the following tasks:

  • Locate and install the packages from your distribution vendor that contain these libraries.

  • Install the GNU gcc and g++ compilers from another location, for example the home page for the GNU compiler collection at http://gcc.gnu.org/ .

Ensure that the libraries listed are included in /usr/lib after installation.

The required packages for SSL support for WebSphere MQ are set out on the following page: http://www.ibm.com/software/integration/wmq/requirements/ .

On 64 bit platforms, install both the 32 bit and the 64 bit versions of the package so that 32 bit and 64 bit processes can both use SSL functions.


WebSphere MQ Explorer requirements

Linux

To use the WebSphere MQ Explorer (available for use with WebSphere MQ for Linux, (x86 and x86-64 platforms) only), your system requires the following things, as a minimum:

  • 512 MB RAM

  • 1 GHz processor

  • 800 MB for Eclipse Platform code and data

  • A suitable monitor for the operating system with a screen size of at least 1024x768

  • Bitstream-vera-fonts


Hardware and software requirements on Windows systems

Check that the server environment meets the prerequisites for installing WebSphere MQ for Windows and install any prerequisite software that is missing from your system from the server DVD.

Before installing WebSphere MQ, you must check that your system meets the hardware and software requirements set out on the WebSphere MQ system requirements page at http://www.ibm.com/software/integration/wmq/requirements/ .

You must also review the release notes file, which is on the product DVD in the \Readmes folder for each national language, and check the READADD.txt file for any changes made between translation and the manufacturing of the installation DVD. READADD.txt is found in the root directory of the server installation DVD. During installation, the release notes file is copied to the WebSphere MQ program files folder.


Storage requirements for WebSphere MQ server

The storage requirements depend on which components you install, and how much working space you need. The storage requirements also depend on the number of queues that you use, the number and size of the messages on the queues, and whether the messages are persistent. You also require archiving capacity on disk, tape, or other media. For more information, see the WebSphere MQ system requirements page at, http://www.ibm.com/software/integration/wmq/requirements/ .

Disk storage is also required:


Requirements for WebSphere MQ Explorer

To use the WebSphere MQ Explorer, the following minimum requirements apply:


Install directory used for 64 bit Windows operating systems

On 64 bit Windows systems, WebSphere MQ is installed into the default 32 bit installation location: C:\Program Files (x86)\IBM\WebSphere MQ.

If you select a non-default directory for installing Windows, do not try to install into C:\Program Files\IBM\WebSphere MQ. C:\Program Files can only contain 64 bit programs.

If you are doing a silent installation and you select C:\Program Files\IBM\WebSphere MQ as the installation directory, the installer writes an error to the error log and the installation fails.

Wherever the default installation location occurs in the documentation or C:\Program Files\IBM\WebSphere MQ is documented, for 64 bit operating systems the file path is C:\Program Files (x86)\IBM\WebSphere MQ.


Install prerequisite software

To install the prerequisite software provided on the WebSphere MQ Server DVD (which does not include service packs or web browsers), do one of the following:


Hardware and software requirements on HP Integrity NonStop Server systems

Check that the server environment meets the prerequisites for installing the WebSphere MQ client for HP Integrity NonStop Server. Check the product readme files and install missing prerequisite software supplied on the server CD.


Hardware

The WebSphere MQ client for HP Integrity NonStop Server typically requires certain hardware specifications to run:


Operating system

Two operating systems are supported by the WebSphere MQ client for HP Integrity NonStop Server:

You must be running one of these operating systems to install the WebSphere MQ client for HP Integrity NonStop Server.


Other software requirements

WebSphere MQ client for HP Integrity NonStop Server has some additional software requirements:


File system requirements

In the selected installation root directory, in the OSS file system, an installation creates:

An installation also creates a single subvolume in the Guardian file system, which is selected during installation.


Verify system software prerequisites

Use the HP Integrity NonStop Server TACL utility, SYSINFO, to verify the base OS level of the HP Integrity NonStop Server.


Procedure

From a TACL command prompt, enter SYSINFO.

The system information is displayed as shown in the following example: 

SYSINFO - T9268H01 - (01 OCT 2004)  SYSTEM \NODE1  Date 05 Nov 2010, 11:56:51
Copyright 2003 Hewlett-Packard Development Company, L.P.

         System name    \NODE1
  EXPAND node number    025
       Current SYSnn    SYS00
       System number    nnnnnn
 Software release ID    J06.10.00

In this example, the base OS level is J06.10.00.


What to do next

Compare the base OS level with the Hardware, software, and file system requirements . Verify any other HP Integrity NonStop Server software prerequisites or recommendations identified in the documentation or the product README; for example, SPRs to particular products.


Disk space requirements

The storage requirements for WebSphere MQ depend on which components you install, and how much working space you need.

Disk storage is required for the optional components you choose to install, including any prerequisite components they require. The total storage requirement also depends on the number of queues that you use, the number and size of the messages on the queues, and whether the messages are persistent. You also require archiving capacity on disk, tape, or other media, as well as space for your own application programs.

The following table shows the approximate disk space required when you install various combinations of the product on different platforms. (Values are rounded up to the nearest 5 MB, where a MB is 1,048,576 bytes.)

Amount of disk space required to install various combinations of the product on different platforms.
Platform Client installation 1 Server installation 2 WebSphere MQ MFT installation 3 Full installation 4
AIX 105 MB 175 MB 615 MB 775 MB
HP-UX 175 MB 300 MB 1110 MB 1340 MB
Linux for System x (32 bit) 60 MB 105 MB 430 MB 640 MB
Linux for System x (64 bit) 95 MB 155 MB 500 MB 760 MB
Linux for System p 110 MB 180 MB 540 MB 660 MB
Linux for System z 95 MB 150 MB 490 MB 605 MB
Solaris x86-64, AMD64, EM64T, and compatible processors 75 MB 5 135 MB 5 585 MB 725 MB
Solaris SPARC 75 MB 5 135 MB 5 595 MB 735 MB
Windows (32 bit and 64 bit) 6 340 MB 410 MB 580 MB 790 MB


Notes

  1. A client installation includes the following components:

    • Runtime

    • Client

  2. A server installation includes the following components:

    • Runtime

    • Server

  3. A WebSphere MQ Managed File Transfer installation includes the following components:

    • WebSphere MQ Managed File Transfer Service, Logger, Agent, Tools, and Base components
    • Runtime
    • Server
    • Java
    • JRE

  4. A full installation includes all available components.

  5. On Solaris platforms you must install silently to get this combination of components.

  6. Not all the components listed here are installable features on Windows systems; their functionality is sometimes included in other features. See WebSphere MQ features for Windows systems .


License requirements

You must have purchased sufficient licenses for your installation. The details of the license agreement is stored on your system at installation time so that you can read it at any time. WebSphere MQ supports ITLM (IBM Tivoli License Manager).


License files

At installation, the license agreement files are copied into the /licenses directory under the MQ_INSTALLATION_PATH. You can read them at any time.


ITLM

If you are using ITLM, WebSphere MQ automatically detects ITLM and checks with it each time a queue manager is started. You do not need to take any further action. You can install ITLM before or after WebSphere MQ.

The automatic detection of ITLM applies to both the WebSphere MQ server, and WebSphere MQ Java products.


Preparing the system

On some operating systems, you might have to complete several tasks before you install WebSphere MQ depending on your installation platform. You might also want to complete other tasks, depending on your installation intentions. The tasks that you perform to prepare your systems for installation are listed here. Complete the appropriate tasks for your platform before installing.


Procedure

  1. On UNIX and Linux systems, set up the user and group. See Setting up the user and group on UNIX and Linux systems

  2. On UNIX and Linux, create file systems. See Creating file systems on UNIX and Linux systems

  3. Configure additional settings for your platform:

    • Additional settings for installing on AIX systems

    • Additional settings for installing on HP-UX systems

    • Additional settings for WebSphere MQ on Linux systems

    • Additional settings for installing on Solaris systems

    • Additional restrictions for installing on Windows


What to do next

When you have completed the tasks to prepare the system, you are ready to start installing WebSphere MQ. To install a server, see Installing a WebSphere MQ server . To install a client, see Installing a WebSphere MQ client .


Set up the user and group on UNIX and Linux systems

On UNIX and Linux systems, WebSphere MQ requires a user ID of the name mqm, with a primary group of mqm. The mqm user ID owns the directories and files that contain the resources associated with the product.


Create the user ID and group on UNIX and Linux systems

Set the primary group of the mqm user to the group mqm.

If you are installing WebSphere MQ on multiple systems you might want to ensure each UID and GID of mqm has the same value on all systems. If you are planning to configure multi-instance queue managers, it is essential the UID and GID are the same from system to system. It is also important to have the same UID and GID values in virtualization scenarios.

AIX

You can use the System Management Interface Tool (smit), for which you require root authority.

  1. To create the mqm group: 

     Security & Users
    Groups
      Add a Group
    Set the group name field to mqm.

  2. To create the user mqm: 

     Security & Users
    Users
      Add a User
    Set the user name field to mqm .

  3. To add a password to the new user ID: 

     Security & Users
     Passwords
      Change a User's Password
    Set the password as required.

HP-UX

The user ID value for user mqm must be less than 60,000 to avoid problems with the maintenance update process.

You can use the System Management Homepage (SMH), or the groupadd and useradd commands to work with user IDs.

Linux

RPM creates the mqm user ID and group ID as part of the installation procedure if they do not exist. You might need to create the IDs before running the installation procedure.

Create the IDs using the groupadd and useradd commands to set the UID and GID the same on each machine.

Solaris

The user ID value for user mqm must be less than 262,143 to avoid problems with the maintenance update process.

Create the IDs using the groupadd and useradd commands to set the UID and GID the same on each machine.


Adding existing user IDs to the group on UNIX and Linux systems

To run administration commands, for example crtmqm (create queue manager) or strmqm (start queue manager), your user ID must be a member of the mqm group. This user ID must not be longer than 12 characters.

Users do not need mqm group authority to run applications that use the queue manager; it is needed only for the administration commands.

AIX

You can use smit to add an existing user ID to the mqm group. Display the required menu using this sequence: 

 Security & Users
    Users
      Change / Show Characteristics of a User
Type the name of the user in the User Name field and press Enter. Add mqm to the Group SET field, which is a comma-separated list of the groups to which the user belongs. Users do not need to have their primary group set to mqm. If mqm is in their set of groups, they can use the administration commands.


Log files created by WebSphere MQ Telemetry service

The umask setting of the user ID that creates a queue manager will determine the permissions of the Telemetry log files generated for that queue manager. Even though the ownership of the log files will be set to mqm .


Set up the user and group on HP Integrity NonStop Server

The administrator user ID must be used to administer the WebSphere MQ client for HP Integrity NonStop Server.

Ensure that you have access to a WebSphere MQ client for HP Integrity NonStop Server user ID in the user group called MQM. The MQM group must be created before the client can be installed. All user IDs that are used to install the client must have MQM as their primary group. If this user group does not exist, or you do not have access to such a user, contact your systems administrator.


Create file systems on UNIX and Linux systems

Before installing WebSphere MQ version 7.5, you might need to create file systems for both the product code and working data to be stored. There are minimum storage requirements for these file systems. The default installation directory for the product code can be changed at installation time, but the working data location cannot be changed.


Determining the size of a server installations file system

To determine the size of the /var/mqm file system for a server installation, consider:

Storage requirements for WebSphere MQ also depend on which components you install, and how much working space you need. For more details, see Disk space requirements .


Create a file system for the working data

Before you install WebSphere MQ, create and mount a file system called /var/mqm which is owned by the user mqm in the group mqm; see Setting up the user and group on UNIX and Linux systems . This file system is used by all installations of WebSphere MQ on a system. If possible, use a partition strategy with a separate volume for the WebSphere MQ data. This means that other system activity is not affected if a large amount of WebSphere MQ work builds up.


Create separate file systems for errors and logs

You can also create separate file systems for your log data (/var/mqm/log) and error files (/var/mqm/errors). If possible, place these directories on different physical disks from the queue manager data (/var/mqm/qmgrs) and from each other.

If you create separate file systems the /var/mqm/errors directory can be NFS mounted. However, if you choose to NFS-mount /var/mqm/errors, the error logs might be lost if the network fails.

You can protect the stability of your queue manager by having separate file systems for:

In the case of /var/mqm/errors, it is rare that this directory receives large quantities of data. But it is sometimes seen, particularly if there is a severe system problem leading to WebSphere MQ writing a lot of diagnostic information in to .FDC files. In the case of /var/mqm/trace, files are only written here when you use strmqtrc to start tracing WebSphere MQ.

You can obtain better performance of normal WebSphere MQ operations (for example, syncpoints, MQPUT, MQGET of persistent messages) by placing the following on separate disks:

In the rare event that you need to trace a WebSphere MQ system for problem determination, you can reduce performance impact by placing the /var/mqm/trace file system on a separate disk.

If you are creating separate file systems, allow a minimum of 30 MB of storage for /var/mqm, 100 MB of storage for /var/mqm/log, and 10 MB of storage for /var/mqm/errors. The 100 MB minimum allowance of storage for /var/mqm/log is the absolute minimum required for a single queue manager and is not a recommended value. The size of a file system must be scaled according to the number of queue managers that you intend to use, the number of pages per log file, and the number of log files per queue manager.

To use individual queues that hold more than 2 GB of data, you must enable /var/mqm to use large files.

For more information about file systems, see File system support .

The size of the log file depends on the log settings that you use. The minimum sizes are for circular logging using the default settings. For more information about log sizes, see Calculating the size of the log .

Linux and Solaris

For a client installation, the file system can be mounted on a remote network device, for example NFS.

If you are performing both a client and a server installation, the requirements of the server installation take precedence over the requirements of the client installation.

Allow 15 MB as a minimum for a WebSphere MQ client.

A new sample WebSphere MQ MQI client configuration file is created in the var/mqm directory, by the client package, during installation, but only if this file does not exist. This file contains the ClientExitPath stanza. An example mqclient.ini file is shown in Configuring a client using a configuration file WebSphere MQ MQI client configuration file .

If you are using a common configuration file for multiple clients, either in the WebSphere MQ installation directory or in another location using the MQCLNTCF environment variable, you must grant read access to all user identifiers under which the WebSphere MQ client applications run. If, for any reason, the file cannot be read, the failure is traced, and the search logic continues as if the file had not existed.


Additional settings for installing on UNIX and Linux systems

Additional settings for installing on AIX systems


File descriptors

When running a multi-threaded process such as the agent process, you might reach the soft limit for file descriptors. This limit gives you the WebSphere MQ reason code MQRC_UNEXPECTED_ERROR (2195) and, if there are enough file descriptors, a WebSphere MQ FFST file.

To avoid this problem, increase the process limit for the number of file descriptors. You must alter the nofiles attribute in /etc/security/limits to 10,000 for the mqm user ID, or in the default stanza. To alter the number of file descriptors do these steps:

  1. In a command prompt, check the maximum number of file descriptors available to a process running as mqm:

      lsuser -a nofiles mqm

  2. Set the value to at least 10240:

      chuser nofiles_hard=10240 mqm
      chuser nofiles=10240 mqm


System Resource Limits

Set the system resource limit for data segment and stack segment to unlimited using the following commands in a command prompt:


Additional settings for installing on HP-UX systems


Kernel configuration

It is possible that the default kernel configuration is not adequate because WebSphere MQ uses semaphores and shared memory.

Before installation, review the configuration of the machine and increase the values if necessary. Consider using the values of the tunable kernel parameters given in Figure 1 . These values might need to be increased if you obtain any First Failure Support Technology (FFST) records.

  1. On platforms earlier than HP-UX 11i v1.6 (11.22), if you intended to run a high number of concurrent connections to WebSphere MQ, you were required to configure the number of kernel timers (CALLOUTS) by altering the NCALLOUT kernel parameter. On HP-UX 11i v1.6 (11.22) platforms or later, the NCALLOUT parameter is obsolete as the kernel automatically adjusts the data structures.

  2. Semaphore and swap usage do not vary significantly with message rate or message persistence.

  3. WebSphere MQ queue managers are independent of each other. Therefore system tunable kernel parameters, for example shmmni, semmni, semmns , and semmnu need to allow for the number of queue managers in the system.

See the HP-UX documentation for information about changing these values.

Figure 1. Minimum tunable kernel parameters values 

  
   shmmax           536870912
   shmseg           1024
   shmmni           1024
   semaem           16384
   semvmx           32767
   semmns           16384
   semmni           1024 (semmni < semmns)
   semmnu           16384
   semume           256
   max_thread_proc  66
   maxfiles         10000
   maxfiles_lim     10000
   nfile            20000

  1. For HP-UX 11.23 (11i V2) and later operating systems, the tunable kernel parameters: shmem, sema , semmap, and maxusers, are obsolete.

  2. For HP-UX 11i V3 and later operating systems, the tunable kernel parameter nfile is obsolete.

You must restart the system once you have changed any of the tunable kernel parameters.


System resource limits

You can set global limits for the size of process data segments and the size of process stack segments for the whole system. These limits are set by altering the tunable kernel parameters.

The tunable kernel parameters are:

Parameter What it controls Consider minimum value
maxdsiz Maximum size of the data segment for 32-bit processes 1073741824
maxdsiz_64bit Maximum size of the data segment for 64-bit processes 1073741824
maxssiz Maximum size of the stack segment for 32-bit processes 8388608
maxssiz_64bit Maximum size of the stack segment for 64-bit processes 8388608
If other software on the same machine needs higher values, then the operation of WebSphere MQ is not adversely affected if those higher values are used.

For the full documentation for these parameters see the HP-UX product documentation.

To apply the settings to an HP-UX 11i system which has the System Administration Manager (SAM) utility, you can use SAM to achieve the following steps:

Other releases of HP-UX might provide different facilities to set the tunable kernel parameters. Consult your HP-UX product documentation for the relevant information.


The ulimit shell command

On a per-shell basis, the available limits can be tuned down from the values stored for the System resource limits preceding parameters. Use the ulimit shell command to tune the values of the parameters with a combination of the following switches:

Switch Meaning
-H The hard limit
-S The soft limit
-d The data segments size
-s The stack segment size


Verify that the kernel settings are applied

You can verify that the resource limits have not been lowered by a ulimit command and that the queue manager experiences the correct limits. To do so, go to the shell from which the queue manager is started and enter the following command: 

ulimit -Ha
ulimit -Sa
Among the console output you can see: 

data(kbytes)   1048576
stack(kbytes)  8192
If lower numbers are returned, then a ulimit command has been issued in the current shell to lower the limits. Consult with your system administrator to resolve the issue.

For more information on configuring your system, see How to configure UNIX and Linux systems for WebSphere MQ .


Additional settings for WebSphere MQ on Linux systems

Use this topic to when configuring WebSphere MQ on Linux systems.


Installation DVD

Ensure that you have the correct 32-bit or 64-bit server DVD. To install the 64-bit Server, you must mount the 64-bit Server DVD.


Shell interpreter

Ensure that /bin/sh shell is a valid shell interpreter compatible with the Bourne shell, otherwise the post-installation configuration of WebSphere MQ does not complete successfully. If the shell was not installed by using RPM, you might see a prerequisites failure of /bin/sh shell when you try to install WebSphere MQ. The failure is because the RPM tables do not recognize that a valid shell interpreter is installed. If the failure occurs, you can reinstall the /bin/sh shell by using RPM, or specify the RPM option --nodeps to disable dependency checking during installation of WebSphere MQ. The dbpath option is not supported when installing Linux.


Kernel configuration

WebSphere MQ uses System V IPC resources, in particular shared memory and semaphores.

The minimum configuration for WebSphere MQ for these resources is as follows

If you plan to run more than one queue manager of moderate size on the server, increase the file-max parameter, fs.file-max.

To view the kernel parameters for your system, enter the following commands:

Each of these commands returns the value of the corresponding kernel parameter. For example, cat /proc/sys/kernel/shmmni returns the value for kernel.shmmni. If any of the values is less than the minimum value, you need to increase it to at least the minimum value.

To add or alter these values, log on as a user with root authority. Open the file /etc/sysctl.conf with a text editor, then add or change the following entries to the values shown: 

kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.shmmax = 268435456
kernel.sem = 500 256000 250 1024
fs.file-max = 524288
Then save and close the file.

To load these sysctl values immediately, enter the following command: 

sysctl -p

If you do not issue the sysctl -p command, the new values are loaded when the system is rebooted.


Maximum open files

If the system is heavily loaded, you might need to increase the maximum possible number of open files. If your distribution supports the proc file system you can query the current limit by issuing the following command:

To report on the current maximum, and in-use, number of file descriptors for your system, enter the following commands:

If you are using a pluggable security module such as PAM (Pluggable Authentication Module), ensure that this module does not unduly restrict the number of open files for the mqm user. To report the maximum number of open file descriptors per process for the mqm user, login as the mqm user and enter the following values:

For a standard WebSphere MQ queue manager, set the nofile value for the mqm user to 10240 or more. To set the maximum number of open file descriptors for processes running under the mqm user, add the following information to the /etc/security/limits.conf file: 

mqm              hard    nofile          10240
mqm              soft    nofile          10240


Maximum processes

A running WebSphere MQ queue manager consists of a number of thread programs. Each connected application increases the number of threads running in the queue manager processes. It is normal for an operating system to limit the maximum number of processes that a user runs. The limit prevents operating system failures due to an individual user or subsystem creating too many processes. You must ensure that the maximum number of processes that the mqm user is allowed to run is sufficient. The number of processes must include the number of channels and applications that connect to the queue manager.

The following calculation is useful when determining the number of processes for the mqm user: 

maximum processes = 2048 + maximum WebSphere MQ connections
 + maximum WebSphere MQ channels

You can use the PAM_limits security module to control the number of processes that users run. You can configure the maximum number of processes for the mqm user as follows: 

mqm             hard    nproc           4096
mqm             soft    nproc           4096

For more details on how to configure the PAM_limits security module type, enter the following command: 

man limits.conf

For more information on configuring your system, see How to configure UNIX and Linux systems for WebSphere MQ .


Additional settings for installing on Solaris systems

Configure Solaris systems with the resource limits required by WebSphere MQ.

WebSphere MQ uses semaphores, shared memory, and file descriptors, and it is probable that the default resource limits are not adequate.

If you are using Solaris 10, you must change the default resource limits for each zone WebSphere MQ will be installed in. To set new default limits for all users in the mqm group, set up a project for the mqm group in each zone.

To find out if you already have a project for the mqm group, log in as root and enter the following command: 

projects -l

If you do not already have a group.mqm project defined, enter the following command: 

projadd -c "WebSphere MQ default settings" 
        -K "process.max-file-descriptor=(basic,10000,deny)" 
        -K "project.max-shm-memory=(priv,4GB,deny)"
        -K "project.max-shm-ids=(priv,1024,deny)" 
        -K "project.max-sem-ids=(priv,1024,deny)" group.mqm

If a project called group.mqm is listed, review the attributes for that project. The attributes must include the following minimum values: 

process.max-file-descriptor=(basic,10000,deny)
project.max-sem-ids=(priv,1024,deny)
project.max-shm-ids=(priv,1024,deny)
project.max-shm-memory=(priv,4294967296,deny)
If you need to change any of these values, enter the following command: 

projmod -s -K "process.max-file-descriptor=(basic,10000,deny)" 
           -K "project.max-shm-memory=(priv,4GB,deny)" 
           -K "project.max-shm-ids=(priv,1024,deny)"
           -K "project.max-sem-ids=(priv,1024,deny)" group.mqm
Note that you can omit any attributes from this command that are already correct.

For example, to change only the number of file descriptors, enter the following command: 

projmod -s -K "process.max-file-descriptor=(basic,10000,deny)" group.mqm

(To set only the limits for starting the queue manager under the mqm user, login as mqm and enter the command projects . The first listed project is likely to be default , and so you can use default instead of group.mqm, with the projmod command.)

You can find out what the file descriptor limits for the current project are, by compiling and running the following program.

Before running the program you must create the tryfd file in the current directory: 

/*********************************************************
You must make the tryfd file in the current directory first
before running this program..
**********************************************************/
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>

main() {
int b=0;
int fd;
  for (;;) {
    fd = open ("./tryfd", O_RDONLY);
    if (fd == -1) {
        printf ("fd is %d\n", b);
        perror("fd");
          break;
        }
        b++;
  }
}

To ensure that the attributes for the project group.mqm are used by a user session when running Websphere MQ, make sure that the primary group of that user ID is mqm. In the examples in this topic, the group.mqm project ID will be used. For further information on how projects are associated with user sessions, see Sun's System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for your release of Solaris.

For more information on configuring your system, see How to configure UNIX and Linux systems for WebSphere MQ .


Install WebSphere MQ


Install a WebSphere MQ server

It is possible to have both a server and a client installation on the same machine, for instructions on how to do this see, Installing a WebSphere MQ client .

WebSphere MQ Telemetry is installed as part of the WebSphere MQ Server installation. It must be selected as part of a custom installation.


Procedure

Interactive installation

Non-interactive installation


Install WebSphere MQ server on AIX

WebSphere MQ can be installed into System Workload Partitions (WPARs) with both shared and private file systems. For installation into private file systems, WebSphere MQ can be installed directly into the System WPAR using the procedure outlined in this topic. For installation into shared file systems, see Installing WebSphere MQ in AIX Workload Partitions . There are some limitations for shared /usr file systems:

During installation, errors relating to errupdate or trcupdate might occur. This can caused by installing to a non-default location, if so these errors can be safely ignored. However, native trace for WebSphere MQ is only supported when installed in the default location.

WebSphere MQ is supplied as a set of filesets that are installed using the standard AIX installation tools. The procedure uses the system management interface tool (SMIT), but you can choose to use installp, geninstall or the web-based System Manager. You can select which components you want to install. The components and file sets are listed in Choosing what to install .

This procedure installs WebSphere MQ into the default location of /usr/mqm.

If you already have an installation of WebSphere MQ in the default location, for example, you have an installation of WebSphere MQ version 7.0.1.6, or later, on the system, you must install in a non-default location. To install to a non-default location, you can either use installp (see Non-interactive installation of WebSphere MQ server on AIX ), or use the Relocatable Software Installation and Maintenance option within smit (see step 3 ).


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Select the required smit window using the following sequence: 

    Software Installation and Maintenance     
    Install and Update Software         
        Install and Update from ALL Available Software

  4. List the software in the SOFTWARE to install field:

    1. Enter .

    2. Press F4

      If the F4 key does not work, use <Esc>-<4>

  5. Select the filesets to install from the list.

    Ensure that you include the appropriate message catalog if you require messages in a language different from the language specified by the locale selected on your system. Enter ALL to install all applicable filesets. If you need to convert data to and from Unicode on your system, you must install the following file sets: 

    bos.iconv.ucs.com     Unicode converters for AIX sets 
bos.iconv.ucs.ebcdic  Unicode converters for EBCDIC sets 
bos.iconv.ucs.pc      Unicode converters for PC sets

  6. Change ACCEPT new license agreements? to yes

  7. Change Preview new LICENSE agreements? to no

  8. Press Enter


What to do next


Non-interactive installation of WebSphere MQ server on AIX

Install WebSphere MQ server from the command line using the AIX installp command.

During installation, errors relating to errupdate or trcupdate might occur. This can caused by installing to a non-default location, if so these errors can be safely ignored. However, native trace for WebSphere MQ is only supported when installed in the default location.

You can use this method to install to a non-default location, and can select which components you want to install. The components and filesets are listed in Choosing what to install .


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the CD, a network location, or a local file system directory.

  3. Install the product in one of the following ways

    • Install the whole product in the default location: 

      installp -acgXYd. all

    • Install selected filesets in the default location: 

      installp -acgXYd. list of file sets

    • Install the whole product in a non-default location using the -R flag: 

      installp -R USIL_Directory -acgXYd. all

    • Install selected filesets in a non-default location using the -R flag: 

      installp -R USIL_Directory -acgXYd. list of file sets

    where USIL_Directory is a directory which exists before the command is run; it must not contain any spaces or usr/mqm. WebSphere MQ is installed underneath the directory specified. For example, if /USIL1 is specified, the WebSphere MQ product files are located in /USIL1/usr/mqm. This location is known as the MQ_INSTALLATION_PATH.


What to do next


Install WebSphere MQ server on HP-UX

Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system . This task describes the installation of a server, using the swinstall program to select which components you want to install. The components are listed in Choosing what to install . If you are using a screen reader, use the non-interactive installation option Non-interactive installation of WebSphere MQ server on HP-UX , so that you can accept the license without viewing it.

If you are installing WebSphere MQ from a depot that contains service update packages, read HP-UX: Applying maintenance level updates on WebSphere MQ version 7.5 before installing the service update packages.


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Accept the license by running the mqlicense script: 

    ./mqlicense.sh

    The license is displayed. If you accept the license, you can continue the installation.

  4. Start the interactive installation procedure by typing the following command, 

    swinstall -s /installation_file
    /installation_file is the absolute path to the installation file. The path must begin with a / and end with the name of the installation file. In the resulting menu screen, select MQSERIES.

    1. If you do not want to install all WebSphere MQ components, open MQSERIES

      1. Mark the components you want to install. The installer resolves dependencies automatically.

      2. Review the information displayed by the installer.

  5. Optional: To install WebSphere MQ to a non-default location, select Actions > Change Product Location. The default installation location is /opt/mqm.

    For each installation, all of the WebSphere MQ components that you require must be installed in the same location.

    The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces. Ensure that you do not select Actions > Change Target by accident, they are not the same.

  6. If this installation is not the first installation on the system, select Options > Allow creation of multiple versions

  7. Select Actions > Install. The log file tells you if there are any problems that need fixing.

  8. Fix any problems, and click OK to install. You are informed when the installation has finished.

  9. If this installation is not the first installation on the system, you must enter the following command to configure WebSphere MQ: 

    swconfig -x allow_multiple_versions=true MQSERIES,l=MQ_INSTALLATION_PATH
    where MQ_INSTALLATION_PATH is the path where you have just installed WebSphere MQ. If you do not enter this command, the swlist command reports the installation as installed instead of configured. You must not use WebSphere MQ unless the installation is configured.


What to do next


Non-interactive installation of WebSphere MQ server on HP-UX

You can perform a non-interactive installation of WebSphere MQ using the swinstall command. A non-interactive installation is also known as a silent, or unattended installation. Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system . This topic describes the non-interactive installation of a server, using the swinstall program to select which components you want to install. The components and are listed in Choosing what to install .


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the CD, a network location, or a local file system directory.

  3. Accept the WebSphere MQ license agreement without an interactive prompt: 

    ./mqlicense.sh -accept

  4. Install WebSphere MQ using the swinstall command:

    1. If this installation is not the first installation on the system, you must add -x allow_multiple_versions=true to the swinstall command.

    2. Add the names of the components to install as parameters of the swinstall command. The installer automatically resolves any dependencies.

    3. Optional: Identify the installation location by adding ,l=MQ_INSTALLATION_PATH as a parameter of the swinstall command. For each installation, all of the WebSphere MQ components that you require must be installed in the same location. The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

    For example, to install all WebSphere MQ components, in a non-default location, as the first installation, enter the following command: 

    swinstall -s /installation_file.v11 MQSERIES,l=/opt/customLocation
    To perform a partial installation, providing a list of components, in the default location, as the second installation, enter the following command: 

    swinstall -x allow_multiple_versions=true -s /installation_file.v11
MQSERIES.MQM-RUNTIME MQSERIES.MQM-BASE MQSERIES.MQM-SERVER
    /installation_file.v11 is the absolute path to the installation file. The path must begin with a / and end with the name of the installation file. The installation file has the extension .v11.

  5. If this installation is not the first installation on the system, you must enter the following command to configure the installation: 

    swconfig -x allow_multiple_versions=true MQSERIES,l=MQ_INSTALLATION_PATH
    where MQ_INSTALLATION_PATH is the path where you have just installed WebSphere MQ. If you do not enter this command, the swlist command reports the installation as installed instead of configured. You must not use WebSphere MQ unless the installation is configured.


Example

The example shows the command to run a silent, full installation in the default location. Notice that all the language features are installed. Run a partial installation to install your chosen languages. 

cd /downloads/WMQInstallFiles
swinstall -v -x source_directory=$PWD/hpUxxxxx.v11 MQSERIES


What to do next


Install WebSphere MQ server on Linux

You can install a WebSphere MQ server on either a 32-bit or 64-bit Linux system.

Install the server by using the Rational Portfolio Manager Package Manager installer to select which components you want to install. The components and package names are listed in Choosing what to install .


Procedure

  1. Log in as root, or switch to the superuser by using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the server DVD, a network location, or a local file system directory.

  3. Run the mqlicense.sh script. To view a text-only version of the license, which can be read by a screen reader, type the following message: 

    ./mqlicense.sh -text_only
    The license is displayed.

    You must accept the license agreement before you can proceed with the installation.

  4. If this installation is not the first installation of WebSphere MQ version 7.5 on the system, you must run the crtmqpkg command to create a unique set of packages to install on the system. To run the crtmqpkg command to run on Linux, you must install the pax command and rpmbuild, which is located in the rpm-build package. The crtmqpkg command is required only if this is not the first installation of WebSphere MQ version 7.5 on the system. If you have earlier versions of WebSphere MQ version 7.5 installed on your system, then installing WebSphere MQ version 7.5 will work correctly if you install it in a different location.

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing, that uniquely identifies the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9. This command creates a full copy of the installation packages in the /var/tmp subdirectory. You must ensure that the system has enough space before running the command.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a subdirectory of the /var/tmp/mq_rpms directory, in which the unique set of packages is created. The packages have the suffix value contained within the file name. In the following example, the suffix of "1"./crtmqpkg 1 means that there is :a subdirectory named /var/tmp/mq_rpms/1/i386.

      The packages are renamed according to the subdirectory, for example: 

      From: MQSeriesRuntime-7.5.0-0.i386.rpm
To: MQSeriesRuntime_1-7.5.0-0.i386.rpm

  5. Install WebSphere MQ. At a minimum, you must install the MQSeriesRuntime and the MQSeriesServer components.

    • To install to the default location, /opt/mqm, use the rpm -ivh command to install each component that you require.

      For example, to install the runtime and server components to the default location, use the following command:

        rpm -ivh MQSeriesRuntime-*.rpm MQSeriesServer-*.rpm

      To install all components to the default location use the following command: 

      rpm -ivh MQSeries*.rpm

    • To install to a non-default location, use the rpm --prefix option. For each installation, all of the WebSphere MQ components that you require must be installed in the same location.

      The installation path specified must be either an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

      For example, enter the following installation path to install the runtime and server components to the /opt/customLocation directory on a 32-bit Linux system: 

      rpm --prefix /opt/customLocation -ivh MQSeriesRuntime_*.rpm
MQSeriesServer_*.rpm


What to do next


Install WebSphere MQ server on Solaris

This task describes the installation of the WebSphere MQ for Solaris server, using the pkgadd program. You can choose which components you want to install. The components are listed in Choosing what to install .


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the server DVD, a network location, or a local file system directory.

  3. Run the mqlicense.sh script to accept the license: 

    ./mqlicense.sh
    To view a text-only version of the license, which can be read by a screen reader, type: 

    ./mqlicense.sh -text_only
    The license is displayed. Follow the instructions to accept the license. If you accept the license, the installation continues. If you do not accept the license, you cannot continue the installation process.

  4. If this installation is not the first installation on the system, you must run crtmqpkg to create a unique set of packages to install on the system:

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing that uniquely identifies the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.

      The ctrmqpkg script can use two environment variables which are useful when you are installing from a non-disk media location:

      • CDROOT, the root of the installation media or downloaded installation files.

      • TMPDIR, the output location of the modified installation files.

      No environment variables are required if you are running the image as ./crtmqpkg.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a subdirectory of /var/spool , in which the unique set of packages is created. The packages have the suffix value contained within the file name.

  5. Start the installation process

    • If the installation is the first installation on the system, enter the following command to start the installation process: 

      pkgadd -d.

    • If the installation is not the first installation on the system, enter the following command to start the installation process: 

      pkgadd mqm-suffix
      where suffix is the suffix chosen in the previous step.

  6. You are prompted to choose a location for installation.
    • To install to the default location, /opt/mqm , enter y.

    • To install to a non-default directory, enter n . Then, enter the required installation path, and confirm your choice.

  7. When the list of components is displayed, enter the numbers of the components that you require, separated by spaces or commas.

  8. If the path chosen in step 6 does not exist, you are asked if you want to create it. You must enter y to proceed.

  9. Answer any questions appropriately for your system. If you are prompted to choose whether to install certain WebSphere MQ files as setuid/setgid files, you must enter y.

  10. A message is issued when the installation is complete. Enter q to exit the pkgadd program.


What to do next


Non-interactive installation of WebSphere MQ server on Solaris

Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system .

You can perform a silent installation of WebSphere MQ. A sample script file called silent.sh is supplied in the silent directory on the DVD. You can use this script to perform a non-interactive installation that requires no input and shows nothing on the screen. It must be run as root.

The installation script silent.sh uses an admin file and a response file, both of which are supplied in the silent directory. You can use these files as supplied to perform a silent installation of all the components, including all the national language features, to the default location.


Procedure

  1. Copy the silent.sh script into a writeable directory.

  2. If this installation is not the first installation on the system, you must run crtmqpkg to create a unique set of packages to install on the system:

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a sub-directory of /var/spool, in which the unique set of packages is created. The packages have the suffix value contained within the filename.

    Once a new package has been generated for the second installation the silent.sh script needs to have its MQ_PACKAGE_NAME variable modified so that its value is not mqm but the new package name.

    Also the MQ_PACKAGE_LOCATION variable needs to be modified so that its value is not $MQ_MEDIA_LOCATION but the location of the new package (which by default is /var/spool/pkg).

  3. Optional: To change where the WebSphere MQ server DVD is mounted, you must update the values in the silent.sh script. By default, the script assumes that the server DVD has been mounted at /cdrom/mq_solaris.

  4. Optional: To change where the output and logs are written to, update the values in the silent.sh script. By default, output and logs are written to the file /var/tmp/mq.install.

  5. Optional: To install to a non-default location, you must update the MQ_INSTALLATION_PATH variable in the silent.sh script.

    • The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

    • The directory specified must exist before running the pkgadd command.

  6. Optional: To change the components that are installed, you must edit the response file. A list of all the installable WebSphere MQ components can be found at: Choosing what to install .

    Solaris does not check, during a silent installation, that prerequisite components are installed. You can use the following procedure to create a response file interactively, before using it to install the product. pkgask prompts you for the names of the components to install.

    1. Run the mqlicense.sh command to accept the license agreement for the product.

    2. pkgask -d path_to_install_image -r response_file mqm

    The inputs to pkgask are the same as those inputs documented for pkgadd, but instead of the product being installed a response file is created.

  7. Optional: If you have edited the response file, you must then edit the silent.sh to use your custom response file.

  8. To start the installation, run silent.sh.

  9. Check the log file for any errors.


What to do next


Install WebSphere MQ server on Windows

This topic describes how to install WebSphere MQ server on Windows systems by using the Launchpad. This procedure can be used for installing a first or a subsequent installation.


Install using the Launchpad

About this task

These instructions cover how to display the installation Launchpad window. You can use the launchpad to make a compact, typical, or custom installation of WebSphere MQ. You can reuse the launchpad multiple times to install further installations. It automatically selects the next available installation name, instance, and location to use. To view all the installation types and the features that are installed with each option, see Plan the installation on Windows systems .

Note that if you have previously uninstalled WebSphere MQ from your system (see Uninstalling WebSphere MQ on Windows systems ), some configuration information might remain, and some default values might be changed.

Procedure

  1. Access the WebSphere MQ installation image. The location might be the mount point of the DVD, a network location, or a local file system directory.

  2. Locate setup.exe in the base directory of the WebSphere MQ installation image.
    • From a DVD, this location might be: 

      E:\setup.exe

    • From a network location, this location might be: 

      m:\instmqs\setup.exe

    • From a local file system directory, this location might be: 

      C:\instmqs\setup.exe

  3. Double-click the Setup icon to start the installation process. It is possible to run either by:
    • Running setup.exe from the command prompt. Or

    • Double-clicking setup.exe from Windows Explorer.

    If you are installing on a Windows system with UAC enabled, accept the Windows prompt to allow the launchpad to run as elevated. During installation, you might also see Open File - Security Warning dialog boxes that list International Business Machines Limited as the publisher. Click Run to allow the installation to continue.

    The WebSphere MQ Installation Launchpad window is displayed.

  4. Continue to follow the Launchpad instructions as shown on screen.

What to do next


Install WebSphere MQ using SCCM

You can install WebSphere MQ using the System Center Configuration Manager (SCCM).


Procedure

  1. Create a folder on the SCCM server and copy the WebSphere MQ DVD image into that folder.

  2. Make the folder the X drive of the SCCM client systems.

  3. Use the Configuration Manager Console for SCCM, create a package:

    1. Click Computer Management > Software Distribution > Packages.

    2. Right-click on Packages and click New > Package from Definition.

    3. In the wizard, select the WebSphere MQ.SMS file from the folder that you copied the WebSphere MQ DVD image into. If you chose to use a drive letter other than X for the client systems, you must modify the commands in the WebSphere MQ.SMS file to use the appropriate drive letter.

  4. Optional: To install WebSphere MQ to a non-default location, you must add the following two parameters to the command line under Program Properties: 

    PGMFOLDER="MQ_INSTALLATION_PATH"
DATFOLDER="MQ_INSTALLATION_PATH\data"
    where MQ_INSTALLATION_PATH refers to the path where you want to install WebSphere MQ.

  5. Under the package you created, Right click Distribution Points and then click New distribution Points.

  6. In the wizard, select the SCCM server as the distribution point.

  7. Use the Configuration Manager Console for SCCM, distribute the software:

    1. Right-click the package you created and click Distribute > Software.

    2. In the wizard, select All Systems for Collections.

  8. Once the Advertisement Status for the package shows as Received, manually initiate the WebSphere MQ unattended installation:

    1. Log on to the SCCM client system
    2. Click Control Panel > Run Advertised Program and select the package to run


Advanced installation using msiexec

If you are running WebSphere MQ on Windows systems with User Account Control (UAC) enabled, you must invoke the installation with elevated privileges. If you are using the Command prompt or WebSphere MQ Explorer elevate privileges by using a right-click to start the program and selecting Run as administrator. If you try to run msiexec without using elevated privileges, the installation fails with an error of AMQ4353 in the installation log.

WebSphere MQ on Windows uses the MSI technology to install software. MSI provides both an interactive installation and a non interactive installation. An interactive installation displays panels and ask questions.

The msiexec command uses parameters to give MSI some or all of the information that can also be specified through panels during an interactive installation. This means that a user can create a reusable automated or semi-automated installation configuration. Parameters can be given through the command line, a transform file, a response file, or a combination of the three.


Procedure

To install using msiexec, at the command line, enter the msiexec command in the following format: 

msiexec parameters [USEINI="response-file"] [TRANSFORMS="transform_file"]

Where:

parameters

are either command-line parameters preceded by a / character, or property=value pairs (if using both forms of parameter always put the command-line parameters first). For further information, see Specifying command line parameters with msiexec , which contains a link to the web site that lists all the command line parameters that are available.

For an unattended installation, you must include the /q or /qn parameter in the command line. Without this parameter, the installation is interactive. You must include the /i parameter and the file location of the WebSphere MQ installer package.

response-file

is the full path and file name of the file that contains the [Response] stanza and the required property=value pairs, for example C:\MyResponseFile.ini. An example response file, Response.ini, is supplied with WebSphere MQ. This file contains default installation parameters. For further information, see Using a response file with msiexec .

transform_file

is the full path and file name of a transform file. For further information, see Using transforms with msiexec and Multiple installation using MSI Instance ID .
For a silent installation to succeed, the AGREETOLICENSE=?YES? property must be defined either on the command line or in the response file.

After the command has been entered, the command prompt immediately reappears. WebSphere MQ is installing as a background process. If you have entered parameters to produce a log, check this file to see how the installation is progressing. If the installation completes successfully, you see the message Installation operation completed successfully in the log file.


Specifying command line parameters with msiexec

About this task

The msiexec command can accept two types of parameters on the command line, as follows:

Example

Here is an example of a typical msiexec command. All parameters, separated by one or more spaces, must be typed on the same line as the msiexec call. 

msiexec
 /i  path\MSI\IBM WebSphere MQ.msi 
 /l*v c:\install.log
 /q
 TRANSFORMS= 1033.mst 
 AGREETOLICENSE= yes 
 ADDLOCAL= Server

Here is an example of a typical msiexec command when you are installing a second copy of WebSphere MQ version 7.5. All parameters, separated by one or more spaces, must be typed on the same line as the msiexec call. 

msiexec
 /i  path\MSI\IBM WebSphere MQ.msi 
 /l*v c:\install.log
 /q
 TRANSFORMS= :InstanceId2.mst;1033.mst 
 AGREETOLICENSE= yes 
 ADDLOCAL= Server 
 MSINEWINSTANCE=1

Where /l*v c:\install.log writes installation log to file c:\install.log.

The following table shows the parameters which can only be provided on the command line and not in a response file.

msiexec property=value parameters

Property Values Meaning
USEINI path\file_name Use the specified response file. See Using a response file with msiexec
SAVEINI path\file_name Generate a response file during installation. The file contains those parameters selected for this installation that a user might make during an interactive installation.
ONLYINI 1|yes| "" 1, yes or any value other than null. End the installation before updating the target system, but after generating a response file, if this is specified.

"". Continue the installation and update the target system (the default).

TRANSFORMS :InstanceIdx.mst|path\file_name|:InstanceIdx.mst;path\file_name The :InstanceIdx.mst value is only required for a subsequent installation of WebSphere MQ version 7.5. The path\file_name specifies what transform (.mst) files must be applied to the product. For example, "1033.mst" specifies the supplied U.S. English transform file.
MSINEWINSTANCE 1 This property is only required for subsequent installations of WebSphere MQ version 7.5


Use a response file with msiexec

About this task

You can use the msiexec command with a parameter which specifies additional properties are defined in a response file. You can combine the msiexec command-line parameters described in Specifying command line parameters with msiexec .

A response file is an ASCII text file, with a format like a Windows .ini file, that contains the stanza [Response]. The [Response] stanza contains some or all the parameters that would normally be specified as part of an interactive installation. The parameters are given in a property=value pair format. Any other stanzas in the response file are ignored by msiexec. An example response file, Response.ini, is supplied with WebSphere MQ. It contains the default installation parameters.

Procedure

A typical example of an msiexec command is: msiexec /i path\MSI\IBM WebSphere MQ.msi /l*v c:\install.log TRANSFORMS= 1033.mst USEINI= C:\MQ\Responsefile

If a parameter is specified both on the command line and in a response file, the setting on the command line takes precedence. All the parameters available for use in a response file can also be used on the command line, for a list of these see Table 2 .

In the response file, all text is in English, and comments begin with a ; character.

For information about creating a response file, see Creating a response file .

Example

An example of a typical response file: 

[Response]
PGMFOLDER="c:\mqm"
DATFOLDER="c:\mqm\data"
LOGFOLDER="c:\mqm\log"
AGREETOLICENSE="yes"
LAUNCHWIZ=""
WIZPARMFILE="d:\MQParms.ini"
ADDLOCAL="Server,Client"
REMOVE="Toolkit"

Response file parameters

Property Values Meaning
PGMFOLDER path Folder for the WebSphere MQ program files. For example, c:\mqm.
DATFOLDER path Folder for the WebSphere MQ data files. For example, c:\mqm\data. Multiple installations of WebSphere MQ all use the same DATFOLDER.
LOGFOLDER path Folder for the WebSphere MQ queue manager log files. For example, c:\mqm\log. Multiple installations of WebSphere MQ all use the same LOGFOLDER.
USERCHOICE 0|no If the command line or response file specifies parameters to install features, a dialog can be displayed to prompt the user to accept the preselected options, or review and possibly change them.

0 or no. Suppresses display of the dialog.

Anything else. Dialog is displayed.

Not used for a silent installation.

AGREETOLICENSE yes Accept the terms of the license. Set to yes before a silent installation.

If the installation is not silent, this parameter is ignored.

KEEPQMDATA keep |delete If the Server feature is to be uninstalled, whether to delete any existing queue managers.

delete removes any existing queue managers.

keep, or any other value, keeps them. This property is only valid on a final server uninstall. If used on any other server unistalls this property is ignored.

LAUNCHWIZ 0|1|yes|no| "" 0 or no. Do not launch the Prepare WebSphere MQ wizard after WebSphere MQ is installed.

1 or yes. Launch the Prepare WebSphere MQ wizard if the Server feature is installed.

"". Launch the Prepare WebSphere MQ wizard to install the Server (the default).

If this option is to launch the Prepare WebSphere MQ wizard, you can specify the WIZPARMFILE, either in this file, or on the command line.

The Prepare WebSphere MQ wizard must be run to make your WebSphere MQ installation operational. If you choose not to launch it here, you must run it before using WebSphere MQ.

WIZPARMFILE path\file_name When specified, the file that contains the parameters to pass to the Prepare WebSphere MQ wizard when it is launched. These are in the [Services].
ADDLOCAL feature, feature, All| "" A comma-separated list of features to install locally. For a list of valid feature names, see WebSphere MQ features for Windows systems .

All installs all features

"" installs the typical features. If you do not want a feature use REMOVE="feature" If this is a new installation the typical features (Server, Explorer, Java™ Messaging and SOAP Transport, and Development Toolkit) are installed by default irrespective of the feature list provided in the ADDLOCAL property. If you do not want a feature use REMOVE="feature"

REMOVE feature, feature, |All| "" A comma-separated list of features to remove. For a list of valid feature names, see WebSphere MQ features for Windows systems .

All uninstalls all features

"" uninstalls no features (the default).

STARTSERVICE 0|no| "" 0 or no. Do not start the WebSphere MQ Service at the end of installation.

"" (the default). Start the WebSphere MQ Service at the end of installation if it was running at the start, or if this is a new installation.

Anything else. Start the Service at the end of the installation.

Ignored if the server feature is not installed.

If you do not start the WebSphere MQ Service, WebSphere MQ will not be operational and queue managers will not start. You must run the Prepare WebSphere MQ wizard for the service to be correctly configured.

This parameter is only valid if LAUNCHWIZ is set to no.

STARTTASKBAR 0|no| "" 0 or no. Do not start the WebSphere MQ taskbar application at the end of installation.

"" (the default). Start the WebSphere MQ taskbar application at the end of installation if it was running at the start, or if this is a new installation.

Anything else. Start the taskbar application at the end of the installation.

Ignored if the server feature is not installed.

This parameter is only valid if LAUNCHWIZ is set to no.

INSTALLATIONDESC ?Description of installation? Sets the installation description from the command line. Subject to the documented installation description length limitations
INSTALLATIONNAME [INSTALLATION0,]?Name? Sets the installation name from the command line. Subject to the documented installation name character and length limitations. Supply INSTALLATION0,Name only when upgrading from versions of WebSphere MQ before version 7.5.
MAKEPRIMARY 0|1| "" Makes the installation primary, if possible, or removes the primary flag. 1 = Make primary, 0 = Make non-primary, - use default algorithm This option is ignored if a version of WebSphere MQ before version 7.5 is installed, or if another installation of WebSphere MQ version 7.5 is present and set as the primary.


Multiple installation using MSI Instance ID

This topic describes how to choose the MSI instance ID you require for non-interactive multiple installations. In order to support non-interactive multiple installations, you need to find out whether the instance ID you want to use is already in use or not and choose the appropriate one. For each installation media (for example, each 7.5 client and 7.5 server), Instance ID 1 is the default ID which is used for single installations. To install alongside Instance ID 1 you need to specify which instance you want to use. If you have already installed instance 1, 2, and 3 then you need to find out what the next available instance is, for instance, Instance ID 4. Similarly, if instance 2 has been removed, you need to find out that there is a gap that can be reused. You can find out which Instance ID is currently in use using the dspmqinst command.


Procedure

  1. Type dspmqinst to find a free MSI Instance in the media being installed by reviewing the MSIMedia and MSIInstanceId values for the versions already installed. For example: 

    InstName:      Installation1
InstDesc:
Identifier:    2
InstPath:      C:\mq\install1
Version:       7.5.0.0
Primary:       Yes
State:         Available
MSIProdCode:   {0730749B-080D-4A2E-B63D-85CF09AE0EF0}
MSIMedia:      7.5 Server MSIInstanceId: 1

  2. If MSI Instance ID 1 is in use and you want to use MSI Instance ID 2, the following parameters must be added to the msiexec call: 

    MSINEWINSTANCE=1 TRANSFORMS=:InstanceId2.mst


What to do next

For multiple installations, the INSTALLATIONNAME or PGMFOLDER must be supplied as an additional parameter on any non-interactive installation command. Supplying the INSTALLATIONNAME or PGMFOLDER ensures that you do not work with the wrong installation in case you omit or incorrectly specify the TRANSFORMS parameter.


Use transforms with msiexec

MSI can use transforms to modify an installation. During WebSphere MQ installation, transforms can be used to support different national languages. WebSphere MQ is supplied with transform files in the \MSI folder of the Server image. These files are also embedded in the WebSphere MQ Windows installer package, IBM WebSphere MQ.msi.

On the msiexec command line, you can specify the required language by using the TRANSFORMS property in a property=value pair. For example: 

TRANSFORMS="1033.mst"

You can also specify the full path and file name of the transform file. Again, the quotation marks surrounding the value are optional. For example: 

TRANSFORMS="D:\Msi\1033.mst"

Table 1 shows the locale identifier, language, and the transform file name to use in the msiexec command line.

You might need to merge transforms to install multiple installations of the same version, for example: 

TRANSFORMS=":InstanceId2.mst;D:\Msi\1033.mst"

You can also specify the required language by using the MQLANGUAGE property with the MQParms command. For information about the msiexec property=value parameters, see MQParms parameter file .


Parameters

Supplied transform files for various language support. This table shows the supplied transform files, the resulting language, and the numeric value to use in the msiexec command line.

Language Transform File name Value
U.S. English 1033.mst 1033
German 1031.mst 1031
French 1036.mst 1036
Spanish 1034.mst 1034
Italian 1040.mst 1040
Brazilian Portuguese 1046.mst 1046
Japanese 1041.mst 1041
Korean 1042.mst 1042
Simplified Chinese 2052.mst 2052
Traditional Chinese 1028.mst 1028
Czech 1029.mst 1029
Russian 1049.mst 1049
Hungarian 1038.mst 1038
Polish 1045.mst 1045


Create a response file

A response file is used with msiexec. You can create it in three ways. A response file is used with the msiexec command, for further information see Using a response file with msiexec .


Procedure

There are three ways to create a response file for installation


Example

A typical example of using msiexec with the SAVEINI parameter is here: 

msiexec /i "path\IBM WebSphere MQ.msi" /q SAVEINI="response_file" 
TRANSFORMS="1033.mst" AGREETOLICENSE="yes"


Use the MQParms command

You can use the MQParms command to invoke installation or uninstallation. This command can use parameters on a command line, or those specified in a parameter file. The parameter file is an ASCII text file that contains the parameter values that you want to set for the installation. The MQParms command takes the specified parameters and generates the corresponding msiexec command line.

This means that you can save all the parameters that you want to use with the msiexec command in a single file.

If you are running WebSphere MQ on Windows systems with User Account Control (UAC) enabled, you must invoke the installation with elevated privileges. If you are using the Command prompt or WebSphere MQ Explorer elevate privileges by using a right-click to start the program and selecting Run as administrator. If you try to run the MQParms program without using elevated privileges, the installation fails with an error of AMQ4353 in the installation log.

For silent operations, this must include the /q or /qn parameter, either on the command line, or in the [MSI] stanza of the parameter file. You must also set the AGREETOLICENSE parameter to "yes".

You can specify many more parameters in the parameter file that you use with the MQParms command than you can in the response file that you use directly with the msiexec command. Also, as well as parameters that the WebSphere MQ installation uses, you can specify parameters that can be used by the Prepare WebSphere MQ wizard.

If you do not complete the Prepare WebSphere MQ Wizard directly after WebSphere MQ installations or if for any reason your machine is rebooted between completing WebSphere MQ installation and completing the Prepare WebSphere MQ Wizard, ensure that the wizard is run with Administrator privilege afterward, otherwise the installation is incomplete, and might fail. You might also see Open File - Security Warning dialog boxes that list International Business Machines Limited as the publisher. Click Run to allow the wizard to continue

An example of the file MQParms.ini is supplied with WebSphere MQ. This file contains default installation parameters.

There are two ways to create a parameter file for installation:

To invoke installation using the MQParms command:


Procedure

  1. From a command line, change to the root folder of the WebSphere MQ Server DVD (that is, the location of the file MQParms.exe).

  2. Enter the following command: 

    MQParms parameter_file parameters]

    where:

    parameter_file

    is the file that contains the required parameter values. If this file is not in the same folder as MQParms.exe, specify the full path and file name. If you do not specify a parameter file, the default is MQParms.ini. For a silent install, the MQParms_silent.ini parameter file can be used. For further details, see MQParms parameter file .

    parameters

    are one or more command-line parameters, for a list of these, see the MSDN Command-Line Options web page .


Example

A typical example of an MQParms command is: 

MQParms "c:\MyParamsFile.ini" /l*v c:\install.log

A typical example of an MQParms command when you are installing a second copy of WebSphere MQ version 7.5 is: 

MQParms "c:\MyParamsFile.ini" /l*v c:\install.log TRANSFORMS=":InstanceId2.mst;1033.mst" MSINEWINSTANCE=1
Alternatively, TRANSFORMS and MSINEWINSTANCE can be specified in the MSI stanza of the parameter file.

If you specify a parameter both on the command line and in the parameter file, the setting on the command line takes precedence.

If you specify a parameter file, you might want to run the encryption utility before you use the MQParms command (see Encrypting a parameter file ).

If you do not specify /i, /x, /a, or /j, MQParms defaults to standard installation using the WebSphere MQ Windows Installer package, IBM WebSphere MQ.msi. That is, it generates the following part of the command line: 

/i "current_folder\MSI\IBM WebSphere MQ.msi"

If you do not specify a WIZPARMFILE parameter, MQParms defaults to the current parameter file. That is, it generates the following part of the command: 

WIZPARMFILE="current_folder\current_parameter_file"


MQParms parameter file

A parameter file is an ASCII text file that contains sections (stanzas) with parameters that can be used by the MQParms command. Typically, this is an initialization file such as MQParms.ini.

The MQParms command takes parameters from the following stanzas in the file:

[MSI]

Contains general properties related to how the MQParms command runs and to the installation of WebSphere MQ.

The properties that you can set in this stanza are listed in Advanced installation using msiexec , and Table 1 .

[Services]

Contains properties related to WebSphere MQ account configuration, in particular, the user account required for WebSphere MQ Services. If you are installing WebSphere MQ on a network where the domain controller is on a Windows 2003 server, you probably need details of a special domain account. For further information, see Configuring WebSphere MQ accounts and Configuring WebSphere MQ with the Prepare WebSphere MQ wizard .

The properties that you can set in this stanza are listed in Table 3 .

MQParms ignores any other stanzas in the file.

The stanza parameters are in the form property=value, where property is always interpreted as uppercase, but value is case sensitive. If a value string includes a blank, it must be enclosed in double quotation marks. Most other values can be enclosed in double quotation marks. Some properties can take more than one value, for example: 

ADDLOCAL="Server,Client"

To clear a property, set its value to an empty string, for example: 

REINSTALL=""

The following tables show the properties that you can set. The default is shown in bold.

For the [MSI] stanza, you can enter parameters in command line format (for example, /q) and parameters in property=value format (for example, ADDLOCAL="Server"). Refer to Table 1 , Table 2 , and Table 3 for the properties used to install WebSphere MQ. Table 1 shows additional properties in the stanza that affect how the MQParms command runs, but that do not affect the installation.

Properties used by MQParms in the MSI stanza

Property Values Description
MQPLOG path|file_name MQParms generates a text log file with the specified name and location.
MQPLANGUAGE


system |user|
transform_value|existing

The installation language.

system. Install using the language of the default system locale (the default).

User. Install using the language of the default locale of the user.

transform_value. Install using the language specified by this value. See Table 2 .

existing. If MQ already exists on the system, the same language will be used by default, otherwise system is used.

MQPSMS 0 |no 0 or no. MQParms does not wait for the msiexec command to end (the default).

Any other value. MQParms waits for the msiexec command to end.

MQPINUSE 0 |1 If MQPINUSE is set to 1, MQParams continues installing even if WebSphere MQ files are in use. If this option is used a reboot will be required to complete the installation.
MQPNOREBOOT 0 |1 If MQPNOREBOOT is set to 1, the reboot that is required if installation takes place while WebSphere MQ files are still in use will be suppressed.

Valid values for the MQPLANGUAGE property

Language Valid values
U.S. English English en_us 1033
German German de_de 1031
French French fr_fr 1036
Spanish Spanish es_es 1034
Italian Italian it_it 1040
Brazilian Portuguese Brazilian Portuguese pt_br 1046
Japanese Japanese ja_jp 1041
Korean Korean ko_kr 1042
Simplified Chinese Simplified Chinese zh_cn 2052
Traditional Chinese Traditional Chinese zh_tw 1028
Czech Czech cs_cz 1029
Russian Russian ru_ru 1049
Hungarian Hungarian hu_hu 1038
Polish Polish pl_pl 1045

For the [Services] stanza, you can enter parameters in property=value format. You might want to encrypt the values in this stanza. See Encrypting a parameter file .

Properties in the Services stanza

Property Values Description
USERTYPE local | domain | onlydomain The type of user account to use:

local

Creates a local user account.

domain

Creates a local user account. If this does not have the required security authorities, it uses the domain user account specified by DOMAINNAME, USERNAME, and PASSWORD.

onlydomain

Does not create a local user account, but immediately uses the domain user account specified by DOMAINNAME, USERNAME and PASSWORD. If any of these three properties are missing, a USERTYPE of local is assumed.

The properties DOMAINNAME, USERNAME, and PASSWORD are required if USERTYPE is set to onlydomain.

DOMAINNAME domain_name 1 The domain for the domain user account.

Required if USERTYPE is set to domain or onlydomain.

USERNAME User_name 1 The user name for the domain user account.

Required if USERTYPE is set to domain or onlydomain..

PASSWORD password 1 The password for the domain user account.

Required if USERTYPE is set to domain or onlydomain.

  1. Do not enclose this value in double quotation marks.

A typical example of a parameter file is: 

[MSI]
MQPLANGUAGE=1033
MQPLOG=%temp%\MQParms.log
MQPSMS=no
ADDLOCAL=Server
/m miffile
REMOVE=""
/l*v c:\install.log

[Services]
USERTYPE=domain
DOMAINNAME=mqm*df349edfcab12
USERNAME=mqm*a087ed4b9e9c
PASSWORD=mqm*d7eba3463bd0a3


Encrypt a parameter file

Use the setmqipw utility to encrypt the DOMAINNAME, USERNAME, and PASSWORD values in the [Services] stanza of a parameter file, if they are not already encrypted. (These values might be encrypted if you have run the utility before.) setmqipw will also encrypt the QMGRPASSWORD and CLIENTPASSWORD values in the [SSLMigration] stanza of a parameter file.

This encryption means that, if you need a special domain account to configure WebSphere MQ (see Configuring WebSphere MQ accounts ), or you need to keep key database passwords secret, details are kept secure. Otherwise, these values, including the domain account password, flow across the network as clear text. You do not have to use this utility, but it is useful if security in your network is an issue. To run the script:


Procedure

  1. From a command line, change to the folder that contains your parameter file.

  2. Enter the following command: 

    CD_drive:\setmqipw
    You can run the command from a different folder,, where parameter_file is the full path and file name of the parameter file: 

    CD_drive:\setmqipw parameter_file

If you view the resulting parameter file, the encrypted values start with the string mqm*. Do not use this prefix for any other values; passwords or names that begin with this prefix are not supported.

The utility creates a log file, setmqipw.log, in the current directory. This file contains messages related to the encryption process. When encryption is successful, messages are similar to: 

Encryption complete
Configuration file closed
Processing complete


What to do next

After you encrypt the parameter file, you can use it in the normal way with the MQParms command (see Using the MQParms command ).


Modify your installation


Modify the installation using WebSphere MQ Installation Launchpad

To modify an installation, some features of WebSphere MQ must already be installed. To remove or install WebSphere MQ features follow the instructions. This procedure is the only way to interactively remove or install WebSphere MQ features on Windows Vista and Windows Server 2008:


Procedure

  1. Insert the WebSphere MQ for Windows Server DVD into the DVD drive.

  2. If autorun is installed, the installation process starts.

    Otherwise, double-click the Setup icon in the root folder of the DVD to start the installation process.

    The WebSphere MQ Installation Launchpad window is displayed.

  3. Click the WebSphere MQ Installation option.

  4. Click Launch WebSphere MQ Installer. Wait until the WebSphere MQ Setup window is displayed with a welcome message.

  5. If you have multiple installations on your system, you must choose the installation you want to modify. Do this by selecting the Maintain or upgrade an existing instance option and choosing the appropriate instance. If you are upgrading a WebSphere MQ Version 7.0.1 installation (or earlier) to Version 7.1.0, and you already have a Version 7.1.0 or greater installation, you need to select Install a new instance. A subsequent panel then allows you to choose the installation you would like to upgrade.

  6. Click Next to continue. The Program Maintenance panel is displayed.

  7. Select Modify, then click Next.

    The Features panel is displayed.

  8. Click the + symbol next to a feature to show any dependent features (subfeatures).

  9. To change the installation of a feature:

    1. Click the symbol next to the feature name to display a menu.

    2. Select the required option from:

      • Install this feature

      • Install this feature and all its subfeatures (if any)

      • Do not install this feature (remove if already installed)

      The symbol next to the the feature name changes to show the current installation option.

  10. When your selections are complete, click Next. WebSphere MQ installation begins.


Silently modifying a WebSphere MQ server installation using msiexec

To silently modify an installation using msiexec, set the ADDLOCAL parameter to include the features you want to add, and set the REMOVE parameter to the features you want to remove.

For example if you use ADDLOCAL="JavaMsg" and REMOVE="" it modifies the installation to include the Java Messaging and Web Services feature. 

msiexec /i {PRODUCT CODE} /q ADDLOCAL="JavaMsg" REMOVE="" INSTALLATIONNAME="Installation1"

The instructions for msiexec begin here: Advanced installation using msiexec


Post installation tasks


Configure WebSphere MQ with the Prepare WebSphere MQ wizard

The Prepare WebSphere MQ wizard helps you to configure WebSphere MQ files and a user account for your network, and migrate any queue managers and data from a previous installation. You must run the wizard to configure the WebSphere MQ Service before you can start any queue managers.

The Prepare WebSphere MQ wizard window is displayed when WebSphere MQ installation completes. Follow the instructions given by the wizard to configure WebSphere MQ. At any time while the wizard is running you can click More Information in the wizard to view online help about the task you are doing. On Windows systems with UAC enabled, if you do not complete the Prepare WebSphere MQ Wizard directly after WebSphere MQ is installed, or if for any reason your machine is rebooted between completing WebSphere MQ installation and completing the Prepare WebSphere MQ Wizard, you must accept the Windows prompt when it appears to allow the wizard to run as elevated.


Procedure

  1. When WebSphere MQ installation completes, the Prepare WebSphere MQ Wizard window is displayed with a welcome message. To continue, click Next

  2. If you have run the Prepare WebSphere MQ wizard before, this step is skipped. If you have not run the Prepare WebSphere MQ wizard before, the Prepare WebSphere MQ Wizard window displays a progress bar with the following message: 

    Status: Setting up WebSphere MQ Configuration
    Wait until the progress bar completes.

  3. The Prepare WebSphere MQ Wizard window displays a progress bar with the following message: 

    Status: Setting up the WebSphere MQ Service.
    Wait until the progress bar completes.

  4. WebSphere MQ attempts to detect whether you must configure WebSphere MQ for use with Windows Active Directory Server or later domain users. Depending on the results of the detection, WebSphere MQ does one of the following things:

    • If WebSphere MQ detects that you need to configure WebSphere MQ for Windows Active Directory Server or later domain users, the Prepare WebSphere MQ Wizard window displays a message that starts: 

      WebSphere MQ does not have the authority to query information about
your user account

      Optionally, to see online help about configuring the domain account, select More Information. When you are finished, close the WebSphere MQ Help Center window to return to the current window.

      Click Next, and go to step 5 .

    • If you are not installing on a Windows Active Directory Server or later domain server and WebSphere MQ cannot detect whether you need to configure WebSphere MQ for Windows Active Directory Server or later domain users, the Prepare WebSphere MQ Wizard window displays the following message: 

      Are any of the domain controllers in your network running 
Windows 2000 or later domain server?

      If you select Yes, click Next, then go to step 5 .

      If you select No, click Next, then go to step 9 .

      If you select Don't know, you cannot continue. Select one of the other options, or click Cancel and contact your domain administrator.

    • If WebSphere MQ detects that you do not need to configure WebSphere MQ for Windows Active Directory Server or later domain users, go to step 9 .

    At any time, you can click More Information to view online help about configuring the domain account, or see Configuring WebSphere MQ accounts . When you are finished, close the WebSphere MQ Help Center window to return to the current window.

  5. The Prepare WebSphere MQ Wizard window displays the following message: 

    Do you need to configure WebSphere MQ for users defined on Windows 2000 
or later domain controllers?

    If you select Yes, click Next, then go to step 6 .

    If you select No, click Next, then go to step 9 .

    If you select Don't know, you cannot continue. Select one of the other options, or click Cancel and contact your domain administrator. At any time, you can click More Information to view online help about configuring the domain account, or see Configuring WebSphere MQ accounts . When you are finished, close the WebSphere MQ Help Center window to return to the current window.

  6. Give the domain user that you obtained from your domain administrator the right to run as a service.

    1. Click Start > Run..., type the command secpol.msc and click OK.

    2. Open Security Settings > Local Policies > User Rights Assignments. In the list of policies, right-click Log on as a service > Properties.

    3. Click Add User or Group... and type the name of the user you obtained from your domain administrator, and click Check Names

    4. If prompted by a Windows Security window, type the user name and password of an account user or administrator with sufficient authority, and click OK > Apply > OK. Close the Local Security Policy window.

  7. In the next window, enter the Domain and user ID of the domain user account that you obtained from your domain administrator. Either enter the Password for this account, or select the option This account does not have a password. Click Next.

  8. The Prepare WebSphere MQ Wizard window displays a progress bar with the following message: 

    Status: Configuring WebSphere MQ with the special domain user account
    Wait until the progress bar completes.

    If there are any problems with the domain user account, a further window is displayed. Follow the advice on this window before you continue with this procedure.

  9. The Prepare WebSphere MQ Wizard window displays a progress bar with the following message: 

    Status: Starting WebSphere MQ services
    Wait until the progress bar completes.

  10. Next, select the options that you require. The Prepare WebSphere MQ Wizard window displays the following message: 

    You have completed the Prepare WebSphere MQ Wizard

    Select the options that you require, then click Finish . Select one or more from:

    • Remove the shortcut to this wizard from the desktop

      This option is available only if you have previously attempted installation, but you canceled the procedure from the Prepare WebSphere MQ wizard and you created a desktop shortcut to this wizard. Select this option to remove the shortcut. You do not need it now that you have completed the Prepare WebSphere MQ wizard.

    • Launch WebSphere MQ Explorer

      The WebSphere MQ Explorer allows you to view and administer your WebSphere MQ network.

    • Launch Notepad to view the release notes

      The release notes contain information about installing WebSphere MQ and also late-breaking news that is available after the published documentation is produced.

  11. Follow the procedure described in Checking for problems after installing .


Configure a WebSphere MQ Server

After installing WebSphere MQ, it is necessary to configure it. The configuration described in this topic is for an environment that uses TCP/IP. The configuration procedure is the same for environments that use other communications protocols (for example, SNA, SPX, or NetBIOS). However, not all of the functions and facilities of WebSphere MQ for Windows are available in these environments. The items that are not available are:

If you are setting up WebSphere MQ for use with the Microsoft Cluster Service (MSCS), see Supporting the Microsoft Cluster Service (MSCS) for more information.


Configure WebSphere MQ accounts

You can configure theWebSphere MQ service and queue managers to check that any users attempting to access queue managers or queue manager resources such as queues, have the permission to access them.

Most networked Windows systems are members of a Windows domain where user accounts, other security principals, and security groups are maintained and managed by a directory service, Active Directory, running on a number of domain controllers. WebSphere MQ checks that only authorized users can access queue managers or queues.

In such networks, WebSphere MQ queue manager processes access the Active Directory information to find the security group membership of any users attempting to use WebSphere MQ resources. The accounts under which WebSphere MQ services run must be authorized to look up such information from the directory. In most Windows domains, local accounts defined at individual Windows servers cannot access directory information, so the WebSphere MQ services must run under a domain account that has the appropriate permission.

If the Windows server is not a member of a Windows domain or the domain has a reduced security or functional level, then the WebSphere MQ services can run under a local account that was created during installation.

Assuming that a domain account is needed, provide the information described in the Information for domain administrator to your domain administrator, and ask for one of the special accounts it describes. When you install the product, towards the end of the installation procedure, in the Prepare WebSphere MQ wizard, you are asked to enter details of this account (domain, user name, and password).

If a domain account is needed and you install WebSphere MQ without a special account (or without entering its details), many or all parts of WebSphere MQ do not work, depending upon the particular user accounts involved. Also, WebSphere MQ connections to queue managers that run under domain accounts on other systems might fail. The account can be changed by running the Prepare WebSphere MQ wizard and specifying the details of the account to be used.

For information about the user rights required to take advantage of the Active Directory support, see Using Active directory (Windows only) .

For information about the user rights required to take advantage of the Kerberos authentication support, see Security .


Information for domain administrators

Use this topic to understand how WebSphere MQ services check the authorization of user accounts attempting to access WebSphere MQ.

The user account must either have an individual WebSphere MQ authorisation set or belong to a local group that has been authorized. A domain account can also be authorized through membership of a domain group included under an authorized local group through a single level of nesting.

The account under which the WebSphere MQ services are run must have the ability to query group memberships of domain accounts and have the authority to administer WebSphere MQ. Without the ability to query group memberships the access checks made by the services fail.

On most Windows domains, with domain controllers running Windows Active Directory, local accounts do not have the required authorization and a special domain user account with the required permissions must be used. The WebSphere MQ installer must be given the userid and password details so that they can be used to configure the WebSphere MQ service after the product is installed.

Typically, this special account has the WebSphere MQ administrator rights through membership of the domain group DOMAIN\Domain mqm. The domain group is automatically nested by the installation program under the local mqm group of the system on which WebSphere MQ is being installed.

See Setup domain accounts for WebSphere MQ for instructions on creating a suitable domain account. If an installer configures WebSphere MQ without a special account, many or all parts of WebSphere MQ do not work, depending upon the particular user accounts involved, as follows:


Setup domain accounts for WebSphere MQ

The following information is aimed at Domain Administrators. Repeat Steps 1 and 2 for each domain that has user names that will install WebSphere MQ, to create an account for WebSphere MQ on each domain:


Procedure

  1. Create a domain group with a special name that is known to WebSphere MQ and give members of this group the authority to query the group membership of any account:

    1. Log on to the domain controller as an account with domain administrator authority.

    2. From the Start menu, open Active Directory Users and Computers.

    3. Find the domain name in the navigation pane, right-click it and select New Group.

    4. Type a group name into the Group name field.

      The preferred group name is Domain mqm. Type it exactly as shown.

      1. Calling the group Domain mqm modifies the behavior of the Prepare WebSphere MQ wizard on a domain workstation or server. It causes the Prepare WebSphere MQ wizard automatically to add the group Domain mqm to the local mqm group on each new installation of WebSphere MQ in the domain.

      2. You can install workstations or servers in a domain with no Domain mqm global group. If you do so, you must define a group with the same properties as Domain mqm group. You must make that group, or the users that are members of it, members of the local mqm group where ever WebSphere MQ is installed in a domain. You can place domain users into multiple groups. Create multiple domain groups, each group corresponding to a set of installations that you want to manage separately. Split domain users, according to the installations they manage, into different domain groups. Add each domain group or groups to the local mqm group of different WebSphere MQ installations. Only domain users in the domain groups that are members of a specific local mqm group can create, administer, and run queue managers for that installation.

      3. The domain user that you nominate when installing WebSphere MQ on a workstation or server in a domain must be a member of the Domain mqm group, or of an alternative group you defined with same properties as the Domain mqm group.

    5. Leave Global clicked as the Group scope, or change it to Universal. Leave Security clicked as the Group type. Click OK.

    6. Follow these steps to assign permissions to the group based on Windows version of the domain controller:

      On the Windows Server 2008 and later versions:

      1. In the Server Manager action bar, click View > Advanced features

      2. In the Server Manager navigation tree, click Users

      3. In the Users window, right-click Domain mqm > Properties

      4. Click Security > Advanced > Add.... Type Domain mqm and click Check names > OK.

        The Name field is prefilled with the string, Domain mqm (domain name\Domain mqm).

      5. Click Properties. In the Apply to list, select Descendant User Objects.

      6. From the Permissions list, select the Read group membership and Read groupMembershipSAM Allow check boxes; click OK > Apply > OK > OK.

      On the Windows 2003 Server:

      1. In the Server Manager action bar, click View > Advanced features > Active Directory Users and Computers.

      2. In the Server Manager navigation tree, search for the domain name. Select the domain name, right-click and select Properties.

      3. Click Security > Advanced > Add.... Type Domain mqm and click Check names > OK.

      4. Click Properties. In the Apply to list, select User Objects

      5. From the Permissions list, select the Read group membership and Read groupMembershipSAM Allow check boxes; click OK > Apply > OK > OK.

      On the Windows 2000 Server:

      1. In the Server Manager navigation tree, search for the domain name. Select the domain name, right-click and select Delegate Control Next.

      2. Click Selected Groups and Users > Add.... Select Domain mqm and click Add > OK.

      3. Select Domain mqm and click Next.

      4. Click Create a custom task to delegate and click Next.

      5. Select Only the following objects in the folder, and then check User Objects in the alphabetical list. Click Next.

      6. Check Property-specific, then select from the list (it is in alphabetical order on the second word) the following options:

        • Read group membership

        • Read groupMembershipSAM

      7. Click OK to close each window.

  2. Create one or more accounts, and add them to the group:

    1. In Active Directory Users and Computers, create a user account with a name of your choosing and add it to group Domain mqm (or a group that is a member of the local mqm group).

    2. Repeat for all the accounts you want to create.

  3. Repeat Steps 1 and 2 for each domain that has user names that will install WebSphere MQ, to create an account for WebSphere MQ on each domain.

  4. Use the accounts to configure each installation of WebSphere MQ:

    1. Either use the same domain user account (as created in Step 1 ) for each installation of WebSphere MQ, or create a separate account for each one, adding each to the Domain mqm group (or a group that is a member of the local mqm group).

    2. When you have created the account or accounts, give one to each person configuring an installation of WebSphere MQ. They must enter the account details (domain name, user name, and password) into the Prepare WebSphere MQ wizard. Give them the account that exists on the same domain as their installing userid.

    3. When you install WebSphere MQ on any system on the domain, the WebSphere MQ install program detects the existence of the Domain mqm group on the LAN, and automatically adds it to the local mqm group. (The local mqm group is created during installation; all user accounts in it have authority to manage WebSphere MQ). Thus all members of the Domain mqm group will have authority to manage WebSphere MQ on this system.

    4. However, you do still need to provide a domain user account (as created in Step 1 ) for each installation, and configure WebSphere MQ to use it when making its queries. The account details must be entered into the Prepare WebSphere MQ wizard that runs automatically at the end of installation (the wizard can also be run at any time from the start menu).

  5. Set the password expiry periods

    • If you use just one account for all users of WebSphere MQ, consider making the password of the account never expire, otherwise all instances of WebSphere MQ will stop working at the same time when the password expires.

    • If you give each user of WebSphere MQ their own user account you will have more user accounts to create and manage, but only one instance of WebSphere MQ will stop working at a time when the password expires.

    If you set the password to expire, warn the users that they will see a message from WebSphere MQ each time it expires - the message warns that the password has expired, and describes how to reset it.

  6. Running WebSphere MQ as a service. If you need to run WebSphere MQ as a service, and then give the domain user (that you obtained from your domain administrator) the right to run as a service, carry out the following procedure:

    1. Click Start > Run.... Type the command secpol.msc and click OK.

    2. Open Security Settings > Local Policies > User Rights Assignments. In the list of policies, right-click Log on as a service > Properties.

    3. Click Add User or Group... Type the name of the user you obtained from your domain administrator, and click Check Names

    4. If prompted by a Windows Security window, type the user name and password of an account user or administrator with sufficient authority, and click OK > Apply > OK. Close the Local Security Policy window.

    On Windows Vista and Windows Server 2008 the User Account Control (UAC) is enabled by default.

    The UAC feature restricts the actions users can perform on certain operating system facilities, even if they are members of the Administrators group. You must take appropriate steps to overcome this restriction.


Use the Default Configuration wizard

You can use the Default Configuration wizard to add the first configured queue manager to this system. This enables you to connect easily with other queue managers in the same WebSphere MQ cluster. You can use the Default Configuration wizard to create, view, or alter your default configuration. You can also use this wizard to alter or display details of an existing queue manager that was created by the default configuration.

For a new installation of WebSphere MQ, creating a default configuration enables you to explore features of WebSphere MQ using the Postcard application, and the WebSphere MQ Explorer.

The Postcard application provides a fast and simple way to verify that your WebSphere MQ installation completed successfully. It uses the default queue manager that is created during the default configuration. To use the Postcard application for verification, and you do not have any existing queue managers, run the Default Configuration wizard first.

If you have migrated existing queue managers, or created any queue managers since installing WebSphere MQ, you might not want to run the Default Configuration wizard. This is because you cannot create the default configuration if other queue managers already exist. If you have previously created any other queue managers on this system and you still want to set up a default configuration, you must delete them before running the Default Configuration wizard.

Start the Default Configuration wizard by selecting Create the Default Configuration on the Welcome to WebSphere MQ Explorer Content view page.


Use WebSphere MQ Remotely

If you are connecting to a Windows machine using either Terminal Services or a Remote Desktop Connection and you have problems creating, starting or deleting a queue manager this might be because of the user right Create global objects.

The Create global objects user right limits the users authorized to create objects in the global namespace. In order for an application to create a global object, it must either be running in the global namespace, or the user under which the application is running must have the Create global objects user right applied to it.

When you connect remotely to a Windows machine using either Terminal Services or Remote Desktop Connection, applications run in their own local namespace. If you attempt to create or delete a queue manager using WebSphere MQ Explorer or the crtmqm or dltmqm command, or to start a queue manager using the strmqm command, it results in an authorization failure. This creates a WebSphere MQ FDC with Probe ID XY132002.

Starting a queue manager using the WebSphere MQ Explorer, or using the amqmdain qmgr start command works correctly because these commands do not directly start the queue manager. Instead the commands send the request to start the queue manager to a separate process running in the global namespace.

If you need to perform any of these operations on a queue manager when connected remotely to a Windows machine, you must have the Create global objects user right. For information on how to assign a user this right, see your operating system documentation.

Administrators have the Create global objects user right by default, so if you are an administrator you can create and start queue managers when connected remotely without altering your user rights.


Use the Welcome to WebSphere MQ Explorer Content view page

The Welcome to WebSphere MQ Explorer Content view page points you to any relevant applications, documentation, tutorials, and education. This page is displayed the first time you launch WebSphere MQ Explorer.

You can use the items in the Welcome to WebSphere MQ Explorer Content view page to explore the facilities in WebSphere MQ. This page is launched the first time the WebSphere MQ Explorer is launched. The Welcome page can be viewed at any time from the Explorer by clicking IBM WebSphere MQ in the Navigator view. There are links to the following subjects from this page:


Create the Default Configuration

Allows you to add a configured queue manager to this system for connecting easily with other queue managers in the same WebSphere MQ cluster. You can also use it to alter or display details of an existing queue manager created by the default configuration. This feature is available only using TCP/IP. If you migrated existing queue managers, or if you have created any queue managers after you installed WebSphere MQ, you might not want to use this facility. This is because you can only set up a default configuration if there are no queue managers already, and you might not want to delete your existing queue managers.


Launch Postcard

Allows you to try out WebSphere MQ messaging quickly and easily. You can send a message either to your own machine or to another named user's machine. It is described in detail in Verify the installation using the Postcard application .


Use the Help Center

The Help Center gives you access to all task-oriented help, information on the IBM website, and a link to the WebSphere MQ Information Center if you have installed it from the WebSphere MQ Documentation CD.

The WebSphere MQ Help Center can be accessed from the WebSphere MQ Explorer by selecting Help > Help Contents.


Checking for problems after installing

These are optional tasks that you can use to check the installation if you believe there was a problem, or to verify installation messages after an unattended (silent) installation for example.

Use these steps as a guide to check the following files for messages:


Procedure

  1. MSInnnnn.LOG. This file is in your user Temp folder. It is an application log that contains English messages written during installation. The log includes a message indicating whether the installation was successful and complete.

    This file is created if you have set up default logging.

  2. If you used the launchpad to install WebSphere MQ, check MQv7_Install_YYYY-MM-DDTHH-MM-SS.log in your user Temp folder, where:

    YYYY

    This is the year that you installed WebSphere MQ Version 7.0

    MM

    This is the month that you installed WebSphere MQ, for example this would be 09 if you installed in September

    DD

    This is the day that you installed WebSphere MQ

    HH-MM-SS

    This is the time at which WebSphere MQ was installed

    You can get to your user Temp directory at the command prompt: 

    cd %TEMP%

  3. amqmsccw.txt. This file is in the WebSphere MQ data files folder (default c:\Program Files\IBM\WebSphere MQ). It is an application log that contains English messages written by the Check WebSphere MQ Certificate Stores wizard.

  4. amqmjpse.txt. This file is in the WebSphere MQ data files folder (default c:\Program Files\IBM\WebSphere MQ). It is an application log that contains English messages written during installation by the Prepare WebSphere MQ wizard.


What to do next

  1. Verify your installation, as described in Verifying a server installation


Converting a trial license on UNIX, Linux, and Windows

Convert a trial license to a full license without reinstalling WebSphere MQ.

When the trial license expires, the count-down displayed by the strmqm command informs you the license has expired, and the command does not run.

  1. WebSphere MQ is installed with a trial license.

  2. You have access to the installation media of a fully licensed copy of WebSphere MQ.

Run the setmqprd command to convert a trial license to a full license.

If you do not want to apply a full license to your trial copy of WebSphere MQ, you can uninstall it at any time.


Procedure

  1. Obtain the full license from the fully licensed installation media.

    The full license file is amqpcert.lic. On UNIX and Linux, it is in the /MediaRoot/licenses directory on the installation media. On Windows it is in the \MediaRoot\licenses directory on the installation media. It is installed into the bin directory on the WebSphere MQ installation path.

  2. Run the setmqprd command from the installation that you are upgrading: 

    $MQ_INSTALLATION_PATH/bin/setmqprd /MediaRoot/licenses/amqpcert.lic


Display messages in your national language on UNIX and Linux systems

To display messages from a different national language message catalog, you must install the appropriate catalog and set the LANG environment variable.

Non-AIX platforms

Messages in U.S. English are automatically installed with WebSphere MQ.

AIX

Messages in the language specified by the locale selected on your machine at install time are installed by default.

To find out which language is currently in use, run the locale command.

If this returns a language which is not one of the national languages provided by WebSphere MQ, you must select a national language, otherwise you will not get a message catalog installed on your system.

Message catalogs for all languages are installed in MQ_INSTALLATION_PATH/msg/language identifier, where language identifier is one of the identifiers in Table 1 . If you require messages in a different language, perform the following steps:


Procedure

  1. Install the appropriate message catalog (see Choosing what to install ).

  2. To select messages in a different language, ensure the LANG environment variable is set to the identifier for the language you want to install:

    Language identifiers

    Identifier Language
    cs_CZ Czech
    de_DE German
    es_ES Spanish
    fr_FR French
    hu_HU Hungarian
    it_IT Italian
    ja_JP Japanese
    ko_KR Korean
    pl_PL Polish
    pt_BR Brazilian Portuguese
    ru_RU Russian
    zh_CN Simplified Chinese
    zh_TW Traditional Chinese

    AIX has some additional message catalogs:

    AIX specific language identifiers

    Identifier Language
    Ja_JP Japanese
    Zh_CN Simplified Chinese
    Zh_TW Traditional Chinese


Install a WebSphere MQ client

After preparing your system for installation, you can install a WebSphere MQ client by following the appropriate instructions for your platform. After installation, you might want to verify your installation to check that installation has been successful.

Before you start the installation procedure, make sure that you have prepared your system as described in Preparing the system

To begin the installing procedure, select the appropriate platform:


Install WebSphere MQ clients and servers on the same system

To install a WebSphere MQ client on a system that is already running a WebSphere MQ server, use the appropriate Server DVD. Use a Client DVD to install a WebSphere MQ client only on a system that is not running a WebSphere MQ server.

If you install a WebSphere MQ client from a Client DVD and later decide to install the WebSphere MQ server on the same system, you must first remove all the client components from the system. Then use the appropriate Server DVD to install both the server and client components. You cannot install a WebSphere MQ server on a system that already has client components installed from a Client DVD.

Remember that even if your client and server are installed on the same system, you must still define the MQI channel between them. See Defining MQI channels for details.


Install a WebSphere MQ client on AIX systems

You can interactively install the WebSphere MQ client for AIX using smit. Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system .

WebSphere MQ is supplied as a set of filesets that are installed using the standard AIX installation tools. The procedure uses the System Management Interface Tool (smit), but you can choose to use installp, geninstall or the Web-based System Manager. You can select which components you want to install. The components and filesets are listed in Choosing what to install . You must install at least the Runtime and Client components.


Procedure

  1. This procedure installs WebSphere MQ into the default location. To install to a non-default location, you must use installp, see Non-interactive installation of WebSphere MQ client for AIX .

  2. Log in as root, or switch to the superuser using the su command.

  3. Make your current directory the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  4. Select the required smit window using the following sequence: 

    Software Installation and Maintenance     
    Install and Update Software         
    Install and Update from ALL Available Software

  5. Click List to display the input device or directory for the software, select the location that contains the installation images.

  6. Use the SOFTWARE to install field to obtain a list of available filesets, and select the filesets you want to install. Ensure that you include the appropriate message catalog if you require messages in a language different from the language specified by the locale specified on your system. Enter ALL to install all applicable filesets.

  7. Change Preview new LICENSE agreements? to yes and press Enter to view the license agreements.

  8. If you have a previous version of the product on your system, change the Automatically install requisite software to No.

  9. Change ACCEPT new license agreements? to yes and press Enter to accept the license agreements.

  10. Change Preview new LICENSE agreements? to no and press Enter to install WebSphere MQ.


What to do next


Non-interactive installation of WebSphere MQ client for AIX

Silently install WebSphere MQ client from the command line using the AIX installp command. Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system .

You can use this method to install to a non-default location, and can select which components you want to install. The components and filesets are listed in Choosing what to install . You must install at least the Runtime and Client components.


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Make your current directory the location of the installation file. The location might be the mount point of the CD, a network location, or a local file system directory.

  3. Install the product in one of the following ways

    • Install the whole product in the default location: 

      installp -acgXYd. all

    • Install selected filesets in the default location: 

      installp -acgXYd. list of file sets

    • Install the whole product in a non-default location using the -R flag: 

      installp -R MQ_INSTALLATION_PATH -acgXYd. all

    • Install selected filesets in a non-default location using the -R flag: 

      installp -R MQ_INSTALLATION_PATH -acgXYd. list of file sets

    The directory specified with the -R flag is an AIX User Specified Install Location (USIL). WebSphere MQ is installed underneath the directory specified. For example, if -R /USIL1 is specified, the WebSphere MQ product files are located in /USIL1/usr/mqm.


What to do next


Install WebSphere MQ client on HP Integrity NonStop Server systems

Install a WebSphere MQ client on a HP Integrity NonStop Server system.

Before you start the installation procedure, make sure that you complete the necessary steps that are outlined in Setting up the user and group on HP Integrity NonStop Server . After preparing your system for installation, install the WebSphere MQ client for HP Integrity NonStop Server by following the instructions. After installation, you might want to verify your installation to check that it installed successfully. There are three steps to the installation:

  1. Downloading the installation package.

  2. Running the installer.

  3. Setting the environment.


Procedure

  1. Log in to the OSS user ID that owns the installation. The OSS user ID must have MQM as its primary group.

  2. Download the installation package file. Ensure that you use "binary mode" when you download the installation package file to OSS. Any corruption in the file causes the self-extracting archive to fail to run. After you have downloaded the package file, ensure that it has read and execute permissions for the user ID that is installing the package.

  3. Optional: Make your current directory the location of the installation file.

  4. Type the following command to start the interactive installation procedure: 

    ./<name of package file> -i <OSS install_root> -g <Guardian install_root>

    where

    <name of package file> is the name of the installation package.

    <OSS install_root> is the OSS root directory of the new installation.

    <Guardian install_root> is the Guardian subvolume for the new installation.

    Both -i and -g options are mandatory.

    • -i specifies the new or empty OSS directory that contains the opt/mqm and var/mqm directories of the installation.

    • -g specifies the subvolume into which the Guardian components of the WebSphere MQ client on a HP Integrity NonStop Server are installed. The Guardian subvolume can be specified in either OSS-form or Guardian-form and can be abbreviated. The Guardian subvolume specification is not case sensitive. The following are examples of valid Guardian subvolume specifications:

      • /G/vol/subvol

      • vol/subvol

      • \$VOL.SUBVOL

      • vol.subvol

  5. Optional: For OSS, set your environment by installing the binaries into your path. To do this, type the following command: 

    export PATH=$PATH:<OSS_install_root>/opt/mqm/bin

    where <OSS_install_root> is the OSS root directory of the new installation.


Example

To install the WebSphere MQ client for HP Integrity NonStop Server from package mat1.run, type the following command: 

./mat1.run -i ~install/mq75client -g /G/data04/mqm

The command installs the OSS components into new opt/mqm and var/mqm directories in ~install/mq75client. It installs the Guardian components into /G/data04/mqm.


What to do next

For instructions on how to verify your installation, see Verifying a client installation .


Install a WebSphere MQ client on HP-UX systems

Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system . This topic describes the installation of a client, using the swinstall program to select which components you want to install. The components and are listed in Choosing what to install ; you must install at least the Runtime and Client components.


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Make your current directory the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Accept the license by running the mqlicense script: 

    ./mqlicense.sh

    The license is displayed. If you accept the license, you can continue the installation.

  4. Type the following command to start the interactive installation procedure: 

    swinstall -s installation_file
    installation_file is the absolute path to the installation file. The path must begin with a / and end with the name of the installation file. The installation file has the extension .v11.

    If the files on your DVD are in uppercase with a ";1" suffix, use this name for the depot.

  5. In the resulting menu screen, select MQSERIES.

    1. If you do not want to install all WebSphere MQ components, open MQSERIES

      1. Mark the components you want to install. The installer resolves dependencies automatically.

      2. Review the information displayed by the installer.

  6. Optional: To install WebSphere MQ to a non-default location, select Actions > Change Product Location.

    For each installation, all of the WebSphere MQ components that you require must be installed in the same location.

    The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

  7. Select Actions > Install. The log file tells you if there are any problems that need fixing.

  8. Fix any problems, and click OK to install. You are informed when the installation has finished.

  9. If this installation is not the first installation on the system, you must enter the following command: 

    swconfig -x allow_multiple_versions=true MQSERIES,l=MQ_INSTALLATION_PATH
    where MQ_INSTALLATION_PATH is the path where you have just installed WebSphere MQ. If you do not enter this command, the swlist command reports the installation as installed instead of configured. You must not use WebSphere MQ unless the installation is configured.


What to do next


Non-interactive installation of WebSphere MQ client on HP-UX

You can perform a non-interactive installation of the WebSphere MQ client using the swinstall command. A non-interactive installation is also known as a silent, or unattended installation. Before you start the installation procedure, make sure that you have completed the necessary steps outlined in Preparing the system . This topic describes the non-interactive installation of a client, using the swinstall program to select which components you want to install. The components and are listed in Choosing what to install ; you must install at least the Runtime and client components.


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Make your current directory the location of the installation file. The location might be the mount point of the CD, a network location, or a local file system directory.

  3. Accept the WebSphere MQ license agreement without an interactive prompt: 

    ./mqlicense.sh -accept

  4. Install WebSphere MQ using the swinstall command:

    1. If this installation is not the first installation on the system, you must add -x allow_multiple_versions=true to the swinstall command.

    2. Add the names of the components to install as parameters of the swinstall command. The installer automatically resolves any dependencies.

    3. Optional: Identify the installation location by adding ,l=MQ_INSTALLATION_PATH as a parameter of the swinstall command. For each installation, all of the WebSphere MQ components that you require must be installed in the same location. The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

    For example, to install all WebSphere MQ components, in a non-default location, as the first installation, enter the following command: 

    swinstall -s /installation_file.v11 MQSERIES,l=/opt/customLocation
    To perform a partial installation, providing a list of components, in the default location, as the second installation, enter the following command: 

    swinstall -s /installation_file.v11
MQSERIES.MQM-RUNTIME MQSERIES.MQM-BASE MQSERIES.MQM-CL-HPUX -x allow_multiple_versions=true
    /installation_file.v11 is the absolute path to the installation file. The path must begin with a / and end with the name of the installation file. The installation file has the extension .v11.

  5. If this installation is not the first installation on the system, you must enter the following command: 

    swconfig -x allow_multiple_versions=true MQSERIES,l=MQ_INSTALLATION_PATH
    where MQ_INSTALLATION_PATH is the path where you have just installed WebSphere MQ. If you do not enter this command, the swlist command reports the installation as installed instead of configured. You must not use WebSphere MQ unless the installation is configured.


What to do next

For instructions on how to verify your installation, see Verifying a client installation .


Install WebSphere MQ client on Linux

Install a WebSphere MQ client on a 32 bit or 64 bit Linux system.

This task describes the installation of the client, using the RPM Package Manager installer to select which components you want to install. You must install at least the Runtime and Client components. The components are listed in Choosing what to install .


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Make your current directory the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Run the mqlicense.sh script. To view a text-only version of license, which can be read by a screen-reader, type: 

    ./mqlicense.sh -text_only
    The license is displayed.

    If want to accept the license without it being displayed, you can run the mqlicense.sh script with the -accept option. 

    ./mqlicense.sh -accept

    You must accept the license agreement before you can proceed with the installation.

  4. If this installation is not the first installation on the system, you must run crtmqpkg to create a unique set of packages to install on the system:

    1. Enter the following command: 

      crtmqpkg suffix
      where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a sub-directory of /var/tmp/mq_rpms, in which the unique set of packages is created. The packages have the suffix value contained within the filename.

  5. Install WebSphere MQ. The minimum components you must install are the MQSeriesRuntime and the MQSeriesClient.

    • To install to the default location, /opt/mqm, use the rpm -ivh command to install each component that you require.

      For example, to install all components to the default location use the following command: 

      rpm -ivh MQSeries*.rpm

    • To install to a non-default location use the rpm --prefix option. For each installation, all of the WebSphere MQ components that you require must be installed in the same location.

      The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

      For example, to install the runtime and server components to /opt/customLocation on a 32-bit Linux system: 

      rpm --prefix /opt/customLocation -ivh MQSeriesRuntime-7.1.0-0.i386.rpm
MQSeriesClient-7.1.0-0.i386.rpm


What to do next


Install a WebSphere MQ client on Solaris

This task describes the installation of the WebSphere MQ for Solaris client, using the pkgadd program. You can choose which components you want to install. The components (or file sets) are listed in Choosing what to install ; you must install at least the Client component.


Procedure

  1. Log in as root, or switch to the superuser using the su command.

  2. Make your current directory the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Run the mqlicense.sh script to accept the license: 

    ./mqlicense.sh
    If you want to view a text-only version of the license, which can be read by a screen-reader, type: 

    ./mqlicense.sh -text_only
    The license is displayed. Follow the instructions to accept the license. If you accept the license, the installation continues. If you do not accept the license, you cannot continue the installation process.

  4. If this installation is not the first installation on the system, you must run crtmqpkg to create a unique set of packages to install on the system:

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a sub-directory of /var/spool, in which the unique set of packages is created. The packages have the suffix value contained within the filename.

  5. Start the installation process

    • If the installation is the first installation on the system, enter the following command to start the installation process: 

      pkgadd -d ./mqclient.img

    • If the installation is not the first installation on the system, enter the following command to start the installation process: 

      pkgadd mqm-suffix
      where suffix is the suffix chosen in the previous step.

  6. You are presented with a list of the packages that are available. Enter the number of the mqm package.

  7. You are prompted to choose a location for installation.
    • To install to the default location, enter y.

    • To install to a non-default directory, enter n. Then enter the required installation path, and confirm your choice.

  8. You receive a number of messages, after which a list of components is displayed. Enter the numbers of the components that you require separated by spaces or commas.

  9. If the path chosen in step 7 does not exist, you are asked if you want to create it. You must enter y to proceed.

  10. Answer any questions appropriately for your system.

  11. A message tells you when installation is complete. Enter q to exit the pkgadd program.


What to do next


Install a WebSphere MQ client on Windows systems

This topic describes how to install WebSphere MQ client on Windows systems. This procedure can be used for installing a first or a subsequent installation. To install a WebSphere MQ client, you must be logged on to Windows as an administrator.

Follow these instructions to perform an interactive compact, typical, or custom installation of WebSphere MQ. To view all the installation types and the features that are installed with each option consult Table 1 . To install the extended transactional client Use the server installation image.


Procedure

  1. Access the WebSphere MQ installation image. The location might be the mount point of the DVD, a network location, or a local file system directory.

  2. Locate setup.exe in the Windows directory of the WebSphere MQ installation image.
    • From a DVD, this location might be: 

      E:\Windows\setup.exe

    • From a network location, this location might be: 

      m:\instmqs\Windows\setup.exe

    • From a local file system directory, this location might be: 

      C:\instmqs\Windows\setup.exe

  3. Double-click the Setup icon to start the installation process. It is possible to run either by:
    • Running setup.exe from the command prompt. Or

    • Double-clicking setup.exe from Windows Explorer.

    If you are installing on a Windows system with UAC enabled, accept the Windows prompt to allow the launchpad to run as elevated. During installation, you might also see Open File - Security Warning dialog boxes that list International Business Machines Limited as the publisher. Click Run to allow the installation to continue.

    The WebSphere MQ Installation window is displayed.

  4. Continue to follow the instructions as shown on screen.

A new sample WebSphere MQ MQI client configuration file is created in the WebSphere MQ installation directory (for example C:\Program Files\IBM\WebSphere MQ\, by the WebSphere MQ MQI client package, during installation, but only if this file does not exist. This file contains the ClientExitPath stanza. An example mqclient.ini file is shown in Configuring a client using a configuration file .

If you are using a common configuration file for multiple clients, either in the WebSphere MQ installation directory or in another location using the MQCLNTCF environment variable, you must grant read access to all user identifiers under which the WebSphere MQ client applications run. If the file cannot be read, the failure is traced and the search logic continues as if the file had not existed.


What to do next


Advanced installation using msiexec

WebSphere MQ on Windows uses the MSI technology to install software. MSI provides both an interactive installation and a non interactive installation. An interactive installation displays panels and ask questions.

The msiexec command uses parameters to give MSI some or all of the information that can also be specified through panels during an interactive installation. This means that a user can create a reusable automated or semi-automated installation configuration. Parameters can be given through the command line, a transform file, a response file, or a combination of the three.


Procedure

To install using msiexec, at the command line, enter the msiexec command in the following format: 

msiexec parameters [USEINI="response-file"] [TRANSFORMS="transform_file"]

Where:

parameters

are either command-line parameters preceded by a / character, or property=value pairs (if using both forms of parameter always put the command-line parameters first). For further information, see Specifying command line parameters with msiexec .

For an unattended installation, you must include the /q or /qn parameter in the command line. Without this parameter, the installation is interactive. You must include the /i parameter and the file location of the WebSphere MQ installer package.

response-file

is the full path and file name of the file that contains the [Response] stanza and the required property=value pairs, for example C:\MyResponseFile.ini. An example response file, Response.ini, is supplied with WebSphere MQ. This file contains default installation parameters. For further information, see Using a response file with msiexec .

transform_file

is the full path and file name of a transform file. For further information, see Using transforms with msiexec and Multiple installation using MSI Instance ID .
For a silent installation to succeed, the AGREETOLICENSE=?YES? property must be defined either on the command line or in the response file.

After the command has been entered, the command prompt immediately reappears. WebSphere MQ is installing as a background process. If you have entered parameters to produce a log, check this file to see how the installation is progressing. If the installation completes successfully, you see the message Installation operation completed successfully in the log file.


Specifying command line parameters with msiexec

About this task

The msiexec command can accept two types of parameters on the command line, as follows:

Example

A typical example of an msiexec command is: 

msiexec /i  path\MSI\IBM WebSphere MQ.msi /l*v c:\install.log 
/q TRANSFORMS= 1033.mst AGREETOLICENSE= yes ADDLOCAL= Client

A typical example of an msiexec command when you are installing a second copy of WebSphere MQ version 7.1 is: 

msiexec /i  path\MSI\IBM WebSphere MQ.msi /l*v c:\install.log 
/q TRANSFORMS= :InstanceId2.mst;1033.mst AGREETOLICENSE= yes 
ADDLOCAL= Client MSINEWINSTANCE=1

The following table shows the parameters which can only be provided on the command line and not in a response file.

msiexec property=value parameters

Property Values Meaning
USEINI path\file_name Use the specified response file. See Using a response file with msiexec
SAVEINI path\file_name Generate a response file during installation. The file contains those parameters selected for this installation that a user might make during an interactive installation.
ONLYINI 1|yes| "" 1, yes or any value other than null. End the installation before updating the target system, but after generating a response file, if this is specified.

"". Continue the installation and update the target system (the default).

TRANSFORMS :InstanceIdx.mst|path\file_name|:InstanceIdx.mst;path\file_name The :InstanceIdx.mst value is only required for a subsequent installation of WebSphere MQ version 7.1 or greater. The path\file_name specifies what transform (.mst) files must be applied to the product. For example, "1033.mst" specifies the supplied U.S. English transform file.
MSINEWINSTANCE 1 This property is only required for subsequent installations of WebSphere MQ version 7.1 or greater.
REMOVEFEATURES yes Required with value "yes" for a silent installation, otherwise ignored. Allows obsolete features, no longer part of WebSphere MQ, to be deleted.


Use a response file with msiexec

About this task

You can use the msiexec command with a parameter which specifies additional properties are defined in a response file. You can combine the msiexec command-line parameters described in Specifying command line parameters with msiexec .

A response file is an ASCII text file, with a format like a Windows .ini file, that contains the stanza [Response]. The [Response] stanza contains some or all the parameters that would normally be specified as part of an interactive installation. The parameters are given in a property=value pair format. Any other stanzas in the response file are ignored by msiexec. An example response file, Response.ini, is supplied with WebSphere MQ. It contains the default installation parameters.

Procedure

A typical example of an msiexec command is: msiexec /i path\MSI\IBM WebSphere MQ.msi /l*v c:\install.log TRANSFORMS= 1033.mst USEINI= C:\MQ\Responsefile

If a parameter is specified both on the command line and in a response file, the setting on the command line takes precedence. All the parameters available for use in a response file can also be used on the command line, for a list of these see Table 2 .

In the response file, all text is in English, and comments begin with a ; character.

For information about creating a response file, see Creating a response file .

Example

An example of a typical response file: 

[Response]
PGMFOLDER="c:\mqm"
DATFOLDER="c:\mqm\data"
AGREETOLICENSE="yes"
ADDLOCAL="Client"
REMOVE="Toolkit"

Response file parameters

Property Values Meaning
PGMFOLDER path Folder for the WebSphere MQ program files. For example, c:\mqm.
DATFOLDER path Folder for the WebSphere MQ data files. For example, c:\mqm\data.
USERCHOICE 0|no If the command line or response file specifies parameters to install features, a dialog can be displayed to prompt you to accept the preselected options, or review and possibly change them.

0 or no. Suppresses display of the dialog.

Anything else. Dialog is displayed and you can amend the options.

Not used for a silent installation.

AGREETOLICENSE yes Accept the terms of the license. Set to yes before a silent installation.

If the installation is not silent, this parameter is ignored.

ADDLOCAL feature, feature, All| "" A comma-separated list of features to install locally. For a list of valid feature names, see WebSphere MQ features for Windows systems .

All installs all features

"" installs the typical features. If you do not want a feature use REMOVE="feature" If this is a new installation the typical features (Client, Java™, .NET Messaging, and Development Toolkit) are installed by default irrespective of the feature list provided in the ADDLOCAL property. If you do not want a feature use REMOVE="feature"

REMOVE feature, feature, |All| "" A comma-separated list of features to remove. For a list of valid feature names, see WebSphere MQ features for Windows systems .

All uninstalls all features

"" uninstalls no features (the default).

INSTALLATIONDESC ?Description of installation? Sets the installation description from the command line. Subject to the documented installation description length limitations
INSTALLATIONNAME [INSTALLATION0,]?Name? Sets the installation name from the command line. Subject to the documented installation name character and length limitations. Supply INSTALLATION0,Name only when upgrading from pre-WebSphere MQ version 7.1.
MAKEPRIMARY 0|1| "" Makes the installation primary, if possible, or removes the primary flag. 1 = Make primary, 0 = Make non-primary, - use default algorithm This option is ignored if a pre-version 7.1 WebSphere MQ is installed, or if another version 7.1 or greater installation is present and set as the primary.


Multiple installation using MSI Instance ID

This topic describes how to choose the MSI instance ID you require for non-interactive multiple installations. In order to support non-interactive multiple installations, you need to find out whether the instance ID you want to use is already in use or not and choose the appropriate one. For each installation media (for example, each 7.5 client and 7.5 server), Instance ID 1 is the default ID which is used for single installations. To install alongside Instance ID 1 you need to specify which instance you want to use. If you have already installed instance 1, 2, and 3 then you need to find out what the next available instance is, for instance, Instance ID 4. Similarly, if instance 2 has been removed, you need to find out that there is a gap that can be reused. You can find out which Instance ID is currently in use using the dspmqinst command.


Procedure

  1. Type dspmqinst to find a free MSI Instance in the media being installed by reviewing the MSIMedia and MSIInstanceId values for the versions already installed. For example: 

    InstName:      Installation1
InstDesc:
Identifier:    2
InstPath:      C:\mq\install1
Version:       7.5.0.0
Primary:       Yes
State:         Available
MSIProdCode:   {0730749B-080D-4A2E-B63D-85CF09AE0EF0}
MSIMedia:      7.5 Server MSIInstanceId: 1

  2. If MSI Instance ID 1 is in use and you want to use MSI Instance ID 2, the following parameters must be added to the msiexec call: 

    MSINEWINSTANCE=1 TRANSFORMS=:InstanceId2.mst


What to do next

For multiple installations, the INSTALLATIONNAME or PGMFOLDER must be supplied as an additional parameter on any non-interactive installation command. Supplying the INSTALLATIONNAME or PGMFOLDER ensures that you do not work with the wrong installation in case you omit or incorrectly specify the TRANSFORMS parameter.


Use transforms with msiexec

MSI can use transforms to modify an installation. During WebSphere MQ installation, transforms can be used to support different national languages. WebSphere MQ is supplied with transform files in the \MSI folder of the client image. These files are also embedded in the WebSphere MQ Windows installer package, IBM WebSphere MQ.msi.

On the msiexec command line, you can specify the required language by using the TRANSFORMS property in a property=value pair. For example: 

TRANSFORMS="1033.mst"

You can also specify the full path and file name of the transform file. Again, the quotation marks surrounding the value are optional. For example: 

TRANSFORMS="D:\Msi\1033.mst"

Table 1 shows the locale identifier, language, and the transform file name to use in the msiexec command line.

You might need to merge transforms to install multiple installations of the same version, for example: 

TRANSFORMS=":InstanceId2.mst;D:\Msi\1033.mst"

You can also specify the required language by using the MQLANGUAGE property with the MQParms command. For information about the msiexec property=value parameters, see MQParms parameter file .


Parameters

Supplied transform files for various language support. This table shows the supplied transform files, the resulting language, and the numeric value to use in the msiexec command line.

Language Transform File name Value
U.S. English 1033.mst 1033
German 1031.mst 1031
French 1036.mst 1036
Spanish 1034.mst 1034
Italian 1040.mst 1040
Brazilian Portuguese 1046.mst 1046
Japanese 1041.mst 1041
Korean 1042.mst 1042
Simplified Chinese 2052.mst 2052
Traditional Chinese 1028.mst 1028
Czech 1029.mst 1029
Russian 1049.mst 1049
Hungarian 1038.mst 1038
Polish 1045.mst 1045


Create a response file

A response file is used with msiexec. You can create it in three ways. A response file is used with the msiexec command, for further information see Using a response file with msiexec .


Procedure

There are three ways to create a response file for installation


Example

A typical example of using msiexec with the SAVEINI parameter is here: 

msiexec /i "path\IBM WebSphere MQ.msi" /q SAVEINI="response_file" 
TRANSFORMS="1033.mst" AGREETOLICENSE="yes"


Use the MQParms command

You can use the MQParms command to invoke installation or uninstallation. This command can use parameters on a command line, or those specified in a parameter file. The parameter file is an ASCII text file that contains the parameter values that you want to set for the installation. The MQParms command takes the specified parameters and generates the corresponding msiexec command line.

This means that you can save all the parameters that you want to use with the msiexec command in a single file.

If you are running WebSphere MQ on Windows systems with User Account Control (UAC) enabled, you must invoke the installation with elevated privileges. If you are using the Command prompt or WebSphere MQ Explorer elevate privileges by using a right-click to start the program and selecting Run as administrator. If you try to run the MQParms program without using elevated privileges, the installation fails with an error of AMQ4353 in the installation log.

For silent operations, this must include the /q or /qn parameter, either on the command line, or in the [MSI] stanza of the parameter file. You must also set the AGREETOLICENSE parameter to "yes".

You can specify many more parameters in the parameter file that you use with the MQParms command than you can in the response file that you use directly with the msiexec command. Also, as well as parameters that the WebSphere MQ installation uses, you can specify parameters that can be used by the Prepare WebSphere MQ wizard.

If you do not complete the Prepare WebSphere MQ Wizard directly after WebSphere MQ installations or if for any reason your machine is rebooted between completing WebSphere MQ installation and completing the Prepare WebSphere MQ Wizard, ensure that the wizard is run with Administrator privilege afterward, otherwise the installation is incomplete, and might fail. You might also see Open File - Security Warning dialog boxes that list International Business Machines Limited as the publisher. Click Run to allow the wizard to continue

An example of the file MQParms.ini is supplied with WebSphere MQ. This file contains default installation parameters.

There are two ways to create a parameter file for installation:

To invoke installation using the MQParms command:


Procedure

  1. From a command line, change to the root folder of the WebSphere MQ client CD (that is, the location of the file MQParms.exe).

  2. Enter the following command: 

    MQParms [parameter_file] [parameters]

    where:

    parameter_file

    is the file that contains the required parameter values. If this file is not in the same folder as MQParms.exe, specify the full path and file name. If you do not specify a parameter file, the default is MQParms.ini. For further details, see MQParms parameter file .

    parameters

    are one or more command-line parameters, for a list of these, see the MSDN Command-Line Options web page .


Example

A typical example of an MQParms command is: 

MQParms "c:\MyParamsFile.ini" /l*v c:\install.log

If you specify a parameter both on the command line and in the parameter file, the setting on the command line takes precedence.

If you do not specify /i, /x, /a, or /j, MQParms defaults to standard installation using the WebSphere MQ Windows Installer package, IBM WebSphere MQ.msi. That is, it generates the following part of the command line: 

/i "current_folder\MSI\IBM WebSphere MQ.msi"


MQParms parameter file

A parameter file is an ASCII text file that contains sections (stanzas) with parameters that can be used by the MQParms command. Typically, this is an initialization file such as MQParms.ini.

The MQParms command takes parameters from the following stanzas in the file:

[MSI]

Contains general properties related to how the MQParms command runs and to the installation of WebSphere MQ.

The properties that you can set in this stanza are listed in Advanced installation using msiexec , and Table 1 .

MQParms ignores any other stanzas in the file.

The stanza parameters are in the form property=value, where property is always interpreted as uppercase, but value is case sensitive. If a value string includes a blank, it must be enclosed in double quotation marks. Most other values can be enclosed in double quotation marks. Some properties can take more than one value, for example: 

ADDLOCAL="Server,Client"

To clear a property, set its value to an empty string, for example: 

REINSTALL=""

The following tables show the properties that you can set. The default is shown in bold.

For the [MSI] stanza, you can enter parameters in command line format (for example, /q) and parameters in property=value format (for example, ADDLOCAL="client"). Refer to Table 1 , and Table 2 for the properties used to install WebSphere MQ. Table 1 shows additional properties in the stanza that affect how the MQParms command runs, but that do not affect the installation.

Properties used by MQParms in the MSI stanza

Property Values Description
MQPLOG path|file_name MQParms generates a text log file with the specified name and location.
MQPLANGUAGE


system |user|transform_value|existing

The installation language.

system. Install using the language of the default system locale (the default).

User. Install using the language of the default locale of the user.

transform_value. Install using the language specified by this value. See Table 2 .

existing. If MQ already exists on the system, the same language will be used by default, otherwise system is used.

MQPSMS 0 |no 0 or no. MQParms does not wait for the msiexec command to end (the default).

Any other value. MQParms waits for the msiexec command to end.

MQPINUSE 0 |1 If MQPINUSE is set to 1, MQParams continues installing even if WebSphere MQ files are in use. If this option is used a reboot will be required to complete the installation.
MQPNOREBOOT 0 |1 If MQPNOREBOOT is set to 1, the reboot that is required if installation takes place while WebSphere MQ files are still in use will be suppressed.

Valid values for the MQPLANGUAGE property

Language Valid values
U.S. English English en_us 1033
German German de_de 1031
French French fr_fr 1036
Spanish Spanish es_es 1034
Italian Italian it_it 1040
Brazilian Portuguese   pt_br 1046
Japanese Japanese ja_jp 1041
Korean Korean ko_kr 1042
Simplified Chinese   zh_cn 2052
Traditional Chinese   zh_tw 1028
Czech Czech cs_cz 1029
Russian Russian ru_ru 1049
Hungarian Hungarian hu_hu 1038
Polish Polish pl_pl 1045

A typical example of a parameter file is: 

[MSI]
MQPLANGUAGE=1033
MQPLOG=%temp%\MQParms.log
MQPSMS=no
ADDLOCAL=CLIENT
/m miffile
REMOVE=""
/l*v c:\install.log


Modify the client installation on Windows

You modify the installation when WebSphere MQ for Windows client is installed and you want to remove or install some WebSphere MQ client features.

  1. Insert WebSphere MQ client DVD into the DVD drive.

  2. If autorun is installed, the installation process starts.

    Otherwise, double-click Setup in the root folder of the DVD to start the installation process.

    The WebSphere MQ client Setup window is displayed. Click Next to continue.

  3. Select Modify , then click Next.

    The Features panel is displayed.

  4. To change the installation of a feature:

    1. Click the symbol next to the feature name to display a menu.

    2. Select the required option from:

      • Install this feature

      • Install this feature and all its subfeatures (if any)

      • Do not install this feature (remove if already installed).

      The symbol next to the feature name changes to show the current installation option.

  5. When your selections are complete, click Next.

  6. The WebSphere MQ client Setup window displays a summary of the installation you selected.

    To continue, click Modify.

  7. Wait until the progress bar is complete.

    When the WebSphere MQ client is successfully installed, the WebSphere MQ client Setup window displays the following message: Installation Wizard Completed Successfully

    Click Finish to close the window.


Modify the client installation on Windows using Add/Remove Programs

On some versions of Windows, you can modify an installation by using Add/Remove Programs.

For Windows Active Directory Server, Windows XP, or Windows 2003, follow these steps. You cannot use this method to modify an installation on any other version of Windows.

  1. From the Windows taskbar, select Start > Settings > Control Panel.

  2. Select Add/Remove Programs.

  3. Select IBM WebSphere MQ .

  4. Select Change.

    The WebSphere MQ Setup window with the Program Maintenance panel is displayed. Follow the procedure for modifying the installation by using the process from step 3 to the end.


Silently modifying a WebSphere MQ client installation using msiexec

To silently modify an installation using msiexec, follow the instructions on the installation pages, but set the ADDLOCAL parameter to include the features you want to add, and set the REMOVE parameter to the features you want to remove.

For example if you used ADDLOCAL="JavaMsg" and REMOVE="" it would modify the installation to include the Java Messaging and Web Services feature.

The instructions for msiexec begin here: Advanced installation using msiexec


Silently modifying a WebSphere MQ client installation using MQParms

To silently modify an installation using MQParms, follow the instructions on the installation pages, but set the ADDLOCAL parameter to include the features you want to add, and set the REMOVE parameter to the features you want to remove.

For example if you used ADDLOCAL="JavaMsg" and REMOVE="" it would modify the installation to include the Java Messaging and Web Services feature.

For details of the MQParms command, see Using the MQParms command .


Install WebSphere MQ Advanced Message Security

Install and uninstall IBM WebSphere MQ Advanced Message Security component. WebSphere MQ Advanced Message Security is a separately installed and licensed component of WebSphere MQ and is another option on the WebSphere MQ installer. Make sure that you purchase a license for using WebSphere MQ Advanced Message Security before the installation.

Additionally, make sure the following WebSphere MQ components are installed in your environment:


Install WebSphere MQ Advanced Message Security on AIX

You can install IBM WebSphere MQ Advanced Message Security component on AIX platforms using either system management interface tool (SMIT) or the command line.


Install using SMIT

Procedure

  1. Log on as root.

  2. Change the directory to the location of the installation packages.

  3. Start the system management interface tool (SMIT). The system management menu is displayed.

  4. Select the required SMIT window using the following sequence: 

    Software Installation and Maintenance    
            Install and Update Software 
         Install Software

  5. Enter the directory location of the installation package.

  6. Press F4 to list the software in the SOFTWARE name option.

  7. Select the mqm.ams.rte and press Enter.

  8. Accept the default setting for the remaining options and press Enter.

Results

WebSphere MQ Advanced Message Security has been installed successfully.


Install using command line

Procedure

  1. Log on as root.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. Run the following command: 

    installp -a -c -Y -d. mqm.ams.rte
    Note the period, signifying the current directory, following the -d parameter.

Results

WebSphere MQ Advanced Message Security component has been installed successfully.


Install WebSphere MQ Advanced Message Security on HP-UX

You can install IBM WebSphere MQ Advanced Message Security component on HP-UX platforms.


Procedure

  1. Log on as root.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the DVD, a network location, or a local file system directory.

  3. In the command line, issue the following command: 

    swinstall -s MQSERIES.MQM-AMS

WebSphere MQ Advanced Message Security component has been installed successfully.


Install WebSphere MQ Advanced Message Security on Linux

You can install IBM WebSphere MQ Advanced Message Security on Linux platforms.


Procedure

  1. Log on as root.

  2. Set your current directory to the location of the installation file. The location might be the mount point of the server CD, a network share, or a local file system directory.

  3. If this installation is not the first installation on the system, you must run the crtmqpkg command to create a unique set of packages to install on the system. In order for the crtmqpkg command to run on Linux, the pax command must be installed.

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing, that uniquely identifies the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9. This command creates a full copy of the installation packages in a subdirectory of /var/tmp. You must ensure that the system has enough space before running the command.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a subdirectory of /var/tmp/mq_rpms, in which the unique set of packages is created. The packages have the suffix value contained within the filename. For example, using a suffix of "1": 

      ./crtmqpkg 1
      there will be a subdirectory named /var/tmp/mq_rpms/1/i386 and the packages will be renamed, for example: 

      From: MQSeriesAMS-7.5.0-0.i386.rpm
To: MQSeriesAMS_1-7.5.0-0.i386.rpm

  4. In the command line, issue the following command:

    This example shows a minimum installation: 

    rpm -iv <package_name>
    where <package_name> is one of the following:

    • MQSeriesAMS-7.5.0-0.i386.rpm

    • MQSeriesAMS-7.5.0-0.x86_64.rpm

    • MQSeriesAMS-7.5.0-0.ppc.rpm

    • MQSeriesAMS-7.5.0-0.s390.rpm

WebSphere MQ Advanced Message Security has been installed successfully.


Install WebSphere MQ Advanced Message Security on Solaris

You can install IBM WebSphere MQ Advanced Message Security component on Solaris platforms.


Procedure

  1. Log on as root.

  2. If this installation is not the first installation on the system, you must run crtmqpkg to create a unique set of packages to install on the system:

    1. Enter the following command: 

      ./crtmqpkg suffix
      where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.

    2. Set your current directory to the location specified when the crtmqpkg command completes. This directory is a sub-directory of /var/spool, in which the unique set of packages is created. The packages have the suffix value contained within the filename.

  3. Start the installation process

    • If the installation is the first installation on the system, enter the following command to start the installation process: 

      pkgadd -d.

    • If the installation is not the first installation on the system, enter the following command to start the installation process: 

      pkgadd mqm-suffix
      where suffix is the suffix chosen in the previous step.

  4. You are prompted to choose a location for installation.
    • To install to the default location, /opt/mqm, enter y.

    • To install to a non-default directory, enter n. Then enter the required installation path, and confirm your choice.

  5. Choose the mqams component.

  6. If the path chosen in step 4 does not exist, you are asked if you want to create it. You must enter y to proceed.

  7. A message is issued when the installation is complete. Enter q to exit the pkgadd program.

WebSphere MQ Advanced Message Security component has been installed successfully.


Install WebSphere MQ Advanced Message Security on Windows

Once you purchase the IBM WebSphere MQ Advanced Message Security license, you can install the component on Windows platforms.


Use the Launchpad

Procedure

  1. Access the WebSphere MQ installation image. The location might be the mount point of the DVD, a network location, or a local file system directory.

  2. Locate setup.exe in the base directory of the WebSphere MQ installation image.
    • From a DVD, this location might be: 

      E:\setup.exe

    • From a network location, this location might be: 

      m:\instmqs\setup.exe

    • From a local file system directory, this location might be: 

      C:\instmqs\setup.exe

  3. Double-click the Setup icon to start the installation process. It is possible to start the process by either

    • Running setup.exe from the command prompt.

    • Double-clicking setup.exe from WebSphere MQ Explorer.

    If you are installing on a Windows system with UAC enabled, accept the Windows prompt to allow the launchpad to run as elevated. During installation, you might also see Open File - Security Warning dialog boxes that list International Business Machines Limited as the publisher. Click Run to allow the installation to continue.

    The WebSphere MQ Installation Launchpad window is displayed.

  4. Continue to follow the Launchpad instructions as shown on screen.


Verify a WebSphere MQ installation


Verify a server installation

You can verify a local (stand-alone) installation or a server-to-server installation of the WebSphere MQ server. A local installation has no communication links with other WebSphere MQ installations while a server-to-server installation does have links to other installations.

You can use either the command line or the postcard application to verify your installation. The postcard application is Java™ based and requires a system with the ability to view a graphical display.

A local installation uses a single queue manager while a server-to-server installation has multiple queue managers and queues, and both sender and receiver channels.

For a server-to-server verification, the communication links between the two systems must be checked. Before you can do the verification, you must ensure that the communications protocol is installed and configured on both systems. The examples explain how to verify your installation using TCP.

UNIX systems

WebSphere MQ supports both TCP and SNA. If you do not use TCP, see Setting up communication on UNIX and Linux systems .

Linux

WebSphere MQ for Linux supports TCP on all Linux platforms. On x86 platforms and Power platforms, SNA is also supported. To use the SNA LU6.2 support on these platforms, you need the IBM Communications Server for Linux Version 6.2. The Communications Server is available as a PRPQ product from IBM. For more details, see http://www.ibm.com/software/network/commserver/about .

If you do not use TCP, see Setting up communication on UNIX and Linux systems .

Windows

WebSphere MQ for Windows supports TCP, SNA, NetBios, and SPX. If you do not use TCP, see Setting up communication for Windows .


Verify the installation using the command line

You can use the command line to verify a local installation or a server-to-server installation.

Use the command line to verify that WebSphere MQ is successfully installed, and that the associated communication links are working properly.

You can also verify an installation using the postcard application. The postcard application is Java based and requires a system with the ability to view a graphical display. See Verify the installation using the Postcard application .


Verify a local installation using the command line

You can verify a local installation by using the command line to create a simple configuration of one queue manager and one queue. To verify the installation, you must first install the samples package.

Before beginning the verification procedure, you might want to check that you have the latest fixes for your system. For more information about where to find the latest updates, see Finding the latest information .

Use the following steps to configure your default queue manager from the command line. After the queue manager is configured, use the amqsput sample program to put a message on the queue. You then use the amqsget sample program to get the message back from the queue.

This procedure is for Windows, UNIX and Linux systems.

WebSphere MQ object definitions are case-sensitive. Any text entered as an MQSC command in lowercase is converted automatically to uppercase unless you enclose it in single quotation marks. Make sure that you type the examples exactly as shown.


Procedure

  1. If you are verifying an installation on a UNIX or Linux system, log in as a user in the mqm group.

  2. Set up your environment:

    1. Set up environment variables for use with a particular installation by entering one of the following commands:

      • On Windows: 

        MQ_INSTALLATION_PATH/bin/setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

      • On UNIX systems: 

        . MQ_INSTALLATION_PATH/bin/setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

      • On Linux systems: 

        . source/ MQ_INSTALLATION_PATH/bin/setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    2. Check that the environment is set up correctly: 

      dspmqver
      If the command completes successfully, and the expected version number and installation name are returned, the environment is set up correctly.

  3. Create a queue manager called QMAby entering the following command: 

    crtmqm QMA
    Messages indicate when the queue manager is created, and when the default WebSphere MQ objects are created.

  4. Start the queue manager: 

    strmqm QMA
    A message indicates when the queue manager starts.

  5. Start MQSC: 

    runmqsc QMA
    A message indicates when MQSC starts. MQSC has no command prompt.

  6. Define a local queue called QUEUE1 by entering the following command: 

    DEFINE QLOCAL (QUEUE1)
    A message indicates when the queue is created.

  7. Stop MQSC: 

    end
    Messages are shown, followed by the command prompt.

Subsequent steps require that the samples package is installed.

  1. If you are verifying an installation on a UNIX or Linux system, change into the MQ_INSTALLATION_PATH/samp/bin directory, which contains the sample programs. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

  2. Put a message on the queue by entering one of the following commands:

    • On UNIX and Linux systems: 

      ./amqsput QUEUE1 QMA

    • On Windows systems: 

      amqsput QUEUE1 QMA

    The following messages are shown: 

    Sample AMQSPUT0 start target queue is QUEUE1

  3. Type some message text on one or more lines, where each line is a different message. Enter a blank line to end the message input. The following message is shown: 

    Sample AMQSPUT0 end
    Your messages are now on the queue and the command prompt is shown.

  4. Get the messages from the queue, by entering one of the following commands:

    • On UNIX and Linux systems: 

      ./amqsget QUEUE1 QMA

    • On Windows systems: 

      amqsget QUEUE1 QMA

    The sample program starts, and your messages are displayed.

You have successfully verified your local installation.


Verify a server-to-server installation using the command line

You can verify a server-to-server installation using two servers, one as a sender and one as a receiver.

This procedure provides instructions for Windows, UNIX and Linux systems only.

WebSphere MQ object definitions are case-sensitive. Any text entered as an MQSC command in lowercase is converted automatically to uppercase unless you enclose it in single quotation marks. Make sure that you type the examples exactly as shown.


Procedure

  1. On the receiver server:

    1. If the receiver server is a UNIX or Linux system, log in as a user in the mqm group.

    2. Check which ports are free, for example by running netstat. For more information about this command, see the documentation of your operating system.

      If port 1414 is not in use, make a note of 1414 to use as the port number in step 2 h . Use the same number for the port for your listener later in the verification. If it is in use, note a port that is not in use; for example 1415.

    3. Set up the environment for the installation you are using by entering one of the following commands at the command prompt:

      • On Windows: 

        MQ_INSTALLATION_PATH\bin\setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

      • On UNIX and Linux systems: 

        . MQ_INSTALLATION_PATH/bin/setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    4. Create a queue manager called QMB at the command prompt: 

      crtmqm QMB
      Messages tell you that the queue manager has been created, and that the default WebSphere MQ objects have been created.

    5. Start the queue manager: 

      strmqm QMB
      A message tells you when the queue manager has started.

    6. Start MQSC: 

      runmqsc QMB
      A message tells you that MQSC has started. MQSC has no command prompt.

    7. Define a local queue called RECEIVER.Q: 

      DEFINE QLOCAL (RECEIVER.Q)
      A message tells you the queue has been created.

    8. Define a listener: 

      DEFINE LISTENER (LISTENER1) TRPTYPE (TCP) CONTROL (QMGR) PORT (PORT_NUMBER)
      Where port_number is the name of the port the listener runs on. This number must be the same as the number used when defining your sender channel.

    9. Start the listener: 

      START LISTENER (LISTENER1)
      Do not start the listener in the background from any shell that automatically lowers the priority of background processes.

    10. Define a receiver channel: 

      DEFINE CHANNEL (QMA.QMB) CHLTYPE (RCVR) TRPTYPE (TCP)
      A message tells you when the channel has been created.

    11. End MQSC by typing: 

      end
      Some messages are displayed, followed by the command prompt.

  2. On the sender server:

    1. If the sender server is a UNIX or Linux system, log in as a user in the mqm group.

    2. Set up the environment for the installation you are using by entering one of the following commands at the command prompt:

      • On Windows: 

        MQ_INSTALLATION_PATH\bin\setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

      • On UNIX and Linux systems: 

        . MQ_INSTALLATION_PATH/bin/setmqenv -s
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Create a queue manager called QMA at the command prompt: 

      crtmqm QMA
      Messages tell you that the queue manager has been created, and that the default WebSphere MQ objects have been created.

    4. Start the queue manager,: 

      strmqm QMA
      A message tells you when the queue manager has started.

    5. Start MQSC: 

      runmqsc QMA
      A message tells you that an MQSC session has started. MQSC had no command prompt.

    6. Define a local queue called QMB (to be used as a transmission queue): 

      DEFINE QLOCAL (QMB) USAGE (XMITQ)
      A message tells you when the queue has been created.

    7. Define a local definition of the remote queue with: 

      DEFINE QREMOTE (LOCAL.DEF.OF.REMOTE.QUEUE) RNAME (RECEIVER.Q) 
RQMNAME ('QMB') XMITQ (QMB)

    8. Define a sender channel by entering one of the following commands:

      con-name is the TCP/IP address of the receiver system. If both installations are on the same system, the con-name is localhost. port is the port you noted in 1 b . If you do not specify a port, the default value of 1414 is used. 

      DEFINE CHANNEL (QMA.QMB) CHLTYPE (SDR) 
CONNAME ('CON-NAME(PORT)') XMITQ (QMB) TRPTYPE (TCP)

    9. Start the sender channel: 

      START CHANNEL(QMA.QMB)
      The receiver channel on the receiver server starts automatically when the sender channel starts.

    10. Stop MQSC: 

      end
      Some messages are displayed, followed by the command prompt.

    11. If the sender server is a UNIX or Linux system, change into the MQ_INSTALLATION_PATH/samp/bin directory. This directory contains the sample programs. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

    12. If both the sender server and receiver server are installations on the same system, check that the queue managers have been created on different installations: 

      dspmq -o installation
      If the queue managers are on the same installation, move either QMA to the sender installation or QMB to the receiver installation by using the setmqm command. For more information, see setmqm .

    13. Put a message on the local definition of the remote queue, which in turn specifies the name of the remote queue. Enter one of the following commands:

      • On Windows: 

        amqsput LOCAL.DEF.OF.REMOTE.QUEUE QMA

      • On UNIX and Linux systems: 

        ./amqsput LOCAL.DEF.OF.REMOTE.QUEUE QMA

      A message tells you that amqsput has started.

    14. Type some message text on one or more lines, followed by a blank line. A message tells you that amqsput has ended. Your message is now on the queue and the command prompt is displayed again.

  3. On the receiver server:

    1. If your receiver server is a UNIX or Linux system, change into the MQ_INSTALLATION_PATH/samp/bin directory. This directory contains the sample programs. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

    2. Get the message from the queue on the receiver by entering one of the following commands:

      • On Windows: 

        amqsget RECEIVER.Q QMB

      • On UNIX and Linux systems: 

        ./amqsget RECEIVER.Q QMB

      The sample program starts, and your message is displayed. After a pause, the sample ends. Then the command prompt is displayed.

You have now successfully verified the server-to-server installation.


Verify the installation using the Postcard application

You can set up and use the Postcard application to verify a local installation or a server-to-server installation.

Use the Postcard application to verify that WebSphere MQ is successfully installed, and that the associated communication links are working properly.

The postcard application is Java based and requires a system with the ability to view a graphical display. You can also verify an installation using the command line, see Verify the installation using the command line .

Using Postcard to verify a WebSphere MQ installation is only possible if there is one WebSphere MQ installation on that box. The Default Configuration wizard will not create a default configuration if a queue manager already exists on the box. The Default Configuration wizard will run on any installation on a box but only one default configuration can be created per box. Using Postcard to verify second and subsequent installations of WebSphere MQ on the same box is not possible.


Use the Postcard application to verify a local installation

Sending messages successfully between two Postcard applications verifies a local installation. To verify that the local installation is working, you can run two instances of the Postcard application on the same server. The postcard application can send messages to, and receive messages from, other postcard applications. Successful sending and receiving of messages verifies that WebSphere MQ is installed and working correctly on the server.


Procedure

  1. If you are verifying an installation on UNIX, Linux or Windows systems, log on as a user in group mqm.

  2. Start the postcard application in one of the following ways:

    1. From the command line:

      1. Change the directory to MQ_INSTALLATION_PATH/java/bin. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

      2. Run the postcard application by entering one of the following commands:

        • UNIX and Linux systems: 

          ./postcard

        • Windows systems: 

          postcard

    2. From the WebSphere MQ Explorer: On Windows and Linux systems (x86-64 platforms), you can start MQ Explorer by using the system menu, the MQExplorer command (preferred command), or the MQExplorer executable file. The strmqcfg command is still usable.

      1. If the Welcome to WebSphere MQ Explorer Content view page does not show, click IBM WebSphere MQ in the Navigator view to show the Welcome page.

      2. Click Launch Postcard to start the Postcard.

  3. At the Postcard - Sign On window, type in a nickname to use to send messages within the Postcard application (for example, User1).

  4. Select the queue manager to use as the mailbox:

    • If you do not have any queue managers, you are prompted to either launch the Default Configuration or close the Postcard application. Launching the Default Configuration creates a default queue manager.

    • If the only queue manager on your server is the default queue manager, this queue manager is used automatically for the postcard application. The default queue manager is created by running the Default Configuration wizard

    • If you have created your own queue managers, but you have not run the Default Configuration wizard, select an appropriate queue manager from the list.

    • If you have run the Default Configuration wizard and you want to use the default queue manager, but there are other queue managers on your server, select the Advanced check box. Then select Use Default Configuration as mailbox.

    • If you have run the Default Configuration wizard and also created your own queue managers, and you do not want to use the default queue manager, select the Advanced check box. Then select Choose queue manager as mailbox, and then select the appropriate queue manager from the list.

    When your selection is complete, click OK to display your first Postcard window.

  5. Run a second instance of the Postcard application by following the steps used to open the first instance of the Postcard application.

  6. The Postcard - Sign On panel is displayed again. Type in a second nickname to use to send messages within this second Postcard application (for example, User2).

  7. Repeat the selection of the queue manager that you want to use as the mailbox (as described in step 4). The queue manager you select for this second Postcard must be the same queue manager as used for the first instance of the Postcard application.

  8. In the first Postcard, (User1), enter the nickname (User2) for the second Postcard application in the To: field. Because the sender and receiver are on the same server, you can leave the On: field blank.

  9. Type a message in the Message: field and click Send.

  10. The Postcards sent and received area of the Postcard shows details of the message. In the sending Postcard, the message is displayed as sent. In the receiving Postcard, the message is displayed as received.

  11. In the receiving Postcard, (User2), double-click the message in the Postcards sent and received area to view it. When this message arrives, it verifies that WebSphere MQ is correctly installed.


What to do next

Depending on your situation, you might want to do the following tasks:


Use the Postcard application to verify a server-to-server installation

You can use two instances of the Postcard application to verify that a server-to-server installation is working. You can use the Postcard application on two servers, one instance of the Postcard application on each server, to verify that a server-to-server installation is working. Successful sending and receiving of messages verifies that WebSphere MQ is successfully installed, and that communication between the two servers is working correctly.


Procedure

  1. If you are verifying an installation on UNIX or Linux systems, log on as a user in group mqm.

  2. Start the postcard application in one of the following ways:

    1. From the command line:

      1. Change the directory to MQ_INSTALLATION_PATH/java/bin. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

      2. Run the postcard application by entering one of the following commands:

        • UNIX and Linux systems: 

          ./postcard

        • Windows systems: 

          postcard

    2. From the WebSphere MQ Explorer: On Windows and Linux systems (x86-64 platforms), you can start MQ Explorer by using the system menu, the MQExplorer executable file, or the strmqcfg command.

      1. If the Welcome to WebSphere MQ Explorer Content view page does not show, click IBM WebSphere MQ in the Navigator view to show the Welcome page.

      2. Click Launch Postcard to start the Postcard.

  3. At the Postcard - Sign On window, type a nickname to use to send messages within the Postcard application. For example, User1 for the first server, and User2 for the second server.

  4. When you have completed the wizard, you are taken back to the Postcard - Sign On window.

  5. Select the queue manager to use as the mailbox:

    • If you do not have any queue managers, you are prompted to either launch the Default Configuration or close the Postcard application. Work through the Default Configuration wizard. When you get to the option to join the queue manager to the default cluster, tick the check box. On the next screen:

      • For the first server, select yes, make it the repository for the cluster.

      • For the second server, select No another computer has already joined the cluster as a repository. When requested, enter the location of the repository, by typing the name of the sender server.

    • If the only queue manager on your server is the default queue manager, this queue manager is used automatically for the postcard application. The default queue manager is created by running the Default Configuration wizard

    • If you have created your own queue managers, but you have not run the Default Configuration wizard, select an appropriate queue manager from the list.

    • If you have run the Default Configuration wizard and you want to use the default queue manager, but there are other queue managers on your server, select the Advanced check box. Then select Use Default Configuration as mailbox.

    • If you have run the Default Configuration wizard and also created your own queue managers, and you do not want to use the default queue manager, select the Advanced check box. Then select Choose queue manager as mailbox, and then select the appropriate queue manager from the list.

    When your selection is complete, click OK.

  6. Complete steps 1 - 5 for the second server.

  7. In the Postcard on the first server:

    1. Enter the nickname (user2) for the Postcard application on the second server in the To: field.

    2. Enter the queue manager on the second server in the On: field.

    3. Type a message in the Message: field and click Send.

  8. In the Postcard on the second server:

    1. In the Postcards sent and received, double-click the message marked as received to view the message from the first server.

    2. Optional: Send a postcard to the first server by adapting the instructions in step 7. You must enter details of the first server in the To: field and the On: field.

    The messages verify that WebSphere MQ is correctly installed and that your communication link between the two servers is working correctly.


Verify a client installation

You can verify that your WebSphere MQ MQI client installation completed successfully and that the communication link is working.

The verification procedure shows how to create a queue manager called queue.manager.1, a local queue called QUEUE1, and a server-connection channel called CHANNEL1 on the server.

It shows how to create the client-connection channel on the WebSphere MQ MQI client workstation. It then shows how to use the sample programs to put a message onto a queue, and get the message from the queue.

The example does not address any client security issues. See Setting up WebSphere MQ MQI client security for details if you are concerned with WebSphere MQ MQI client security issues.

The verification procedure assumes that:

To begin the verification procedure using the command line, see Verifying a client installation using the command line .

To begin the verification procedure for the Windows and Linux operating systems when you are using the WebSphere MQ Explorer, see Verifying a client installation using WebSphere MQ Explorer .


Verify a client installation using the command line

You can verify a client installation using the command line. On the server you create a queue manager, a local queue, a listener, and a server-connection channel. You must also apply security rules to allow the client to connect and make use of the queue defined. On the client you create a client-connection channel, and then use the sample PUT and GET programs to complete the verification procedure.

First, set up the server using the command line, using the instructions in Setting up the server using the command line .

Once you have set up the server, you must set up the client, using the instructions in Connecting a WebSphere MQ MQI client to a queue manager, using the MQSERVER environment variable .

Finally, you can test the communications between client and server, using the instructions in Testing communication between a client and a server .


Set up the server using the command line

Follow these instructions to create a queue manager, queue, and channel on the server. You can then use these objects to verify the installation.

These instructions assume that no queue manager or other WebSphere MQ objects have been defined.

WebSphere MQ object definitions are case-sensitive. Any text entered as an MQSC command in lowercase is converted automatically to uppercase unless you enclose it in single quotation marks. Make sure that you type the examples exactly as shown.


Procedure

  1. Create a user ID on the server that is not in the mqm group.

  2. If your server is on a UNIX or Linux system, log in as a user in the mqm group.

  3. If you are verifying an installation on a Windows, UNIX or Linux system, you must set various environment variables so that the installation can be used in the current shell. You can set the environment variables by entering one of the following commands

    • On Windows: 

      . MQ_INSTALLATION_PATH\bin\setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    • On UNIX and Linux systems: 

      . MQ_INSTALLATION_PATH/bin/setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

  4. Create a queue manager called QUEUE.MANAGER.1: 

    crtmqm QUEUE.MANAGER.1
    You see messages telling you that the queue manager has been created.

  5. Start the queue manager: 

    strmqm QUEUE.MANAGER.1
    A message tells you when the queue manager has started.

  6. Start MQSC: 

    runmqsc QUEUE.MANAGER.1
    A message tells you that an MQSC session has started. MQSC has no command prompt.

  7. Define a local queue called QUEUE1: 

    DEFINE QLOCAL (QUEUE1)
    A message tells you when the queue has been created.

  8. Allow the user ID that you created in step 1 to use QUEUE1: 

    SET AUTHREC PROFILE(QUEUE1) OBJTYPE(QUEUE) PRINCIPAL('non_mqm_user') AUTHADD(PUT,GET)
    where non_mqm_user is the user ID created in step 1. A message tells you when the authorisation has been set. You must also run the following command to give the user ID authority to connect: 

    SET AUTHREC OBJTYPE(QMGR) PRINCIPAL('non_mqm_user') AUTHADD(CONNECT)
    If this command is not run, a 2305 stop error is returned.

  9. Define a server-connection channel: 

    DEFINE CHANNEL (CHANNEL1) CHLTYPE (SVRCONN) TRPTYPE (TCP)
    A message tells you when the channel has been created.

  10. Allow your client channel to connect to the queue manager and run under the user ID that you created in step 1, by entering the following MQSC command: 

    SET CHLAUTH(CHANNEL1) TYPE(ADDRESSMAP) ADDRESS('client_ipaddr') MCAUSER('non_mqm_user')
    where client_ipaddr is the IP address of the client system, and non_mqm_user is the user ID created in step 1. A message tells you when the rule has been set.

  11. Define a listener: 

    DEFINE LISTENER (LISTENER1) TRPTYPE (TCP) CONTROL (QMGR) PORT (port_number)
    where port_number is the number of the port the listener is to run on. This number must be the same as the number used when defining your client-connection channel in Installing a WebSphere MQ client ; see the appropriate HP-UX and Linux sections for more information. If you omit the port parameter from the command, a default value of 1414 is used for the listener port. To specify a port other than 1414, you must include the port parameter in the command, as shown.

  12. Start the listener: 

    START LISTENER (LISTENER1)

  13. Stop MQSC by entering: 

    end
    You see some messages, followed by the command prompt.


What to do next

Follow the instructions to set up the client. See Connecting a WebSphere MQ MQI client to a queue manager, using the MQSERVER environment variable .


Connecting a WebSphere MQ MQI client to a queue manager, using the MQSERVER environment variable

When a WebSphere MQ application is run on the WebSphere MQ MQI client, it requires the name of the MQI channel, the communication type, and the address of the server to be used. Provide these parameters by defining the MQSERVER environment variable. Before you start this task, you must complete the task, Setting up the server using the command line , and save the following information:

This task describes how to connect a WebSphere MQ MQI client, by defining the MQSERVER environment variable on the client.

If you are using Windows, HP Integrity NonStop Server, UNIX or Linux systems, you can give the client access to the generated client channel definition table, amqclchl.tab instead; see Accessing client-connection channel definitions .

Alternatively, on Windows, if Active Directory support is enabled, the client discovers the client-connection information dynamically from the Active Directory.


Procedure

  1. Check the TCP/IP connection. From the client, enter one of the following commands

    • ping server-hostname

    • ping n.n.n.n

      n.n.n.n represents the network address. You can set the network address in IPv4 dotted decimal form, for example, 192.0.2.0. Alternatively, set the address in IPv6 hexadecimal form, for example 2001:0DB8:0204:acff:fe97:2c34:fde0:3485.

    If the ping command fails, correct your TCP/IP configuration.

  2. Set the MQSERVER environment variable. From the client, enter one of the following commands:

    1. On Windows: 

      SET MQSERVER=channelName/TCP/server-address(port)

    2. On UNIX and Linux, and WebSphere MQ client for HP Integrity NonStop Server OSS systems: 

      export MQSERVER=channelName/TCP/'server-address(port)'

    3. On WebSphere MQ client for HP Integrity NonStop Server Guardian systems: 

      param MQSERVER CHANNEL1/TCP/server-address(port)

    4. On IBM i: 

      ADDENVVAR ENVVAR(MQSERVER) VALUE('channelName/TCP/server-address(port)')

    Where:

    • channelName is the server-connection channel name.

    • server-address is the TCP/IP host name of the server.

    • port is the TCP/IP port number the server is listening on.

    If you do not give a port number, WebSphere MQ uses the one specified in the qm.ini file, or the client configuration file. If no value is specified in these files, WebSphere MQ uses the port number identified in the TCP/IP services file for the service name MQSeries. If an MQSeries entry in the services file does not exist, a default value of 1414 is used. It is important that the port number used by the client and the port number used by the server listener program are the same.


What to do next

Use the sample programs to test communication between the client and server; see Testing communication between a client and a server .


Verify a client installation using WebSphere MQ Explorer

You can verify a client installation using the WebSphere MQ Explorer on Windows and Linux. On the server, you create a queue manager, a local queue, a listener and a server-connection channel. On the client system you create a client-connection channel. Then from the command line you use the sample PUT and GET programs to complete the verification procedure.

To begin the verification setup, see Setting up the server using WebSphere MQ Explorer .


Set up the server using WebSphere MQ Explorer

You can use the WebSphere MQ Explorer to create a queue manager, queue and server-connection channel on Windows and Linux systems .


Procedure

  1. Create a queue manager:

    1. Open WebSphere MQ Explorer.

    2. Right-click the folder called Queue Managers, select New > Queue Manager.

    3. In the first entry field, type the queue manager name, QUEUE.MANAGER.1, and click Finish.

  2. Create a local queue:

    1. Expand the queue manager you have just created and right-click queues.

    2. Select New > Local Queue.

    3. Enter the queue name, QUEUE1, and click Finish.

  3. Define the server-connection channel:

    1. Right-click Channels.

    2. Select New > Server Connection Channel.

    3. Enter the channel name, CHANNEL1, and click Next.

    4. In the dialog navigation pane, click MCA to open the MCA page.

    5. In the MCA User ID field, enter a userid that is a member of the mqm group, typically your own.

    6. Click Finish.

  4. Run the listener.

    The listener is automatically started when the queue manager is configured. To check that the listener is running, open Listeners and look for LISTENER.TCP.


What to do next

Set up the client. See Setting up the client using WebSphere MQ Explorer .


Set up the client using WebSphere MQ Explorer

You can use WebSphere MQ Explorer to define the client-connection if you are setting up the client and server on the same workstation on a Windows or Linux system.


Procedure

  1. Select the queue manager, QUEUE.MANAGER.1

  2. Open the Channels folder, then right click Client Connections > New > Client-connection Channel...

  3. Enter the channel name, CHANNEL1, for the client connection, and click Next.

  4. Enter the queue manager name, QUEUE.MANAGER.1

  5. Enter the following string as the connection name: 

    server-address(port)
    Where:

    • server-address is the TCP/IP host name of the server

    • port is the TCP/IP port number the server is listening on

  6. Click Finish.

  7. From the command line, set the MQCHLLIB environment variable:

    • For Windows clients, enter the following command, where MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed: 

      SET MQCHLLIB=MQ_INSTALLATION_PATH\qmgrs\QUEUE!MANAGER!1\@ipcc

    • For Linux clients, enter the following command: 

      export MQCHLLIB=var/mqm/qmgrs/QUEUE!MANAGER!1/@ipcc

    The queue manager name contains . . WebSphere MQ creates the queue manager directory with the name, QUEUE!MANAGER!1


What to do next

Use the sample programs to test communication between the client and server. See Testing communication between a client and a server .


Test communication between a client and a server

On the WebSphere MQ MQI client workstation, use the amqsputc sample program to put a message on the queue at the server workstation. Use the amqsgetc sample program to get the message from the queue back to the client. Complete the previous topics in this section:

Note that WebSphere MQ object definitions are case-sensitive. Text entered as an MQSC command in lowercase is converted automatically to uppercase unless you enclose it in single quotation marks. Make sure that you type the examples exactly as shown.


Procedure

  1. On UNIX and Linux systems, change into the MQ_INSTALLATION_PATH/samp/bin directory, which contains the sample programs. For WebSphere MQ client for HP Integrity NonStop Server, change into the MQ_INSTALLATION_PATH/opt/mqm/samp/bin directory, which contains the sample programs. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed.

  2. If you are verifying an installation on a UNIX, Linux, or Windows system, you must set certain environment variables so that the installation can be used in the current shell. This step is not applicable to WebSphere MQ client for HP Integrity NonStop Server. You can set the environment variables by entering one of the following commands

    • Windows: 

      MQ_INSTALLATION_PATH\bin\setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    • UNIX and Linux: 

      . MQ_INSTALLATION_PATH/bin/setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

  3. Start the PUT program for QUEUE1 on QUEUE.MANAGER.1 by entering one of the following commands

    • Windows: 

      amqsputc QUEUE1 QUEUE.MANAGER.1

    • UNIX and Linux, and WebSphere MQ client for HP Integrity NonStop Server: 

      ./amqsputc QUEUE1 QUEUE.MANAGER.1

    If the command is successful, the following messages are displayed:

    Sample AMQSPUT0 start target queue is QUEUE1

    You might get the error, MQRC_NOT_AUTHORIZED (2035). By default, channel authentication is enabled when a queue manager is created. Channel authentication prevents privileged users accessing a queue manager as a WebSphere MQ MQI client. For verifying the installation, you can either change the MCA user ID to a non-privileged user, or disable channel authentication. To disable channel authentication run the following MQSC command: 

    ALTER QMGR CHLAUTH(DISABLED)
    When you finish the test, if you do not delete the queue manager, re-enable channel authentication: 

    ALTER QMGR CHLAUTH(ENABLED)

  4. Type some message text, then press Enter twice. The following message is displayed: 

    Sample AMQSPUT0 end
    Your message is now on the queue that is on the server queue manager.

  5. Start the GET program for QUEUE1 on QUEUE.MANAGER.1 by entering one of the following commands

    • Windows: 

      amqsgetc QUEUE1 QUEUE.MANAGER.1

    • UNIX and Linux, and WebSphere MQ client for HP Integrity NonStop Server: 

      ./amqsgetc QUEUE1 QUEUE.MANAGER.1

    The sample program starts, and your message is displayed. After a short pause (approximately 30 seconds), the sample ends and the command prompt is displayed again.

You have now successfully verified the client installation.


What to do next

  1. If your server is a Windows, UNIX, or Linux system, you must set various environment variables so that the installation can be used in the current shell. You can set the environment variables by entering one of the following commands:

    • Windows: 

      MQ_INSTALLATION_PATH\bin\setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    • UNIX and Linux systems: 

      . MQ_INSTALLATION_PATH/bin/setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

  2. On the server, stop the queue manager: 

    endmqm QUEUE.MANAGER.1

  3. On the server, delete the queue manager: 

    dltmqm QUEUE.MANAGER.1


Verify the installation of WebSphere MQ Telemetry

There are two ways to verify the installation of WebSphere MQ Telemetry. Either one or both can be used, regardless of whether WebSphere MQ Telemetry was installed as a custom installation of WebSphere MQ, or added to an existing installation of WebSphere MQ.

The two ways to verify the installation of WebSphere MQ Telemetry are:


Verify the installation of WebSphere MQ Telemetry by using WebSphere MQ Explorer

Use the Define sample configuration wizard and the MQTT client utility in WebSphere MQ Explorer to verify that the WebSphere MQ Telemetry components have installed. Also check that publish/subscribe works correctly.

The WebSphere MQ Telemetry runtime and support for WebSphere MQ Explorer must be installed. The telemetry folder is part of a queue manager. To view the telemetry folder, you must start a queue manager.

Before running the define sample configuration wizard on an existing queue manager, review the information provided by the wizard about the configuration changes that are made. The changes might have implications for the configuration of the existing queue manager. Alternatively, run the sample configuration wizard on a newly created queue manager to avoid changing any security settings.

To configure WebSphere MQ Telemetry there is a define sample configuration wizard that can be run from WebSphere MQ Explorer. The wizard runs through a series of steps, including defining and starting the telemetry (MQXR) service, setting up the default transmission queue, and configuring a telemetry channel.

If you would prefer to do this manually, see Configuring a queue manager for telemetry on Linux and AIX . For Windows, see Configuring a queue manager for telemetry on Windows .

You can open the define sample configuration wizard from the WebSphere MQ Telemetry Welcome page in WebSphere MQ Explorer. The wizard determines which steps are required based on the current configuration.

For example, the following actions might be specified by the wizard:

If telemetry is already configured for this queue manager, the link to open the wizard is replaced with static text. The text confirms that the sample configuration has been set up.

After the configuration has finished, you can use WebSphere MQ Explorer to open the MQTT client utility. Use the MQTT client utility to verify that WebSphere MQ Telemetry is set up correctly.

The following items summarize the main goals that can be achieved using the MQTT client utility:

You can find additional information within the WebSphere MQ Explorer by using the Help menu or pressing the F1 key.


Procedure

  1. Start WebSphere MQ Explorer.

    On Windows and Linux systems, you can start WebSphere MQ Explorer by using the system menu, the MQExplorer executable file, the mqexplorer command, or the strmqcfg command.

  2. Open the Welcome to MQ Telemetry page.
    • To use an existing queue manager, click on IBM WebSphere MQ\Queue Managers\qMgrName\Telemetry folder to open the Welcome to MQ Telemetry page.

    • If, for the reasons mentioned, you decide to use a new queue manager,

      1. Click Queue Managers > New > Queue Manager.

      2. Type MQTTVerification as the Queue manager name > Next > Next > Next.

      3. Change the default port in Listen on port number, if the port is in use > Finish.

      4. When the queue manager starts, click on IBM WebSphere MQ\Queue Managers\MQTTVerification\Telemetry folder to open the Welcome to MQ Telemetry page.

  3. From the Welcome to MQ Telemetry page in WebSphere MQ Explorer, click Define sample configuration.

    If this link is not present, and instead you see the text, The sample configuration has been set up for this queue manager , then telemetry has already been configured. Proceed to step 6 .

    If you clicked Define sample configuration, the page opens, and lists actions that are to be performed as part of the sample configuration.

  4. Leave Launch MQTT client utility checked, if you want to automatically start the MQTT client utility. The check box is selected by default.

  5. Click Finish.

  6. Click Connect.

    In the MQTT client utility panel, ensure that the host and port names are correct.

    If you did not automatically start the MQTT client utility panel in step 4, you can start it either by using a direct link from the Welcome to MQ Telemetry panel, or by right-clicking a NON-SSL channel, which allows you to control the channel it runs on.

    The client history records a Connected event.

  7. Click Subscribe.

    The client history records a Subscribed event.

  8. Click Publish.

    The client history records a Published and Received event.

If the publish/subscribe finishes successfully, the WebSphere MQ Telemetry installation is verified.

If you encounter problems during the installation process, view the error log:


Verify the installation of WebSphere MQ Telemetry using the command line

Follow these instructions to run scripts to verify that the WebSphere MQ Telemetry components have installed, and are able to publish and subscribe.

The telemetry (MQXR) service must be started to run the sample programs. The user ID must be a member of the mqm group. You must run the SampleMQM script first, followed by the MQTTV3Sample script to perform a publish and subscribe. The CleanupMQM sample script can be run to delete the queue manager created by the SampleMQM script. There are two commands to run the MQTTV3Sample script. These commands are shown in the Procedure section of this topic. The commands must be entered into different command lines or shell windows.

The SampleMQM script creates and uses a queue manager called MQXR_SAMPLE_QM. Therefore, do not run unaltered on a system with a MQXR_SAMPLE_QM queue manager. Any changes made might have implications for the configuration of the existing queue manager.

To perform verification on a server or device without a GUI, scripts are provided in the samples directory. The SampleMQM script performs the required steps to configure WebSphere MQ Telemetry. The SampleMQM script runs through a series of steps, including defining and starting the telemetry (MQXR) service, setting up the default transmission queue, and configuring a telemetry channel.

For information about performing this manually, see Configuring a queue manager for telemetry on Linux and AIX , or Configuring a queue manager for telemetry on Windows .

The MQTTV3Sample script can then be run to validate the basic or custom WebSphere MQ Telemetry configuration by connecting, subscribing to topics, and publishing messages.

The following items summarize the main goals that can be achieved using the verification scripts provided.


Procedure

  1. Type the following command on a command line to run the SampleMQM script

    • On Windows, the command to run the SampleMQM script is as follows: 

      MQ_INSTALLATION_PATH\mqxr\samples\SampleMQM.bat

    • On Linux the command to run the SampleMQM script is as follows: 

      MQ_INSTALLATION_PATH/mqxr/samples/SampleMQM.sh

    where MQ_INSTALLATION_PATH is the location in which WebSphere MQ is installed.

    A queue manager called MQXR_SAMPLE_QM is created.

  2. Type the following command to run the first part of the MQTTV3Sample script;

    • On Windows, on one command line, type the following command; 

      MQ_INSTALLATION_PATH\mqxr\samples\RunMQTTV3Sample.bat -a subscribe

    • On AIX and Linux, in one shell window, type the following command; 

      MQ_INSTALLATION_PATH/mqxr/samples/RunMQTTV3Sample.sh -a subscribe

  3. Type the following command to run second part of the MQTTV3Sample script;

    • On Windows, on another command line, type the following command; 

      MQ_INSTALLATION_PATH\mqxr\samples\RunMQTTV3Sample.bat -m "Hello from an MQTT v3 application"

    • On AIX and Linux, in another shell window, type the following command; 

      MQ_INSTALLATION_PATH/mqxr/samples/RunMQTTV3Sample.sh -m "Hello from an MQTT v3 application"

  4. To remove the queue manager created by the SampleMQM script, you can run the CleanupMQM script using the following command;

    • On Windows, type the following command; 

      MQ_INSTALLATION_PATH\mqxr\samples\CleanupMQM.bat

    • On AIX and Linux in another shell window, type the following command; 

      MQ_INSTALLATION_PATH/mqxr/samples/CleanupMQM.sh

The Hello from an MQTT v3 application message, that you typed into the second command line or window, is published by that application, and received by the application in the first window. The application in the first window shows it on the screen.

Press Enter in the first window to end the subscribing application.

If the scripts finish and messages can be sent and received, the WebSphere MQ Telemetry installation is verified.

If you encounter any problems during the installation process, see Troubleshooting . Alternatively, you can view the Error Log.

where queue manager name is the name of the queue manager.


Uninstall WebSphere MQ components

Information to help you uninstall components of WebSphere MQ.

Refer to the following topics to uninstall components of WebSphere MQ:


Uninstall

Uninstall WebSphere MQ on AIX

On AIX, you can uninstall theWebSphere MQ server or client using the System Management Interface Tool (SMIT) or the installp command. If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see AIX: Restoring the previous maintenance level on WebSphere MQ version 7.5 .


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. Uninstall WebSphere MQ using either installp or smit. If WebSphere MQ was installed in a non-default location, you must use installp to uninstall.
    • Uninstall using installp by entering one of the following commands:

      • For an installation in the default location /usr/mqm 

        installp -u mqm

      • For an installation in a non-default location: 

        installp -R usil -u mqm
        where usil is the path of the User Specified Install Location (USIL) specified when the product was installed.

    • Uninstall using smit:

      1. Select the required smit window using the following sequence: 

         Software Installation and Maintenance     Software Maintenance and Utilities
      Remove Installed Software

      2. List the software in the SOFTWARE name field:

        1. Enter .

        2. Press F4

      3. Select the file sets to uninstall from the list (those beginning with mqm), and press Enter. There is an option at this stage to do a preview. Leave the option set to the default value of Yes to preview the file sets you are uninstalling, or select No to not preview these file sets.

      4. Press Enter on the Remove Installed Software panel, it asks whether you are sure, press Enter.

You might find that certain files remain after uninstalling WebSphere MQ. For example, mqinst.ini remains after uninstallation. This is to enable information to be reused by subsequent installs. See below for more information.


What to do next


Uninstall WebSphere MQ on HP Integrity NonStop Server

On HP Integrity NonStop Server systems, you can uninstall the WebSphere MQ client by using the rm command.


Procedure

  1. Stop all WebSphere MQ applications that are associated with the installation you are uninstalling.

  2. Log in to the OSS as the user ID that owns the installation.

  3. Use the OSS rm command to delete the files from the Guardian subvolume used by the installation. For example, use the following command: 

    rm -rf <mqpath>/opt/mqm/bin/G/*

  4. Use the OSS rm command to delete the OSS directory trees for the installation. For example, use the following command: 

    rm -rf <mqpath>


Uninstall WebSphere MQ on HP-UX

On HP-UX, you can uninstall theWebSphere MQ server or client using the swremove command. If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see HP-UX: Restoring the previous maintenance level on WebSphere MQ version 7.5 .


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. Uninstall WebSphere MQ using swremove

    • To uninstall all WebSphere MQ components, enter the following command: 

      swremove MQSERIES,l=MQ_INSTALLATION_PATH
      where MQ_INSTALLATION_PATH is the path where WebSphere MQ is installed.

    • To uninstall selected WebSphere MQ components, enter the following command: 

      swremove componentname,l=MQ_INSTALLATION_PATH
      where componentname is the name of the component to uninstall, and MQ_INSTALLATION_PATH is the path where WebSphere MQ is installed.

      For example, to uninstall the client and the telemetry client components, from an installation in /opt/myLocation, enter the following command: 

      swremove MQSERIES.MQM-TXCLIENT,l=/opt/myLocation MQSERIES.MQM-CL-HPUX,l=/opt/myLocation

You might find that certain files remain after uninstalling WebSphere MQ. For example, mqinst.ini remains after uninstallation. This is to enable information to be reused by subsequent installs. See below for more information.


What to do next


Uninstall WebSphere MQ on Linux

On Linux, you can uninstall theWebSphere MQ server or client using the rpm command. If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see Linux: Restoring the previous maintenance level on WebSphere MQ version 7.5 .


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv -s
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. Uninstall WebSphere MQ using the rpm command:

    1. On a system with a single installation:

      1. Find out the names of the packages (components) currently installed on your system,: 

        rpm -qa | grep MQSeries

      2. Remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components enter the following command: 

        rpm -ev MQSeriesRuntime MQSeriesServer MQSeriesSDK

    2. On a system with multiple installations:

      1. Find out the names of the packages (components) currently installed on your system,: 

        rpm -qa | grep suffix
        where suffix is the unique name given to the packages when crtmqpkg was run at installation time. suffix is included in each of the package names that belong to a particular installation.

      2. Remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components for an installation with the suffix MQ71, enter the following command: 

        rpm -ev MQSeriesRuntime-MQ71 MQSeriesServer-MQ71 MQSeriesSDK-MQ71

You might find that certain files remain after uninstalling WebSphere MQ. For example, mqinst.ini remains after uninstallation. This is to enable information to be reused by subsequent installs. See below for more information.


What to do next


Uninstall WebSphere MQ on Solaris

On Solaris, you can uninstall theWebSphere MQ server or client using the pkgrm command. If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see Solaris: Restoring the previous maintenance level on WebSphere MQ version 7.5 .


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. Uninstall WebSphere MQ using pkgrm:

    1. On a system with a single installation, enter the following command: 

      pkgrm mqm

    2. On a system with multiple installations: 

      pkgrm mqm-suffix
      where suffix is the unique name given to the packages when crtmqpkg was run at installation time. suffix is included in each of the package names that belong to a particular installation. The first installation on the system does not have a suffix, and is uninstalled using the same method as for a single installation.

    If a package has a dependency on mqm, pkgrm returns the name of the package. Uninstall the dependent packages first.

You might find that certain files remain after uninstalling WebSphere MQ. For example, mqinst.ini remains after uninstallation. This is to enable information to be reused by subsequent installs. See below for more information.


What to do next


Uninstall WebSphere MQ on Windows systems

You can uninstall the WebSphere MQ MQI clients and servers on Windows systems by using the control panel, the command line (msiexec), MQParms, or by using the installation media, in which case you can optionally remove queue managers as well.


Procedure

The first part of the procedure ensures that there are no WebSphere MQ programs or processes running:

  1. If you are running WebSphere MQ with the Microsoft Cluster Service (MSCS), remove the queue managers from MSCS control before uninstalling WebSphere MQ. Perform the following steps for each queue manager currently under MSCS control :

    1. Take the queue manager resource offline.

    2. Destroy the resource instance.

    3. Migrate the queue manager files back from shared drives. This step is shown as optional in Removing a queue manager from MSCS control . However, it is mandatory in this case.

  2. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  3. Close all WebSphere MQ Managed File Transfer agents. If you have a WebSphere MQ Managed File Transfer agent running, close it by using the fteStopAgent command; see fteStopAgent (stop a WebSphere MQ Managed File Transfer agent) .

  4. For a server installation, end all WebSphere MQ activity:

    1. Log in as a user in the group mqm.

    2. Stop all running queue managers and listeners by using the WebSphere MQ Explorer, ors:

      1. Set up your environment to work with the installation you want to uninstall: 

        MQ_INSTALLATION_PATH\bin\setmqenv -s
        where MQ_INSTALLATION_PATH is the location where WebSphere MQ is installed.

      2. For each queue manager, enter the following command to stop the queue manager: 

        endmqm queue_manager_name

      3. For each queue manager, enter the following command to stop any listeners associated with the queue manager: 

        endmqlsr -m queue_manager_name

  5. Stop WebSphere MQ. To do this right-click the WebSphere MQ icon in the system tray, then select Stop WebSphere MQ.

  6. Close all WebSphere MQ windows.

  7. Stop any monitoring service.

When all processaes associated with WebSphere MQ are no longer running, you can uninstall WebSphere MQ:

  1. Uninstall WebSphere MQ by using one of the following methods

    • Use the Windows Control Panel. This process is described in: Uninstalling WebSphere MQ by using the control panel . This method does not remove the queue manager data.

    • Use the command line by running the msiexec command as described in: Uninstalling WebSphere MQ by using the command line . This method does not remove the queue manager data.

    • Use the appropriate parameters with MQParms. This process is described in Uninstalling WebSphere MQ by using MQParms . This method does not remove the queue manager data.

    • Use the installation media, by selecting the appropriate option as described in: Uninstalling WebSphere MQ on Windows by using the installation media . The option to remove queue manager data is displayed in the Removing Server feature panel, if appropriate.

    If you have to cancel the uninstall process before it is finished, you might have to reconfigure WebSphere MQ with the Prepare WebSphere MQ wizard because the rollback of the deletion of the WebSphere MQ service is unable to set the service's user account password. Use the following command to reconfigure WebSphere MQ: 

    MQ_INSTALLATION_PATH\bin\amqmjpse.exe -r
    For more information about the Prepare WebSphere MQ wizard, see Configuring WebSphere MQ with the Prepare WebSphere MQ wizard .

  2. Check the Windows event log and restart the system if necessary. If event ID 10005 is written to the Windows event log, you must restart the system to complete the uninstall.

  3. Optional: If you are uninstalling the last or only installation of WebSphere MQ, you can remove all the information about previous installations that is retained on the system, if you want to.

    Two registry values remain after uninstallation:

    • 32 bit systems:

      • My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ\LogDefaultPath

      • My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ\WorkPath

    • 64 bit systems:

      • My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\WebSphere MQ\LogDefaultPath

      • My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\WebSphere MQ\WorkPath

    Data folders are also left intact, located at MQ_DATA_PATH\Config, where MQ_DATA_PATH is the location of the WebSphere MQ data directory.

    If a client is installed on a system where the LogDefaultPath registry value remains from a previous server install, a client installation will attempt to create this directory if it does not already exist. If this behavior is not wanted, remove the LogDefaultPath registry value before installing the client.


Uninstall WebSphere MQ by using the control panel

You can uninstall WebSphere MQ by using the control panel to remove all currently installed features. Start the uninstalling process by following the steps described in Uninstalling WebSphere MQ on Windows systems .

If you no longer require the queue managers that are on the system, delete them by using the WebSphere MQ Explorer or the dltmqm command.


Procedure

  1. From the Windows taskbar, open the control panel by clicking Start > Settings > Control Panel, or Start > Control Panel.

  2. Click Add/Remove Programs, or Programs and Features.

  3. Click IBM WebSphere MQ (installation_name), where installation_name is the name of the installation you want to remove.

  4. Click Remove or Uninstall and click Yes to confirm. If User Account Control (UAC) is enabled, accept the Windows prompt to allow the uninstallation to run as elevated. The program then begins and runs to completion.


What to do next

Complete the steps that you started in Uninstalling WebSphere MQ on Windows systems .


Uninstall WebSphere MQ by using the command line

You can uninstall WebSphere MQ by running the msiexec command from the command line to remove all currently installed features. Start the uninstalling process by following the steps described in Uninstalling WebSphere MQ on Windows systems .

If you no longer require the queue managers that are on the system, delete them by using the WebSphere MQ Explorer or the dltmqm command. To start uninstalling, use the msiexec command.

If you are running WebSphere MQ on Windows with User Account Control (UAC) enabled, you must invoke the silent uninstallation from an elevated command prompt. Elevate a command prompt by using a right-click to start the command prompt and choose Run as administrator.

In all of the examples of commands shown, the variable names used are as follows:


Procedure

To uninstall all WebSphere MQ features, use one of the following methods

After the command is entered, the command prompt immediately reappears and WebSphere MQ is uninstalled as a background process. If you entered parameters to produce a log, check this file to see how the uninstallation is progressing. If the uninstallation finishes successfully, you see the message Removal completed successfully in the log file.


What to do next

Complete the steps that you started in Uninstalling WebSphere MQ on Windows systems .


Uninstall WebSphere MQ by using MQParms

You can uninstall WebSphere MQ by running the MQParms command from the command line to remove all currently installed features. Start the uninstalling process by following the steps described in Uninstalling WebSphere MQ on Windows systems .


Procedure

  1. Follow the instructions on the MQParms installation pages to uninstall WebSphere MQ non-interactively. See: Using the MQParms command .

    1. Set the ADDLOCAL parameter to empty (ADDLOCAL="").

    2. Set the REMOVE parameter to "ALL" (REMOVE="ALL").

  2. If you have multiple versions of WebSphere MQ installed on your system, specify the product code that identifies the installation you want to remove. Type the following command: 

    MQParms.exe parameter_file /i "{product_code}"
    where

    • parameter_file is the file that contains the required parameter values. If this file is not in the same folder as MQParms.exe, specify the full path and file name. If you do not specify a parameter file, the default is MQParms.ini.

    • product_code is the value shown for MSIProdCode in the output of the following command: 

      dspmqinst -n installation_name
      where installation_name is the name of the installation you want to remove. An example of a product code is {0730749B-080D-4A2E-B63D-85CF09AE0EF0}.


What to do next

Complete the steps that you started in Uninstalling WebSphere MQ on Windows systems .


Uninstall WebSphere MQ on Windows by using the installation media

You can uninstall WebSphere MQ by using the installation media to remove all currently installed features and optionally remove existing queue managers and their data. Start the uninstalling process by following the steps described in Uninstalling WebSphere MQ on Windows systems .


Procedure

  1. Insert the WebSphere MQ for Windows Server DVD into the DVD drive.

  2. Start the installation process.
    • If autorun is enabled, the installation process starts automatically.

    • If autorun is not enabled, double-click the Setup icon in the root folder of the DVD to start the installation process.

    The WebSphere MQ Installation Launchpad window opens.

  3. Click WebSphere MQ Installation.

  4. Click Launch IBM WebSphere MQ Installer and click Next until the WebSphere MQ Program Maintenance panel is displayed with a welcome message. If this panel is not displayed, WebSphere MQ for Windows is not currently installed.

  5. Click Maintain or upgrade an existing instance and if there is more than one installation of WebSphere MQ on the system, select which installation you want to remove. Click Next and in the Program Maintenance panel, click Remove, then Next.

  6. If you are uninstalling the last or only server, and there are any queue managers on the system, the Removing Server feature panel is shown. Click one of the following options:

    • Keep: keep existing queue managers and their objects.

    • Remove: remove existing queue managers and their objects.

    Click Next. The Remove WebSphere MQ panel is displayed, with a summary of the installation to be removed.

  7. Click Remove to continue. If there are any messages that state that locked files are found, ensure that there are no WebSphere MQ programs running; see Uninstalling WebSphere MQ on Windows systems . When WebSphere MQ has been uninstalled, a message indicates completion.

  8. Click Finish.


What to do next

Complete the steps that you started in Uninstalling WebSphere MQ on Windows systems .


Uninstall WebSphere MQ Telemetry components

Remove WebSphere MQ Telemetry components from your computer.

Check that your user ID has the following authority to complete uninstallation tasks:


Procedure


Uninstall WebSphere MQ Advanced Message Security

Information provided guides you through the uninstallation process of IBM WebSphere MQ Advanced Message Security component.


Uninstall on AIX

On AIX platforms, you can remove IBM WebSphere MQ Advanced Message Security component either using SMIT or the command line.


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where. MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. UninstallWebSphere MQ AMS component using either installp or smit. If WebSphere MQ AMS component was installed in a non-default location, you must use installp to uninstall.
    • Uninstall using installp by entering one of the following commands:

      • For an installation in the default location /usr/mqm 

        installp -u mqm.ams.rte

      • For an installation in a non-default location: 

        installp -R usil -u mqm.ams.rte
        where usil is the path of the User Specified Install Location (USIL) specified when the product was installed.

    • Uninstall using smit:

      1. Select the required smit window using the following sequence: 

         Software Installation and Maintenance     Software Maintenance and Utilities
      Remove Installed Software

      2. List the software in the SOFTWARE name field:

        1. Enter .

        2. Press F4

      3. Select the file sets to uninstall from the list (those beginning with mqm), and press Enter. There is an option at this stage to do a preview. Leave the option set to the default value of Yes to preview the file sets you are uninstalling, or select No to not preview these file sets.

      4. Press Enter on the Remove Installed Software panel, it asks whether you are sure, press Enter.

The WebSphere MQ Advanced Message Security component has been uninstalled.


Uninstall on HP-UX

Use the swremove command to remove IBM WebSphere MQ Advanced Message Security component on HP-UX platforms.


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where. MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log on as root.

  4. Run the following command: 

    swremove MQSERIES.MQM-AMS

The WebSphere MQ Advanced Message Security component has been uninstalled.


Uninstall on Linux

Use the rpm command to remove IBM WebSphere MQ Advanced Message Security component on Linux platforms.


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where. MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq -o installation

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log in as root.

  4. Run the following command: 

    rpm -e <package_name>
    where <package_name> is one of the following:

    • MQSeriesAMS-7.5.0-0.i386.rpm

    • MQSeriesAMS-7.5.0-0.x86_64.rpm

    • MQSeriesAMS-7.5.0-0.ppc.rpm

    • MQSeriesAMS-7.5.0-0.s390.rpm

The WebSphere MQ Advanced Message Security component has been uninstalled.


Uninstall on Solaris

Use the pkgrm to uninstall IBM WebSphere MQ Advanced Message Security component on Solaris platforms.


Procedure

  1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.

  2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:

    1. Log in as a user in the group mqm.

    2. Set up your environment to work with the installation you want to uninstall. Enter the following command: 

      . MQ_INSTALLATION_PATH/bin/setmqenv
      where . MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.

    3. Display the state of all queue managers on the system. Enter the following command: 

      dspmq

    4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager: 

      endmqm QMgrName

    5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager: 

      endmqlsr -m QMgrName

  3. Log on as root.

  4. Run the following command: 

    pkgrm mqams

The WebSphere MQ Advanced Message Security component has been uninstalled.


Uninstall on Windows

You can uninstall IBM WebSphere MQ Advanced Message Security component using the GUI uninstallation wizard, or a command-line interface.


Use the installation wizard

Procedure

  1. Insert the WebSphere MQ Server DVD into the DVD-ROM drive.

  2. If autorun is enabled, the installation process starts.

    Otherwise, double-click the Setup icon in the root folder of the DVD to start the installation process.

    The WebSphere MQ Installation Launchpad window is displayed.

  3. Click the WebSphere MQ Installation.

  4. Click Launch IBM WebSphere MQ Installer. Click Next until the WebSphere MQ Program Maintenance panel is displayed with a welcome message.

    If this panel is not displayed, WebSphere MQ for Windows, Version 7.5 is not installed on this machine. When presented with the option, select to remove/maintain or upgrade.

  5. Select Maintain or upgrade an existing instance, then click Next.

  6. If there are any existing queue managers, the Removing Server feature panel is displayed.

    Click one of the following options, then click Next:

    • Keep - keep existing queue managers and their objects.
    • Remove - remove existing queue managers and their objects.

    The Program Maintenance panel is displayed, with a summary of the installation to be removed.

  7. Click Modify and click Next.

  8. On the list of available WebSphere MQ features, click Advanced Message Security, select Do not install this feature (remove if already intalled) , and click Next. The Ready to modify WebSphere MQ panel appears with the summary of your changes.

  9. Click Modify and Next on the following panel to continue.