IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Configuring the storage of events for Collector nodes

You can use a Collector policy to control the storage of events for Collector nodes.

About this task

Information about the state of in-flight messages is held on storage queues that are controlled by IBM® MQ, so you must install WebSphere MQ on the same computer as your integration server if you want to use the capabilities that are provided by the Collector node. The storage queues that hold the state information are owned by the queue manager that is associated with the integration server.

If the integration server has the necessary permissions to create the default system queues, they are created automatically when a flow that contains Collector nodes is deployed. If the default queues are not created automatically, you can create them manually; see Creating the default system queues on a WebSphere MQ queue manager.

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 policy 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:

Procedure

  1. 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 App Connect Enterprise creates the 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.

  2. Create a Collector policy (see Creating policies with the IBM App Connect Enterprise Toolkit).

    You can create a policy to be used with either a specific collection or with all collections in an integration server. If you are creating a policy to be used with a specific collection, ensure that the name of the policy is the same as the name that you specify in the Configurable service property on the Collector node. If you are creating a policy to be used with all collections in the integration server, ensure that the policy has the same name as the integration server. However, the name of a policy cannot start with a digit; if the name of the policy 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.

    If you delete a Collector policy, the storage queues are not deleted automatically when the policy is deleted, so you must delete them separately.

  3. Set the Queue prefix property to the required value.
  4. Optional: Set the Collection expiry property to an appropriate value (for example, 60).
  5. In the Collector node, if the policy is to be used for a specific collection, specify the name of the policy in the Configurable service property on the Advanced tab; for example, myCollectorService. If you do not set the Configurable service property, and if a policy exists with the same name as the integration server, that policy is used instead.

What to do next

The properties for the policy are not used by the integration server until you restart or redeploy the message flow, or restart the integration server.

bc28120_.htm | Last updated 2018-11-02 14:46:16