When I recently created my own Machine on Weblogic on Linux , I found that the status of the monitored nodeManager was always abnormal. After searching the information, it is found that the configuration used when starting the nodeManager is enabled by the secure access protocol by default, that is, SecureListener=true . When creating Machine , the communication method was selected as normal, so that the two could not be connected, so the problem this time is actually caused by the inconsistency of the protocols used between the two, as long as the communication protocol between the two is guaranteed. You can agree. That is, if the default configuration is used, the communication method needs to be selected as SSL when establishing the Machine .
The command path to start nodeManager on Linux is $WL_HOME/wlserver/server/bin/startNodeManager.sh . The default nodeManager home directory it uses is $WL_HOME/oracle_common/common/nodemanager , in which there is a nodemanager.properties file, which is the default configuration file used when calling startNodeManager.sh . The default configuration of nodemanager.properties on my machine is as follows:
DomainsFile=/home/weblogic/Oracle/Middleware/Oracle_Home/oracle_common/common/nodemanager/nodemanager.domains
LogLimit = 0
PropertiesVersion=12.1.3
DomainsDirRemoteSharingEnabled=false
AuthenticationEnabled=true
JavaHome=/usr/java/jdk1.8.0_31
LogLevel=INFO
DomainsFileEnabled=true
ListenAddress=127.0.0.1
NativeVersionEnabled=true
ProcessDestroyTimeout=20000
ListenPort=5556
weblogic.StartScriptName=startWebLogic.sh
LogToStderr=true
SecureListener=true
LogCount=1
LogAppend=true
weblogic.StopScriptEnabled=false
StateCheckInterval = 500
CrashRecoveryEnabled=false
weblogic.StartScriptEnabled=true
LogFile=/home/weblogic/Oracle/Middleware/Oracle_Home/oracle_common/common/nodemanager/nodemanager.log
coherence.StartScriptEnabled=false
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
When we start the nodeManager under the managed server, we may be prompted that a certain domain does not exist. At this time, we need to manually specify the path of the corresponding domain in the nodeManager.domains file in the home directory of the nodeManager . The format is : domainName=domainPath .