If the Web server that you are setting up is an IBM HTTP
Server, and you plan to manage that Web server through a node agent
that is running as a non-root user, you must make sure that you adhere
to the following requirements:
- The user ID that you designate as the user ID that owns the IBM
HTTP Server directories and files, is the same user ID under which
the non-root node agent is running. You cannot run an IBM HTTP Server
as a root user if the node agent that is managing that IBM HTTP Server
is running as non-root node agent because a node agent process that
is running as a non-root user cannot spawn off an IBM HTTP Server
that is running as a root user.
- The value you specify for the listener port value must be greater
than 1024. An IBM HTTP Server that is running under a non-root user
ID does not start if the port number for its listener port is 1024
or less.
You can ensure that the non-root node agent and the IBM
HTTP Server are using the same user ID if you specify the user ID
that you used to install the product as the user ID for the IBM HTTP
Server when you install the IBM HTTP Server. However, if, you decide
to run the node agent as a non-root user after you install the IBM
HTTP Server, and Web server plug-in, you can take the following actions
to enable both the node agent and the IBM HTTP Server to run as non-root
users:
- Change the user ID for WebSphere Application Server to a non-root
user ID.
- Configure the run-as setting for the node agent.
- Use the administrative console to create a new IBM HTTP Web server,
unless an already defined IBM HTTP Server has the required properties.
- Change the ownership of the IBM HTTP Server directory and files
to the non-root user ID under which the non-root node agent is running.