Configure portal light mode

To benefit from a higher performance improvement, you can adapt the default list of lazy applications to needs.

Before you configure the list of lazy applications, you can ...

To configure the list of lazy applications with additional applications...

  1. To view the applications that are deployed in the portal and determine which of these you want to configure as lazy applications:

    1. Log on to the WAS administrative console.

    2. Select Applications -> Application Types -> WebSphere Enterprise Applications.

    3. Write down the names of the applications that you want to add to the list of lazy applications. Add only applications to the list that are not used by usual scenarios and that are not required for portal start up.

  2. Stop the portal server.

  3. Make sure that portal light mode is disabled.

      To disable portal light mode,

        cd WP_PROFILE/ConfigEngine

      and run the configuration task 

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

  4. Change to the directory WP_PROFILE/PortalServer/config/StartupPerformance .

  5. Modify the file wp.base_TargetMapInclList.properties.

      This file contains the list of applications that are not loaded when the server is started.

      • To add an application to this list, type the required application names from the WebSphere Enterprise Applications list.

      • To remove an application, comment out the appropriate application name or delete it from the list.

      where App_name is the name of the application. Make sure that 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.

  6. Save changes.

  7. Enable portal light mode.

      To do this,

        cd WP_PROFILE/ConfigEngine

      and run the configuration task 

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

  8. Restart the portal server.

  9. After this adaptation verify that scenarios are still running.


Limitations:

  1. If you have portal light mode enabled and you stop an application manually, for example by using the administrative console or the wsadmin command line interface, and a user then accesses that application, that applications is restarted.

  2. If you have portal light mode enabled and you use the activation task ConfigEngine.sh activate-portlets to activate all portlets, all portlets are indeed started, even if they are set for lazy load.


Parent

Use portal light mode


Enable portal light mode

 


+

Search Tips   |   Advanced Search