+

Search Tips   |   Advanced Search

 

Creating a profile as an installer and assigning ownership to a non-root user

 

The installer can create a profile and assign ownership of the profile directory to a non-root user so that the non-root user can start WAS for a specific profile. Use this example to accomplish the tasks through commands. This task assumes a basic familiarity with the manageprofiles command and system commands.This task uses the following terms:

Before you can create a profile, install WAS.

 

Overview

Have the installer perform the following steps to create a profile and assign ownership for the profile directory and the logs directory. The ownership is assigned to a non-root user ID that is different from the installer ID. The non-root user needs access to these directories to start WAS.

 

Procedure

  1. Create the profile: [Linux] [HP-UX] [Solaris] [AIX]

    ./manageprofiles.sh -create -profileName profile01 -profilePath
    
    
    app_server_root/profiles/profile01 -templatePath
    app_server_root/profileTemplates/default

    [Windows]

    manageprofiles -create -profileName profile01 -profilePath C:\
    
    
    app_server_root\profiles\profile01 -templatePath C:\
    app_server_root\profileTemplates\default
    The commands are split on multiple lines for printing purposes.

  2. Change ownership of the profile01 profile directory to the user1 non-root user: [Linux] [HP-UX] [Solaris] [AIX] For example, issue the following command:

    chown -R user1 app_server_root/profiles/profile01
    

    [Windows] Follow instructions in the Windows documentation to grant user1 access to the following directory:

    C:\app_server_root\profiles\profile01
    

  3. Change the ownership of the logs directory for the profile01 profile to the user1 non-root user to prevent displaying log messages to the console: [Linux] [HP-UX] [Solaris] [AIX] Issue the following command:

    chown -R user1 app_server_root/logs/manageprofiles/profile01
    

    [Windows] Follow instructions in the Windows documentation to grant user1 access to the following directory:

    C:\app_server_root\logs\manageprofiles\profile01
    

 

Results

The installer has created a profile and changed ownership of the profile directory and log directory to a non-root user.

 

What to do next

The non-root user can start WAS associated with, in this example, profile01.



manageprofiles command