You can also create channel definitions for one or more queue managers in a configuration file, and provide the fully qualified file name to Connect in the DMX_CONNECTOR_ENV_MQ_WS_INI_FILE environment variable. This populates the Queue manager combo box of the Message Queue Connection dialog with the defined queue managers or their aliases.
The contents of the file must be formatted as follows:
- Anything following a “#” character until the end of the line is a comment. Comments are allowed anywhere.
- Empty lines are allowed anywhere.
- The file is organized in sections. The beginning of each section (the section header) is specified by a string enclosed in square brackets. The enclosed string may be a queue manager name or a queue manager alias.
- The section headers must be unique.
- The lines between section headers contain the channel definition parameters for that particular queue manager or alias. There are 4 supported parameters: queuemanager, channel, transport, connectionname. The parameter values are separated from the parameter name by an “=” character. The parameter names are case insensitive, but their values are case sensitive, except for the transport parameter. Each line may contain at most one parameter definition.
- The queuemanager parameter is used for cases where the section name is not a queue manager name, but a queue manager alias. This is to allow potential configuration of different channel definition options for the same queue manager.
If there is a configuration section with just the name but no parameters, the MQSERVER environment variable definition is used at connection time. This saves you from typing in the queue manager's name in the GUI, as the name appears in the list of known queue managers.
The connection parameters defined in this file override the MQSERVER environment
variable only if all 3 parameters (channel, transport and
connectionname) are defined for a particular queue manager. If you would
like to define several different parameter sets for the same queue manager, use an alias for
the section name and override the queue manager name by defining the
queuemanager parameter inside the parameters section for that alias.
A sample configuration file (DMXWebSphereConnector.ini) is installed in the directory:
- On Windows: <connect_install>\Examples\WebSphereConnector\DMXWebSphereConnector.ini
- On Unix: <connect_install>/etc/DMXWebSphereConnector.ini
where <connect_install> is the directory where Connect is installed.
Example
SET DMX_CONNECTOR_ENV_MQ_WS_INI_FILE = C:\tmp\DMXWSConfig.ini[my.local.queue.manager]
Channel = all.clients
Transport = tcp
Connectionname = mw-server.com