Portal service configuration
The configuration for each service is set through the WAS console. The portal configuration services are spelled as one word, for some services abbreviated, and preceded by the letters WP. Example: In the WAS console, the portal Configuration Service is listed as WP ConfigService. For more information about how to set properties see the topic about Setting service configuration properties.
The following topics describe the services that can be of interest to the portal administrator. Services that are not described in the following are purely for portal internal usage. Do not modify them in any way.
The following topics describe the portal services and their configuration properties. In these lists, the values given in parentheses are the default values. Properties given with a value of <none> have no default values.
We configure the portal configuration services in the WAS console. We cannot set the service configuration properties by simply changing the property value in the properties file and restarting the portal.
For details about how to export a configuration from an existing portal and import it to another portal, refer to the documentation about the portal XML configuration interface.
See
- Administrator Unique Names Mapping Service
- Cache Manager Service
- Common Component Configuration Service
- Configuration Service
- CP Configuration Service for tagging and rating
- Content Access Service
- Data Store Service
- Deployment Service
- HTTP Client Service
- Live Object Service
- Loader Service
- Localizer Service
- Model WebDAV Service
- Navigator Service
- Portal Security Services
- Portlet Container Service
- Project Identification Service
- Registry Service
- State Manager Service
- Virtual Portal Configuration Service