|
|
|
You can configure the SAML Affiliate Agent to generate different levels of log messages. Choosing a log level can facilitate troubleshooting by dictating the severity and extent of the logged messages.
The following is an example of a log message that includes the log level. The log level is in bold.
3:49:57/94468/238/2>Process-User 'jstar' accessing resource /realmA/page1.html
The following table lists the log levels that you can select.
|
Log Level |
Type of Messages |
|---|---|
|
0 |
Critical error messages only with the least amount of detail. For example, the inability of the SAML Affiliate Agent to communicate with the SAML Affiliate Agent. This is the default log level. |
|
1 |
Warning error messages, trace messages, and flow state messages. These messages provide information about processes without a lot of detail. |
|
2 |
Various data messages, including those of the least importance, such as header details and cookie variables, with the highest level of detail. |
For the chosen log level, the SAML Affiliate Agent prints messages for that level and messages from any lower level. For example, if you choose level 2, the SAML Affiliate Agent prints all messages from levels 0 through 2.
To specify the log level
For example: <LogLevel>2</LogLevel>
Note: If the SAML Affiliate Agent uses SMConAPI to produce tracing messages, the following message may be included in the log: SMConAPI - Trace:at least one of the NETE_PS_RPPT or NETE_WA_ROOT has to be defined. You can ignore this message. When the Agent does not find either variable, it uses build-in variable values.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |