IM Relationship Resolution Information Center, Version 4.2

Message queue transports

Message queue transports allow you to send data from system queues to pipelines for processing. To use a queue transport, you enter the queue transport that corresponds to the type of message queue using an Universal Resource Identifer (URI). IBM® Relationship Resolution supports two types of message queues: IBM WebSphere® MQ Series queues and Microsoft® MQ (MSMQ) queues.

IBM WebSphere MQ message queue transport

The format for the IBM WebSphere MQ queue transport is:

mq:/queue_name?manager=manager_name?concurrency=n

mq:/
Required parameter that indicates the transport method is an IBM WebSphere MQ Series queue.
queue_name
Required parameter that specifies the name of the queue to use.
?manager=manager_name
Optional parameter that specifies the name of the queue manager.
If this parameter is not specified, the default queue manager is used. If the host does not have a default queue manager, this parameter is required. The queue specified with queue_name must already be created in the queue manager, or specified under the default if no queue manager is specified.
?concurrency=n
This optional parameter enables you to specify the number of incoming records (a positive integer greater than or equal to 0) that can be processed simultaneously using the parallel pipeline processing feature.
The higher the number, the more records are processed simultaneously. For example, a concurrency of 0 indicates do not process records. A concurrency of 1 indicates process records one-at-a-time. The default number of incoming records pulled for this transport is 1, unless you specify otherwise.
You should coordinate this setting with the number of pipeline process threads spawned by the concurrency setting in the pipeline configuration file or the DEFAULT_CONCURRENCY system parameter group in the Configuration Console. The pipeline concurrency setting determines the number of simultaneous pipeline processing threads that begin when a pipeline is started. If your system is set to spawn multiple pipeline processing threads for each pipeline started, you might want to increase this transport concurrency setting so that the pipeline threads are not waiting for records to process.

Examples of IBM WebSphere MQ queue transports

mq/:relres

Using this IBM WebSphere MQ queue transport, the system reads incoming records from the IBM WebSphere MQ queue named "relres".

mq/:relres?manager=secondary.queue.manager

Using this IBM WebSphere MQ Series queue transport, the system reads incoming records from the IBM WebSphere MQ queue named "relres" using the queue manager named "secondary.queue.manager".

Microsoft Message Queueing (MSMQ) queue transport

The format for the Microsoft Message Queueing queue transport is:

msmq:/queue_name/?concurrency=n

msmq:/
Required parameter that indicates the transport method is a Microsoft MQ (MSMQ) queue.
queue_name
Required parameter that specifies the name of the queue to use.
/?concurrency=n
This optional parameter enables you to specify the number of incoming records (a positive integer greater than or equal to 0) that can be processed simultaneously using the parallel pipeline processing feature.
The higher the number, the more records are processed simultaneously. For example, a concurrency of 0 indicates do not process records. A concurrency of 1 indicates process records one-at-a-time. The default number of incoming records pulled for this transport is 1, unless you specify otherwise.
You should coordinate this setting with the number of pipeline process threads spawned by the concurrency setting in the pipeline configuration file or the DEFAULT_CONCURRENCY system parameter group in the Configuration Console. The pipeline concurrency setting determines the number of simultaneous pipeline processing threads that begin when a pipeline is started. If your system is set to spawn multiple pipeline processing threads for each pipeline started, you might want to increase this transport concurrency setting so that the pipeline threads are not waiting for records to process.

Example MSMQ queue transport

msmq/:relres

Using this Microsoft MQ queue transport command, the system reads incoming records from the MSMQ queue named "relres".



Feedback

Last updated: 2009