Skip to main content

Settings for the IBM WebSphere MQ Adapters

This section provides reference information for the IBM WebSphere MQ adapters.

Also see Settings in All Productions.

Introduction

For both the inbound and outbound adapters to IBM WebSphere MQ, you specify settings that describe the connection to a given queue. The details are nearly identical for both adapters.

Also see Prerequisites.

Specifying the Queue Manager, Channel, and Queue

Specify values for the following settings in order to specify the message queue of interest, the queue manager to use, and the channel to use:

QueueName

(Required) Specifies the queue name; this should be a valid queue for the specified queue manager. Also, you must have permission to use this queue.

QueueManager

Specifies the queue manager; this should be a valid queue manager on the IBM WebSphere MQ server and you must have permission to use it.

If you omit this setting, the system uses the default queue manager, as configured in IBM WebSphere MQ. Or, if IBM WebSphere MQ has been the configured so that the queue manager is determined by the queue name, the system uses the queue manager that is appropriate for the given queue name.

Channel

The specification for the channel, in the following form:

"channel_name/transport/host_name(port)"

Here channel_name is the name of the channel to use, transport is the transport used by the channel, host_name is the server name (or IP address) that is running the IBM WebSphere MQ server, and port is the port that this channel should use.

Transport can be one of the following: TCP, LU62, NETBIOS, SPX

For example:

"CHAN_1/TCP/rodan(1401)"
"CHAN_1/TCP/127.0.0.1(1401)"

If you omit this setting, the system uses the default channel specification, as configured in IBM WebSphere MQ. Or, if the system has been the configured so that the channel is determined by the queue name, the system uses the channel that is appropriate for the given queue name.

Specifying the Log File to Use

Use the following setting to specify the log file to write to.

ErrorFile

Specifies the log file to write error messages to. If you omit this setting, no logging occurs.

Specifying the Character Set of the Messages

You can specify the character set to use for message conversion.

CharSet

Specifies an integer Coded Character Set ID (CCSID) as used in IBM WebSphere MQ.

  • For the inbound adapter, this is the character set to convert the messages to. If you do not specify a character set, the MQ system assumes the messages use the default character set specified for the MQ client.

  • For the outbound adapter, this setting specifies the character set that the messages are already in; no conversion is done.

For information on character sets and translation tables, see Translation Tables.

Specifying How Often to Check for Messages

This applies only to the inbound adapter. To specify how often to check for messages, use the following setting:

CallInterval

Number of seconds that the adapter will wait before checking again for new messages, before checking for a shutdown signal from the production framework.

If the adapter finds input, it acquires the data and passes it to the business service. The business service processes the data, and then the adapter immediately begins waiting for new input. This cycle continues whenever the production is running and the business service is enabled and scheduled to be active.

The default CallInterval is 5 seconds. The minimum is 0.1 seconds.

For any settings not listed here, see Configuring Productions.

Example

The examples in this book used an IBM WebSphere MQ server running on a machine named testsystem, using the port 1414. The user ID under which the examples were run was authorized to use the queue manager QM_testsystem and a queue named testqueue. InterSystems IRIS used a TCP channel named S_testsystem to communicate with the server. The following table lists the settings:

Setting Value
Queue Manager QM_testsystem
Channel S_testsystem/TCP/testsystem(1414)
Queue Name testqueue
Error File c:\mq-log.txt
FeedbackOpens in a new tab