UDS (arcotuds.log)
- Navigate to <ARCOT_HOME>\conf directory.
- Edit udsserver.ini and change “ERROR” to “DEBUG” and “INFO” to “DEBUG”. The example below is turning debug
- Restart the Application Server.
Before: log4j.rootCategory=ERROR, debuglog
After: log4j.rootCategory=DEBUG, debuglog
Before: log4j.logger.com.arcot.euds=INFO
After: log4j.logger.com.arcot.euds=DEBUG
Admin Console (arcotadmin.log)
- Navigate to <ARCOT_HOME>\conf directory.
- Edit adminserver.ini and change “ERROR” to “DEBUG” and “INFO” to “DEBUG” on operations you want to debug. The example below is turning debug on the UDS modules that Admin interacts with.
- Restart the Application Server.
Before: log4j.rootCategory=ERROR, roothandle
After: log4j.rootCategory=DEBUG, roothandle
Before: log4j.logger.com.arcot.euds=INFO
After: log4j.logger.com.arcot.euds=DEBUG
Authentication Flow Manager (arcotafm.log)
Advanced Authentication 7.1 and above releases - (Adapter 2.2.9 and above)
- Navigate to <ARCOT_HOME>\conf\afm directory.
- Edit arcotafm-log4j.properties and change “INFO” to “DEBUG” on operations you want to debug then save. The example below is turning debug on the front-end Authentication Flow Manager modules. The application server restart is required.
Adaptershim (adaptershim.log on CA Siteminder Policy Server)
- Navigate to <ARCOT_HOME>\conf on the CA Siteminder box.
- Edit adaptershim.ini file and set debug parameter as such- “HandleLevel=1”.
- Save adaptershhim.ini
- The parameter will turn debug on in about 5 minutes; a restart of the CA Siteminder Policy Server is not required.