Global.cfg
The Global.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. The text is case sensitive. Each of the different modules has its own section allocated within the file.
You can find an example of a configuration file on the installation medium in directory QBM\dvd\AddOn\SDK\ConfigSample. If the file Global.cfg is in the program directory, it is used when the One Identity Manager tools start up.
The root in the XML file is always called configuration. Each configuration file module and its values are defined in a section category respectively.
|
|
NOTE: Both the sections and the names of the values must be written in lower case. |
Format of Global.cfg
<configuration>
<category name="settings">
<value name="language">English</value>
<value name="autoupdateenabled">true</value>
<value name="connectiontimeout">15</value>
</category>
<category name="connections">
<value name="database display 1">ConnectionString</value>
<value name="database display 2">ConnectionString</value>
</category>
</configuration>
|
|
TIP: Use the program "Config Encryptor" to create the connection string. You will find this program on the installation medium in the directory QBM\dvd\AddOn\ConfigEncryptor. |
Related Topics
One Identity Manager Service Configuration Files
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. The text is case sensitive. There is a configuration section in the file for each of the different modules in the One Identity Manager Service.
The root in the XML file is always called configuration. Each configuration file module and its values are defined in a section category respectively. At the moment the program only supports the section type "System.Configuration.NameValueSectionHandler".
|
|
NOTE: Both the sections and the names of the values must be written in lower case. |
<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 for a simple configuration with:
- direct connection to an 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. The text is case sensitive. There is a configuration section in the file for each of the different modules in the One Identity Manager Service.
The root in the XML file is always called configuration. All other sections of the configuration file must be in the mandatory section configSections and their type must be defined. At the moment the program only supports the section type System.Configuration.NameValueSectionHandler.
<configuration>
<configSections>
<section name="sectionname" type="System.Configuration.NameValueSectionHandler" />
</configSections>
<sectionname>
...
</sectionname>
</configuration>
Example for a simple configuration with:
- direct connection to an 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>