Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 29 Agent and Processing Unit Configuration : Collections, Agent Classes, and Processing Units

Collections, Agent Classes, and Processing Units
Destinations require additional configuration, which can be done in this tab. (Destinations that are added to agent classes individually can be configured at the Agent Classes tab.)
Collections
At the Collections tab, you can (optionally) group rules, rule functions, and destinations into collections so that they can be easily assigned to agent classes (and processing units in the case of log configurations).
See Configuring Collections of Rules, Rule Functions, and Destinations.
Agent Classes
Agent classes define the different sorts of agents you can deploy. Various agent types are available depending on the object management (OM) type and on the add-on products used. Each agent type is configured differently.
See Using Properties at Different Levels to understand the effect of using agent class properties at the cluster level and at the processing unit level to widen the scope of the property.
See Configuring Agent Classes (All OM Types)
How Collections and Individual Resources are Used to Configure Agents
Different agent types use different types of resources.
In the Agent Classes node (on the left side of the CDD editor) you see categories of collections. Here, you add collections you defined earlier, as needed to configure the agent class:
Rules  (Inference agent classes only.) It can be convenient to organize rules into collections for use in different inference agent classes. Select rule collections and individual rules as needed to define what rules will execute on inference agents of such classes at runtime.
Input Destinations  Different agents listen for messages arriving at different destinations. When you select a destination for use in a collection or an individual agent, you add deploytime configuration settings, to create a destination configuration. For example, you define an event preprocessor and a threading model to use. Each destination configuration is assigned a unique ID.
Startup Functions and Shutdown Functions  Select function collections and individual functions as needed, to define which functions execute at engine startup and shutdown respectively.
Log Configurations
Also in the Collections tab, you can add different log configurations. These are used when you configure processing units.
See Understanding and Configuring Log Configurations

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved