Configure NodeManager in a machine

Sometimes, it becomes little tricky to configure a nodemanager in a machine although it is quite simple. Follow the below steps:

1. Install Weblogic Fusion Middleware that comes along with the nodemanager component.
2. Navigate to /<Middleware_Home>/<Oracle_Home>/wlserver/server/bin
3. Check if there is any value set for NODEMGR_HOME => echo $NODEMGR_HOME
4. The default Home that is set is NODEMGR_HOME=”${WL_HOME}/../oracle_common/common/nodemanager”. This turns out to be /<Middleware_Home>/<Oracle_Home>/oracle_common/common/nodemanager
5. Make sure that you have the nodemanager.properties and the security/SerializedSystemIni.dat in your nodemanager home. Below is a most common nodemanager.properties used for Custom Identity and Custom Trust:

DomainsFile=<DOMAIN_HOME>/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=12.2.1.3.0
AuthenticationEnabled=true
NodeManagerHome=/<Middleware_Home>/<Oracle_Home>/oracle_common/common/nodemanager
JavaHome=<JDK_HOME>
LogLevel=INFO
DomainsFileEnabled=true
ListenAddress=10.207.76.227
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
weblogic.StartScriptName=startWebLogic.sh
SecureListener=true
LogCount=1
QuitEnabled=false
LogAppend=true
weblogic.StopScriptEnabled=false
StateCheckInterval=500
CrashRecoveryEnabled=false
weblogic.StartScriptEnabled=true
LogFile=<DOMAIN_HOME>/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=<CustomKeystorePath.jks>
CustomIdentityAlias=mwexpert.com
CustomIdentityKeyStorePassPhrase=<custompassword>
CustomIdentityKeyStoreType=JKS
CustomIdentityPrivateKeyPassPhrase=<custompassword>

Start the nodemanager using startNodeManager.sh