+

Search Tips   |   Advanced Search

Administer Portlet load monitoring

    Portal wide configuration

    We can do the following ConfigEngine tasks for Portlet load monitoring:

    • Enable or disable Portlet load monitoring in the portal.

    • Set the sample number of requests by which the average response time for portlets is calculated. For example, if set the sample number to 50, the average response time is calculated from the latest 50 requests that this portlet served. This setting is related to the average response time setting listed under administrative tasks.

    Perform both of these tasks in the WAS admin console. These settings apply to all portlets that Portlet load monitoring monitors.

    Portlet preferences configuration and administration

    We can set the following parameters for individual portlets in the portlet preferences. We can either configure these parameters portlet.xml before deploying the portlet or administer them later using the Manage Portlets administration portlet:

    • Maximum number of concurrent requests allowed for a portlet

    • Reactivation limit of concurrent requests allowed for reactivating the portlet

    • Allowed average response time. We can configure the sample number of requests by which this average response time for portlets is calculated as mentioned previously under ConfigEngine tasks.

    Portlet load monitoring administration

    We can also do the following administrative tasks on individual portlets using the Manage Portlets portlet only:

    • Check whether a portlet is being monitored by Portlet load monitoring

    • Manually reenable a portlet that Portlet load monitoring has blocked

    • Manually block a portlet being monitored by Portlet load monitoring from responding to requests.


Parent Portlet load monitoring for WebSphere Portal