#oracleweblogic
To work with this NodeManager tutorial you must visit 'WebLogic domain configuration'.
Configure 2 WebLogic domains to test the Nodemanager per host.
NODEMANAGER PER HOST
=================
Assumption here FT_domain, uat_domain are readily available for nodemanager to start the corresponding adminServer.
NM_HOME we need to create when we place the nodemanager.domains file placed that will becomes the NM_HOME. And when you run startNodeManager.sh script will automatically creates the nodemanager.properties file.
1. Create nodemanager.domains file in $MW_HOME/oracle_common/common/nodemanager
mkdir -p $MW_HOME/oracle_common/common/nodemanager
cd $MW_HOME/oracle_common/common/nodemanager
touch nodemanager.domains
2. insert the following lines to tell the nodemanager that on this host two domains exists with domainpaths.
vi nodemanager.domains
FT_domain=/u01/app/oracle/domains/FT_domain
uat_domain=/u01/app/oracle/domains/uat_domain
3. Create wrapper script for common nodemanager. Start the per host NodeManager.
cd $WL_HOME/server/bin/
vi startnm.sh
clear
nohup $WL_HOME/server/bin/startNodeManager.sh greater than nm.out 2greater than &1 &
echo "less nm.out"
chmod +x startnm.sh
./startnm.sh
4. Using WLST connect the nodemanager with last argument as domain name. Then do the server control that is starting weblogic server instance or stop them.
wlst
nmConnect('weblogic','welcome1','192.168.33.102','5556', 'FT_domain')
nm()
nmStart('FT_admin')
nmDisconnect()
nmConnect('weblogic','welcome1','192.168.33.102','5556', 'uat_domain')
nm()
nmStart('uat_admin')
nmDisconnect()
nmConnect('weblogic','welcome1','192.168.33.102','5556', 'FT_domain')
nmKill('FT_admin')
nmDisconnect()
nmConnect('weblogic','welcome1','192.168.33.102','5556', 'uat_domain')
nmKill('uat_admin')
nmDisconnect()
NODEMANAGER PER DOMAIN
==================
Step 1: Select a domain to use the PER DOMAIN nodemanager, here I choosen demo_domain.
cd $DOMAIN_HOME/demo_domain
Step 2:[optional] modify ListenAddress, ListenPort in $DOMAIN_HOME/demo_domain/nodemanager/nodemanager.properties file.
Step 3: Start the per domain nodemanager
cd $DOMAIN_HOME/demo_domain/bin; ./startNodeManager.sh
Step 4: Assign the managed servers to the machine configured in the Admin console as shown in the video.
Step 5. Check the machine monitoring ensure it is reachable.
Step 6. Navigate to Servers in the domain structure, select "control" tab, check the desired server to be controlled. and click 'start' button. click on the refresh button given on the console -work area. Once a managed server is started then turn to another server on the same machine. If the servers on the multiple nodes then corresponding nodemagers must be started and then you can start multiple servers as well.
Please visit our blogs:
My FMW Experiments : https://myofmwexperiments.blogspot.com
WLST By Examples : https://wlstbyexamples.blogspot.com
WebLogic Tricks Tips: https://wlatricksntips.blogspot.com
DevOps Hunter : https://devopshunter.blogspot.com
#PavanDevarakonda