Web server definition

To administer or manage a web server using the console, create a web server definition or object in the WAS repository.

The creation of this object is exclusive of the actual installation of a web server. The web server object in the WAS repository represents the web server for administering and managing the web server from the console.

The web server object contains the following web server properties:

• installation root
• port
• configuration file paths
• log file paths

In addition to web server properties, the web server contains a plug-in object. The plug-in object contains properties that define the plugin-cfg.xml file.

The definitions of the web server object are made using wsadmin or the console. We can also define a web server object in the WAS repository using the profile create script during installation, a .jacl script, and using the console wizard.

There are three types of WAS nodes upon which we can create a web server. The type depends on the version of WAS, as follows:

• Managed node. A node containing 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 console. Support for administration and configuration through the 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.

  (zos) 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) or WebSphere Application Server Express 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 console is limited to IBM HTTP Server only.

• Unmanaged node. A node that is not associated with a WAS node agent. This node cannot be federated. Typically, the unmanaged node represents a remote machine that does not have WAS installed. However, we can define an unmanaged node on a machine where WAS is installed. This node can exist in a WAS (base), WebSphere Application Server Express, 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 console is limited to IBM HTTP Server only.

Web servers, which are not IBM HTTP Servers for WebSphere Application Server, are not fully administered from the WAS console. The administration functions for Web servers, which are not IBM HTTP Servers for WebSphere Application Server, are:

• 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

(zos) Special consideration for IBM HTTP Server for z/OS, powered by Apache: To support remote administration and configuration of IBM HTTP Server for z/OS, a web server type IHSZOS must be defined in the WAS repository.

Important: During profile creation, using the z/OSProfile Management Tool, if you select Advanced profile creation and Create a web server definition, you will not be permitted to select the combination of web server type IBM HTTP Server and web server operating system of z/OS. However, we can create the web server type for IBM HTTP Server on z/OS through the console wizard, createWebServerDefintion.jacl, or wsadmin after the profile create, using the z/OS Profile Management Tool.

(zos) 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.