Node Managers Fight

Many a times we have a situation where there are two managed server instances both belonging to two different domains residing on the same physical box.

Well, under such a situation both managed servers may use the same nodemanager.properties and booting on different ports, if they both use the same property configuration.

However, such a situation is unrealistic. More often it is observed that two domain have thier own SSL certicates which are different. Also the nodemanager logs for both the managed instances be generated seperately. One may require CrashRecoveryEnabled set to true and the other may not require.

Thus, we would need two nodemanager.properties file each for each managed server.

Well, this is how it can be achieved.

1. Make two copies of "${weblogic_home}/common/nodemanager" folder.

You may place it at any location of your choice.

Say:

(managed server 1)

"/opt1/nodemanager"

(managed server 2)

"/opt2/nodemanager"

2. While enrolling managed server 1 using WLST give the path of the first copy of the nodemanager folder

While enrolling managed server 2 using WLST give the path of the second copy of the nodemanager.

(managed server 1)

nmEnroll("/opt1/nodemanager")

(managed server 2)

nmEnroll("/opt2/nodemanager")

3. Now you may use startNodeManager.cmd script and pass different port numbers inorder to start two different instances of nodemanager process.

Windows:

(managed server 1)

startNodeManager.cmd 192.12.1.17 4445

(managed server 2)

startNodeManager.cmd 192.12.1.17 4444

Unix:

(managed server 1)

nohup ./startNodeManager.sh 192.12.1.17 4445 &

(managed server 2)

nohup ./startNodeManager.sh 192.12.1.17 4444 &

Kindly let me know if it was helpful.