[AIX Solaris HP-UX Linux Windows]

Managing profiles for nonroot users

The nonroot user can receive permissions for files and directories so that the nonroot 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 nonroot users who create profiles. Mechanisms within the Profile Management Tool that suggest unique names and port values are disabled for nonroot users. The nonroot 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 nonroot users a range of values for each of the fields. You can assign responsibility to the nonroot users for adhering to their assigned value ranges and for maintaining the integrity of their own definitions.
Best practice Best practice: IBM recommends starting processes that run on the same profile with user IDs that have mutually compatible file permissions, meaning that each process can read or update files that the other processes create. This ensures that the processes can access the same files without encountering a permission-denied error. For example, if you run the deployment manager as user wasuser and then also run the command line tool to generate plug-ins on that same profile, you should run the tool as user wasuser.bprac
[Windows] Tip: In WebSphere Application Server Version 8.5, files created by an administrator outside of the Program Files directory are usable by non-administrators. Therefore, profiles created outside of the Program Files directory can be used by non-administrators to start the server and so on.

About this task

Nonroot 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:
  • Created a profile for a nonroot user and assigned ownership of the profile directory to the nonroot user
  • Granted permission to the appropriate directories so that nonroot users can create profiles
  • After installing maintenance, changed ownership of new profile files in a directory that is owned by a nonroot user, so that the nonroot user can successfully start the application server
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: 
/opt/wasprofile/derby/derby.log derby.stream.error.field=java.lang.System.err

What to do next

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

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=tpro_manage_nonroot
File name: tpro_manage_nonroot.html