The following three settings can be used to address the right MQSeries queue manager. Their meaning is as described in the MQSeries manuals. The channel en connection settings only have meaning in a client set-up. If you are connecting to the default queue manager, and use the default channel and connection of your client setup, these setting can be left blank.
QueueManager=MyManager
Channel=MyChannel
Connection=machine.domain.com
The following settings control the queue that will be used for retrieving WindowsEnabler/MQSeries requests. If you are logged on as 'user' and specify the prefix and the postfix as follows, the queue WE.user.Request will be taken.
QueuePrefix=WE.
QueuePostfix=.Request
It is also possible to let WindowsEnabler/MQSeries create a temporary request queue from a model queue. The model queue name can be specified as follows
ModelQueue=MyModelQueue
The name of the temporary queue will be constructed from the QueuePrefix, the user name and the QueuePostfix as described above.
Only a single user will be able to connect to a request queue simultaneously. If a model queue is used this is automatically guaranteed, because one cannot create two temporary queues with the same name. If the queue is specified directly, this is guaranteed because WindowsEnabler/MQSeries will open the queue for exclusive input.
The request queue must be configured in such a way that WindowsEnabler has read-access and write access to it. Read access (obviously) is needed in order to be able to retrieve requests from the queue. Write access is needed in order to initiate a disconnect via the WindowsEnabler GUI (but also see the Timeout value).
The CodePage setting determines the code page that WindowsEnabler/MQSeries will use when interacting with MQSeries. The default CodePage setting is 13488, which indicates a Unicode Codepage. If possible, use this code page. WindowsEnabler uses Unicode internally, and using Unicode ensures that special characters in your request messages do not get lost. If you are able to submit Unicode requests and read Unicode replies, or if your MQSeries software supports automatic conversion between the code page of your messages and Unicode, you do not have to change this setting.
Some versions of MQSeries however, do not support automatic conversion to Unicode. If this is the case (and you cannot supply Unicode messages yourself), you will have to specify a different code page. There are two requirements for this code page:
In other words, the CodePage setting specifies an intermediate code page. Note that windows in general does not support conversion from/to EBCDIC code pages, but MQSeries usually supports conversions between EBCDIC and some ASCII-compatible codepage. Usually, one of the following (ascii-compatible) CodePage settings will do (others might work as well, but have not been tested):
The Timeout setting specifies the timeout in milliseconds that WindowsEnabler will use when retrieving a request from the queue. The default value is zero, which means that WindowsEnabler will not use a timeout, but wait indefinitely until a message arrives. Usually, this is best, because WindowsEnabler will then use the least system resources.
The downside of an indefinite timeout is that WindowsEnabler requires write access to the request queue in order to initiate a proper disconnect via the WindowsEnabler GUI. If you do not allow this, you will have to specify a Timeout. The maximum time it takes to disconnect will then depend on the timeout value that you have specified.
This setting specifies whether or not WindowsEnabler requires request messages to have type MQMT_REQUEST and feedback options MQRO_PAN and MQFB_NAN. The default value is 'Y', which means that WindowsEnabler will not accept other types of messages. It will try to move such messages to the dead-letter queue.
Setting this value to 'N' has the effect that WindowsEnabler will accept other types of messages as well. It will not complain about these messages, but will treat them as an ordinary request, except that it will not return any replies for messages that are not of type MQMT_REQUEST.
This setting specifies the time in milliseconds that WindowsEnabler will use between attempts to automatically reconnect to MQSeries after a broken connection. The default value is zero, which means that WindowsEnabler will not automatically reconnect after a broken connection but deliver an error message.
If you specify an automatic reconnect interval, be aware that the automatic reconnect is a feature of the MQSeries interface. It is not a feature of the core WindowsEnabler software. This means that: