立即与支持人员聊天
与支持团队交流

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

Example of communication during processing

The following example show the entries in the QBMDBQueueSlot table during processing.

  • Slot initialization

    Slot number Status Task name

    001

    0

     

  • Starts the process using the central dispatcher.

    Slot number Status Task name

    001

    1

     

  • The process is ready for operation. Preparations, for example, for temporary tables, are complete. The slot status is regularly tested.

    Slot number Status Task name

    001

    2

     

  • The central dispatcher distributes tasks. The central dispatcher checks slots for readiness and enters the task from DialogDBQueue table in the QBMDBQueueCurrent table with the slot number. The status of each slots is updated once the QBMDBQueueCurrent table has taken over.

    Slot number Status Task name

    001

    3

    OrgRoot

  • The process recognizes a task on the basis of the status, starts processing and updates its slots' status.

    Slot number Status Task name

    001

    4

    OrgRoot

  • The process has completed the processing and sets slot number in the DialogDBQueueCurrent table to 0. The process changes the status of its slots to operational.

    Slot number Status Task name

    001

    2

     

One Identity Manager Service configuration files

One Identity Manager Service is configured using a configuration file. The configuration file has to be in the same directory as the viNetworkService.exe. Two configuration files are supported:

Detailed information about this topic

Jobservice.cfg

The file Jobservice.cfg is an XML configuration file in One Identity Manager’s own simplified format. The advantage of this file is that run-time loading is supported. There is a configuration section in the file for each of the different modules in the One Identity Manager Service.

NOTE: Entries are case-sensitive. Both the sections and the names of the values must be written in lower case.

The root in the XML file is always called configuration. Each configuration file module and its values are defined in a category section respectively. At the moment the program only supports the System.Configuration.NameValueSectionHandler section type.

<configuration>

<category name="serviceconfiguration">

<value name="jobprovider">VI.JobService.MSSqlJobProvider,jobservice</value>

<value name="HttpPort">1180</value>

<value name="logwriter">VI.JobService.FileLogWriter,jobservice</value>

</category>

</configuration>

Example

Simple configuration with:

  • Direct connection to a SQL Server

  • Only one Job destination (JobProcessor)

<configuration>

<category name="serviceconfiguration">

<value name="jobprovider">VI.JobService.MSSqlJobProvider,jobservice</value>

<value name="logwriter">VI.JobService.FileLogWriter,jobservice</value>

</category>

<category name="sqlprovider">

<value name="connectstring">User ID=sa;initial Catalog=<Database>;Data Source=<SQL-Server>;Password=<Password></value>

</category>

<category name="filelogwriter">

<value name="loglifetime">0.01:00:00</value>

<value name="logseverity">Info</value>

</category>

<category name="dispatcher" />

<category name="jobdestinations">

<value name="queuex">VI.JobService.JobServiceDestination,jobservice</value>

</category>

<category name="queuex">

<value name="queue">\%COMPUTERNAME%</value>

</category>

</configuration>

Related topics

viNetworkService.exe.config

The viNetworkService.exe.config file is the default configuration file for .NET exes and has the specified format. There is a configuration section in the file for each of the different modules in the One Identity Manager Service.

NOTE: Entries are case-sensitive.

The root in the XML file is always called configuration. All other sections of the configuration file must be in the mandatory configSections section and their type must be defined. At the moment the program only supports the System.Configuration.NameValueSectionHandler section type.

<configuration>

<configSections>

<section name="sectionname" type="System.Configuration.NameValueSectionHandler" />

</configSections>

<sectionname>

...

</sectionname>

</configuration>

Example

Simple configuration with:

  • Direct connection to a SQL Server

  • Only one Job destination (JobProcessor)

<configuration>

<configSections>

<section name="serviceconfiguration" type="System.Configuration.NameValueSectionHandler" />

<section name="sqlprovider" type="System.Configuration.NameValueSectionHandler" />

<section name="filelogwriter" type="System.Configuration.NameValueSectionHandler" />

<section name="dispatcher" type="System.Configuration.NameValueSectionHandler" />

<section name="jobdestinations" type="System.Configuration.NameValueSectionHandler" />

<section name="queuex" type="System.Configuration.NameValueSectionHandler" />

<section name="plugins" type="System.Configuration.NameValueSectionHandler" />

</configSections>

<serviceconfiguration>

<add key="jobprovider" value="VI.JobService.MSSqlJobProvider,jobservice" />

<add key="logwriter" value="VI.JobService.FileLogWriter,jobservice" />

</serviceconfiguration>

<sqlprovider>

<add key="ConnectString" value="User ID=sa;initial Catalog=<Database>;Data Source=<SQL-Server>;Password=<Password>" />

</sqlprovider>

<filelogwriter>

<add key="LogLifeTime" value="0.01:00:00" />

<add key="LogSeverity" value="Info" />

</filelogwriter>

<dispatcher />

<jobdestinations>

<add key="QueueX" value="VI.JobService.JobServiceDestination,jobservice" />

</jobdestinations>

<queuex>

<add key="queue" value="\%COMPUTERNAME%" />

</queuex>

</configuration>

Related topics
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级