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:

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 task

Non-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.

 

Procedure

 

Results

Depending on the tasks that the root usercompletes, 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.

 

See also


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
Related reference
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.