bn28721_.htm |
Last updated Friday, 21 July 2017Select the objects and properties that you want to change for the Aggregation configurable service.
For Aggregation configurable services, you must stop and start the integration server for a change of property value to take effect.
| Supplied configurable services that are created for each broker | Properties for each configurable service that is defined | Description of properties |
|---|---|---|
| None | queuePrefix | The queue prefix used to specify the storage queues that are generated for use by the aggregation nodes. This property is optional. Five queues are required:
The prefix can contain any characters that are valid in a WebSphere® MQ queue name, but must be no longer than eight characters and must not begin or end with a period (.). For example, SET.1 is valid, but .SET1 and SET1. are invalid. Multiple configurable services can use the same queue prefix. If
no queue prefix is specified, the aggregation nodes use the default
queues that are generated when the broker is created:
|
| timeoutSeconds | The timeout value used by the AggregateControl node to set the expiry time (in seconds) of an aggregation. The value can be any positive integer. This property is optional; if it is not set, the value set on the node is used. The value of this property overrides the value set on the node, but it can be overridden by a value in the local environment. |
|
| timeoutThreads | The number of threads used by the AggregateReply node to process expired messages. The value can be any positive integer. This property is optional. When the property is set, a unique queuePrefix property must be set on the Aggregation configurable service, and this Aggregation configurable service must be used only in a single integration server. If the property is not set, a single thread is used to process expired messages. |
Last updated Friday, 21 July 2017