These sections provide information on how to start and stop the Java-based and script-based Node Manager. It also provides information on the recommended procedures for starting servers using Node Manager:
On Windows, you can use a shortcut on the Start menu to start the Node Manager (ToolsNode Manager).
It is recommended that you install Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted. Seein the Installation Guide.
By default, Node Manager listens only from the local host. If you want Node Manager to accept commands from remote systems, you must uninstall the default Node Manager service, then reinstall it to listen on a non-localhost listen address. See Reconfigure Startup Service for Windows Installations.
Although running Node Manager as an operating system service is recommended, you can also start Node Manager manually at the command prompt or with a script. The environment variables Node Manager requires are described in Step 8: Set the Node Manager Environment Variables.
Sample start scripts for Node Manager are installed in the
\server\bin directory, where
WL_HOME is the top-level installation directory for WebLogic Server. Use
startNodeManager.cmd on Windows systems and
startNodeManager.sh on UNIX systems.
The scripts set the required environment variables and start Node Manager in
/common/nodemanager. Node Manager uses this directory as a working directory for output and log files. To specify a different working directory, edit the start script with a text editor and set the value of the
NODEMGR_HOME variable to the desired directory.
Edit the sample start script to make sure that the command qualifiers set the correct listen address and port number for your Node Manager process.
The syntax for starting Java-based Node Manager is:
java_optionis a direct argument to the
javaexecutable, such as
|Note:||If you did not set the
nodemanager_propertyis a Node Manager property. Instead of supplying Node Manager property values on the command line, you can edit the
nodemanager.propertiesfile, which is installed in the directory where you start Node Manager. For more information, see Reviewing nodemanager.properties.
server_propertyis a server-level property that Node Manager accepts on the command line, including:
|Note:||If you run Node Manager on a UNIX operating system other than Solaris or HP UX, you cannot have any white space characters in any of the parameters that will be passed to the
|Note:||For UNIX systems other than Solaris, HP-UX, and Linux operating systems, you must disable the
To use the SSH Node Manager Command Shell, start the Administration Server using the following command line option:
weblogic.nodemanager.ShellCommand=’ssh -o PasswordAuthentication=no %H wlscontrol.sh -d %D -r %R -s %S -x -c -f sample_custom_startscript.sh %C’
weblogic.nodemanager.ShellCommand attribute specifies the command template to use to communicate with a remote SSH Node Manager and execute Node Manager functions for server instances under its control.
The template assumes that
wlscontrol.sh is in the default path on the remote machine hosting Node Manager.
ShellCommand syntax is:
ssh -o PasswordAuthentication=no %H wlscontrol.sh -d %D -r %R -s %S %C'
The possible command line options are listed in Table 6-1. The possible parameter values are listed in Table 6-2.
For example, if you type this command,
ssh -o PasswordAuthentication=no wlscontrol.sh myserver start
The listen address and port of the SSH server default to the listen address and port used by Node Manager on the remote machine. The domain name and domain directory are assumed to be the root directory specified for the target server instance,
ssh -o PasswordAuthentication=no 184.108.40.206 wlscontrol.sh -d ProductionDomain -r ProductionDomain -s ServerA'
START command to the server instance named
ServerA, in the domain called
ProductionDomain, located in the d
The ssh command must include the string:
This string passes the ssh
PasswordAuthentication option. A value of
yes causes the client to hang when it tries to read from the console.
To stop Node Manager, close the command shell in which it is running.
In general, it is recommended that you use the WebLogic Scripting Tool and Node Manager to start and stop the Administration Server and Managed Servers. This section describes the recommended procedures for starting servers using Node Manager and WLST.
For more information, seeand the in WebLogic Scripting Tool.
The following general procedures are recommended for starting an Administration Server using WLST and Node Manager.
After the Administration Server has been started, you can use WLST to start the Managed Servers in your domain.
|Notes:||Starting the server using the |
The following general procedures are recommended for starting a Managed Server using WLST and Node Manager.
start command causes WLST to contact the Administration Server to determine the Managed Servers startup properties. These are in turn passed to Node Manager and are used to start the Managed Server.
The following general procedures are recommended for starting a Managed Server using WLST and Node Manager if you do not want to use the Administration Server to determine a Managed Server’s startup properties:
Using the nmStart command allows you to restart a Managed Server without the Administration Server and to specify the server startup properties you want. However, the following considerations apply:
startup.propertiesare already defined.
nmStartshould not be used to permanently change the startup properties for a server. The next time a server is migrated or restarted from the Administration Server, these properties will not be used.
nmStart, these values are not encrypted.