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:

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

 

Results

Depending on the tasks that the installer completes, the installer has:

 

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