Accelerating provisioning and single object synchronization
To smooth out spikes in data traffic, handling of processes for provisioning and single object synchronization can be distributed over several Job servers. This will also accelerate these processes.
NOTE: You should not implement load balancing for provisioning or single object synchronization on a permanent basis. Parallel processing of objects might result in dependencies not being resolved because referenced objects from another Job server have not been completely processed.
Once load balancing is no longer required, ensure that the synchronization server executes the provisioning processes and single object synchronization.
To configure load balancing
-
Configure the server and declare it as a Job server in One Identity Manager.
All Job servers must access the same Azure Active Directory tenant as the synchronization server for the respective base object.
-
In the Synchronization Editor, assign a custom server function to the base object.
This server function is used to identify all the Job servers being used for load balancing.
If there is no custom server function for the base object, create a new one.
For more information about editing base objects, see the One Identity Manager Target System Synchronization Reference Guide.
-
In the Manager, assign this server function to all the Job servers that will be processing provisioning and single object synchronization for the base object.
Only select those Job servers that have the same configuration as the base object's synchronization server.
For more detailed information about editing server, see the One Identity Manager Administration Guide for Connecting to Azure Active Directory.
Once all the processes have been handled, the synchronization server takes over provisioning and single object synchronization again.
To use the synchronization server without load balancing.
- In the Synchronization Editor, remove the server function from the base object.
For detailed information about load balancing, see the One Identity Manager Target System Synchronization Reference Guide.
Disabling synchronization
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
-
Open the synchronization project in the Synchronization Editor.
-
Select the start up configuration and deactivate the configured schedule.
Now you can only start synchronization manually.
An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.
Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the synchronization project
-
Open the synchronization project in the Synchronization Editor.
-
Select the General view on the start page.
-
Click Deactivate project.
Related topics
Basic data for managing an Exchange Online environment
To manage an Exchange Online environment in One Identity Manager, the following basic data is relevant.
- Configuration parameter
Use configuration parameters to configure the behavior of the system's basic settings. One Identity Manager provides default settings for different configuration parameters. Check the configuration parameters and modify them as necessary to suit your requirements.
Configuration parameters are defined in the One Identity Manager modules. Each One Identity Manager module can also install configuration parameters. In the Designer, you can find an overview of all configuration parameters in the Base data | General | Configuration parameters category.
For more information, see Configuration parameters for managing an Exchange Online environment.
- Account definitions
One Identity Manager has account definitions for automatically allocating user accounts to employees during working hours. You can create account definitions for every target system. If an employee does not yet have a user account in a target system, a new user account is created. This is done by assigning account definitions to an employee.
For more information, see Setting up account definitions.
- Target system types
Target system types are required for configuring target system comparisons. Tables containing outstanding objects are maintained on target system types.
For more information, see Post-processing outstanding objects.
- Target system managers
A default application role exists for the target system manager in One Identity Manager. Assign the employees who are authorized to edit all Exchange Online objects in One Identity Manager to this application role.
Define additional application roles if you want to limit the edit permissions for target system managers to individual Exchange Online objects. The application roles must be added under the default application role.
For more information, see Target system managers.
Setting up account definitions
One Identity Manager has account definitions for automatically allocating user accounts to employees during working hours. You can create account definitions for every target system. If an employee does not yet have a user account in a target system, a new user account is created. This is done by assigning account definitions to an employee.
The data for the user accounts in the respective target system comes from the basic employee data. The employee must own user account. The assignment of the IT operating data to the employee’s user account is controlled through the primary assignment of the employee to a location, a department, a cost center, or a business role. Processing is done through templates. There are predefined templates for determining the data required for user accounts included in the default installation. You can customize templates as required.
For detailed information about account definitions, see the One Identity Manager Target System Base Module Administration Guide.
The following steps are required to implement an account definition:
