MQSI

In this section:

Reference:

The iWay WebSphere Business Integration Message Broker (formerly WebSphere MQ Integration Broker) transforms and enriches in-flight information to provide a level of intermediation between applications that use different message structures and formats.

The iWay Enterprise Integration Broker suite adds over 250 iWay adapters and transformation agents to the IBM brokered architecture.

For more information, see the iWay WebSphere Business Integration Message Broker Plug-In Suite User's Guide. The following procedure describes how to configure an iWay MQSI listener to communicate with the iWay Adapter node hosted by the WebSphere Business Integration Message Broker.


Top of page

x
MQSI Listener Properties

The following table lists and describes the MQSI listener properties. For instructions on creating a listener, see Configuring Listeners.

Property Name

Property Description

Port (required)

TCP port used to receive requests from MQSI.

Allowable Client

If used, accepts messages only from this fully qualified host name.

Accepts non-XML (flat) only

If true, the input data is sent directly to the business logic step. The data is not preparsed, parsed, or validated. This flag is used primarily to send non-XML to the business logic or replyTo without processing it.

Optimize Favoring

Use this option to customize how the listener performs. For smaller transactions, select performance. For large input documents that could monopolize the amount of memory used by iWay Service Manager, select memory.

Multithreading

Indicates the number of worker threads (documents or requests) that iWay Service Manager can handle in parallel. Setting this to a value of greater than 1 enables the listener to handle a second request while an earlier request is still being processed. The total throughput of a system can be affected by the number of threads operating. Increasing the number of parallel operations may not necessarily improve throughput.

Default: 1

Max Value: 99

Maximum threads

Parallel threads can grow to this count automatically on demand. Over time, the worker count will decrease back to the multithreading level. Use this parameter to respond to bursts of activity.

Execution Time Limit

Maximum time that a request may take to complete. Used to prevent runaway requests. Any request that takes longer to complete than this value will be attempted to be terminated. (See the "kill interval" for related information in Global Options.)

Polling Interval

Maximum wait interval (in seconds) between checks for new requests or commands. The higher this value, the longer the interval, and the fewer system resources that are used. The side effect of a high value is that the worker thread will not be able to respond to a stop command.

Default: 2.0 seconds.

Default Java File Encoding

Default encoding if incoming message is not self-declaring (that is, XML).

Agent Precedence

Sets the order by which iWay Service Manager selects agents. iWay Service Manager selects the agent or agents to process the document by searching through the configuration dictionary. Usually, it looks for a document entry in the configuration and when a match is found, the agent specified in that document entry is selected. If a matching document entry is not found, or no agent is specified, the engine looks in the input protocol configuration (listener). To have the processing agent taken directly from the listener (thus ignoring the document entry), use <listener> overrides <document>.

Possible values are <document> overrides <listener> and <listener> overrides <document>.

The default value is: <document> overrides <listener>

Always reply to listener default

If true, the default reply definition is used in addition to defined reply-to and error-to destinations.

Error Documents treated normally

If true, error documents are processed by any configured preemitters.

Listener is Transaction Manager

If true, agents run in a local transaction. Agents can roll back uncompleted transactions.

Initialization Agent

Name (parameters) of the processing module called at listener start up. (Internal use only.)



x
Reference: MQSI Listener Special Registers

The following table lists and describes the special registers (SREGs) available on the MQSI listener.

Name

Level

Type

Description

iwayconfig

System

String

Current active configuration name.

msgsize

Document

Integer

Physical length of the message payload.

name

System

String

Assigned name of the master (listener).

protocol

System

String

Protocol on which message was received.


iWay Software