Portal light mode in WPS 7.0

The WebSphere Portal Server 7.0 has a concept of portal light node, this is what the infocenter says "Portal now provides a portal light mode which can improve portal startup time and reduce memory consumption in production environments. When you enable portal light mode, specific portlet applications are not started at portal start up. Instead they are started later by the first standard HTTP request that occurs and renders a portal page with the portlet application on the server. This occurs, for example, when a user accesses the portlet application. The default list of these applications whose initialization is deferred until first use (sometimes called "lazy applications"), contains administrative and sample portlet applications. To benefit from a higher performance improvement, you can adapt the default list of these applications to your needs."

Important Note: WebSphere Portal Server had a concept of enable-develop-mode-startup-performance task for some time now. This configuration task is still there in the WPS 70


You will have to follow these steps to enable portal light mode on your WPS 7.0 environment

  • First make sure that the light mode is disabled by executing following command

    ConfigEngine.sh disable-portal-light-startup-performance -DWasPassword=


  • Unless you want to change the list of applications to either add or remove one of the applications from the startup list you can execute this config command to disable startup performance

    ConfigEngine.sh enable-portal-light-startup-performance -DWasPassword=


  • Startup your portal server



How to customize startup application list

If you want to add or remove application from the server startup list then you can do that by going to /WebSphere/wp_profile/PortalServer/config/StartupPerformance directory and modifying one of the following files

  1. wp.base_TargetMapInclList.properties: This file has list of applications which will not be started at the time of server startup, you can add the application name, which you can get from the WAS Admin console to this file to disable its startup

    PA_Blurb
    PA_MPagesandFavorites
    PA_Properties
    PA_Eecontentandlayout
    PA_appearance
    PA_Set_Permissions
    PA_portletWiring
    PA_ThemesAndSkinsMgr
    PA_Resource_Manager
    PA_TCustomizerPortApp
    PA_Portlet_Manager
    PA_Manage_Webservices
    PA_Web
    PA_Principals_Manager
    PA_ResourceView
    PA_Credential_Admin
    PA_PolicyExplorer
    PA_PolicyEditor
    PA_PolicyEditorCA
    PA_Settings
    PA_URL_mapping
    PA_UniqueNames
    PA_Markups_Manager
    PA_Clients_Manager
    PA_Import_XML
    PA_WCM_Admin
    PA_FrequentUsers
    PA_Tracing
    PA_WPS_Welcome
    PA_MageVirtualPortals
    PA_TateCatalogPortApp
    PA_PropertiesPortApp
    PA_ParamConfig
    PA_Roles
    PA_ApplicationCatalog
    #lwp_peoplefinder_war
    PA_Policy_Status
    #PA_Selfcare_Port_App
    #TemplateLibrary_Servlets


  2. wp.base_TargetMapExclList.properties: COntains list of applications that should not be disabled. Make sure that your list of lazy applications does not contain applications that are either required for portal startup or frequently used. Do not add portlet applications to the list that hold portal services or a plug-in for an Eclipse extension point. If you have application that you do not want to disabled then add one line for that application to the wp.base_TargetMapExclList.properties file this is the default list

    wps
    wps_theme
    wps_scheduler
    isclite
    Personalization_Lists
    Personalization_Workspace
    PA_Login_Portlet_App
    PA_WebScanner
    content_j2ee
    JavaContentRepository
    wcm
    TemplateLibrary_Servlets
    PA_Selfcare_Port_App
    UserProfileRESTServlet
    MashupMaker_Integration
    MashupCommonComponent
    Enhanced_Theme
    Dojo_Resources
    Quickr_Document_Picker
    qkr.docpicker
    AJAX Proxy Configuration
    Live_Object_Framework
    Feed_Servlet
    PageBuilder2_Theme
    feedReader
    eventExplorer
    websiteDisplayer
    lwp_peoplefinder_war
    odc
    PA_WCM_Authoring_UI
    SpellChecker




Important Note: I build and install lot of sample portlets for my blog and as result my server statup performance goes down over period of time. So i run this task frequently to disable some of the sample applications.

2 comments:

pn said...

I am looking to do some tuning similar to what you mentioned.
Have you come across a description of the sample portelets and administrative portlets to determine which ones are really required.

Thanks
Pradeep

GF said...

Hi, thank you for your post. this one i didn't know about.
I am looking for a way to have faster deploys from RAD to WPS. Whenever i edit code files, RAD automatically deploys them to server, and that takes up to 2 minutes (give or take) . Can you offer any suggestion regarding making this process faster?