You can define a Web server definition in a managed node or in an unmanaged node.
WebSphere Application Server for z/OS does not support remote administration of IBM HTTP Server.
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 WebSphere Application Server for z/OS cell. Create the managed node with the Customization Dialog, either directly or by federating a stand-alone application server; then use the administrative console to create the Web server definition.
WebSphere Application Server for z/OS V6.0.1 provided optional jobs BBOACFGW and BBOMCFGW for this purpose; these jobs were removed in V6.0.2.
When a Web server definition is defined in a managed node, you can regenerate the plugin-cfg.xml configuration file directly to the Web server configuration directory location. You can then retrieve, edit, and replace the httpd.conf file that controls Web server operation.
In WebSphere Application Server for z/OS V6.0.2, you can also start and stop the Web server using the administrative console.
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 WebSphere Application Server for z/OS managed node.
Use the Customization Dialog job BBOWCFGW (stand-alone application server) or BBODCFGW (for a Network Deployment cell) to create an unmanaged node and a Web server definition.
When a Web server definition is defined in an unmanaged node, you can regenerate the plug-in configuration file, but cannot edit the httpd.conf file. If the Web server does not share a read and write configuration directory with the z/OS system running the stand-alone application server or deployment manager, you are responsible for moving the plugin-conf.xml file to the z/OS system for the Web server.