Servers: Configuration: Server Start
Configuration Options Related Tasks Related Topics
Node Manager is a WebLogic Server utility that you can use to start, suspend, shut down, and restart servers in normal or unexpected conditions. Use this page to configure the startup settings that Node Manager will use to start this server on a remote machine.
Name Description Java Home
The Java home directory (path on the machine running Node Manager) to use when starting this server.
Specify the parent directory of the JDK's
bindirectory. For example,
The Java Vendor value to use when starting this server For example,
BEA, Sun, HP etc
If the server is part of a cluster and configured for automatic migration across possibly different platforms with different vendors providing the JDKs, then, both JavaVendor and JavaHome should be set in the generated configuration file instead.
The BEA home directory (path on the machine running Node Manager) to use when starting this server.
Specify the directory on the Node Manager machine under which all BEA products were installed. For example,
The directory that this server uses as its root directory. This directory must be on the computer that hosts the Node Manager. If you do not specify a Root Directory value, the domain directory is used by default.
The classpath (path on the machine running Node Manager) to use when starting this server.
At a minimum you will need to specify the following values for the class path option:
WL_HOMEis the directory in which you installed WebLogic Server on the Node Manager machine.
The shell environment determines which character you use to separate path elements. On Windows, you typically use a semicolon (;). In a BASH shell, you typically use a colon (:).
The arguments to use when starting this server.
These are the first arguments appended immediately after
javaportion of the startup command. For example, you can set Java heap memory or specify any
This property should not be used to specify weblogic.management.username or weblogic.management.password as these values will be ignored during server startup. Instead the username and password properties should be set. This will also enable node manager to properly encrypt these values on the managed server's machine.
Separate arguments with a space.
Security Policy File
The security policy file (directory and filename on the machine running Node Manager) to use when starting this server.
The user name to use when booting this server.
The Administration Console inserts the user name that you supplied when you logged in to the console. The Domain Configuration Wizard inserts the user name that you defined when you created the domain.
The password of the username used to boot the server and perform server health monitoring.
As of 8.1 sp4, when you get the value of this attribute, WebLogic Server does the following:
Retrieves the value of the
Decrypts the value and returns the unencrypted password as a String.
When you set the value of this attribute, WebLogic Server does the following:
Encrypts the value.
Sets the value of the
PasswordEncryptedattribute to the encrypted value.
Using this attribute (
Password) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM's memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory.
Instead of using this attribute, use
- Configure startup arguments for Managed Servers
- Start Managed Servers from the Administration Console
- Shut down a server instance