|NOTE: The templates are only available in the program "Job Service Configuration".|
Templates for a One Identity Manager Service configuration are supplied.
This template already contains the most important modules with settings for a simple One Identity Manager Service configuration with a direct connection to a SQL Server. You can load the template using the menu item Templates | SQL server direct. After loading, the configuration the template needs to be modified as required.
This template already contains the most important modules with settings for a simple One Identity Manager Service configuration with a direct connection to a Oracle Database. You can load the template using the menu item Templates | SQL server direct. After loading, the configuration the template needs to be modified as required.
Each of the configuration sections are listed in the module list. A selection of module types is available for certain modules.
To select a module type
To change the name of a module type
To delete a module type
To edit a parameter value
When a item is selected in the module list, all possible parameters and their values are displayed. You can change some values by clicking in input field or on the option button in the Value column.
NOTE: The parameter description in each module contains the parameter name, in brackets, which is used in the configuration file.
The following icons are used:
|The parameter is preset with a standard value. The value is passed as a string.|
|Compulsory input. The parameter must be altered as required. The value is passed as a string.|
|The parameter is preset with a standard value. The value is passed as an integer.|
|The parameter can be activated and deactivated.|
|This parameter is added during run-time. The One Identity Manager Service does not need to be restarted.|
|The parameter takes effect after the One Identity Manager Service is restarted.|
The verification test ensures that the minimum requirements for a configuration file are met.
To start the verification test
Use the button to test the configuration.
Errors and warnings are sent to a message window.
|No Job provider found.||error|
|No Logwriter found.||error|
|No input in compulsory field.||error|
|No Job destination found.||warning|
|No plugins found.||warning|
The server service "One Identity Manager Service" ensures distribution in the network of data managed in the One Identity Manager database. The One Identity Manager Service performs data synchronization between the database and any connected target systems and executes actions at the database and file level. The One Identity Manager Service retrieves process steps from the JobQueue. Process steps are executed by process components. One Identity Manager Service also creates an instance of the required process component and passes the parameters to the process step. Decision logic monitors the execution of the process steps and determines how processing should continue depending on the results of the executed process components. The One Identity Manager Service enables parallel processing of process steps because it can create several instances of process components.
A Job provider function makes a Job destination process step available within the One Identity Manager Service. The Job destination function handles the process steps and returns a result to the Job provider. The Job provider evaluates the result.
The combination of a Job provider on one server and a Job destination on another server is called a "Job gate". The Job provider and Job destination are configured within the Jobgate such that they can communicate with each other.
Figure 42: One Identity Manager Service Operating Mode
|MSSQLJobProvider||The MSSQLJobProvider collects process steps from the One Identity Manager database under SQL Server and sends them to a Job destination.|
|OracleJobProvider||The OracleJobProvider collects process steps from the One Identity Manager database under Oracle Database and sends them to a Job destination.|
The FTPJobProvider reads process queries and results from files and writes them to file. These files can be processed by FileJobGate (File or FTP Job destination). The data is transferred using these files.
The FTPJobProvider is based on the functionality of the FileJobProvider. The FTPJobProvider reads process queries and results from files and writes them to file. After the files have been created in the local directory, the FTPJobProvider connects to the FTP server and transfers all the files. A connection is also made to the FTP Server when it gets a signal and the data is collected.
The HTTPJobProvider receives process steps from a parent Job server. The data transfer is done by HyperText Transfer Protocol (HTTP).
The AppServerJobProvider gets process steps from the application server and sends them to a Job destination.
|JobServiceDestination||The JobServiceDestination is the One Identity Manager Service component that actually deals with handling process steps. It requests the process steps from the Job provider, processes them with the process component and returns the result.|
|FileJobDestination||The FileJobDestination processes the process steps that are queued by the FileJobGate (FileJobProvider or FTPJobProvider) and returns the results to the Job provider.|
|FTPJobDestination||The FTPJobDestination handles the process steps that are queued in the FileJobGate (FileJobProvider or FTPJobProvider) and returns the results to the Job provider.|
|HTTPJobDestination||An HTTPJobDestination sends process steps to a follow-on Job server. The data transfer is in HyperText Transfer Protocol.|
|HTTPJobGate||Consists of HTTPJobProvider and HTTPJobDestination.|
|FileJobGate||Consists of FileJobProvider, FileJobDestination, FTPJobProvier and FTPJobDestination. JobProvider and JobDestinations can be combined with each other.|
Figure 43: Example Configuration for FileJobGate