サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.0 LTS - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing 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
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Configuring the Job server for connecting to the application server

To configure the Job server for connecting to the application server

  • Declare the Job server in the One Identity Manager database.

  • Install the One Identity Manager Service and configure the AppServerJobProvider for process collection.

  • To generate processes through an application server, enter the connection data in the Job server.

    • Enter the connection data for the application server.

    • Label the Job server with the No direct database connection option and assign the connection data to the application server.

Related topics

The One Identity Manager Service functionality

The One Identity Manager Service enables the distribution throughout the network of information that is administrated in the One Identity Manager database. The One Identity Manager Service performs data synchronization between the database and any connected target systems and runs actions at the database and file level.

Process steps are run by process components. The One Identity Manager Service also creates an instance of the required process component and transfers the process step parameters. Decision logic monitors the performance of the process steps and determines how processing should continue depending on the results of the run process components.

For more information about installing and updating the One Identity Manager Service, see the One Identity Manager Installation Guide.

For more information about logging and monitoring process handling and support for troubleshooting, see the One Identity Manager Process Monitoring and Troubleshooting Guide.

Related topics

Handling processes with the One Identity Manager Service

The processing tasks for the One Identity Manager Service are saved in the Job queue (JobQueue table) for a defined queue. A One Identity Manager Service can process several queues. The queues that a One Identity Manager Service can process are declared in the One Identity Manager Service's configuration. A Job server must be known in the One Identity Manager database for each queue. The One Identity Manager Service queries the Job queue to see which processes are waiting for its own queue. A queue is initialized when the One Identity Manager Service starts.

The process requests and processing results are cached internally in a request queue (RequestQueue) and a result queue (ResultQueue). The request queue is processed in parallel to the result queue. The following requests use the two internal queues:

  • Request queue

    • Request for pending process steps

    • Request for statistics data

  • Results queue

    • Process results request

    • Processing status request

    • Request for events

    • Initial request of the pending process step when the One Identity Manager Service starts up. This ensures that any missing processing results in the database have arrived before enabling process steps that still have Loaded status.

When the One Identity Manager Service is downloaded, any requests that may still be in the results queue are serialized in a file that is processed the next time the One Identity Manager Service starts. This should ensure that no processing results go missing. The backup files are kept in the local program data directory (%APPDATA%\One Identity\One Identity Manager\JobService).

Related topics

Parallel processing of processes by the One Identity Manager Service

The One Identity Manager Service enables parallel processing of process steps because it can create several instances of process components. You specify for each process component and its process tasks on an individual basis whether parallel processing of process steps is possible.

Parallelization is affected by the following properties of the process components and process tasks.

  • Maximum number of valid instances of one process task (JobTask.MaxInstance)

    Permitted values are:

    • -1: All instances of this process task are processed sequentially. Other process task instances of the same process component are not run simultaneously.

    • 0: The maximum number of instances given for the process component is used.

    • 1 or greater: The exact number of instances of a process task, which are processed simultaneously.

  • Maximum number of valid instances of one process component (JobComponent.MaxInstance)

    The value is only used if the maximum number of instances of a process task is set to 0. Otherwise, the value applies that is set for the process task.

    Permitted values are:

    • -1: All instances of this process component are processed sequentially.

      It must be ensured that these components are run exclusively on one Job server, which means no other queue can exist to process these components.

    • 0: All instances of this process component can be processed simultaneously.

    • 1 or greater: The exact number of instances of a process component, which are processed simultaneously.

  • Specifies whether it is necessary to run one process task per object (JobTask.IsExclusivePerObject)

    If this option is enabled in a process task, only one process step with this process task can be run for a specific object. There is no parallel processing.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択