Skip to main content

35 docs tagged with "Collector"

View all tags

Data import

The configuration of the AWS collector is based on the REST collector with the following

Data import

This section lists prerequisites and configuration instructions required to enable the Microsoft Entra ID collector in Omada Identity.

Data import

The Exchange Hybrid Connectivity relies on Microsoft Active Directory Connectivity and Microsoft Microsoft Entra ID Connectivity if using Exchange Hybrid for the correct operation. It is necessary to configure and import data from Active Directory and Microsoft Entra ID (for Exchange Hybrid Connectivity) before you can import data from Microsoft Exchange.

Data import

MijnCaress may contain duplicated user groups assigned to the same person. Thanks to the XPath used in the data import mappings for user group assignments, these duplicates are ignored.

Data import

Here you can find information on how to configure REST collector.

Data import

In this section, you can find information about how to configure the SAP Access Data collector.

Data import

In this section, you can find information about how to configure the SAP HANA DB collector.

Data import

In this section, you can find information about how to configure the SAP HCM collector.

Data import

In this section, you can find information about how to configure the SAP SuccessFactors collector.

Data import

You need to configure the system to contain both Identity data and Access rights if you want to provision identity data to the Workday System. If you are only importing HR information form Workday, select Identity data.

Migrating the REST-based collector to a .NET Query collector

Since Omada Identity 14.0.6 (Update 6) all collectors based on the generic REST collector have their Collector ID migrated from REST to Omada ODW NET Query. For the existing REST-based template collectors the migration process is performed during the update process, and it is transparent to the users.

Migration to REST-based collectors

If you have existing custom OData collectors (a new ODW Collector data object has been created by the customer and uses the OData collector technology), perform a migration process to a REST-based collector: