How to set up SQL logging, Job-Generation-Logs and Object-Logs for various Front Ends, i.e. Manager, Designer.
On the server where Quest One Identity Manager is installed, in the directory (by default) C:\Program Files (x86)\Quest Software\Quest One Identity Manager there are several ".exe.config" files, for example, "Manager.exe.config".
Edit this file using notepad (an example of the file is attached).
Logging is controlled by the following line:
<section name="connectionbehaviour" type="System.Configuration.NameValueSectionHandler" />
And this section:
<!-- Directory for SQL-Logs -->
<add key="SqlLogDir" value="" />
<!-- Directory for Job-Generation-Logs -->
<add key="JobGenLogDir" value="" />
<!-- Directory for Object-Logs -->
<add key="ObjectLogDir" value="" />
<!-- Life time of the logs above. (in days) -->
<add key="LogLifeTime" value="1" />
<!-- No beep tone while reloading data. -->
<add key="NoReloadBeep" value="False" />
Populate the value="" with a file path in order to enable logging.
Please note, to configure these logs for the jobservice, determine first whether the job is set to internal or external execution. For internal jobs, the file viNetworkService.exe is used, and for external jobs, the config file has to be named stdioprocessor.exe.config.
Please note that the behaviour may be overridden by registry values beneath HKCU\Software\Quest Software\Identity Manager\*\ConnectionBehaviour.
One Identity does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 "Description of the Microsoft Windows registry" at Microsoft Support.