This section contains instructions on how to install the WebSphere MQ client from a LAN, and how to install the WebSphere MQ client using System Management Server (SMS).
There are two ways to put WebSphere MQ installation files on a LAN server for easier access:
md m:\instmqc
xcopy e:\*.* m:\instmqc /e
\\servername\installation_folder\Windows\setup.exewhere servername is the name of the server and installation_folder is the full path of the installation folder.
Alternatively:
To install the extended transactional function from a LAN server, you must first make the installation files accessible on a target system. There are two ways of doing this:
md m:\instmqc
If autorun is enabled, the Select Setup Language window opens. Click Cancel to close this window.
xcopy e:\*.* m:\instmqc\ /eAlternatively, if you want to copy only the directories required for installing on Windows systems, enter the following commands at a command prompt:
xcopy e:\Windows\*.* m:\instmqc\Windows\ /e xcopy e:\Readmes\Windows\*.* m:\instmqc\Readmes\Windows\ /e xcopy e:\Licenses\Windows\*.* m:\instmqc\Licenses\Windows\ /e
You can now use the following procedure to install the extended transactional function:
\\server_name\share_name\Windows\setup.exewhere server_name is the name of the LAN server and share_name is the share name of the CD-ROM drive or installation folder on the LAN server.
Alternatively:
The Select Setup Language window opens.
WebSphere MQ for Windows client is installed using the Microsoft(R) Installer (MSI). You can invoke MSI directly, without using setup.exe.
This means that you can install WebSphere MQ on a machine without interaction. This process is called unattended (or silent) installation, and is particularly useful for installing WebSphere MQ over a network on a remote machine, because you can install from a shared drive on a LAN server.
To do this, you can invoke MSI with a parameter that calls a response file. A response file is an ASCII text file that contains the parameter values you want to set for the installation.
The machine on which you want to install must be able to share the WebSphere MQ Server CD, or a copy of the files on it, and you must be able to execute a command on that machine.
To invoke a silent installation using a response file, you use the Msiexec command.
The response file is an ASCII text file, with a format similar to a Windows .ini file, that contains the stanza [Response]. This stanza contains parameters that the Msiexec command can use, in the form of PROPERTY=value pairs. The Msiexec command ignores any other stanzas in the file. An example response file, Response.ini, is supplied with WebSphere MQ. This file contains default installation parameters.
There are three ways to create a response file for installation:
In the response file, all text is in English, and comments begin with a ; character.
To invoke a typical silent installation, enter the following command at a command line:
Msiexec /i "path\MSI\IBM WebSphere MQ.msi" /q
TRANSFORMS=:1033
where:
TRANSFORMS=:1033 specifies that the installation is in US English. For further information about installing in different national languages, see WebSphere MQ LotusScript Extension.
You can also specify PROPERTY=value pairs on the command line (the property must be in upper case), for example:
Msiexec /i "path\MSI\IBM WebSphere MQ.msi" /q ADDLOCAL="Client""
TRANSFORMS=:1033 AGREETOLICENSE="yes"
ADDLOCAL="Client,Toolkit"
See WebSphere MQ for Windows, V6.0 Quick Beginnings for details of the features that can be values for the ADDLOCAL and REMOVE properties.
Feature Name | Description |
---|---|
Client | The WebSphere MQ for Windows client. |
Toolkit | Sample WebSphere MQ program source and sample executable code. |
An example of a typical response file is:
[Response] PGMFOLDER="c:\mqm" DATFOLDER="c:\mqm\data" AGREETOLICENSE="yes" ADDLOCAL="Client" REMOVE="Toolkit"
The extended transactional function is installed using the Microsoft Windows Installer (MSI). You can invoke MSI directly, without using setup.exe. This means that you can install the extended transactional function on a system without any interaction. This process is called unattended, or silent, installation.
To invoke an unattended installation, insert the WebSphere MQ Extended Transactional Clients CD-ROM into the CD-ROM drive and enter the following command at a command prompt:
msiexec /i "path\MSI\IBM WebSphere MQ Extended Transactional Client.msi" /q
TRANSFORMS=:1033 AGREETOLICENSE="yes"
where /q requests an unattended installation.
TRANSFORMS=:1033 specifies that the installation language is US English. For more information about installing in other national languages, see WebSphere MQ for Windows, V6.0 Quick Beginnings.
AGREETOLICENSE="yes" means that you have read the licence agreement and accept its terms.
You cannot use a response file.
WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). It is possible to install WebSphere MQ by invoking MSI directly, without using setup.exe. You can use this process for more complex unattended (or silent) installation, or for interactive installation, from a command line.
You can use the Msiexec command with command line parameters to invoke installation or uninstallation. At a command line, enter the following command, followed by the parameters you require:
Msiexec
Table 6 shows the parameters you can use. For a silent installation, this must include the /q or /qn parameter.
A typical example of an Msiexec command is:
Msiexec /i "path\MSI\IBM WebSphere MQ.msi" /l*v c:\install.log /m mif_file TRANSFORMS=":1033" ADDLOCAL="Client" REMOVE=""
Table 7 and Table 8 show the parameters that you can enter as property=value pairs on the Msiexec command line (defaults are shown in bold). Note that:
Parameter | Options | Description |
---|---|---|
/a | Package | Installs a product on the network using administrative installation, that is, installs a source image of the application onto the network that is similar to a source image on a CD-ROM. |
/i | Package|ProductCode | Installs or configures a product using the specified
.msi file.
The WebSphere(R) MQ Windows Installer package is IBM(R) WebSphere MQ.msi. |
/j |
[u|m]Package| [u|m]Package /t Transform List| [u|m]Package /g LanguageID |
Advertises the product.
This option ignores any property values entered on the command line.
|
/l |
[i|w|e|a|r|u|c|m|o|p |v|+|!]Logfile |
Specifies path to log file, with flags to set which
information to log.
|
/m | filename | Generates a Microsoft System Management Server (SMS)
status .mif file.
Must be used with either the install (/i), remove (/x), administrative installation (/a), or reinstall (/f) options. The ISMIF32.DLL is installed as part of SMS and must be on the path. The fields of the status .mif file are filled with the following information:
|
/q | n|b|r|f | Sets the level of user interface displayed during
the install.
|
/x | Package|ProductCode | Uninstalls the product. |
Note:
|
Property | Values | Meaning |
---|---|---|
USEINI | path\file_name | Use the specified response file. See Using Msiexec with a response file. |
SAVEINI | path\file_name | Generate a response file during installation. The file will contain those parameters selected for this installation that a user could 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 machine (the default). |
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 | Not used for a silent installation.
If the installation is not silent, for any other value (including null), if the command line or response file specifies parameters to install features, a dialog is displayed. This dialog prompts the user to accept the preselected options, or review and possibly change them. For other types of installation, when set to 0 or no, suppresses display of the dialog. |
AGREETOLICENSE | yes | Accept the terms of the license. For a silent installation,
this must be set to yes.
If the installation is not silent, this parameter is ignored. |
ADDLOCAL | feature, feature, ...|All|"" | A comma-separated list of features to install locally.1
All installs all features "" installs the typical features. If you do not want a feature use REMOVE="feature name" |
REMOVE | feature, feature, ...|All|"" | A comma-separated list of features to remove.1
All uninstalls all features "" uninstalls no features (the default). |
HIGHCONTRAST | 0|no|"" | 0 or no. Do not set high-contrast mode for the installation.
"". (The default) Set high-contrast mode for the installation if Windows 2000 or Windows XP high-contrast mode is set or if WebSphere MQ high-contrast mode is set. Anything else. Set high-contrast mode for the installation. |
|
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 WebSphere MQ client CD-ROM. These files are also embedded in the WebSphere MQ Windows Installer package, 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
The : (colon) character means use the embedded transform. Otherwise, you must specify the full path and file name of the transform file, for example: TRANSFORMS=D:\Msi\1033.mst
Table 9 shows the supplied transform files, the resulting language, and the numerical value to use in the Msiexec command line.
You can also specify the required language by using the MQPLANGUAGE property with the MQParms command. See Table 7.
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 |
You can use the Msiexec command with a parameter that calls a response file, as described in Unattended (silent) installation. The response file contains the parameters that a user normally specifies during an interactive installation.
You can combine the Msiexec command line parameters described in Using Msiexec with command line parameters with the response file to invoke a complex installation or uninstallation. This could be silent or interactive. For a silent installation, this must include the /q or /qn parameter.
To invoke the Msiexec command using a response file, enter the following command at a command line:
Msiexec [parameters] USEINI="response_file"
where:
If a parameter is specified both on the command line and in the response file, the setting on the command line takes precedence.
For example:
Msiexec /i "path\MSI\IBM WebSphere MQ.msi" /l*v c:\install.log /q AGREETOLICENSE="yes" USEINI="c:\MyResponseFile.ini"
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.
For a silent installation, this must include the /q or /qn parameter, either on the command line, or in the [MSI] stanza of the parameter file.
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.
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:
MQParms [parameter_file] [parameters]where:
A typical example of an MQParms command is: MQParms MyParams.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, WebSphere MQ.msi. That is, it generates the following part of the command line: /i current_folder\MSI\IBM WebSphere MQ.msi
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 stanza in the file:
The properties that you can set in this stanza are listed in Table 6, Table 7, Table 8, and Table 10.
MQParms ignores any other stanzas in the file.
In the [MSI] stanza, the properties can be in command line format (for example, /q) or property=value format.
Some properties can take more than one value, for example: ADDLOCAL="Client,Toolkit"
To clear a property, set its value to an empty string, for example: REMOVE=""
You can enter parameters in command line format (for example, /q) and in property=value format (for example, ADDLOCAL="Client"). Refer to Table 8, Table 6, and Table 7 for the properties used to install WebSphere MQ.
Table 10 shows additional properties in the stanza that affect how the MQParms command runs, but that do not affect the installation.
A typical example of a parameter file is:
[MSI] MQPLANGUAGE=1033 MQPLOG=%temp%\MQParms.log MQPSMS=1 ADDLOCAL=Client /m miffile REMOVE="" /l*v c:\install.log
Property | Values | Description |
---|---|---|
MQPLOG | path|file_name | MQParms generates a text log file with the specified name and location. |
MQPLANGUAGE |
system|user| transform_value |
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 9. |
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. |
WebSphere MQ is supplied with two sample definition files to create a System Management Server (SMS) Package (these can be found on the WebSphere MQ server CD). These are:
You will need to update the CommandLine parameter supplied in the definition files by stating the path to where you have the file IBM WebSphere MQ.msi. This file is supplied on the WebSphere MQ server CD by going to MSI\IBM WebSphere MQ.msi.
Please refer to the Microsoft System Management Server documentation for the version of SMS you are using to get full information on how to create and run a job.
Once the Package has been created, an SMS job can be configured to install WebSphere MQ.
You must be logged onto the target machine with Administrator authority to install WebSphere MQ.
To install the extended transactional client, proceed as above, but using the WebSphere MQ Extended Transactional Clients CD.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
amq2513 |