Data import

Connection details

Choose the location of the assembly to use for the .NET Query collector, for example, File system or Global Assembly Cache (GAC). Depending on the assembly location that you choose, you can see different settings in the dialog box:

1. When the Assembly location is File system:
   1. In the Assembly name, specify the assembly name including extension (e.g. MyCollector.dll).
   2. In the Assembly folder, specify the assembly folder path where the assembly is stored.
2. When the Assembly location is Global Assembly Cache (GAC), in the Assembly name field, specify the assembly name including version, culture, public key token and processor architecture.

note

If the assembly is present in the Global Assembly Cache (GAC), this assembly file will take precedence over the file selected through the Assembly name and Assembly folder fields, unless the selected file has a different strong name.

Queries and mappings

The .NET Query collector supports any number of queries. You need to specify the following parameters when you create or edit a query.

1. In the Queries and mappings dialog box, click New, then select the object type to create a query for.
2. In the New query and mapping dialog box, under the Parameters heading, specify any relevant query parameters including the Query field. Optionally, in the Description field, enter a description of what this query is doing.
3. Under the Mappings header, map the relevant Destination properties in the left column to a value in the Source on the right side. You can specify whether the Operator is a Map, a Constant, aLookup, or an Expression. You must always type a value for the Destination properties that are followed by a red asterisk (*).
4. The Destination property Action should be completed for a delta import. It must specify if the data has been deleted (D) or created/changed (C) in the source system.

Mapping of resource owners

If you create a query to import resource owners, it is possible to specify the resource's owner in two ways. You can do it either by directly importing the UID of the identity or by specifying the account from which the resolved owner is imported as a resource owner. When mapping directly to the UID of identity, ensure that identities are already imported to Omada Identity.

When mapping to an owned account, it is possible to either specify the business key of the account or the composed business key. The former should be used if the account is in the same system as the resource; the latter should be used if the account is imported into any of the trusted systems. When the account stems from another system, you should use a Lookup mapping.

Advanced configuration

The .NET Query collector supports the use of delta import which allows you to import individual data object types without loading a full dataset. This can be found in the Advanced settings menu.

Parameter	Description
Import mode for identities, accounts, and resources	Choose either Delta or Full.
Import mode for contexts	Choose either Delta or Full.
Import mode for context assignments	Choose either Delta or Full.
Import mode for context owners	Choose either Delta or Full.
Import mode for identity owners	Choose either Delta or Full.
Import mode for resource assignments	Choose either Delta or Full.
Import mode for resource owners	Choose either Delta or Full.
Import mode for systems	Choose either Delta or Full.
Import mode for system owners	Choose either Delta or Full.
Row count per batch	Set the number of objects that will be collected and staged as a batch when paging is implemented in the collector. The default value is 100000. Applying a low value (e.g., 50 or 500) to this setting may result in extended import time.

The data supplied by the .NET assembly during import, must adhere exactly to the import type settings for each data type object. If the load method for a data object type is set to Delta, and the .NET assembly does not supply a value for the Action column, the import process will fail. And if method is set to Full, the Action attribute from the .NET assembly must be empty (NULL).

Configure thresholds

The Configure thresholds function allows you to set the amount of changes that cannot be exceeded, relevant to the last import. In the Configure import thresholds view, type a number (integer) in percentage for New objects, Modified objects, and Deleted objects to enable thresholds for the import of objects from this system. The value for each operation is by default set to 0, which means that no threshold calculations take place for the operations until you change the integer.

For more information, see Thresholds.

note

For all .NET-based collectors, thresholds are calculated in the following relation:

• If the system category is set to Identity data, the thresholds are calculated.
• If the system category is set to Access data, the thresholds are calculated.
• If the system category set to Both, the thresholds only apply to Access data, that is, Accounts, Resources, and ResourceAssignments.