This section describes how to install the Web server and the Web server plug-in on the machine where you installed WebSphere Application Server.
Why and when to perform 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. Non IBM HTTP Server Web servers 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.
Steps for this task
You must create an application server profile or a custom profile and federate the node before you can use the administrative console of the deployment manager to create a Web server definition. The same is true for running the configuration script that the plug-ins installation wizard created. You must assign the Web server to a managed node when you create it.
The managed node must exist before running the plug-ins installation wizard. Otherwise, the installation is considered a remote installation.
If you install the plug-in, save the plug-in configuration script to run after you create a managed node, otherwise an error occurs. Wait until the script runs successfully and creates the Web server definition on the managed node and node synchronization occurs before starting the Web server.
Related reference
Web server collection
Web server configuration
Web server log file
Web server plug-in properties settings
Web server configuration file
Web server custom properties
Remote Web server management