Set the logging level from the command line
Use the psdebug program on an application server to configure logging output from various Bravura Security Fabric software components. It is helpful when troubleshooting installation or functionality problems.
The psdebug utility allows for adding specific exceptions (one binary or script at a time) to global application-wide logging settings configured in the Logging Service, for more refined logging. Using psdebug allows for smaller, more relevant and more readable logs; there is less interference from other subsystems when troubleshooting a specific issue.
Open an Administrative instance prompt
Execute the psdebug command by running:
util\psdebug -level 6 -prog <executable>
where <executable> is the name, without file extension , of the core product binary, script (default or custom), connector pack agent or interface for which we want to increase logging specifically. The debug level for most binaries is 5, but here we use 6 as the increased debug level for some agents and interfaces.
For example, to enable the most detailed logging (Verbose = 99) for the Active Directory DN agent, the command to execute would be:
util\psdebug -level 99 -prog agtaddn
If more than one binary, custom script, or connector pack agent is relevant to the issue, repeat the last step as necessary.
To create an
idmsuite.logfile which contains only the time period in which the issue is reproduced, execute the command:service\idmsuite.exe -rotatelog
If the affected binary is a service, ensure the log level change takes effect by executing:
service\idmlogsvc.exe -trace-restart
Execute the steps required to reproduce the issue.
To remove the additional logging settings added at step 2 (change "
agtaddn" to match the required binary) execute:util\psdebug -remove -prog agtaddn
If the affected binary is a service, apply the default settings by execurting:
service\idmlogsvc.exe -trace-restart
See psdebug usage for more command-line usage information and examples.