Web server definition
To manage Web servers using the admin console, create a Web server definition 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 the Web server from the admin console.
The Web server object contains the following Web server properties:
- installation root
- port
- configuration file paths
- log file paths
- plug-in object
The plug-in object contains properties that define plugin-cfg.xml.
Web server definitions are made using...
- admin console wizard
- wsadmin profile create script
WAS nodes upon which we can create a Web server...
- Managed node
Contains a node agent. Exists only in a dmgr environment. Administration of the Web server is handled through the node agent from the admin console. Support is limited to IBM HTTP Server only.
Non-IBM HTTP Server Web servers must be on a managed node to handle plug-in admin functions and the generation and propagation of plugin-cfg.xml.
- Stand-alone node
Does not contain a node agent. Exists in an base or Express WAS environment. A stand-alone node can become a managed node in a dmgr environment after the node is federated.
To administer IHS, there must be an IHS administration server running on the stand-alone machine that the node represents. IHS ships with the IHS administration server, which is installed by default. Support for administration through the admin console is limited to IHS only.
- Unmanaged node
Does not contain a node agent. Cannot be federated. Typically, unmanaged nodes represent remote machines that do not have WAS installed.
We can define an unmanaged node on a machine where WAS is installed. This node can exist in a WAS Express, base, or dmgr environment. An unmanaged node does not contain a node agent, so to administer and manage IHS, an IHS administration server must be installed and running on the stand-alone machine that the node represents.
Support for administration and configuration through the admin console is limited to IBM HTTP Server only.
Admin functions for non-IHS Web servers include...
- On managed nodes:
- Web server status in the Web server collection panel or serverStatus.sh
- Generation of plugin-cfg.xml
- Propagation of plugin-cfg.xml
- On unmanaged nodes:
- Web server status in the Web server collection panel or serverStatus.sh
- Generation of the plugin-cfg.xml
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 WAS repository.
During profile creation, using the z/OS Profile Management Tool, if we 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 admin console wizard, createWebServerDefintion.jacl, or the wsadmin command after the profile create, using the z/OS Profile Management Tool.