Administer nodes and resources
We can monitor and control incorporated nodes and the resources on those nodes using these tasks with the administrative console or other administrative tools.
After setting up the WAS Network Deployment product, you mainly need to monitor and control incorporated nodes and the resources on those nodes using the administrative console or other administrative tools. Use the following tasks to perform these activities.
- Manage nodes.
- Configure cells.
- Configure deployment managers.
- Manage node agents.
- Manage node groups.
- Administer stand-alone application servers on the same computer using an administrative agent.
- Administer stand-alone application servers and deployment managers remotely using a job manager.
- Configure remote file services.
- Use the settings page for an administrative service to configure administrative services.
- (zos) Configure location service daemons on the z/OS system.
- Administer job managers.
- Change the host name.
What to do next
Administer nodes and node resources as needed using the administrative console or other administrative tools.
- Work with nodes - groups of managed servers
A node is a grouping of managed or unmanaged servers. We can add both managed and unmanaged nodes to the product topology. If we add a new node for an existing WebSphere application server to the network deployment cell, you add a managed node. If we create a node in the topology for managing web servers or servers other than WebSphere application servers, you add an unmanaged node. We can add, configure, remove, and otherwise work with nodes, node agents, and node groups.
- Work with cells - groups of nodes
When creating a dmgr profile, a cell is created. A cell provides a way to group one or more nodes of the product. We can configure the cell. After configuring a cell, you probably do not need to configure the cell again.
- Work with deployment managers - centralized cell management
A deployment manager is an administration application created when you add a cell or deployment manager management profile to a Network Deployment product. With the deployment manager, we can administer multiple nodes.
- Administer stand-alone nodes using the administrative agent
We can configure an administrative agent, view or change stand-alone application server nodes registered to the administrative agent, and view or change job manager configurations for a registered node. An administrative agent provides a single interface to administer application servers in, development, unit test, or server farm environments, for example.
- Administer nodes remotely using the job manager
In a flexible management environment, we can asynchronously submit and administer jobs for large numbers of stand-alone application servers, deployment managers, and host computers over a geographically dispersed area. At the remote machines, we can use jobs to manage applications, modify the product configuration, or do general purpose tasks such as run a script.
- Configure administration services
We can configure administration services such as remote file services, repository services, and JMX (JMX) connectors.
- Administration service settings
Use this page to view and change the configuration for an administration service.
- Administration services custom properties
This topic discusses the administration services custom properties that we can set on the administrative console.
- (zos) Manage nodes and resources on z/OS
The z/OS location service daemon starts automatically if it is not already running when you start an application server or a deployment manager server. Manage the location service daemon in a console. Location service daemons provide the CORBA location service in support of Remote Method Invocation and Internet Inter-ORB Protocol (RMI/IIOP). The daemon works with z/OS workload management to distribute RMI requests (for example, enterprise bean requests) among application servers in a cell. A location service daemon process runs on each system that has a node in a sysplex node group. One location service daemon exists for each sysplex node group in a cell.
- Administrative topology: Resources for learning
Use the following links to find relevant supplemental information about WebSphere Application Server administrative topologies and distributed administration. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.
- Configure checkpoints
Repository checkpoints represent saved images of the repository before configuration changes are made. Checkpoints are either full or delta images. A full checkpoint is created manually by the administrator and is a copy of the entire configuration repository. This includes applications and connectors. Delta checkpoints are optional and are not enabled by default. A delta checkpoint is created automatically when configuration changes are made and saved to the configuration repository. The delta checkpoint is formed by making a copy of the configuration documents affected by the configuration change before changes are actually applied.
Managed and unmanaged nodes Node groups Administrative agent Job manager Configuration documents Remote files services for file transfer and file synchronization
Adding, managing, and removing nodes Configure cells
(iseries) Start the WAS Network Deployment environment
Configure deployment managers Start and stop the deployment manager
(iseries) Start and stop a node
Viewing, configuring, creating, and deleting node groups Manage node agents Start and stop the administrative agent Start and stop the job manager Administer nodes remotely using the job manager Configure remote file services
(zos) Stopping or canceling the z/OS location service daemon from the MVS console
(zos) Determine if the z/OS location service daemon is running
(zos) Modify z/OS location service daemon settings
Change the node host names