Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Validity check on configuration file

The verification test ensures that the minimum requirements for a configuration file are met.

To start the validity check in the One Identity Manager Service configuration

  • Use the button to test the configuration.

    Errors and warnings are sent to a message window.

Table 85: Verification Test Error Output
Error Output
No Job provider found. Error
No Logwriter found. Error
No input in compulsory field. Error
No Job destination found. Warning
No plugins found. Warning
Related Topics

Process collection module

In this module you define the Job providers. The Job provider supplies a Job destination process step and evaluates the result. The following module types may be selected:

You can configure any number of Job providers in one configuration file. The associated configuration sections are determined by name. Therefore, you should rename Job providers that are added.


The MSSQLJobProvider handles One Identity Manager database process requests on an SQL Server.

Table 86: MSSQLJobProvider parameters



Connection parameter (ConnectString)

Access data for the database server and the database to be used

Table 87: SQL Server Database Connection Data
Data Description


Database server.

Windows authentication

Specifies whether integrated Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.


SQL Server Login name.


SQL Server login password.



Max. number of pending requests (RequestQueueLimit)

The process requests are internally cached. This parameter defines the maximum number of cache entries. The default value is 1000.

Max. number of pending results (ResultQueueLimit)

The process results are internally cached. This parameter defines the maximum number of cache entries. The default value is 10000.


Data transfer takes place in the FileJobProvider by means of files. Process requests and results are written to file or read from file. These files can be processed by the FileJobDestination.


Table 88: FileJobProvider parameters



Backup of transferred files (BackupFiles)

If this option is enabled, all files (with or without errors) are moved to a Backup subdirectory. In the default case (not set) only files with errors are saved.

Check file index (CheckInputIndex)

If this option is set, the file name index is checked to see if has increased in size. Files with the same or a lower index are not processed. This option is not set by default.

Max. number of process trees in a transfer file (MaxListCount)

Maximum number of process steps that can be grouped together as a file. This allows limiting of the file size.

Use encryption (UseEncryption)

Specifies whether the data is to be written to the files in encrypted form.

NOTE: The setting for encryption must be identically configured in the job provider and the related job destination.

Notification methods (EventTypes)

The job provider supports three different methods for providing notification about new data. The notification methods can be combined when separated by commas.



Table 89: Supported notification methods
Method Description


Newly stored data is queried at defined intervals.


The provider queries the parent Job server via HTTP and processes the stored data once the server replies.


Newly stored data is queried after a file system event.

Remote host for HTTP notification (HostName)

If using the HTTP notification method, enter the name of the remote host here to which the queries are transferred.

HTTP notification port (Port)

If using the HTTP notification method, enter the port for transfer here.

File lookup timer interval (ms) (TimerInterval)

If using the TIMER notification method, enter the interval in milliseconds here.

Input directory (InputDirectory)

The module reads and processes the process files (*.fjg) in this directory.

NOTE: Ensure that the job provider and related job destination use the same directory. Input directory and output directory are then reversed accordingly.

Output directory (OutputDirectory)

Directory to which the processed files are written.

Subdirectories (SubDirectories)

You can enter a list of directory names separated by a pipe character (|) here. All the directories are then monitored and processed correspondingly. The following directory structure is expected:

SubDirectories = "ServerA|ServerB"








where Request and Response are the directories specified in the Input directory (InputDirectory) and Output directory (OutputDirectory) parameters.

NOTE: You can only use the Timer notification method. The HTTP and FSEvent notification methods are not available.

Automatic identification of subdirectories (AutoSubDirectories)

If this option is enabled, the module automatically processes all the files in the subdirectories. Processing is not recursive.

Related Topics
Related Documents