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.You must have root authority to accomplish the following tasks.
Before you can create a profile, you must install WebSphere Application Server.
Why and when to perform 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.
Steps for this task
./wasprofile.sh -create -profileName profile01 -profilePath install_root/profiles/profile01 -templatePath install_root/profileTemplates/default
wasprofile -create -profileName profile01 -profilePath C:\install_root\profiles\profile01 -templatePath C:\install_root\profileTemplates\default
chown -R user1 install_root/profiles/profile01
C:\install_root\profiles\profile01
chown -R user1 install_root/logs/wasprofile/profile01
C:\install_root\logs\wasprofile\profile01
Result
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