+

Search Tips   |   Advanced Search

Configure portal light mode

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

  1. Determine which of the applications deployed in the portal to configure as lazy applications. To do this procedure, perform the following steps:

    1. Log on to the WAS console.

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

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

  2. Stop the portal server.

  3. Disable portal light mode

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

    Edit...

      WP_PROFILE/PortalServer/config/StartupPerformance/wp.base_TargetMapInclList.properties

    This file contains the list of applications that are not loaded when the portal 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.

    Make sure the list of lazy applications does not contain any 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.

    Use the white list in the wp.base_TargetMapExclList.properties file as a reference. Never disable any of the applications listed in that properties file. See Configure developer mode on Windows.

  4. Save the changes.

  5. Enable portal light mode

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

  6. Restart the portal server.

  7. After this adaptation, verify the scenarios are still running.


What to do next

Limitations:

  1. If we have portal light mode enabled and you stop an application manually, for example using the WAS console or wsadmin-line interface, and a user then accesses that application, that applications are restarted.

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


Parent Use portal light mode