| |
|
| |
When the log method of a logging bean is called, the feedback facility generates a log event. A log event is also generated when a rule is executed. Log listeners process these log events and either store the event data or perform custom processing with these events. |
| |
|
| |
To implement rating logging, insert a Rating bean into your JSP. |
| |
|
| |
Create and set up the Feedback database. Then enable logging on the runtime server that hosts Feedback data. |
| |
|
| |
To implement Web usage logging, insert a PageView bean in your JSP. |
| |
|
| |
To implement custom logging, insert a CustomLog bean into your JSP. |
| |
|
| |
Log listeners process the log events originating from either logging beans or rules. |
| |
|
| |
When data is logged by either logging beans or rules, log events are generated and are routed to a controller for processing. LogManager is the class that implements this controller. There is a single instance of the LogManager within the Personalization runtime. It is responsible for receiving ... |
| |
|
| |
To implement action logging, insert an Action bean into your JSP. To log additional application data associated with the action, add keyvalue pair information to the log method call. |
| |
|
| |
If logging is enabled, rule information is automatically logged whenever a rule is executed. |
| |
|
| |
From time to time you may need to reset the web content event log. The event log can be reset only on a syndicator server. Any changes made by resetting the event log are then syndicated to its corresponding subscribers. In most cases you reset the event log on the server you have imported or ... |
| |
|
| |
If you encounter issues when syndicating, there are some common methods available to troubleshoot these issues. |
| |
|
| |
To implement custom logging, insert a CustomLog bean into your JSP. |
| |
|
| |
To implement action logging, insert an Action bean into your JSP. To log additional application data associated with the action, add keyvalue pair information to the log method call. |
| |
|
| |
Log listeners process the log events originating from either logging beans or rules. |
| |
|
| |
When the log method of a logging bean is called, the feedback facility generates a log event. A log event is also generated when a rule is executed. Log listeners process these log events and either store the event data or perform custom processing with these events. |
| |
|
| |
Create and set up the Feedback database. Then enable logging on the runtime server that hosts Feedback data. |
| |
|
| |
To implement rating logging, insert a Rating bean into your JSP. |
| |
|
| |
To implement Web usage logging, insert a PageView bean in your JSP. |
| |
|
| |
If logging is enabled, rule information is automatically logged whenever a rule is executed. |
| |
|
| |
When data is logged by either logging beans or rules, log events are generated and are routed to a controller for processing. LogManager is the class that implements this controller. There is a single instance of the LogManager within the Personalization runtime. It is responsible for receiving ... |
| |
|
| |
If you encounter issues when syndicating, there are some common methods available to troubleshoot these issues. |
| |
|
| |
To implement action logging, insert an Action bean into your JSP. To log additional application data associated with the action, add keyvalue pair information to the log method call. |
| |
|
| |
Log listeners process the log events originating from either logging beans or rules. |
| |
|
| |
To implement rating logging, insert a Rating bean into your JSP. |
| |
|
| |
Create and set up the Feedback database. Then enable logging on the runtime server that hosts Feedback data. |