For each hub, there is always a default queue that can hold messages of unlimited size. To allow fast-track processing of small messages, you need to create one or more additional, size-restricted queues. You do this by editing the registry.
Queue Settings
For each additional queue, you can specify:
If a message exceeds this maximum size limit, the hub automatically assigns the message to the next appropriate queue.
For example, two additional queues are defined: Small (for messages up to 10 KB) and Medium (up to 100 KB). If a 15 KB message arrives at the hub, it is immediately assigned to the Medium queue; conversely, if a 2 MB message arrives, it is immediately assigned to the default queue, which handles messages of unlimited size.
You can specify separate lists of policy engines available for processing each queue. However, to minimize processing times, if a queue is empty then any idle policy engines assigned to that queue are also permitted to poach messages from other queues (but only from queues with a smaller maximum size limit).
Note: The default queue is not represented in the registry by a dedicated registry key and has no maximum size limit for queued messages; by contrast, any additional queues are represented by a dedicated registry key.
Monitoring the Queue Status
To monitor the status of individual event queues, check the relevant counters in the CA DataMinder Hub Queues performance object.
|
Copyright © 2014 CA.
All rights reserved.
|
|