This topic discusses how to give a non-root user permissions for files and directories so that the non-root user can create a profile.
Before you begin
This task assumes a basic familiarity with the wasprofile command, the Update Installer wizard, and system commands.Why and when to perform this task
Non-root users might typically need these tasks completed so that they can start their own WebSphere Application Servers in development environments. For instance, an application developer might test an application on a WebSphere Application Server in a profile that he owns.Steps for this task
This topic describes how the root user creates a profile and assigns 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.
This topic describes how a root user authorizes a group to certain files and directories so that non-root users in the group can create profiles.
This topic describes how to install WebSphere Application Server maintenance and change the ownership of new profile files to the non-root user that owns the profile. The root user changes ownership of the files so that the non-root user can then successfully start WebSphere Application Server.
Result
Depending on the tasks that the root user completes, the root user has:What to do next
Depending on the tasks that the root user completes, a non-root user can create a profile, start WebSphere Application Server, or do both.Related reference
Installing maintenance packages