Cluster Deployment Descriptor Reference : Collections Tab — Destinations Settings and Properties

Collections Tab — Destinations Settings and Properties
Also available from the Agent Classes Tab.
When you select a destination in the CDD editor, you add deploytime settings and properties as needed (shown below). Doing so creates a destination configuration. Each destination configuration is assigned a unique ID. You can select and configure a destination in two places in the CDD: in the Collections tab, or in the Agent Classes tab.
Uniquely identifies this destination configuration at runtime. Edit as needed to ensure that each destination in the cluster has a unique deployment name.
Specifying a preprocessor is optional. Event preprocessors are rule functions with one argument of type simple event. If you specify a preprocessor, also specify worker thread settings. (Exception: HTTP destinations that use TOMCAT can use only the Caller worker thread setting.)
For more detailed information about preprocessors see Event Preprocessors in TIBCO BusinessEvents Architect’s Guide, and Event Preprocessors in TIBCO BusinessEvents Developer’s Guide.
Shared Queue  Uses the TIBCO BusinessEvents system-wide shared queue and threads. See Settings for queue size and number of threads are set by Agent settings Size and Workers. See Agent Classes Tab Settings and Properties.
Caller  Uses the thread (and queue size) provided by the channel resource client. There is one thread per destination. (This is the only option for HTTP destinations that use the TOMCAT server type. See Adding Channels and Destinations in TIBCO BusinessEvents Developer’s Guide.)
Workers  TIBCO BusinessEvents creates a dedicated thread pool and set of worker threads in each destination. See Thread Count and Queue Size below.
For more information on threading models see TIBCO BusinessEvents Architect’s Guide.