Configure portal light mode

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

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

1. Determine which of the applications deployed in the portal to configure as lazy applications:

   1. Log on to the WAS admin 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 up.

2. Stop the portal server.

3. To disable portal light mode...
   cd WP_PROFILE/ConfigEngine

   ...and run...

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

4. cd 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 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 that 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. We can use the white list in

   wp.base_TargetMapExclList.properties

   ...as a reference. Never disable any of the applications listed in that properties file.

6. Save your changes.

7. Enable portal light mode...
   cd WP_PROFILE/ConfigEngine

   ...and run

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

8. Restart the portal server.

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

Limitations:

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

2. If you have portal light mode enabled and we use the activation task...
   ConfigEngine.sh activate-portlets

   ...all portlets are indeed started, even if they are set for lazy load.

Parent: Use portal light mode
Related:
Enable portal light mode
Configure developer mode on Windows