Web-based workloads on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


Application server configuration on z/OS

Web-based workloads on z/OS

An application server configuration on z/OS® includes base server node and the Network Deployment Manager.

Base server node

The base application server node is the simplest operating structure in the Application Server for z/OS. It consists of an application server and a daemon server (one node and one cell), as shown in Figure 1. All of the configuration files and definitions are kept in the HFS directory structure created for this base application server. The daemon server is a special server with one controller region. The system architecture of WebSphere® for z/OS calls for one daemon server per cell per system or LPAR.

Each base application server node contains administration for its own cell domain and a separate repository for its configuration. Therefore, you can have many base application servers, each isolated from the others, having their own administration policy for their specific business needs.

Figure 1. Base server nodeBase server node

Network Deployment Manager

Network Deployment Manager (Figure 2) is an extension to the base application server. It allows the system to administer multiple application servers from one centralized location. Here, application servers are attached to nodes, and multiple nodes belong to a cell. With the Deployment Manager, horizontally and vertically scaled systems, as well as distributed applications, can be easily administered.

The Network Deployment Manager also manages the repositories on each node, performing such tasks as creating, maintaining, and removing the repositories. The system uses an extract/modify method to update the configuration.

Figure 2. Network Deployment ManagerNetwork Deployment Manager




Copyright IBM Corporation 1990, 2010