Technical data

3 Overview of Node Manager
3-4 Configuring and Managing WebLogic Server
development environment, you may wish to run Node Manager on a machine that
hosts an Administration Server and one or more Managed Servers, because doing so
allows you to start and stop the Managed Servers using the Administration Console.
Node Manager Should Run as a Service
The WebLogic Server installation process installs Node Manager to run as a daemon
on UNIX machines or as a Windows service on Windows-based machines. A key
Node Manager feature is the ability to restart Managed Servers after a failure. If the
failure is a machine crash, running Node Manager as a service ensures that Node
Manager starts up automatically when the machine reboots, and is available to restart
Managed Servers on that machine.
Node Manager is Domain-Independent
A Node Manager process is not associated with a specific WebLogic domain. Node
Manager resides outside the scope of a domain, and you can use a single Node
Manager process to start Managed Servers in any WebLogic Server domain that it can
access—in Figure 3-1, Managed Server 2 and Managed Server 3 could be in separate
domains, and controlled by a single Node Manager process.
Node Manager Clients
You can invoke Node Manager’s capabilities using the WebLogic Server
Administration Console or JMX clients such as the
weblogic.Admin command-line
utility. Typically, Node Manager is called by an Administration Server on a remote
machine. However, Node Manager can be called by local Administration Server as
well—allowing you to issue commands to co-resident Managed Servers using the
Administration Console.