Home

 

Other methods of installing the WebSphere MQ client

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).

 

Installing from a LAN

There are two ways to put WebSphere MQ installation files on a LAN server for easier access:

• We can make the drive, into which the WebSphere MQ Client CD is inserted, shareable.

• We can copy the installation files from the CD to a server. To do this, use the following steps:

  1. Create a folder on the LAN server to store the installation files. For example:

     md m:\instmqc

  2. Load WebSphere MQ Client CD 5. If autorun is enabled, the WebSphere MQ language_selection window is displayed. Select Cancel to close this window.

  3. Copy the entire CD to the installation folder. For example:

     xcopy e:\*.* m:\instmqc /e

  4. Give all licensed users access to the folder that now contains the CD image (in this example, the

     m: drive).

  5. From a command prompt on the target machine, type the following:

     \\servername\installation_folder\Windows\setup.exe

     where servername is the name of the server and installation_folder is the full path of the installation folder.

     Alternatively:

     1. Map the shared resource to a drive letter. We can use the net use command, or the Windows Explorer.

     2. Change to the installation folder.

     3. Type

        setup, then press Enter.

  6. Follow the prompts.

 

Installing the extended transactional client from a LAN server

To install the extended transactional function from a LAN server, first make the installation files accessible on a target system. There are two ways of doing this:

• On the LAN server, create a share name for the drive into which the WebSphere MQ Extended Transactional Clients CD-ROM is inserted. Give all licensed users access to drive.

• Copy the installation files from the CD-ROM to a folder on the LAN server and make the folder shareable. To do this, use the following procedure:

  1. Create a folder on the LAN server to store the installation files. For example, enter the following command at a command prompt:

     md m:\instmqc

  2. Insert the WebSphere MQ Extended Transactional Clients CD-ROM into the CD-ROM drive.

     If autorun is enabled, the Select Setup Language window opens. Click Cancel to close this window.

  3. Copy the contents of the CD-ROM to the installation folder. For example, enter the following command at a command prompt:

     xcopy e:\*.* m:\instmqc\ /e

     Alternatively, 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  

  4. Create a share name for the installation folder and give all licensed users access to the folder.

We can now use the following procedure to install the extended transactional function:

1. From a command prompt on a target system, enter the following command:

   \\server_name\share_name\Windows\setup.exe

   where 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:

   1. Map \\server_name\share_name to a drive letter using the net use command or Windows Explorer.

   2. At a command prompt, change to the drive letter, and then to the Windows directory within the drive.

   3. Type

      setup, and press Enter.

   The Select Setup Language window opens.

2. Follow the procedure in Installing the extended transactional function from step 2 to the end.

 

Unattended (silent) installation

WebSphere MQ for Windows client is installed using the Microsoft Installer (MSI). We can invoke MSI directly, without using setup.exe.

This means that we 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, we 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 be able to execute a command on that machine.

Notes:

1. The response file you use to install WebSphere MQ for Windows using the WebSphere MQ Client CD is not the same as the one used with earlier non-MSI versions of MQSeries. For details about the response file you use with WebSphere MQ Client CD, see Unattended (silent) installation.

2. There are several other methods to invoke MSI without setup.exe. For details, see Advanced installation methods.

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:

• Copy and edit the file Response.ini that is supplied on WebSphere MQ Client CD 5, using an ASCII file editor.

• Create your own response file using an ASCII file editor.

• Use an advanced method to invoke an installation and specify the SAVEINI property (and optionally, the ONLYINI property) to generate a response file that contains the same installation options. For more information, see WebSphere MQ for Windows, V6.0 Quick Beginnings.

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

Invoking a silent installation

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:

/q

Specifies a silent installation.

TRANSFORMS=:1033 specifies that the installation is in US English. For further information about installing in different national languages, see WebSphere MQ LotusScript Extension.

We 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"

• PROPERTY strings must be in upper case.

• Value strings are not case sensitive, except for feature names. They can be enclosed in double quotation marks. If a value string includes a blank, it must be enclosed in double quotation marks.

• For a property that can take more than one value, use the format:

  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.

Table 5. Valid feature names

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"

Unattended installation of the extended transactional client

The extended transactional function is installed using the Microsoft Windows Installer (MSI). We can invoke MSI directly, without using setup.exe. This means that we 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.

We cannot use a response file.

 

Advanced installation methods

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. We can use this process for more complex unattended (or silent) installation, or for interactive installation, from a command line.

Using Msiexec with command line parameters

We 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 we can use. For a silent installation, this must include the /q or /qn parameter.

Note:

The Msiexec command can take further parameters that are not supported or listed here. If we need details of these, refer to the help file for the Windows Installer that is supplied with the MSI software development kit. See the Microsoft Web site at: http://www.microsoft.com.

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 we can enter as property=value pairs on the Msiexec command line (defaults are shown in bold). Note that:

• Property strings must be in upper case.

• Value strings are case sensitive. They can be enclosed in quotation marks. If a value string includes a blank, it must be enclosed in quotation marks.

• For a property that can take more than one value, use the format:

  ADDLOCAL="Client,Toolkit"

Table 6. Msiexec command line parameters

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 MQ Windows Installer package is IBM 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. u Advertise to the current user m Advertise to all users of this machine g Language ID t Applies transform to advertised package
/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. i Status messages w Non-fatal warnings e All error messages a Start up of actions r Action-specific records u User requests c Initial user interface parameters m Out-of-memory or fatal exit information o Out-of-disk-space messages p Terminal properties v Verbose output + Append to existing file ! Flush each line to the log * Log all information except for the v option. To log all information including the v option, specify "/l*v"
/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: Manufacturer - Author Product - Revision Number V- Subject Locale - Template Serial Number - not set Installation - set by ISMIF32.DLL to DateTime InstallStatus - Success or Failed Description - Error messages in the following order: Error messages generated by installer. Resource from msi.dll if install could not commence or user exit System error message file. Formatted message: Installer error %i, where %i is the error returned from msi.dll.
/q	n|b|r|f	Sets the level of user interface displayed during the install. q, qn No user interface. A silent installation that displays no user interface. qb Basic user interface. Displays the built-in dialog boxes that show progress messages qr Reduced user interface with a modal dialog box displayed at the end of the installation. qf Full user interface with a modal dialog box displayed at the end. qn+ No user interface except for a modal dialog box displayed at the end of installation. qb+ Basic user interface with a modal dialog box displayed at the end. The modal box is not displayed if the user cancels the installation. qb- Basic user interface with no modal dialog boxes. Note that /qb+- is not a supported UI level.
/x	Package|ProductCode	Uninstalls the product.
Note: Do not use the options /i, /x, /j[u|m], and /a together. Use the options /t and /g only with /j. Use the options /l and /q with /i, /x, /j[u|m], and /a.

Table 7. Msiexec PROPERTY= value parameters

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).

Table 8. 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	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.
For a list of valid feature names, see Table 5.

Using transforms

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, we 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, 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.

We can also specify the required language by using the MQPLANGUAGE property with the MQParms command. See Table 7.

Table 9. Supplied transform files

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

Using Msiexec with a response file

We 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.

We 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:

parameters

are command line parameters listed in Table 6, or property=value pairs on the command line (always put the command line parameters first).

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, Response.ini.

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" 

Using the MQParms command

We 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 we 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.

We can specify many more parameters in the parameter file that you use with the MQParms command than we 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:

• Copy and edit the file MQParms.ini that is supplied in the root folder of the WebSphere MQ Client CD-ROM, using an ASCII file editor.

• Create your own parameter file using an ASCII file editor.

To invoke installation using the MQParms command:

1. From a command line, change to the root folder of the WebSphere MQ Client CD-ROM (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 Parameter file.

   parameters

   are one or more command line parameters, as listed in Table 6.

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

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 stanza in the file:

[MSI]

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

The properties that we 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=""

We 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 

Table 10. 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	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.

 

Using Microsoft System Management Server

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:

• WebSphere MQ.pdf

• WebSphere MQ.sms

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.

Note:

You must be logged onto the target machine with Administrator authority to install WebSphere MQ.

 

Installing the extended transactional client using SMS

To install the extended transactional client, proceed as above, but using the WebSphere MQ Extended Transactional Clients CD.

 

Home