Log and audit events

Portlet load monitoring allows you to log events. For example, this can help you audit events. When Portlet load monitoring blocks or enables a portlet, it creates a log file entry in the WebSphere Portal log file SystemOut.log . This log file entry contains the portlet object ID, the portlet name, the WAR file name of the portlet and the EAR file display name. The log file entries consist of translated messages. If you use tools that monitor log files for events, you can check for log file entries related to Portlet load monitoring as described in the following.
Portlet load monitoring blocks a portlet because the portlet exceeds the maximum number of requests.


Portlet load monitoring blocks a portlet because the portlet exceeds the average response time.


Portlet load monitoring activates a portlet because the portlet returns to the reactivation limit.


Administrator manually blocks requests to a portlet.


Administrator manually unblocks requests to a portlet.

In the log entry, the variables Object_ID, Portlet_Name, War_File_Name, EAR_File_Dislay_Name, admin_user_ID are substituted with the corresponding values for the affected portlet and the administrative user.
Example: If Portlet load monitoring blocks a portlet with the portlet name StdWorldClock because the portlet exceeded the maximum number of requests allowed, then the log file entry might look like this:

EJPPG3001W: Portlet load monitoring disabled the portlet with 
   ObjectID:  [ObjectIDImpl '3_MLSU3F540O0360ISG212TT2003', 
             PORTLET_DEFINITION, VP: 0, 
              [Domain: rel], DB: 0000-B6723F5E2100836180E45004D1BB0060], 
   portlet name: StdWorldClock, 
   WAR file name: StdWorldClock.war, 
   EAR file display name: PA_StandardWorldClock 
because portlet exceeded its maximum number of requests.


Parent

Portlet load monitoring for WebSphere Portal

 


+

Search Tips   |   Advanced Search