Setting up a local web server
You can install a web server and the web server plug-in on the machine where you installed WebSphere® Application Server.
Before you begin
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 nonroot user, you must make sure that you adhere to
the following requirements:
You can ensure that the nonroot 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 nonroot
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 nonroot users:
About this task
You can define a locally installed Web server on an unmanaged or managed node. If
the web server is defined on an unmanaged node, the administrative functions are handled through the
IBM® HTTP Server
administration server. If the web server is defined on a managed node, the administrative functions
of the web server are handled through the WebSphere Application Server node
agent, which is beneficial.
Important: Web servers that are not
provided with the WebSphere Application Server product do not provide an
administration server. Web servers that do not provide an administration server must reside on a
managed node to facilitate plug-in administration functions and generation and propagation of the
plugin-cfg.xml file.
Important: IBM HTTP Servers that run on z/OS® do not provide the administration server. Web servers that
do not provide the administration server must reside on a managed node to facilitate plug-in
administration functions and generation and propagation of the plugin-cfg.xml file.
The following steps create a web server definition in the default profile.
Procedure
What to do next
The following functions are not supported on a managed node for a non-IBM web server.
For a non-IBM HTTP Server web server on an unmanaged node, you can generate plug-in
configuration, based on WebSphere Application Server repository changes. The
following functions are not supported on an unmanaged node for a non-IBM HTTP Server web server: