There are two parameters available in the One Identity Manager Service configuration module that you can use to extend debugging functionality:
One Identity Manager Service writes more detailed data into the log file if the parameter "DebugMode" is set, for example, all parameters that are passed to a component as well as the processing results together with OUT parameters.
Individual One Identity Manager Service process components can output additional process data to the One Identity Manager Service log file. To do this you set the parameter "ComponentDebugMode" in the configuration module. You should only use "ComponentDebugMode" for localizing errors because the effect on performance means that it is not recommended for normal use.
|Common\Jobservice\DoReturnOutput||The entire output of the parameter is written to the One Identity Manager Service log file when a error occurs in the case of process task that supply an extended return value.|
Individual process components have process tasks with parameters that supply extended return values (OUT). The entire output of the parameter is written to the One Identity Manager Service log file when a error occurs. For example, when a command or program is executed using the process component "CommandComponent", the output text for the command or program can be returned.
To log return values
You can use the script engine methods RaiseMessage and AppData.Instance.RaiseMessage from within process steps to write output messages to the One Identity Manager Service log file. Use the process component "ScriptComponent" to run the script.
Messages are marked in color in the log file depending on the severity level (parameter "MsgSeverity").
Figure 65: Example Output of Messages to a One Identity Manager Service Log File
The output is consolidated with other messages and logged at the end of processing the process step.
RaiseMessage (MsgSeverity, "string")
RaiseMessage (MsgSeverity.Warning, "Example warning message")
RaiseMessage (MsgSeverity.Info, "Example Info message")
RaiseMessage (MsgSeverity.Serious, "Example error marked message")
This output is written immediately during processing; not taking into account the end of the process step.
AppData.Instance.RaiseMessage (MsgSeverity, "string")
AppData.Instance.RaiseMessage (MsgSeverity.Warning, "Example warning message")
AppData.Instance.RaiseMessage (MsgSeverity.Info, "Example Info message")
AppData.Instance.RaiseMessage (MsgSeverity.Serious, "Example error marked message")
For more examples of One Identity Manager Service log file output, see the script example on the installation medium in the directory QBM\dvd\AddOn\SDK\ScriptSamples.
IMPORTANT: You should never use the VB.Net functions Msgbox and Inputbox on servers. Use the functions VID_Write2Log, RaiseMessage or AppData.Instance.RaiseMessage.
To write One Identity Manager Service messages in the server’s event view, the module "EventLogLogWriter" has to modified in the One Identity Manager Service configuration file.
Following parameters are available:
Enter the name for the event log to which the messages should be written. The messages are written to the application log if the default value "Application" is used.
NOTE: If several One Identity Manager Service write event logs on a server, ensure that the first 8 letters of the log name are unique.
Specifies the warning level for logging messages. By default, only warnings and serious errors are logged.
|Info||All messages are written to the event log. The event log quickly becomes large and confusing.|
|Warning||Only warnings and exception errors are written to the event log (default).|
|Serious||Only exception errors are written to the event log (exceptions).|
Define an ID with which messages are written in the event log.
Define a category with which messages are written to the event log.
Define a name for the source with which messages are written to the event log.
Process handling error can also be written to a server’s result log. To do this use the process component "LogComponent".