Web server definition for z/OS

We can define a web server definition in a managed node or in an unmanaged node.

To administer or manage a web server using the administrative console, 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 WAS repository represents the web server for administering and managing the web server from the administrative 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 the wsadmin command or the administrative 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 administrative 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 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 WAS (powered by Apache) on z/OS and for v5.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 a base WAS 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.

  IBM HTTP Server for WAS (powered by Apache) for z/OS and v5.3 HTTP Server for z/OS do not provide an IBM HTTP Server administration server. Administration of IBM HTTP Server powered by Apache is limited to:

  • Web server status in the web server collection panel or the serverStatus.sh
  • Generation of the plugin-cfg.xml

• 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, 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.

  IBM HTTP Server for WAS (powered by Apache) for z/OS and v5.3 HTTP Server for z/OS do not provide an IBM HTTP Server administration server. Administration of IBM HTTP Server powered by Apache is limited to:

  • Web server status in the web server collection panel or the serverStatus.sh
  • Generation of the plugin-cfg.xml

Web servers, which are not IBM HTTP Servers for WAS, are not fully administered from the WAS administrative console. The administration functions for web servers, which are not IBM HTTP Servers for WAS, 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

Using one of the following methods to manage web server customization files:

• Define a web server definition in a managed node.

  This method provides the most function, but requires that the web server configuration files be stored in a read and write directory that is accessible to a managed (application server) node in the WAS for z/OS cell. Create the managed node with the Profile Management Tool or the zpmt command, either directly or by federating a stand-alone application server; then use the administrative console to create the web server definition.

  When a web server definition is defined in a managed node, we can regenerate the plugin-cfg.xml configuration file directly to the web server configuration directory location. We can then retrieve, edit, and replace the httpd.conf file that controls web server operation.

• Define a web server definition in an unmanaged node.

  Use this method when a web server is defined in a stand-alone application server, or on a z/OS system that does not share read and write directories with a WAS for z/OS managed node.

  Use the Profile Management Tool job BBOWCFGW (stand-alone application server) or BBODCFGW (for a WAS ND cell) to create an unmanaged node and a web server definition.

Implement a web server plug-in