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 Configuruing 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.
Note: 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. - Configuring Agents with Collections and Individual Resources
- Different agent types use different types of resources.
- 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 deploy time 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.
Tip:
- How Startup Rulefunctions and Shutdown Rule Functions are Executed
-
- The order of the functions (including the order of functions within collections) is the order in which they execute at runtime.
- Put startup rule functions (for use at start up) into different collections from shutdown rule functions (those used at shut down) so you can select them appropriately at the agent classes tab.
- Log Configurations
-
Also in the Collections tab, you can add different log configurations. These are used when you configure processing units.
See Log Configurations.
- Configuruing Collections of Rules, Rule Functions, and Destinations
-
The purpose of configuring collections of rules, rule functions, and destinations. is to make it simpler to configure agent classes. When you configure an agent, you can add collections of resources or individual resources or both. Two collections are predefined: an all-rules collection and an all-functions collection.
- Using References
-
A collection can have references to items (rules, rule functions, or destinations), and also references to other collections of the same type. References are identified in the groups tree by a reference symbol (
). This mechanism enables you to reuse collections for more efficient configuration.