The installer can grant write permission of the appropriate
files and directories to a non-root user. The non-root user can then
create the profile. The installer can create a group for users who
are authorized to create profiles, or the installer can give individual
users the authority to create profiles. The following example task
shows how to create a group that is authorized to create profiles.
Before you begin
This task assumes a basic familiarity with system commands.
這項作業使用下列術語:
- Root 使用者是指:
- 非 root 使用者是指:
- 安裝者是指 root 使用者或非 root 使用者。
Procedure
- Log on as the installer to the system where the product
is installed.
- Create the profilers group that you can
use to create profiles.
Read the documentation for your
operating system for information about how to create groups.
- Create a user named user1 to create profiles.
Read the documentation for your operating system for information
on how to create users.
- Add the installer and user1 to the profilers group.
![[Linux]](../images/linux.gif)
![[HP-UX]](../images/hpux.gif)
![[Solaris]](../images/solaris.gif)
Log off and log back
on again as the installer to use the new group.
- As the installer, use operating system tools to change
directory and file permissions.
![[HP-UX]](../images/hpux.gif)
chmod -R g+wr /opt/IBM/WebSphere/AppServer/profileTemplates/default/documents
The ownership
of files is preserved when the files are copied to the profile directory
during profile creation. You granted write permission to the profile
directory so that files copied to the profile directory can be modified
as part of the profile creation process. Files that are already in
the profileTemplate directory structure prior
to the start of profile creation are not modified during profile creation.
![[Linux]](../images/linux.gif)
chgrp profilers /opt/IBM/WebSphere/AppServer/properties/Profiles.menu
chmod g+wr /opt/IBM/WebSphere/AppServer/properties/Profiles.menu
![[Windows]](../images/windows.gif)
The following example assumes that the installation
root directory is
C:\Program Files\IBM\WebSphere\AppServer.
Follow instructions in the Windows documentation
to give the profilers group read and write permission to the following
directories and their files:
C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles
C:\Program Files\IBM\WebSphere\AppServer\properties
C:\Program Files\IBM\WebSphere\AppServer\properties\fsdb
C:\Program Files\IBM\WebSphere\AppServer\properties\profileRegistry.xml
You
might have to change the permissions on additional files if the non-root
user encounters permission errors. If you authorize a non-root user
to delete a profile, for example, the user might have to delete the
following file:
![[Linux]](../images/linux.gif)
![[HP-UX]](../images/hpux.gif)
![[Solaris]](../images/solaris.gif)
app_server_root/properties/profileRegistry.xml_LOCK
app_server_root\properties\profileRegistry.xml_LOCK
Give
write access to the non-root user for the file to authorize the user
to delete the file. If the non-root user still cannot delete the profile,
then the installer can delete the profile.
- Make the configuration directory accessible to non-root
users.
Perform one of the following actions:
Results
The installer created
the profilers group and gave the group proper permissions to certain
directories and files to create profiles.
These directories and files are
the only ones in the installation root of the product to which a non-root
user needs to write to create profiles.
What to do next
The non-root user that belongs to the profilers group
can create profiles in a directory that the non-root user owns and
to which the non-root user has write permission. However, the non-root
user cannot create profiles in the installation root directory of
the product.
A non-root user ID
can manage multiple profiles. For a given profile, have the same non-root
user ID manage the entire profile.
The
non-root user can use the same tasks to manage a profile that the
root user uses.