Database Reference
In-Depth Information
Starting up the SOA and BAM managed servers
Start up the SOA and BAM managed servers on each node of the cluster, update
the highlighted managed server name, hostname, and port to reflect your envir-
onment as follows:
cd $MW_HOME/user_projects/domains/$DOMAIN/bin
nohup ./startManagedWebLogic.sh soa_server1 http://soahost1:8001 &
nohup ./startManagedWebLogic.sh bam_server1 http://soahost1:9001 &
Repeat the preceding command for other nodes in the cluster. For example, in a
two-node cluster, start up the second node on the second server as follows:
cd $MW_HOME/user_projects/domains/$DOMAIN/bin
nohup ./startManagedWebLogic.sh soa_server2 http://soahost2:8001 &
nohup ./startManagedWebLogic.sh bam_server2 http://soahost2:9001 &
Shutting down Node Manager
Unfortunately there is no way to gracefully shutdown the Node Manager and it
has to be force killed. To kill Node Manager, simply run the following command
to obtain the process IDs of the Node Manager processes and kill them:
ps -ef | grep NodeManager | grep -v grep | awk '{print $2}' | xargs kill -9
Shutting down AdminServer
Shutting down
AdminServer
involves simply executing the
stopWebLo-
gic.sh
script as shown:
cd $DOMAIN_HOME/bin
./stopWebLogic.sh
