How to slim down a WPS portal development server

During a training session one attendee asked the trainer if there is a list of IBM Portlet that could be uninstalled to improve performances of a WPS development server (to reduce memory consumption and speed up portal restart).
The trainer was not able to answer but I remembered an IBM Portal conference where the speaker provided us such a list (Walter Haenel / Lotusphere 2008):

These Portles can be deinstalled if not used, without any impact to the system.
No system functions nor configuration actions depend on the availability.

com.ibm.wps.portlets.frequentusers.FrequentUsers
com.ibm.wps.portlets.welcome
com.ibm.wps.portlets.xslt
com.ibm.portlets.cpp.calendar
com.ibm.portlets.cpp.mail
com.ibm.wps.portlets.inotes2.WpsiNotes2Portlet
LotusDocViewer.50d4aea48f06001714ddae8d9778c9f0
com.ibm.wps.portlets.domdoc.WpsDomDocPortlet
com.ibm.wps.portlets.notes.LotusNotesMVCPortlet
com.ibm.wps.portlets.quickplace.WpsQPController
LotusMyTeamWorkplaces.50d4aea48f06001714ddae8d9778c9f0
lotus.web.conferencing
PortletApp_com.ibm.wps.portlets.sametime.WIHPortlet
com.ibm.wps.portlets.mylist.MyListPortlet
com.ibm.wps.portlets.reminder
com.ibm.wps.portlet.Newsgroup_1:1
1308807024
com.ibm.wps.banner
com.ibm.portlets.exchange3
com.ibm.portlets.exchange2003
com.ibm.wps.portlets.worldclock
com.ibm.wps.quicklinks
com.ibm.wps.servletinvoker
com.ibm.wps.JSPServer
com.ibm.wps.fileserver
1331917905
com.ibm.wps.csv
com.screamingmedia.openportlet.wps.WPSPortlet.release.Dazzle3
com.ibm.wps.portlets.stlist.StListPortletController

Note : in our case, an error occured when trying to uninstall the following Portlet "com.ibm.wps.portlets.stlist.StListPortletController" (problem with database constraint). So it
has not been uninstalled.


From my experience, to improve performances, you can also perform the following tasks:

- Set the WCM option to "Subscriber-only" (connect.cfg for pre-v6 version, and WCMConfigService.properties for v6), parameter deployment.subscriberOnly=true.

For more details see : Understanding syndication in IBM Workplace Web Content Management

- Disable the JCR text search (which rebuild jcr indexes automatically) : set the jcr.textsearch.enabled=false (WebSphere\PortalServer\jcr\lib\com\ibm\icm\icm.properties).

Please note that I'm not sure of the exact role of this process, but I think it can be disabled on a development server.
For more details: see


- Reduce as much as possible the volume of WCM content (in v5, the rebuild of WCM indexes during server restart could take a very long time !)

- Another best practice for WCM is to run the clean-up tools (especially the Member fixer tool). See v6 infocenter for more details