Web server definition
To administer or manage a web server using the administrative console, you must create a web server definition or object in the WebSphere® Application Server repository.
The creation of this object is exclusive of the actual installation of a web server. The web server object in the WebSphere Application Server repository represents the web server for administering and managing the web server from the administrative console.
- installation root
- port
- configuration file paths
- log file paths
The definitions of the web server object are made using the wsadmin command or the administrative console. You can also define a web server object in the WebSphere Application Server repository using the profile create script during installation, a .jacl script, and by using the administrative console wizard.
- Managed node. A node that contains a node agent. This node can exist only in a
deployment manager environment. The importance of defining a web server on a managed node is that
the administration and configuration of the web server is handled through the node agent from the
administrative console. Support for administration and configuration through the administrative
console is limited to IBM® HTTP Server only. Non-IBM HTTP Server web servers must be on a managed node to handle
plug-in administrative functions and the generation and propagation of the
plugin-cfg.xml file.
For IBM HTTP Server for WebSphere Application Server (powered by Apache) on z/OS® and for the Version 5.3 HTTP Server for z/OS, the administration functions on managed nodes are:
- Web server status in the web server collection panel or the serverStatus.sh
- Generation of the plugin-cfg.xml
- Propagation of the plugin-cfg.xml
- Start and Stop of the web server for z/OS
- View and edit of the configuration file view of the logs
- Stand-alone node. A node that does not contain a node agent. This node usually exists in WebSphere Application Server (base) environment. A stand-alone node can become a managed node in a deployment manager environment after the node is federated . A stand-alone node does not contain a node agent, so to administer and manage IBM HTTP Server, there must be an IBM HTTP Server administration server installed and running on the stand-alone machine that the node represents. IBM HTTP Server ships with the IBM HTTP Server administration server and is installed by default. Support for administration and configuration through the administrative console is limited to IBM HTTP Server only.
- Unmanaged node. A node that is not associated with a node agent. This node cannot be federated. Typically, the unmanaged node represents a remote machine that does not have WebSphere Application Server installed. However, you can define an unmanaged node on a machine where WebSphere Application Server is installed. This node can exist in a WebSphere Application Server (base), or deployment manager environment. An unmanaged node does not contain a node agent, so to administer and manage IBM HTTP Server, an IBM HTTP Server administration server must be installed and running on the stand-alone machine that the node represents. Support for administration and configuration through the administrative console is limited to IBM HTTP Server only.
- On managed nodes:
- Web server status in the web server collection panel or serverStatus.sh
- Generation of the plugin-cfg.xml
- Propagation of the plugin-cfg.xml
- On unmanaged nodes:
- Web server status in the web server collection panel or serverStatus.sh
- Generation of the plugin-cfg.xml
![[z/OS]](../images/ngzos.gif)
For information about the available service levels that include support for the
IBM HTTP Server for
z/OS powered by
Apache, consult the Profile Management Tool Support website for the z/OS platform.