In One Identity Manager, default installation processes for the standard events (Insert, Update, Delete) are made available for tables, which are used for mapping custom target systems.
The processes use scripts for data provisioning. The scripts must be modified to fit the custom target system because each custom target system maps the data differently.
Create custom scripts for your target system. You can use the TSB_Uns_Generic_Templates script as a template for creating custom scripts.
The processes expect functions in the script that are named with the following format:
<customer prefix>_<table>_<Ident_UNSRoot>_<event>
Example: Entering user accounts in the Telephone system custom target system
CCC_UNSAccountB_Telephonesystem_Insert
IMPORTANT: If your target system contains a hyphen (-) in its name, you must remove it from the script function in the <Ident_UNSRoot> part. Otherwise, error may occur during script processing.
The objects in the custom target system are mapped in the following table schema One Identity Manager table.
Table 2: Tables in the One Identity Manager schema for mapping custom target systems
|
UNSAccountB |
User account mapping. |
|
UNSAccountBHasUNSGroupB |
Group assignments to user accounts. |
|
UNSAccountBHasUNSGroupB1, UNSAccountBHasUNSGroupB2, UNSAccountBHasUNSGroupB3 |
Assignments of system entitlements to user accounts. |
|
UNSAccountBHasUNSItemB |
Permissions control assignments to user accounts. |
|
UNSAccountBInUNSGroupB |
Assignments of user accounts to groups. |
|
UNSAccountBInUNSGroupB1, UNSAccountBInUNSGroupB2, UNSAccountBInUNSGroupB3 |
Assignments of user accounts to system entitlements. |
|
UNSContainerB |
Container structure mapping. |
|
UNSGroupB |
Group mapping. |
|
UNSGroupB1, UNSGroupB2, UNSGroupB3 |
Mapping of other system entitlements. |
|
UNSGroupBHasUnsItemB |
Permissions control assignments to groups. |
|
UNSGroupBInUNSGroupB |
Assignments of groups to groups (group hierarchy). |
|
UNSGroupB1InUNSGroupB1, UNSGroupB1InUNSGroupB2, UNSGroupB1InUNSGroupB3 |
Assignments of system entitlements to system entitlements (system entitlement hierarchy). |
|
UNSItemB |
Mapping of additional permissions controls. |
|
UNSRootB |
Basis for mapping custom target systems. |
You can define a server for each custom target system, which runs all the One Identity Manager Service actions required for provisioning target system objects. For more information about installing and configuring the One Identity Manager Service, see the One Identity Manager Installation Guide.
To set up a server
-
Provide a server installed with the One Identity Manager Service.
-
In the Manager, create an entry for the Job server.
-
Select the Custom Target Systems > Basic configuration data > Servers category.
-
Click 
in the result list.
-
Edit the Job server's main data.
- Save the changes.
-
Enter the server as the synchronization server in the custom target system.
Detailed information about this topic
NOTE: All editing options are also available in the Designer under Base Data > Installation > Job server.
NOTE: More properties may be available depending on which modules are installed.
Table 3: Job server properties
|
Server |
Job server name. |
|
Full server name |
Full server name in accordance with DNS syntax.
Syntax:
<Name of server>.<Fully qualified domain name> |
|
Target system |
Computer account target system. |
|
Language |
Language of the server. |
|
Server is cluster |
Specifies whether the server maps a cluster. |
|
Server belongs to cluster |
Cluster to which the server belongs.
NOTE: The Server is cluster and Server belongs to cluster properties are mutually exclusive. |
|
IP address (IPv6) |
Internet protocol version 6 (IPv6) server address. |
|
IP address (IPv4) |
Internet protocol version 4 (IPv4) server address. |
|
Copy process (source server) |
Permitted copying methods that can be used when this server is the source of a copy action. At present, only copy methods that support the Robocopy and rsync programs are supported.
If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication is then performed with the Robocopy program between servers with a Windows operating system or with the rsync program between servers with a Linux operating system. If the operating systems of the source and destination servers differ, it is important that the right copy method is applied for successful replication. A copy method is chosen that supports both servers. |
|
Copy process (target server) |
Permitted copying methods that can be used when this server is the destination of a copy action. |
|
Coding |
Character set coding that is used to write files to the server. |
|
Parent Job server |
Name of the parent Job server. |
|
Executing server |
Name of the implementing server. The name of the server that exists physically and where the processes are handled.
This input is evaluated when the One Identity Manager Service is automatically updated. If the server is handling several queues, the process steps are not supplied until all the queues that are being processed on the same server have completed their automatic update. |
|
Queue |
Name of the queue to handle the process steps. The process steps are requested by the Job queue using this queue identifier. The queue identifier is entered in the One Identity Manager Service configuration file. |
|
Server operating system |
Operating system of the server. This input is required to resolve the path name for replicating software profiles. The values Win32, Windows, Linux, and Unix are permitted. If no value is specified, Win32 is used. |
|
Service account data |
One Identity Manager Service user account information. In order to replicate between non-trusted systems (non-trusted domains, Linux server), the One Identity Manager Service user information has to be declared for the servers in the database. This means that the service account, the service account domain, and the service account password have to be entered for the server. |
|
One Identity Manager Service installed |
Specifies whether a One Identity Manager Service is installed on this server. This option is enabled by the QBM_PJobQueueLoad procedure the moment the queue is called for the first time.
The option is not automatically removed. If necessary, you can reset this option manually for servers whose queue is no longer enabled. |
|
Stop One Identity Manager Service |
Specifies whether the One Identity Manager Service has stopped. If this option is set for the Job server, the One Identity Manager Service does not process any more tasks.
You can make the service start and stop with the appropriate administrative permissions in the Job Queue Info program. For more information, see the One Identity Manager Process Monitoring and Troubleshooting Guide. |
|
Paused due to unavailability of a target system |
Specifies whether task processing for this queue has been stopped because the target system that uses this Job server as a synchronization server is temporarily unavailable. As soon as the target system is available again, processing starts and all outstanding tasks are performed.
For more information about offline mode, see the One Identity Manager Target System Synchronization Reference Guide. |
|
No automatic software update |
Specifies whether to exclude the server from automatic software updating.
NOTE: Servers must be manually updated if this option is set. |
|
Software update running |
Specifies whether a software update is currently running. |
|
Server function |
Server functionality in One Identity Manager. One Identity Manager processes are handled with respect to the server function. |
Related topics
NOTE: All editing options are also available in the Designer under Base Data > Installation > Job server.
NOTE: More server functions may be available depending on which modules are installed.
Table 4: Permitted server functions
|
CSV connector |
Server on which the CSV connector for synchronization is installed. |
|
Domain controller |
The Active Directory domain controller. Servers that are not labeled as domain controllers are considered to be member servers. |
|
Printer server |
Server that acts as a print server. |
|
Generic server |
Server for generic synchronization with a custom target system. |
|
Home server |
Server for adding home directories for user accounts. |
|
Update server |
This server automatically updates the software on all the other servers. The server requires a direct connection to the database server that One Identity Manager database is installed on. It can run SQL tasks.
The server with the One Identity Manager database installed on it is labeled with this functionality during initial installation of the schema. |
|
SQL processing server |
It can run SQL tasks. The server requires a direct connection to the database server that One Identity Manager database is installed on.
Several SQL processing servers can be set up to spread the load of SQL processes. The system distributes the generated SQL processes throughout all the Job servers with this server function. |
|
CSV script server |
This server can process CSV files using the ScriptComponent process component. |
|
Generic database connector |
This server can connect to an ADO.Net database. |
|
One Identity Manager database connector |
Server on which the One Identity Manager connector is installed. This server synchronizes the One Identity Manager target system. |
|
One Identity Manager Service installed |
Server on which a One Identity Manager Service is installed. |
|
Primary domain controller |
Primary domain controller. |
|
Profile server |
Server for setting up profile directories for user accounts. |
|
SAM synchronization Server |
Server for synchronizing an SMB-based target system. |
|
SMTP host |
Server from which One Identity Manager Service sends email notifications. Prerequisite for sending mails using One Identity Manager Service is SMTP host configuration. |
|
Default report server |
Server on which reports are generated. |
|
Windows PowerShell connector |
The server can run Windows PowerShell version 3.0 or later. |
