Setting up a Server for Data Provisioning in a Custom Target System
Setting up a Server for Data Provisioning in a Custom Target System
You can define a server for each custom target system, which executes all the One Identity Manager Service actions required for provisioning target system objects.
To set up a server
- Provide a server installed with the One Identity Manager Service.
- Create an entry for the Job server in the Manager.
- Select the category Custom target systems | Basic configuration data | Servers.
-
Click
in the result list toolbar.
- Edit the Job server's master data.
- Save the changes.
- Enter the server as the synchronization server in the custom target system.
Detailed information about this topic
- Master Data for a Job Server
- Customizing Data Synchronization for a Custom Target System
- For more detailed information about installing and configuring the One Identity Manager Service, see the One Identity Manager Installation Guide.
Master Data for a Job Server
|
|
NOTE: All editing options are available to you in the Designer, in the category Base Data | Installation | Job server. |
|
Property |
Meaning | ||
|---|---|---|---|
| Server | Job server name. | ||
| Full server name | Full server name in accordance with DNS syntax.
Example: <Name of servers>.<Fully qualified domain name> | ||
| Target System | Computer account target system. | ||
| Language culture | Language of the server. | ||
| Server is cluster | Specifies whether the server maps a cluster. | ||
| Server belongs to cluster | Cluster to which the server belongs.
| ||
| 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. Only the methods "Robocopy" and "Rsync" are currently supported.
If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication then takes place between servers with a Windows operating system using "Robocopy" and between servers with the Linux operating system using "rsync". 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 executing server. The name of the server that exists physically and where the processes are handled.
This input is evaluated when 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. Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the job queue using exactly this queue name. 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. Permitted values are "Win32", "Windows", "Linux" and "Unix". If the input is empty, "Win32" is assumed. | ||
| 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 procedure QBM_PJobQueueLoad 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 program "Job Queue Info". | ||
| No automatic software update | Specifies whether to exclude the server from automatic software updating.
| ||
| Software update running | Specifies whether a software update is currently being executed. | ||
| Server Function | Server functionality in One Identity Manager. One Identity Manager processes are handled depending on the server function. |
Related Topics
Specifying Server Functions
|
|
NOTE: All editing options are available to you in the Designer, in the category Base Data | Installation | Job server. |
|
|
NOTE: More server functions may be available depending on which modules are installed. |
|
Server Function |
Remark |
|---|---|
| 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 controller are considered to be member servers. |
|
Printer server |
Server which 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 executes automatic software updating of all other servers. The server requires a direct connection to the database server that the One Identity Manager database is installed on. The server can execute SQL tasks. The server with the installed One Identity Manager database, is labeled with this functionality during initial installation of the schema. |
|
SQL processing server |
This server can process SQL tasks. 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. |
|
Native database connector |
The 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 executes synchronization with the target system One Identity Manager. |
|
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 running synchronization with an SMB-based target system. |
|
SMTP host |
Server from which the One Identity Manager Service sends email notifications. Prerequisite for sending mails using the 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. |
Post-Processing Outstanding Objects
Post-Processing Outstanding Objects
Objects from custom target systems can be loaded in to the One Identity Manager database at regular intervals by custom processes. This gives you the option to either delete objects directly in the One Identity Manager database or mark them as outstanding, if they do not exist in the target system. For more information, see the One Identity Manager Target System Synchronization Reference Guide.
Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizing. This prevents objects being deleted because of an incorrect data situation or an incorrect synchronization configuration.
Objects marked as outstanding:
- Cannot be edited in One Identity Manager.
- Are ignored by subsequent synchronization.
- Must be post-processed separately in One Identity Manager.
Start target system synchronization to do this.
To allow post-processing of outstanding objects
- Configure target system synchronization on the target system type of the target system to be synchronized.
For more information, see Configuring Target System Synchronization.