WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

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

The root user can create a profile and assign ownership of the profile directory to a non-root user so that the non-root user can start WebSphere Application Server for a specific profile. Use this example to accomplish the tasks through commands.

Before you begin

This task assumes a basic familiarity with the wasprofile command and system commands.
This task uses the following terms:
  • Root users refers to:
    • [Linux] [HP-UX] [Solaris] [AIX] Root users
    • [Windows] Administrators
  • Non-root users refers to
    • [Linux] [HP-UX] [Solaris] [AIX] Non-root users
    • [Windows] Non-administrators

You must have root authority to accomplish the following tasks.

Before you can create a profile, you must install WebSphere Application Server.

About this task

Have the root user perform the following steps to create a profile and to assign ownership to a non-root user for the profile directory and the logs directory. The non-root user needs access to these directories in order to start WebSphere Application Server.

Procedure

  1. Create the profile:
    [Linux] [HP-UX] [Solaris] [AIX]
    ./wasprofile.sh
    -create -profileName profile01
    -profilePath app_server_root/profiles/profile01
    -templatePath app_server_root/profileTemplates/default
    -nodeName bl6node
    -cellName bl6ell
    -hostName bl6.rtp.raleigh.ibm.com
    
    
    [Windows]
    wasprofile
    -create -profileName profile01 
    -profilePath C:\
    app_server_root\profiles\profile01
    -templatePath C:\
    app_server_root\profileTemplates\default
    -nodeName bl6node 
    -cellName bl6Cell 
    -hostName bl6.rtp.raleigh.ibm.com
    
    
    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/wasprofile/profile01
    [Windows] Follow instructions in the Windows documentation to grant user1 access to the following directory:
    C:\app_server_root\logs\wasprofile\profile01

Results

The root user 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 WebSphere Application Server associated with, in this example, profile01.




Related reference
wasprofile command
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tpro_rootpro_nonroot_own.html

© Copyright IBM Corporation 2005, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)