Take into account the following behaviors when using the Aggregation profile:

You can apply an Aggregation profile to any number of workflow configurations.
Aggregation sessions created in the storage that is specified by the profile can be accessed by multiple active workflows simultaneously.
When you have selected file storage and are using an Aggregation profile across several workflow configurations, you must consider the read-and-write lock mechanisms that are applied to the stored sessions. For further information about read-and-write locks, see Aggregation Agent Configuration - Batch and Aggregation Agent Configuration - Real-Time.
The Aggregation profile is loaded when you start a workflow that depends on it. Changes to the profile become effective when you restart the workflow.

Session UDR

Each Aggregation profile stores sessions of a specific Session UDR type that you define in ultra. This means that your Aggregation profile configuration must include a session UDR type. See the example below:

Example - Defining a Session UDR type in an Ultra Configuration

session SessionUDRType {
   int intField;
   string strField;
   list<drudr> udrList;
};

It is recommended that you keep the session UDR as small as possible. A larger UDR decreases performance compared to a small one.

Note!

Take particular care when updating the Ultra formats. It is not possible to collect data from the Aggregation session storage if the corresponding UDR has been renamed. However, if you change the format definition, you can still collect the data.

Changes to the formats are handled as follows:

Default values are assigned to fields that are added or renamed.
Fields that have been removed are ignored.
Default values are assigned to fields with data types that have been changed.

For further information on Ultra formats, see Ultra Reference Guide.

Configuration

The contents of the buttons in the menu bar may change depending on which configuration type has been opened in the currently active tab. The Aggregation profile uses the standard buttons that are visible for all configurations, and these are described in Build View.

The profile consists of four tabs:

Session Tab
Association Tab
Storage Tab
Advanced Tab

Session Tab

In the Session tab you can browse and select a Session UDR Type and configure the Storage selection settings.

The Aggregation profile configuration dialog - Session tab

Setting	Description

Setting

Description

Session UDR Type

Click on the Browse... button and select the Session UDR Type. The Session UDR is defined in Ultra see Aggregation Profile | Session UDR above for more information.

Storage

Select the type of storage for aggregation sessions. The available settings are:

Couchbase Storage
Elasticsearch Storage
File Storage
Memory Only
Redis Storage
SQL Storage

File Storage and Memory Only can be used in batch and real-time workflows.

Elasticsearch Storage and SQL Storage can only be used in batch workflows.

Couchbase Storage and Redis Storage can only be used in real-time workflows. These storage types allow highly available systems with geographic redundancy. The session data that is replicated within the storage is available across workflows, EC Groups, and systems. This serves to minimize data loss in failover scenarios.

Note!

Data stored in Couchbase or Redis is not available in the Aggregation Session Inspector .

Session Tab in the Aggregation Profile

Association Tab

You use the Association tab to configure rules that are used to match an incoming UDR with a session. Every UDR type requires a set of rules that are processed in a certain order. In most cases, only one rule per incoming UDR type is defined.

You can use a primary expression to filter out UDRs that are candidates for a specific rule. If the UDR is filtered out by the primary expression, it is matched with the existing sessions by using one or several ID fields as a key.

For UDRs with ID Fields matching an existing session, an additional expression may be used to specify additional matching criteria. For example, if dynamic IP addresses are provided to customers based on time intervals, the field that contains the IP address could be used in ID Fields while the actual time could be compared in Additional Expression.

Setting	Description

Setting	Description
UDR Types	Click on the Add button to select a UDR Type in the UDR Internal Format dialog. The selected UDR type will then appear in this field. Each UDR type may have a list of rules attached to it. Selecting the UDR type will display its rules as separate tabs to the right in the Aggregation profile configuration.
Primary Expression	The Primary Expression is optional. Enter an APL code expression that is going to be evaluated before the ID Fields are evaluated. If the evaluation result is `false` the rule is ignored and the evaluation continues with the next rule. Use the `input` variable to write this filtering expression.
ID Fields	Click on the Add button to select additional ID Fields in the ID Fields dialog. These fields, along with the Additional Expression settings enable the system to determine whether a UDR belongs to an existing session or not. If the contents of the selected fields match the contents of a session, and an Additional Expression evaluation results in `true`, the UDR belongs to the session.
Additional Expression	The Additional Expression is optional. Enter an APL code expression that is going to be evaluated along with the ID Fields. Use the `input` variable to write this filtering expression. The Additional Expression is useful when you have several UDR types with a varying number of ID Fields, that are about to be consolidated. Having several UDR types requires the ID fields to be equal in number and type. If one of the types requires additional fields that do not have any counterpart in the other type or types, these must be evaluated in the Additional Expression field. Save the field contents as a session variable, and compare the new UDRs with it. For an example, see Association - Radius UDRs in Aggregation Example - Association of IP Data.
Create Session on Failure	Select this check box to create a new session if no matching session is found. If the check box is not selected, a new session will not be created when no matching session is found. If the order of the input UDRs is not important, all the rules should have this check box checked. This means that the session object is going to be created regardless of the order in which the UDRs arrive. However, if the UDRs are expected to arrive in a particular sequence, Create Session on Failure must only be selected for the UDR type or field that is considered to be the master UDR, i e the UDR that marks the beginning of the sequence. In this case, all the slave UDR types or fields are targeted for error handling if they arrive before their master UDR. For further information about all available system properties, see System Properties.
Add Rule	Click this button to add a new rule for the selected UDR Type. The rule will appear as a new folder to the right of the UDR Types in the Aggregation profile configuration. Usually, only one rule is required. However, in a situation where a session is based on an IP number, stored in either a target or source IP field, two rules are required. The source IP field can be listed in the ID Fields of the first rule and the target IP field listed in the ID Fields of the second rule.
Remove Rule	Click this button to remove the currently displayed rule.

Storage Tab

The Storage tab contains settings that are specific for File Storage, Couchbase Storage, Redis Storage, Elasticsearch Storage, and SQL Storage.

Couchbase Storage

Setting	Description

Setting

Description

Profile

Select a Couchbase Profile. This profile is used to access the primary storage for aggregation sessions.

Mirror Profile

Selecting this Couchbase profile is optional. It is used to access secondary storage, providing read-only access for aggregation sessions. Typically, the Mirror Profile is identically configured to a (primary) Profile, that is used by workflows on a different EC Group or other MediationZone system. This is useful to minimize data loss in various failover scenarios. The read-only sessions can be retrieved with APL commands. For more information and examples, see Aggregation Functions.

Elasticsearch Storage

Setting	Description

Setting	Description
Elasticsearch	Select an Elasticsearch Profile. This profile is used to access the storage for aggregation sessions.

File Storage

Setting	Description

Setting	Description
Storage Host	Select a Storage Host from the drop-down list. For storage of aggregation sessions select either a specific EC Group or Automatic. If you select Automatic, the same EC Group that has been used by the running workflow will be applied. Alternatively, if the Aggregation Session Inspector is used, a storage host is selected automatically. Refer to Aggregation Session Inspector for further information on the Aggregation Session Inspector.
Directory	Enter the directory on the Storage Host where you want the aggregation data to be stored. If this field is greyed out with a stated directory, it means that the directory path has been hard-coded using the `mz.present.aggregation.storage.path` property. This property is set to `false` by default.
Partial File Count	In this field, you can enter the maximum number of partial files that you want to store. Consider the following: Startup: All the files are read at startup. It takes longer if there are many partial files. Transaction commitment: When the transactions are committed, many small files (large Partial File Count) increase performance. In a batch workflow, use this variable to tune performance.
Max Cached Sessions	Enter the maximum number of sessions to keep in the memory cache. This is a performance-tuning parameter that determines the memory usage of the Aggregation agent. Set this value to be low enough so that there is still enough space for the cache in memory, but not too low, as this will cause performance to deteriorate, see Performance Tuning with File Storage for more information.
Enable Separate Storage Per Workflow	This option enables each workflow to have a separate session storage. Multiple workflows are allowed to run simultaneously using the same Aggregation profile. If this checkbox is selected, a workflow will never see a session from another workflow.

Memory Only

When you have selected Memory Only as storage, there are no additional settings in the Storage tab.

Redis Storage

Setting	Description

Setting	Description
Profile	Select a Redis Profile . This profile is used to access the storage for aggregation sessions.

SQL Storage

Setting	Description

Setting	Description
Profile	Select a Database Profile configured with the SQL database type. This profile is used to access the storage for aggregation sessions.
Index Fields	Click the Add button to select the UDR type.
Table SQL Script	This text box will generate the SQL statements for the selected UDRs' table schema and indexes for Id, TxId. The schema will be generated based on the number of UDRs in the UDR Type Mapping table.

Advanced Tab

The Advanced tab is available when you have selected Couchbase Storage, Redis Storage, Elasticsearch Storage or SQL Storage in the Session tab. It contains properties that can be used for performance tuning. For information about performance tuning, see Aggregation Performance Tuning.

These fields supports parameterization using ${} syntax, see Appendix 1 - Profiles for more information on how parameterization works.

Couchbase Storage

You can also set the properties listed in the Advanced tab as Execution properties in the STR. This will override the values that are set in the profile, including default values.

Elasticsearch Storage

For Elasticsearch Storage, you can modify the properties listed as shown above in the Advanced tab.

Redis Storage

For Redis Storage, you can only modify the properties in the Advanced tab.

SQL Storage

For SQL Storage, you can modify the properties listed as shown above in the Advanced tab.