Managing profiles for non-root users

The non-root user can receive 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 manageprofiles command, the Profile Management Tool, and system commands.

This task uses the following terms:
  • Root users refers to:
    • [Linux] [HP-UX] [Solaris] [AIX] Root users
    • [Windows] Administrators
  • Non-root users refers to:
    • [Linux] [HP-UX] [Solaris] [AIX] Non-root users
    • [Windows] Non-administrators
  • Installer refers to a root user or a non-root user.
Remember: 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, 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 assigned 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 application servers in development environments. For instance, an application developer might test an application on a application server in a profile assigned to that application developer.

Procedure

Results

Depending on the tasks that the installer followed, the installer has completed the following actions:

Note: Connections to the Derby database might not work, and you might see errors like the following in the logs:
java.io.FileNotFoundException: C:\Program Files\IBM\WebSphere\AppServer\derby\derby.log (Access is denied.)
This can happen when files under app_server_root are read-only. You can configure Derby to write its log to another location by setting the following property in the app_server_root/derby/derby.properties file
# This property can be set to make Derby log to System.err.  This is useful if you 
# do not have write permission to the default location: 
WAS_HOME/derby/derby.log derby.stream.error.field=java.lang.System.err

What to do next

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




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 6:15:55 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-dist&topic=tpro_manage_nonroot
File name: tpro_manage_nonroot.html