NonStop Server Guide for BEA WebLogic Server 9.2

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 9.2—529891-002
4-16
Starting the Node Manager from a Non-Default
Location
demo certificates, However, in this sample we have used successfully both true
and false settings:
rlserver 1: GUI, configuration, Keystore & SSL, Advanced
option: "Hostname Verification = BEA Hostname Verifier"
This means weblogic.security.SSL.ignoreHostnameVerification =
false.
rlserver 2: GUI, configuration, Keystore & SSL, Advanced
option: "Hostname Verification = none"
This means weblogic.security.SSL.ignoreHostnameVerification =
true.
•
Additional SSL debugging can be turned on by using the following properties:
-Dweblogic.StdoutDebugEnabled=true
-Dssl.debug=true
Also a debug file can be specified within
$WL_HOME/server/lib/unix/nodemanager.sh
•
It is assumed that the default SSL demo Keystore and certificates shipped with
WebLogic Server 9.2 are used. When the servers are created, they point to the
demo SSL configuration by default (see Keystores and SSL configuration tab).
This default allows an administrator to set up the Node Manager without initial SSL
administration knowledge.
Starting the Node Manager from a Non-Default
Location
The Node Manager can be used to control Managed Servers for several domains.
However, there may be situations where you want to run multiple Node Managers on
the same system, or run the Node Manager from a non-default location. To do either
task may require several changes.
By default, the script used to start the Node Manager sets NODEMGR_HOME to
$WL_HOME/common/nodemanager, and then uses that value as its current working
directory. This directory must contain nm-server.env, the server environment file
that is used by nodemanager.sh. This directory also contains subdirectories that are
used if CPUselector is instructed to use the managed_load load-balancing
algorithm. To use a different directory, change the startNodeManager.sh script to
set NODEMGR_HOME to a different value. Further, update the script to export the
NODEMGR_HOME variable (that is, export NODEMGR_HOME) so that the
nodemanager.sh script will use the new value. You could also update
nodemanager.sh to use the same value for NODEMGR_HOME instead of exporting the
variable.
To change the location of nodemanager.sh or CPUselector, the Node Manager
property named StartTemplate must be changed. By default, the value