Technical data

4 Configuring, Starting, and Stopping Node Manager
4-8 Configuring and Managing WebLogic Server
Properties that are specific to a server instance are specified on the
The syntax for starting Node Manager is:
java [java_property=value ...] -D[nodemanager_property=value]
-D[server_property=value] weblogic.NodeManager
Note: WebLogic Server 8.1 provides a new wrapper to
weblogic.nodeManager.NodeManager. The new wrapper is
weblogic.NodeManager
In the command line, a java_property indicates a direct argument to the java
executable, such as -ms or -mx. If you did not set the CLASSPATH environment
variable, use the
-classpath option to identify required Node Manager classes.
Node Manager communicates with its clients using two-way SSL. The Administration
Server SSL configuration applies to the domain as a whole. After configuring the
Administration Server, each Node Manager instance that you run in the domain must
specify startup arguments that identify the keystore, password, and certificate files to
use for SSL communication:
! weblogic.nodemanager.keyFile
! weblogic.nodemanager.keyPassword
! weblogic.nodemanager.certificateFile
! weblogic.security.SSL. trustedCAKeyStore
! weblogic.nodemanager.sslHostNameVerificationEnabled
For example, to start Node Manager using the SSL configuration provided with the
sample SSL certificate and key files:
java.exe -Xms32m -Xmx200m -classpath %CLASSPATH% -Dbea.home=c:\bea
-Dweblogic.nodemanager.keyFile=e:\bea\user_domains\mydomain\demok
ey.pem
-Dweblogic.security.SSL.trustedCAKeyStore=e:\bea\weblogic700\serv
er\lib\cacerts
-Dweblogic.nodemanager.certificateFile=e:\bea\user_domains\mydoma
in\democert.pem
-Djava.security.policy=e:\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false
weblogic.NodeManager