...
This article provides a quick overview of the procedures of installing, configuring, and running the ADSync utility. To integrate ADSync Utility with the LumaServiceaide Intelligent Service Management application, perform the tasks that are described in this article.
...
- Create the organization structures of the records in Luma before Intelligent Service Management before you start using the ADSync Utility. In the absence of the organization structure, users are not mapped to their respective organizations.
- The latest version of Java (version 8 or later) is installed on the system where you install the ADSync Utility.
- The system has network connectivity with the Active Directory (you You can install on the AD server itself).
...
- Download the ADSync utility from the Downloads section within Luma Intelligent Service Management. Navigate to MANAGE> ADMINISTRATION> Tools> Downloads.
- Create an account on the Active Directory (AD) which can access and run queries on the active directory server.
- Unzip the ADSync folder.
- On the system where you unzip the ADSync Utility, modify the environment variable path. Navigate to My Computer> Advanced Settings> Environment Variables> Path.
Set the path to the install bin directory of the JRE installation.
...
See Get Started with ADSync Utility for more details.
Configuration
To configure the ADSync Utility, follow these steps:
Configure Files
ADSync utility includes three configuration files in the Install directory\AdsyncUtility\ad-user-sync\conf folder. The files are:
...
- LDAP GC and LDAP DC: These values are generally the same. Change these values to your AD server or the domain controller.
Example:
# Global Catalog Server
ldap.gc=ldap://localhost:3268
# Domain Controller Server
ldap.dc=ldap://localhost:389 - Authtoken and slicetoken: These values are auto-populated when you download the ADSync Utility. Do not DO NOT edit these values. If you happen to edit these values by mistake, download the ADSync Utility again.
- action.url: The action.url is the URL to your application instance. This value is auto-populated when you download the ADSync Utility. Do not DO NOT edit this value. If you happen to edit this value by mistake, download the ADSync Utility again.
Note: For large transactions, the support team can provide you with a direct URL to the application, to resolve timeout issues. Only in such cases, you can update this attribute manually. - LDAP Bind credentials= LDAP Bind credentials is the service account that you created in the AD.
- send.data: This parameter determines whether to stream data over to Luma or to Intelligent Service Management or not. The value is set to Yes. However, you can set it to No while running the ADSync Utility for diagnostic purposes.
...
This file is used to map fields from AD with the fields in Luma Intelligent Service Management. Configure it by mapping the application attributes with their corresponding AD attributes, in the following format:
Luma attributeIntelligent Service Management attribute=AD attribute
For more information about these files and attributes, see Configure the ADSync Utility and look for attribute_map.list.
...
You can test the ADSync Utility without actually sending data to Luma Intelligent Service Management. Set the send.data attribute in the sync.properties file to No.
...
- Sync data log file: After the synchronization is complete, Luma generates done, Intelligent Service Management generates an XML file that is written to <install directory>\sync\logs\sync_data.log.0. Any error during the synchronization can be seen here.
- Backup file: The backup file is generated at the following location:
<Install directory>\sync\backup
The backup file stores the changes that are written in the data after the last successful synchronization.
...