Select the type of storage for aggregation sessions. The available settings are File Storage, Couchbase, Redis and Elasticsearch.

• File Storage can be used in batch and real-time workflows.
• Elasticsearch Storage and SQL Storage can only be used in batch workflows.

• Couchbase and Redis 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, ECs, and systems. This serves to minimize data loss in failover scenarios.

  Note
  title Note!
  Data stored in Couchbase or Redis is not available in the Aggregation Inspector(3.0).

• Elasticsearch can only be used in batch workflows.

• 
  

Click the  Add  button to select additional ID Fields in the  ID Fields  dialog. These fields, along with the  Additional Expression  settings, enable  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.

The Additional Expression is optional. Enter an APL code expression that is to be evaluated with the ID Fields.

Use the input variable to write this filtering expression.

This setting is useful when you have several UDR types with a varying number of ID Fields 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.

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 is not created when no matching session is found.

If the order of the input UDRs is unimportant, select this check box for all the rules. This means that the session object is created regardless of the order in which the UDRs arrive.

However, if the UDRs are expected to arrive in a particular sequence, only select Create Session on Failure for the UDR type/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/fields are targeted for error handling if they arrive before their master UDR.

You can only select Automatic.

When you select Automatic, the EC used by the running workflow is automatically applied. Alternatively, if the Aggregation Session Inspector is used, a storage host is selected automatically. For further information, see Aggregation Inspector(3.0).

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.

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 or other  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(3.0) in the APL Reference Guide.

Select a Database profile. This profile is used to access the storage for aggregation sessions.

Click the Add Image Added button to select the UDR type.

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.