Catalog settings
In ELOxc, a catalog, or data source catalog, is the maximum processing scope and is defined for each instance. This basic selection includes all data sources available in an instance that need to be configured for each action tree. If a data source that is available in theory is not in the catalog, it cannot be processed. Not every data source in the catalog must be used in an action tree.
CatalogData sourceDepending on the selected catalog type, ELOxc has access to very different quantities of data. For example, LDAP queries of a local Active Directory will provide ELOxc with significantly more information about data sources than is possible via the EWS interface.
At the same time, it can make sense in some environments to do without LDAP queries and only allow access via EWS. In practice, the access options determine which catalog types will be used.
In the case of Exchange archiving, the unique ID of a catalog entry is the SMTP address. The following fields are available in a catalog data set (XSD: "LoginType"):
XSD- Domain: This specification is required for most Exchange archiving access scenarios. If you use an LDAP catalog, the Active Directory queries are directed to this domain, which is why the value in this field must be correct. However, there are also Microsoft Office 365 environments that require you to specify the domain. If you do not need to specify the domain, the field should be left blank.
- SMTP address: This entry is required for Exchange archiving, since the EWS interface identifies mailboxes using the SMTP address.
- Logon name and password: The user usually has to log on to the Microsoft with a logon name and a corresponding password. This is a requirement in order to be able to access Exchange.
- URL: However, even when using the Exchange archiving method, it may be necessary to configure the correct URL, since this is the URL that is required for Autodiscover redirect validation.
The following table shows you whether configuration is necessary, depending on the catalog type:
Catalog type, configure| Type | Logon/Password | Domain | SMTP address | URL |
| LDAP | Yes | Yes | Yes | Yes/No |
| Office 365 | Yes | Yes/No | Yes | Yes |
| EWS | Yes | Yes/No | Yes | Yes/No |
| Static | Yes | Yes/No | Yes | Yes/No |
If you are using the static catalog, you require the same number of configured catalog data records for any number of data sources, and you may need configure the catalog manually for each data record.
If you are configuring the dynamic catalogs, you need to apply the principle of impersonation instead. In this case, you just need to configure an ELOxc instance using a service account. The account must have sufficient access rights to query and process all the respective data sources. This means that you do not need to configure access to those data sources manually.
A dynamic catalog is applied by default when using LDAP or Office 365, for example. If new data sources are available in the environment, ELOxc can automatically add them to the catalog. If you are using a single service account, however, it is necessary to ensure that this account can query the catalog of data sources, but that the service account also has full access rights to the data sources. This is because ELOxc accesses the data source contents during the processing phase and changes data sets.
The REST API allows you to easily test the catalog queries. The catalog query in the ELOxc Console, for example, is based on this function. The Autodiscover service function is also available in the REST API and in ELOxc Tools. This can help you identify and then solve problems you have resolving mailboxes. It is highly advisable that you run this short test before before you set up a production environment. The Troubleshooting chapter contains a detailed description of both functions.
Catalog, query