Tracking history of data objects (Omada Data Warehouse and Analytics)

The object history tracking consists of the following components implementing different aspects of the functionality:

• The Persistence service is responsible for collecting data from the Enterprise server and the Role and Policy Engine, then merging it to the ODS. It also includes new and deleted resource hierarchies in the process.
• The history tracking is responsible for the data transfer from ODS to ODW as a continuous background process. It allows you, for example, to monitor inconsistent objects in ODS, errors, and history of changes introduced to chosen properties of a data object type.

The following items are transferred by the history tracking feature to the ODW:

• Identity
• System
• Resource
• Context Assignment
• Resource folders
• Contexts
• System categories

The data object transfer is initiated in two ways:

• When a change to the object is introduced.
• A timer value, set to two minutes, is reached.

All of the mentioned data object types have preconfigured properties, allowing for the export to be correct and successful with the default values of the settings. Specific fields of those data objects are mapped to the corresponding fields in ODW and values are configured in the Warehouse attribute name setting of the data object type property.

note

You can export additional data for the following data object types:

• Identity
• System
• Resource
• Context Assignment

You can achieve it by configuring the Warehouse attribute name setting in other properties. This way, they will be exported as extension attributes. For reference, see: Extension attributes.

Context type

A Data Object Type can be used as a Context Type. It requires the following attributes to be configured:

• ComposedBusinessKey - a unique value for a specific context
• Name
• ShortName
• Parent_ComposedBusinessKey - a reference property pointing towards a parent context

Additionally, there are two following attributes supported:

• Type
• SubType

Any other configured property is considered as an extension attribute.

For the Data Object Type to serve as a Context Type, it is also required that it has the Synchronize to ODW setting enabled and the Owner Property has to point to the correct identity reference property of the data object type.

note

When the context is set as personal, the parent assignment is also generated based on the parent context.

When the Membership property is configured, the context assignment is generated when identities are referencing the context by the membership property.

System and System category

Exporting systems and system categories to the Omada Data Warehouse requires the following configuration:

• Every system must have a System category assigned.
• Every system and system category must have a ComposedBusinessKey configured.

exception

Systems marked as Is logical system do not need a category. See the following flag:

warning

Systems or system categories missing this configuration are not correctly represented in the Omada Data Warehouse and Analytics.

Missing system category

To find the systems without a category, open the Setup > All systems list. The Category column is empty for systems that have no category assigned.

How you resolve the issue depends on whether a suitable system category already exists:

• If a suitable category exists, assign it to the system.
• If no suitable category exists, create a system category first, and then assign it to the system.

Make the changes in the Omada Identity UI, not directly in the database. Changes made in the UI are versioned and picked up by the synchronization.

tip

If the same system exists in several environments, for example, development, test, and production, use the same category for it in each environment. Before you create a new category, check the existing categories for duplicates or near-duplicates, for instance, categories with the same name but different IDs.

Create a system category

1. Go to Administration > Developer configuration > System categories.

2. In the System categories list, click New.

   

3. Fill in the required fields, marked with a red asterisk (*):

   
   • ID – a short, unique identifier.
   • Name – the name of the system.
   • Content – the type of data that the system holds: Identity data, Access rights, or Both.
   • Collector

   Leave the other settings at their default values, unless you know that you need to change them.

4. Click OK.

Assign a category to a system

1. In the All systems list, find the system.

2. Click the ellipsis (…) at the end of the row, and select Edit (advanced).

   

3. Under General settings, select the correct category in the Category list.

   

4. Click OK to save the changes.

After the next synchronization, the upload message Failed to upload data object for analytics data. Sequence contains no elements no longer appears for the system.

note

If a system is no longer in use, you can delete it instead of assigning a category to it.