3-2 Node Manager Administrators Guide for Oracle WebLogic Server
Node Manager is ready-to-run after WebLogic Server installation if you run Node Manager and the Administration Server on the same machine, and use the
demonstration SSL configuration. By default, the following behaviors are configured:
■
You can start a Managed Server using Node Manager through the Administration Console.
■
Node Manager monitors the Managed Servers that it has started.
■
Automatic restart of Managed Servers is enabled. Node Manager restarts server instances that it killed or were killed by another method.
3.2.1 Controlling and Configuring Node Manager Using WLST
The WebLogic Scripting Tool WLST is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances
and domains. You can start, stop, and restart server instances remotely or locally, using WLST as a Node Manager client. In addition, WLST can obtain server status and
retrieve the contents of the server output log and Node Manager log. For more information on WLST commands, see WLST Command and Variable Reference in
WebLogic Scripting Tool Command Reference.
3.2.1.1 Using nmConnect in a Production Environment
WLST can connect to a Node Manager that is running on any machine and start one or more WebLogic Server instances on the machine. A domains Administration Server
does not need to be running for WLST and Node Manager to start a server instance using this technique.
However, by default, the nmConnect command cannot be used in a production environment. You must first perform the following procedures to use nmConnect in a
production environment.
1.
Start the Administration Server.
2.
Using the Administration Console, update the Node Manager credentials from the Advanced options under domain_name Security General.
3.
Invoke WLST and connect to an Administration Server using the connect command. See Using the WebLogic Scripting Tool in Oracle WebLogic Scripting
Tool.
4.
Run nmEnroll using the following syntax: nmEnroll[domainDir], [nmHome]
For example, nmEnrollC:oracleuser_projectsdomainsprod_domain,
C:oraclewlserver_10.3commonnodemanager Running nmEnroll ensures that the correct Node Manager user and password
token are supplied to each Managed Server. Once these are available for each Managed Server, you can use nmConnect in a production environment.
Note: You must run nmEnroll on each machine that is running a
Managed Server. Additionally, you should run nmEnroll for each domain directory on each machine.
General Node Manager Configuration 3-3
3.3 Step 2: Specify Node Manager Username and Password
