Sun Java Communications Suite 5 Installation Guide

Configuring Product Components With Non-root Identifiers

You must be root to run the installer. Because of this, all files placed on the machine by the installer are owned by root. However, when performing configuration after installation, you can assign a non-root runtime user or group to some product components. For example, you might be deploying Access Manager in an instance of Application Server that is not owned by root. For purposes of installation or administration, there are many reasons to configure a product component with a non-root identifier. Generally, the non-root user must already exist on the system, but this can vary by product component.

The following table provide links to information on configuring the applicable product components with non-root identifiers.

Table 6–4 Configuring Non-root Identifiers for Product Components


Product Component	Where to Find Instructions
Application Server	Set up an entire administrative domain owned and operated by a non-root user. For instructions, refer to Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.
Calendar Server	Use the Calendar Server configurator to configure for non-root. For instructions, refer to the Sun Java System Calendar Server 6.3 Administration Guide.
Directory Server	To configure Directory Server with a non-root ID, create the server instance as a regular user, or specify the user when creating the instance. For instructions, refer to the Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.
Messaging Server	To configure Messaging Server with a non-root ID, use the Messaging Server configurator. See the Sun Java System Messaging Server 6.3 Administration Guide for instructions.
Web Server	By default, Web Server is configured with `webservd` as the runtime user. When using the Web Server configurator, you can specify any runtime user ID. For additional information, refer to the Sun Java System Web Server 7.0 Administrator’s Guide.