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.
Table 11 Destination Settings 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. If you specify a preprocessor, also specify worker thread settings.For more detailed information about preprocessors and see Event Preprocessors in TIBCO BusinessEvents Architect’s Guide. Shared Queue Uses the TIBCO BusinessEvents system-wide shared queue and threads. See Properties for Shared Queue and Threads Threading Model.Caller Uses the thread (and queue size) provided by the channel resource client. There is one thread per destination.Workers TIBCO BusinessEvents creates a dedicated thread pool and set of worker threads in each destination. See Thread Count and Queue Size below. If you specified Workers in the Threading Model setting, specify the number of threads for this destination here. If you specified Workers in the Threading Model setting, specify the queue size for this destination here. In MM Console, this thread appears with the name $default.be.mt$.See also notes for com.tibco.cep.runtime.scheduler.queueSize For more details, see notes for com.tibco.cep.runtime.scheduler.default.numThreads
Copyright © TIBCO Software Inc. All Rights Reserved.