You 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, you must 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 WebSphere Application
Server 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. You can also define
a Web server object in the WebSphere Application Server repository using the
profile create script during installation, a .jacl script, and by
using the administrative console wizard.
There are three types of WebSphere Application Server
nodes upon which you can create a Web server. The type depends on the version
of WebSphere Application Server, as follows:
- Managed node. A node that contains 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 WebSphere Application Server (powered by Apache) on z/OS
and for 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 an base or Express WebSphere Application Server 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 WebSphere Application Server (powered
by Apache) for zOS and Version 5.3 HTTP Server for zOS 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 WebSphere
Application Server node agent. This node cannot be federated. Typically,
the unmanaged node represents a remote machine that does not have WebSphere
Application Server installed. However, you can define an unmanaged node on
a machine where WebSphere Application Server is installed. This node can exist
in a WebSphere Application Server – Express, 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 WebSphere
Application Server (powered by Apache) for zOS and Version 5.3 HTTP Server
for zOS 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 WebSphere
Application Server, are not fully administered from the WebSphere Application
Server administrative 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
Use 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 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.
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.
- 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 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.