Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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.

Session Tab

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

...

SettingDescription

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, will enable enables 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.

Note
titleNote!

Make sure that the selected fields are of the same type and appear in the same order for all the rules that are defined for the agent.


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.

Note
titleNote!

When using Additional Expressions for Aggregation the caching mechanism only takes into account the primary and secondary rules when creating the session CRC. This means that if the number of sessions that cannot be told apart without use of an Additional Expression is high, the performance of the Aggregation Agent decreases due to cache read/write operations. This is especially true if the Max Cached Sessions property is low compared to the number of sessions. For this reason it is recommended that Max Cached Sessions is set to a high value when using Additional Expressions.


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.

Note
titleNote!

If you provide a primary expression, and it evaluates to false, the rule is ignored and no new session is created.

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.

Note
titleNote!

At least one of all defined rules must have this check box selected. Otherwise, no session will ever be created.

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 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.

...

SettingDescription

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 a 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 Group or other system Image Added 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 in the APL Reference Guide.

...

SettingDescription
Profile

Select an SQL profile. This profile is used to access the storage for aggregation sessions.

Note
titleNote!

Currently the SQL storage only supports PostgreSQL and SAP HANA databases.

Storage sharing functionality is currently not supported.


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.

Info
titleInfo!

Users will have to copy the SQL script generated in the text box to create the PostgreSQL and SAP HANA tables on their own in the database listed in the Database profile. The Aggregation profile will not automatically create the tables for you.


Note
titleNote!

The following table columns are mandatory when creating the database:

Column NameData Type

Id

VARCHAR(24)

TxId

BIGINT

Deleted

BOOLEAN

Timeout

BIGINT

Session

BYTEA



...