WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Root versus non-root installation
The term non-root implies a Linux or UNIX installer, but also means a
non-administrator group installer on a Windows system. Non-root installers can
install WebSphere Application Server V7.0 in both silent and interactive mode for
full product installations and removals, incremental feature installations, and
silent profile creation.
Installing as a non-root user in Version 7.0 was enhanced and works almost the
same as installing as a root user does in previous versions. There are some
specifics you have to consider which are documented at the following Web page:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.web
sphere.installation.nd.doc/info/ae/ae/cins_nonroot.html
There are limitations of which you need to be aware. Refer to the following Web
page:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.web
sphere.installation.nd.doc/info/ae/ae/cins_nonroot.html#cins_nonroot__n
onroot_install_limitations
Secure administration tasks
WebSphere Application Server provides a mechanism to secure the
administrative interfaces. With WebSphere Application Server V7.0, you have the
option to enable security for administrative tasks during profile creation for an
application server or deployment manager (including those created with cell
profiles). This option does not enable application security.
If you intend to create a profile during installation and want to secure your
administrative environment at the same time, you need to identify one user ID to
be used for administration. The user ID and password specified during profile
creation are created in the repository and assigned the Administrator role. This
ID can be used to access the administration tools and to add additional user IDs
for administration. When you enable security during profile creation, LTPA is used
as the authentication mechanism and the federated repository realm used is
used as account repository.
On distributed systems, am XML file-based user repository is created and
populated with the administrator ID. This XML file-based system can be
federated with other repository types to form an overall repository system. If you
do not want to use the file-based repository, do not enable administrative security
during profile creation or change it afterwards. In WebSphere for z/OS, you can
choose to use the file-based repository or use the z/OS system SAF-compliant
security database. Whether you choose to enable administration security during
profile creation or after, it is important that you do it before going into production.
Chapter 6. Installation 225