Creating profiles for non-root users
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 Profile Creation wizard, and system commands.
This task uses the following terms:
- Root users refers to:
- Non-root users refers to
Remember: An ease-of-use limitation exists for non-root users who create profiles. Mechanisms within the Profile Creation wizard that suggest unique names and port values are disabled for non-root users. The non-root user must change the default field values in the Profile Creation wizard for the profile name, node name, cell name, and port assignments. Consider assigning non-root users a range of values for each of the fields. You can assign responsibility to the non-root users for adhering to their proper value ranges and for maintaining the integrity of their own definitions.
About this taskNon-root users might typically need these tasks completed so that they can start their own WAS appservers in development environments. For instance, an application developer might test an application on a WAS in a profile that he owns.
- Create a profile as a root user and assign ownership to a non-root user.
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 WAS for a specific profile.
- Grant write permission of files and directories to a non-root user for profile creation.
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.
- Install maintenance as a root user and change the ownership of profile related files.
This topic describes how to install WAS 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.
ResultsDepending on the tasks that the root usercompletes, the root user has:
- Created a profile for a non-root user and assigned ownership of the profile directory to the non-root user
- Granted permission to the appropriate directories so that non-root users can create profiles
- After installing maintenance, changed ownership of new profile files in a directory that is owned by a non-root user so that the non-root user can successfully start WebSphere Application Server
What to do nextDepending on the tasks that the root user completes, a non-root user can create a profile, start WebSphere Application Server, or do both.
Creating a profile as a root user and assigning ownership to a non-root user
Granting write permission of files and directories to a non-root user for profile creation
Installing maintenance as a root user and changing the ownership of profile related files
Installing maintenance packages
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.