WebSphere MQ (Legacy) input connector

This connector receives input via IBM WebSphere MQ message queues. Before you can use this connector, you must add -webspheremq as a custom argument. You do this in the Configure Platform Export dialog box in Design Center.

Connector settings
Setting	Description
Queue manager	The queue manager to connect to.
Queue name	The name of the queue to use.
Channel name	The name of the client connection channel. The name must be the same as the name of the server connection channel defined on the WebSphere MQ server.
Channel protocol	The protocol to use for WebSphere MQ communication. You can select one of the following: • TCP/IP • NETBIOS • SPX • LU62
Channel server name	Host name or IP address of the server running the queue manager.
Schedule	Opens the Scheduler Configuration dialog where you specify when and how often to retrieve input. See Scheduling actions in the Design Center documentation for more information about scheduling.
Time-out	Specifies a time-out (seconds) for the connector. StreamServer uses job-end sequences in the input data to determine when all data in an input job is received. If there are no job-end sequences in the input data, StreamServer will not know when to stop waiting for more input. To prevent this from happening, you can define a time-out for the input connector.

Additional information

Specifying a client connection channel using environment variable

You can use the environment variable MQSERVER to specify a default client connection channel to a specific queue manager. This will be the default client connection channel for all WebSphere MQ input and output connectors. If you specify MQSERVER and also specify valid Channel settings for a physical layer in the GUI (Channel name, Channel protocol, and Channel server name), this physical layer will use the client connection channel specified by the GUI settings (valid GUI settings override MQSERVER definition).

Use the following syntax to specify a client connection channel:

On Windows: SET MQSERVER=<ChannelName>/<TransportType>/<ConnectionName> On UNIX: export MQSERVER=<ChannelName>/<TransportType>/<ConnectionName>

ChannelName	The name of the client connection channel. The name must be the same as the name of the server connection channel defined on the WebSphere MQ server. The ChannelName must not include forward slash (/).
TransportType	The protocol to use for WebSphere MQ communication. You can use one of the following: • TCP • NETBIOS • SPX • LU62
ConnectionName	Host name or IP address of the server running the queue manager.

Example 50

Specifying client channels on Windows.

SET MQSERVER=CHAN1/TCP/MCID66499

SET MQSERVER=CHAN2/TCP/9.20.4.56(1456)

SET MQSERVER=CHAN3/NETBIOS/BOX643

 

Example 51

Specifying client channels on UNIX.

export MQSERVER=CHAN1/TCP/'MCID66499'

export MQSERVER=CHAN2/TCP/'9.20.4.56'

export MQSERVER=CHAN3/LU62/BOX99

 

Groups and Segments

StreamServer and the application that sends data to StreamServer must handle group and segment properties in the same way. They must both read groups and segments using MQGMO_LOGICAL_ORDER to ensure that all messages are received in the same order as they were sent.

StreamServer uses MQGMO_SYNCPOINT to make sure the message remains in the queue if StreamServer fails to read or process the message. StreamServer will retry to read the message until it succeeds to do so. If it continuously fails to read the message, you must remove the message from the queue.

If a group of messages is sent, MQGMO_ALL_MSGS_AVAILABLE and MQGMO_WAIT are used to ensure that StreamServer waits until all messages in the group are available. StreamServer will also wait until all segments of a message are available.

WebSphere MQ attributes

You can use the scripting function GetConnectorValue to fetch WebSphere MQ attributes.

Attribute	GetConnectorValue("<argument>")
GroupId	GetConnectorValue("IBMMQGroupId")
MessageId	GetConnectorValue("IBMMQMsgId") GetConnectorValue("IBMMQMsgIdBase64")
CorrelationId	GetConnectorValue("IBMMQCorrelId") GetConnectorValue("IBMMQCorrelIdBase64")
Reply-To-Queue	GetConnectorValue("IBMMQReplyToQ")
Reply-To-Queue-Manager	GetConnectorValue("IBMMQReplyToQMgr")
Message type	GetConnectorValue("IBMMQMsgType")
Report option	GetConnectorValue("IBMMQReport")