Administer portlet preferences for Portlet load monitoring
Overview
You can set portlet preferences to influence in which cases Portlet load monitoring blocks or reenables JSR portlets.
- Maximum number of concurrent requests
- Reactivation limit of concurrent requests for reactivating the portlet
- Allowed average response time. Sample number of requests by which this average response time for portlets is calculated as mentioned above under configuration tasks.
Set parameters
- Log in to the portal and select...
Administration | Portlet Management | Portlets | portlet | Configure Portlet
- To set the maximum number of requests allowed for this portlet, set...
com.ibm.wps.pe.plm.maxrequest = xyz
For example, to allow this portlet no more than 15 concurring requests, specify...
com.ibm.wps.pe.plm.maxrequest = 15
- To set the reactivation limit for this portlet, set...
com.ibm.wps.pe.plm.minrequest = xyz
For example, to this portlet be reenabled when concurrent requests fall back to 5 or below, specify...
com.ibm.wps.pe.plm.minrequest = 5
- To set the allowed average response time for this portlet, set...
com.ibm.wps.pe.plm.average.time.processing = xyz
.where xyz is the average response time in milliseconds.
For example, if you specify...
com.ibm.wps.pe.plm.average.time.processing = 3000
.and the average response time for this portlet exceeds 3 seconds, then Portlet load monitoring blocks further requests to this portlet.
- Click the Add button to set the preference.
- Save changes by clicking the OK button.
As an alternative, you can define a portlet preference before deploying the portlet. In this case set the portlet preference to the portlet.xml deployment descriptor of WAR file.
Parent
Administer Portlet load monitoring
Related tasks
Administer portlets for Portlet load monitoring