Siebel Installation Guide for UNIX > Requirements for Installing and Configuring Siebel Business Applications > Planning Your Siebel Deployment >

Setting Permissions and Ownership

This topic is part of Planning Your Siebel Deployment.

This topic provides information about permissions and ownership for user accounts that will perform installations.

  • To install server-based Siebel CRM modules, you must be a nonroot user. You cannot install these modules as the root user using Oracle Universal Installer software. This requirement applies to all new installations of Siebel Enterprise Server and Siebel Web Server Extension (SWSE). It also applies to all migration installations and to all installations of Siebel Patchset releases for the current release (Siebel CRM version or version

    For existing installations of Siebel CRM version or earlier that were originally installed as the root user (using InstallShield installers), you can use the chown command to change the owner for all of the installation directories and files to a nonroot user in order to perform the migration installation.

    After installing as a nonroot user, you can optionally change the installation owner back to the root user. Note that the same requirement will apply every time that you install a new release, including migration installations of a future release or installations of Siebel Patchset releases. In general, it is recommended not to change the owner back to the root user, unless your deployment requires it.

    For example, for new or existing installations of SWSE, after installing as a nonroot user, you might need to change the owner to the root user in order to work with an existing Web server installation that uses privileged ports that are reserved for the root user (for example, port 80).

    For more information, see Requirements for the Installation User for the Siebel Web Server Extension.

  • Before you install each server module discussed in this guide, set umask to 027 on the installation directory of that computer. Changing this setting eliminates other permissions, including group write permissions. This action also sets the default permissions, so that all of the files and directories that are created afterwards have rwxr-x--- permissions. The Siebel service owner account must have all permissions. However, the group must have read and execute (for directory access) permissions only. See also Creating the Siebel Service Owner Account.
Related Topics

Requirements Specific to UNIX or Linux Operating Systems

Configuring the Siebel Gateway Name Server for Automatic Start

Configuring the Siebel Server for Automatic Start

Siebel Installation Guide for UNIX Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.