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

A 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 the product 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 the product.

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. The non-root user needs access to this directory in order to start WebSphere Application Server.

The commands are split on multiple lines for printing purposes.

Procedure

  1. Create the profile by issuing the following code from a command prompt:
    [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.bat
    -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
    
    

  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

Results

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

What to do next

As the installer, you can continue to create profiles and assign ownership to non-root users as needed.

A non-root user ID can manage multiple profiles. Have the same non-root user ID manage an entire profile, whether it is the deployment manager profile, a profile that contains the application servers and the node agent, or a custom profile. A different user ID can be used for each profile in a cell, whether global security or administrative security is enabled or disabled. The user IDs can be a mix of root and non-root user IDs. For example, the root user might manage the deployment manager profile, while a non-root user might manage a profile that contains application servers and the node agent, or vice versa. However, typically, a root user or a non-root user manages all profiles in a cell.

The non-root user can use the same tasks to manage a profile that the root user uses.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=tpro_rootpro_nonroot_own
File name: tpro_rootpro_nonroot_own.html