CA Single Sign On Secure Proxy Server (SiteMinder)AXIOMATICS POLICY SERVERCA Single Sign On SOA Security Manager (SiteMinder)CA Single Sign-On
Issue/Introduction
Sometimes it may be necessary to enable logging of the OneView monitor for troubleshooting. But the manual configuration is not necessarily clear so it may not work properly.
The default trace.conf is broken into 3 sections, Common Settings, API Logging Levels, and Infrastructure modules logging.
# There are three levels: # 0 - no trace events # 1 - error and warning trace events # 2 - all trace events
# Common logging settings nete.enableConsoleLog=0 nete.enableFileLog=0 nete.logFile=
# Connection API logging levels. There are three levels: 0 - no trace events, 1 - error and warning trace events, # 2 - all trace events nete.conapi.logLevel=1 nete.conapi.ipc.logLevel=1 nete.conapi.tcpip.logLevel=1
Here is what the trace.conf looks like when you enable all trace events to be written out to a log file, monitor.log
# Common logging settings nete.enableConsoleLog=0 nete.enableFileLog=1 nete.logFile=C:\\Program Files\\CA\\siteminder\\config\\monitor.log
# Connection API logging levels. There are three levels: 0 - no trace events, 1 - error and warning trace events, # 2 - all trace events nete.conapi.logLevel=2 nete.conapi.ipc.logLevel=2 nete.conapi.tcpip.logLevel=2