This section contains the following topics:
Change the SiteMinder WSS Agent Log File Name
Append Messages to an Existing SiteMinder WSS Agent Log File
Set the SiteMinder WSS Agent File Log Level
Roll Over the SiteMinder WSS Agent Log File
Disable SiteMinder WSS Agent XML Message Processing Logging
SiteMinder WSS Agent Log Configuration File Summary
Set Log Files, and Command-line Help to Another Language
The SiteMinder WSS Agent logger for application servers is implemented using Apache’s log4j. For more information, see http://logging.apache.org/log4j/docs/.
Two log files provide important information about the SiteMinder WSS Agent:
This SiteMinder WSS Agent writes information about its standard operations and performance to the SiteMinder WSS Agent log.
By default, SiteMinder WSS Agent logging is enabled and written to the XmlAgent.log file in:
You can change SiteMinder WSS Agent logging parameters by editing the log-config.properties file located in:
Note: These are the default values; the logging configuration file name and location can be changed by editing the log.log-config-properties JVM system property.
In addition to its standard logging functionality, SiteMinder WSS Agents for IBM WebSphere also log information relating specifically to their processing of XML messages. Like the SiteMinder WSS Agent log, the XML message processing log is also implemented using Apache’s log4j standard.
Note: SiteMinder WSS Agent XML message processing logging does not start until an XML message that needs to be processed is received.
By default, SiteMinder WSS Agent XML message processing logging is enabled and written to the soasm_agent.log file in:
You can change SiteMinder WSS Agent XML message processing logging parameters by editing the log.config file, which can be found in:
To change pathname of the SiteMinder WSS Agent log file, edit the log.logfile-pattern parameter. Possible values are valid pathnames. If you specify a relative value, the path is set relative to the JAVA_AGENT_ROOT JVM system property.
Default value: "log\XmlAgent.log"
For example:
log.logfile-pattern=log\XmlAgent.log
To add logging information to an existing SiteMinder WSS Agent log file instead of rewriting the entire file each time logging is invoked, add the log.logfile-append-on-reset parameter.
For example:
log.logfile-append-on-reset=YES
To change the SiteMinder WSS Agent log level, edit the log.logging-level parameter. Possible values are:
Default value: WARNING
For example:
log.logging-level=INFO
To change file size limit at which the SiteMinder WSS Agent log should rollover, change the log.logfile-limit parameter. Rolling over a log file starts a new log file, preventing a single log file from becoming unmanageable. Possible values are numbers, representing kilobytes.
The default value is 1000.
For example:
log.logfile-limit=512
To disable SiteMinder WSS Agent XML message processing logging, remove or comment out (using a "#" prefix) the following lines from the log.config file located in the Agent config subdirectory:
log4j.appender.A2=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A2.File=${NETE_TXM_ROOT}/bin/soasm_agent.log
The SiteMinder WSS Agent logging configuration file defines default SiteMinder WSS Agent logging settings.
Available configuration parameters are:
|
Name |
Description |
|---|---|
|
log.logfile-append-on-reset |
Add logging information to an existing log file instead of creating a new file each time logging is invoked. Default value: no |
|
log.logfile-pattern |
Specifies the pathname (relative to WSS_Home) of the SiteMinder WSS Agent log file. Default value: log/XmlAgent.log |
|
log.logging-level |
Defines the logging level. The levels are:
Default value: WARNING |
|
log.logfile-limit |
Specifies the size limit, in kilobytes Rollover a log file after it reaches the specified size. Default value: 1,000KB |
Note: Once the SiteMinder WSS Agent connects to the Policy Server, corresponding logging settings found in the Agent Configuration Object override the values in log-config.properties.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|