The common way to install IBM® HTTP
Server is to run the installation program using an administrator user
ID. However, it is sometimes necessary to install IBM HTTP
Server using a non-administrator (non-root) user ID.
On
UNIX platforms, the user ID that performs the installation of IBM HTTP
Server must be the same user ID that will start the IBM HTTP
Server. When IHS is started by the root, which is the recommended
configuration, the user ID is changed to an unprivileged user ID for
the bulk of the runtime processing. ![[may2010]](../../deltaend.gif)
may2010
Before you begin
![[may2010]](../../delta.gif)
You must remember to perform all of the following
actions using the same user ID, whether it is an administrator user
ID or non-administrator user ID:
- Install IBM HTTP Server
- Install the WebSphere plug-in
- Start and stop the IBM HTTP Server
- Start and stop the IHS administration server (when applicable)
- Start and stop the WebSphere node agent (when applicable)
![[may2010]](../../deltaend.gif)
may2010
Administering a non-root IBM HTTP
Server from WebSphere ![[may2010]](../../deltaend.gif)
may2010
![[may2010]](../../delta.gif)
If you are installing
a non-root IBM HTTP Server as a local Web server, it may be managed
by WebSphere only if the following constraints are met:
![[may2010]](../../deltaend.gif)
may2010
About this task
Launching the IBM HTTP Server installation program
is done the same way for a non-root installation as it is for a root
installation, but there are several installation steps that require
root privileges that cannot be completed or must be completed separately.
Complete the installation steps as follows:
Procedure
- Register the installed program with the operating system.
This cannot be done for a non-root installation. The non-root IBM HTTP
Server installation is not listed when using operating system facilities
to display installed programs.
Create the Windows® service
entries for IBM HTTP Server and IBM HTTP
Administration Server. This cannot be done for a non-root
installation. Neither of these service entries are created and IBM HTTP
Server cannot start as a service. Start IBM HTTP
Server as follows:
<ihs_install_directory>/bin/httpd.exe
Start
the IBM HTTP administration server as follows:
<ihs_install_directory>/bin/httpd.exe -f <ihs_install_directory>/conf/admin.conf
Stop IBM HTTP
server as follows:
- Press Control+C in the IBM HTTP Server window, or
- End the httpd.exe processes using the Windows Task
Manager
Create an entry in Start > Programs.
This cannot be done for a non-root installation. No entries
are created.
Create an entry in Add/Remove programs.
This cannot be done for a non-root installation. No entry is
created.
Install AFPA. This
cannot be done for a non-root installation. Do not enable AFPA for
the non-administrator IBM HTTP Server installation, even
if AFPA is already installed from a previous administrator installation.
Only enable AFPA for one instance of IBM HTTP
Server.
- Silent installations. To enable a non-root
installation, add the following option to the silent installation
response file:
-OPT allowNonRootSilentInstall=”true”