Web server collection
To configure Web servers...
Servers | Server Types | Web ServersTo create a new Web server, click New to launch the Create new Web server entry wizard. To manage an installed Web server, select the check box beside the application name in the list and click a button:
Button Resulting Action Generate Plug-in This will manually generated a plugin-cfg.xml file. If the plug-in configuration service is enabled, a plug-in configuration file is automatically generated for a Web server whenever:
- The WAS administrator defines a new Web server.
- An application is deployed to an appserver.
- An application is uninstalled.
- A virtual host definition is updated and saved.
Propagate Plug-in Copy plugin-cfg.xml from the local directory where the appserver is installed to the remote machine. If using IBM HTTP Server V6 or higher for the Web server, WAS can automatically propagate the plug-in configuration file to remote machines provided there is a working HTTP transport mechanism to propagate the file.
New Launches the wizard to create a new Web server entry. Delete Deletes one or more of the selected Web server entries. Templates ... Opens the Web server templates list panel. From this panel we can create a new template or delete existing templates. Start Starts one or more of the selected Web servers. Stop Stops one or more of the selected Web servers. Terminate Terminates one or more of the selected Web servers.
- Name
Logical name for the Web server. This can be the host name of the machine, or any name you choose.
- Web server type
Indicates the type of Web Server we are using.
- Node
Logical name for the Web server. This can be the host name of the machine, or any name you choose.
Name of the node on which the Web server is defined. This column only applies for the WAS ND product.
- Version
Version of the WAS on which the Web server is defined.
- Status
Indicates whether the Web server is started, stopped, or unavailable.
If IBM HTTP Server is defined on an unmanaged node, start the IBM HTTP Server administration server before we can start and stop IBM HTTP Server.
If the status is unavailable, the node agent or IBM HTTP Server administration server is not running in that node, and start the node agent before we can start the Web server.
Started The Web server is running.
Stopped The Web server is not running.
Unknown Status cannot be determined. A Web server with an unknown status might, in fact, be running but has an unknown status because the appserver that is running the admin console cannot communicate with this Web server.
Subtopics
Web server configuration
Web server log file
Web server custom properties
Remote Web server management
Web server configuration file
Global directives
Web server virtual hosts collection
Web server virtual hosts detail
Related tasks
Communicating with Web servers
Related