You can set portlet preferences to influence in which cases Portlet load monitoring blocks or reenables
JSR portlets.
About this task
You can configure parameters for the following:
- Maximum number of concurrent requests
- Reactivation limit of concurrent requests for reactivating the
portlet
- Allowed average response time. You can configure the sample number
of requests by which this average response time for portlets is calculated
as mentioned in configuration tasks.
For more information about these 3 parameters and their meaning
refer to the topic about Portlet configuration parameters for
Portlet load monitoring. For information
about setting the sample by which the average response time is calculated
refer to the topic about Portal configuration parameters for
Portlet load monitoring.
To set
these parameters, proceed by the following steps:
Procedure
- Log in to the portal using a portal administrator user
ID.
- Select Administration.
- Select . The Manage
Portlets portlet is displayed. It lists the portlets in your portal.
- Search for the portlet for which you want to set portlet
preferences.
- Select the Configure Portlet icon.
- Add a new portlet preference as required and type number
for the new portlet preference as required:
- To set the maximum number of requests that you want to allow
for this portlet, add com.ibm.wps.pe.plm.maxrequest
= xyz for the new portlet preference.
For example, if you want 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, add com.ibm.wps.pe.plm.minrequest
= xyz for the new portlet preference.
For example, if you want this portlet to be reenabled when its concurrent
requests fall back to 5 or less, specify com.ibm.wps.pe.plm.minrequest
= 5 .
- To set the allowed average response time for this portlet,
add 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 add the
preference.
- Save your changes by clicking the OK button.
What to do next
As an alternative, you can define a portlet preference before deploying
the portlet. In this case add the portlet preference to the portlet.xml deployment
descriptor of your WAR file.