To benefit from a higher performance
improvement, you can
adapt the default list of lazy applications to your needs.
About this task
To configure
the list of lazy applications with your additional
applications, proceed by the following steps:
Procedure
- Determine which of the applications deployed in your portal
you want to configure as lazy applications. To do this, perform the
following steps:
- Log on to the WebSphere® Integrated Solutions Console.
- Select .
- 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 your usual scenarios and that are not
required for portal start up.
- Stop the portal server.
- Make sure that
portal light mode is disabled. To
disable portal light mode, change to the directory wp_profile_root/ConfigEngine and
run the configuration task
ConfigEngine.sh|bat disable-portal-light-startup-performance -DWasPassword=password
- Change to the directory wp_profile_root/PortalServer/config/StartupPerformance .
- 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.
Note: Make sure that your 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. You can 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. For more information see Configuring developer
mode on Windows.
- Save
your changes.
- Enable portal light mode. To do this, change
to the directory wp_profile_root/ConfigEngine and
run the configuration task
ConfigEngine.sh|bat enable-portal-light-startup-performance -DWasPassword=password
- Restart the portal server.
- After this adaptation verify that your scenarios
are still
running.
What to do next
Limitations: - If you have portal light mode enabled and you
stop an application
manually, for example by using the WebSphere Integrated Solutions Console or the wsadmin command
line interface, and a user then accesses that application, that applications
is restarted.
- If you have portal light mode enabled and you
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.