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 IBM HTTP Server has management capability. Web server definitions facilitate the managing of properties that are related to the plug-in XML and keystore files. Web server definitions facilitate the generation and propagation of the plug-in XML and web server properties. The administrative console displays these management features by following Servers > Server Types > Web Servers. Other non-IBM HTTP servers can have a definition, but lack management features like starting and stopping the web server.

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.

Creation

The web server definition is created using one of the following.
  • Plug-in Configuration Tool (PCT is the recommended option)
  • WCT command line (Command line version of PCT)
  • Wsadmin command
  • Admin console
  • A jacl script
  • Profile create script that is available during installation

Web Server Administrative tasks

The web server definition defines many properties.
  • web server
    • installation root
    • port
    • configuration file paths
    • log file paths
    • plug-in generation and propagation
  • plug-in
    • configuration refresh interval
    • XML and KDB file names
    • management of keystores and certificates
    • log file name and log level
  • intelligent management
    • cell identifier
    • maximum retries and retry intervals
    • user id and password

Management mechanisms

Management mechanisms are the pipelines that are used to push changes from the web server definition to its associated physical web server. There are three mechanism choices. The type depends on the version of WebSphere Application Server installed.
  • Node agent
    A Node agent that is only available in a network deployment environment, is also referred to as a managed node. By having a web server on a managed node, administration is handled through a node sync from the deployment manager to the node through either administrative console or wsadmin commands. All non-IBM HTTP web servers must be on a managed node to have any management capabilities, such as the propagation of the plugin-cfg.xml file. IBM HTTP web servers provide a built-in administration service such that a node agent is not required. Some administrative functions include:
    • Web server status in the web server collection panel or serverStatus.sh
    • Generation of the plugin-cfg.xml file
    • Propagation of the plugin-cfg.xml file
  • Stand-alone node

    A stand-alone node does not use the node agent software and is the node type when you use WebSphere Application Server (base) or WebSphere Application Server Express®. Limited administrative functions are available. For example, plug-in propagation is possible if the web server is collocated on the same platform as the WebSphere Application Server base installation. Plug-in propagation is possible remotely if the web server is IBM HTTP Server and it is using IBM HTTP Server administration service.

[z/OS]

Special considerations - 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 WebSphere Application Server repository.
Important: When you use the z/OS Profile Management Tool, and select advanced profile creation to create a web server definition, you cannot select as web server type, IBM HTTP Server, and web server operating system, z/OS. However, you can create the web server type for IBM HTTP Server on z/OS through one of the following:
  • Administrative console wizard
  • createWebServerDefintion.jacl script
  • wsadmin command after the profile create
  • z/OS profile management tool
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.

IBM HTTP Server Administration Service

When you use IBM HTTP Server, the HTTP Server Administration Service can be installed to allow for limited administration, such as the start and stop of the IBM HTTP Server and the propagation of the plugin-cfg.xml file. These functions are not available to other supported web server types.

Non-IBM HTTP Servers cannot be administered from the WebSphere Application Server administrative console. As such, users must manually administer the propagation of the plug-in configuration file and handle starting and stopping the web server.