Technical data

Configuring Node Manager
Configuring and Managing WebLogic Server 4-3
a. “Set Up the Node Manager Hosts File” on page 4-3
b. “Reconfigure Startup Service” on page 4-4
c. “Update nodemanager.properties” on page 4-4
d. “Configure a Machine to Use Node Manager” on page 4-5
e. “Configure Managed Server Startup Arguments” on page 4-5
f. “Ensure Administration Server Address is Defined” on page 4-5
! Configure Node Manager for production security components—By default
Node Manager runs with demonstration security components. To use production
security components, “Configure SSL for Node Manager” on page 4-6.
! Tailor monitoring and restart behavior—To change Node Manager’s
monitoring, shutdown and restart behaviors, see “Configure Monitoring,
Shutdown and Restart for Managed Servers” on page 4-6.
Set Up the Node Manager Hosts File
Node Manager accepts commands from Administration Servers running on the same
machine and on trusted hosts. Trusted hosts are identified by IP address or DNS name
in the
nodemanager.hosts file, which is installed in the
WL_HOME\common\nodemanager\config directory, where WL_HOME is the top-level
installation directory for WebLogic Server.
Note: You can specify a different name and location for the trusted hosts file using
the
weblogic.nodemanager.trustedHosts command-line argument. For
more information, see “Node Manager Properties” on page 4-10.
By default,
nodemanager.hosts is empty. To add trusted hosts, edit the file with a
text editor, and add one line for each trusted host on which an Administration Server
runs. If you want Node Manager to accept commands from any host, put an asterisk in
the hosts file.
If you identify a trusted host by its DNS name, you must enable reverse DNS lookup
when starting Node Manager. By default, reverse DNS lookup is disabled. You can
enable reverse DNS lookup with the command-line argument:
-Dweblogic.nodemanager.reverseDnsEnabled=true