Create profiles for non-root users

 

+

Search Tips   |   Advanced Search

 

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.

This task assumes a basic familiarity with the manageprofiles command, the Profile Management tool, and system commands. This task uses the following terms:

• Root users refers to:

  • Root users

  • Administrators

• Non-root users refers to

  • Non-root users

  • Non-administrators

• Installer refers to a root user or a non-root user.

An ease-of-use limitation exists for non-root users who create profiles. Mechanisms within the Profile Management tool 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 Management tool 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.

 

Overview

Non-root users might typically need these tasks completed so that they can start their own WAS servers in development environments. For instance, an application developer might test an application on a WAS in a profile that he owns.

 

Procedure

• Create a profile as an installer and assign ownership to a non-root user.

  This topic describes how the installer 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 an installer authorizes a group to certain files and directories so that non-root users in the group can create profiles.

• Install maintenance as an installer 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 installer changes ownership of the files so that the non-root user can then successfully start WAS.

 

Results

Depending on the tasks that the installer completes, the installer 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 WAS

 

What to do next

Depending on the tasks that the installer completes, a non-root user can create a profile, start WAS, or do both.

---

Creating a profile as an installer 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 an installer and changing the ownership of profile related files

 

Related Reference

Installing maintenance packages