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.
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 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.
Procedure
Results
Depending 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 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.