|
|
|
This section provides references on how to troubleshoot an environment with IBM WebSphere Portal and IBM Connections installed. |
|
|
|
Create and set up the Feedback database. Then enable logging on the runtime server that hosts Feedback data. |
|
|
|
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 Web usage logging, insert a PageView bean in 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 run-time. It is responsible for receiving ... |
|
|
|
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. |
|
|
|
To implement rating logging, insert a Rating bean into your JSP. |
|
|
|
If logging is enabled, rule information is automatically logged whenever a rule is executed. |
|
|
|
If you encounter issues when syndicating, there are some common methods available to troubleshoot these issues. |
|
|
|
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 run-time. It is responsible for receiving ... |
|
|
|
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. |
|
|
|
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 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. |
|
|
|
To implement Web usage logging, insert a PageView bean in your JSP. |
|
|
|
To implement custom logging, insert a CustomLog bean into your JSP. |
|
|
|
If logging is enabled, rule information is automatically logged whenever a rule is executed. |
|
|
|
If you encounter issues when syndicating, there are some common methods available to troubleshoot these issues. |
|
|
|
To implement Web usage logging, insert a PageView bean in your JSP. |
|
|
|
To implement rating logging, insert a Rating bean into your JSP. |
|
|
|
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. |
|
|
|
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 run-time. It is responsible for receiving ... |