IBM BS029ML - WebSphere Portal Server Self Help Manual page 155

Cache Manager Service is responsible for managing the different caches used in
WebSphere Portal Version 6.0.x. The portal provides two different types of caches: shared
and non-shared. The shared caches are cluster aware. This means that deleting an
element from the cache on one cluster node results in deleting that element from the
corresponding cache instances on all other nodes. This ensures that frequently changing
data is kept consistent over the whole cluster installation. The non-shared caches are
used for data where cluster awareness is of no concern. This avoids unnecessary network
communication overhead.
Collaborative Services allow developers who are writing portlets for WebSphere Portal or
other application servers to add Lotus collaborative functionality to their portlets.
Configuration Service is responsible for collecting the most essential configuration data of
the portal engine. Many of these parameters are set by the installation procedure.
Therefore, plan well ahead and apply special care when modifying these parameters. The
Configuration Service also holds the configuration properties for WSRP services. They are
listed and described under Using WSRP services with your portal in the respective topics
for which they are relevant.
ContentAccessService allows portlets to access remote systems or content from remote
URLs, including URLs located on the other side of a proxy server.
CredentialVaultService allows portlets to store and retrieve user credentials for their
particular associated application and use those credentials to log in on behalf of the user.
Data Store Service is responsible for managing the data source of the portal as configured
while installing WebSphere Portal Server. Normally there should not be a need to modify
any of the configuration parameters in the DataStore service. One important property of
the DataStore service is the scheduler.cleanup property.
Deployment Service provides services for accessing the configuration parameters
required for the portlet deployment. The portlet deployment component is responsible for
the integration of portlets into the portal. It handles the correct deployment of portlet
applications and their WAR files into WebSphere Portal and WebSphere Application
Server. It uses the WebSphere Application Server management services for the physical
deployment and management of war files in the WebSphere Application Server.
Management of war files includes installing, removing, redeploying, starting, and stopping
portlet applications.
Loader Service is responsible for dynamically loading class files in four categories:
commands, and supporting classes for screen templates, skin templates, and theme
templates. The service does so by looking up a given (class) name in different packages.
Upon loading the respective class file, an instance of that class is returned. To optimize the
efficiency, the implementation of the service is free to cache loaded class files or instances
and return a cached instance. That means that the implementation of any such classes
must be thread-safe.
Navigator Service allows you to specify a number of settings. Among these are settings for
cache scope and cache expiration. Depending on your configuration, you might be able
improve your performance by modifying these settings. For detailed information about
page caching for improved performance, refer to 5.2, "Optimization" on page 142.
PropertyBrokerService allows Portlets to cooperate and exchange data even if they were
developed independently, without the programmer's awareness of the existence of the
other cooperative portlets.
141
Chapter 5. WebSphere Portal runtime and services