By default, the storage queues used
by all
Collector nodes
are:
- SYSTEM.BROKER.EDA.EVENTS
- SYSTEM.BROKER.EDA.COLLECTIONS
These queues are also used by the Resequence node.
However,
you can control the queues that are used by different Collector nodes by creating
alternative queues that contain a QueuePrefix variable,
and by using a Collector configurable service to specify the names
of those queues for storing events.
Follow these steps to specify
the queues that are used to store event states, and to set the expiry
for the collection:
- Create the storage queues to be used by the Collector node. The
following queues are required:
- SYSTEM.BROKER.EDA.QueuePrefix.EVENTS
- SYSTEM.BROKER.EDA.QueuePrefix.COLLECTIONS
The QueuePrefix variable 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, SET1 and SET.1 are
valid queue prefixes, but .SET1 and SET1. are
invalid.
If you do not create the storage queues, IBM® Integration Bus creates the set of queues when
the node is deployed; these queues are based on the default queues.
If the queues cannot be created, the message flow is not deployed.
- Use the mqsicreateconfigurableservice command
to create a Collector configurable service. You can create a configurable
service to be used with either a specific collection or with all collections
in an integration server.
- If you are creating a configurable service to be used with a specific collection, ensure that the name of the configurable service is the same as the name that you specify in the Configurable service property on the Collector node. If you are creating a configurable service to be used with all collections in the integration server, ensure that the configurable service has the same name as the integration server. However, the name of a configurable service cannot start with a digit; if the name of the configurable service is to be the same as that of the integration server, ensure that the name of the integration server does not start with a digit.
- Set the Queue prefix property to
the required value.
- Optional: Set the Collection expiry
property.
For example, create a Collector configurable service called myCollectorService,
which uses queues prefixed with SYSTEM.BROKER.EDA.SET1, and with a
collection expiry of 60 seconds:
mqsicreateconfigurableservice MYBROKER -c Collector -o myCollectorService
-n queuePrefix,collectionExpirySeconds -v SET1,60
You can use the mqsideleteconfigurableservice command
to delete the Collector configurable service. However, the storage
queues are not deleted automatically when the configurable service
is deleted, so you must delete them separately.
For more information,
see Configurable services properties
- In the Collector node:
- If the configurable service is to be used for a specific
collection, specify the name of the configurable service in the Configurable service property on
the Advanced tab; for example, myCollectorService. If you do not set the Configurable
service property, and if a configurable service exists with
the same name as the integration server, that configurable service is
used instead.
- Optional: Use the mqsichangeproperties and mqsireportproperties commands
to change or view the properties of the configurable service. Alternatively, you can use the IBM Integration Explorer to
view or modify a configurable service. For more information about
working with configurable services, see Using the IBM Integration Explorer to work with configurable services.
The properties for the configurable service are not used
by the broker until you restart or redeploy the message flow, or restart
the broker.
Last updated Friday, 21 July 2017