To shut down the SOA, OSB, BAM, ESS, and WSM managed servers, simply run the following commands:

cd $DOMAIN_HOME/bin
./stopManagedWebLogic.sh soa_server1 t3://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1
./stopManagedWebLogic.sh osb_server1 t3://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1
./stopManagedWebLogic.sh bam_server1 t3://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1
./stopManagedWebLogic.sh ess_server1 t3://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1
./stopManagedWebLogic.sh wsm_server1 t3://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1

In a clustered installation, you can run the commands to start up and shut down all the managed servers from the same host, as the commands are anyway sent to AdminServer for processing, making no difference as to where they are initiated from.

Shutting down AdminServer simply involves the execution of the stopWebLogic.sh script as shown via the following commands:

cd $DOMAIN_HOME/bin
./stopWebLogic.sh

There is no way but through the command line (or WLST) to stop the Node Manager process. This can simply be done by running the stopNodeManager.sh script:

cd $DOMAIN_HOME/bin
./stopNodeManager.sh

This can also be done by running the following command to obtain the process IDs of the Node Manager processes and killing them:

ps -ef | grep NodeManager | grep -v grep | awk '{print $2}' | xargs kill -9

Simply shutting down one or more of the managed servers, including AdminServer, can be done from the WebLogic Server Administration Console.

To shut down a managed server, go through the following steps:

This can simply be done by running the stopNodeManager.sh script:

cd $DOMAIN_HOME/bin
./stopNodeManager.sh

Or, the process can be killed directly:

ps -ef | grep NodeManager | grep -v grep | awk '{print $2}' | xargs kill -9

WLST can be used to shut down the managed servers. The instructions here connect to and issue commands through AdminServer. It is possible to shut down all managed servers in a cluster or each managed server individually.

To shut down any of the SOA, OSB, BAM, or WSM managed servers, use WLST to connect to AdminServer and then initiate the start commands for each managed server:

$WL_HOME/common/bin/wlst.sh
wls:/offline> connect('weblogic', 'welcome1', 't3://adminhost:7001')
wls:/soa_domain/serverConfig> shutdown('soa_server1', 'Server')
wls:/soa_domain/serverConfig> shutdown('osb_server1', 'Server')
wls:/soa_domain/serverConfig> shutdown('bam_server1', 'Server')
wls:/soa_domain/serverConfig> shutdown('ess_server1', 'Server')
wls:/soa_domain/serverConfig> shutdown('wsm_server1', 'Server')

Alternatively, you can shut down an entire cluster by issuing a single command as shown in the following commands:

wls:/soa_domain/serverConfig> shutdown('soacluster', 'Cluster')
wls:/soa_domain/serverConfig> shutdown('osbcluster', 'Cluster')
wls:/soa_domain/serverConfig> shutdown('bamcluster', 'Cluster')
wls:/soa_domain/serverConfig> shutdown('esscluster', 'Cluster')
wls:/soa_domain/serverConfig> shutdown('wsmcluster', 'Cluster')

Thus, all managed servers within that cluster are brought down with a single command.

AdminServer is stopped no differently than a regular managed server. The following WLST command shuts down AdminServer:

$WL_HOME/common/bin/wlst.sh
wls:/offline> connect('weblogic', 'welcome1', 't3://adminhost:7001')
wls:/soa_domain/serverConfig> shutdown('AdminServer', 'Server')

Stopping Node Manager is done manually on every node of the cluster. Unless you are going through a major upgrade, it is often rare and unnecessary to bring down Node Manager, even when performing regular administrative or maintenance activities. But should you choose to, you must connect to Node Manager before shutting it down through WLST. Execute the following commands to shut down Node Manager:

$WL_HOME/common/bin/wlst.sh
wls:/offline> nmConnect('weblogic', 'welcome1', 'soahost1', '5556', 'soa_domain', '/u01/oracle/products/Oracle_SOA1/user_projects/domains/soa_domain')
wls:/offline> stopNodeManager()
Verifying server shutdown

On Linux, when a managed server is successfully shut down, there are no active processes. Issuing a simple operating system command to check processes should return no active processes. For example, running the ps command should return nothing if the server is indeed down:

ps -ef | grep soa_server1 | grep -v grep
ps -ef | grep osb_server1 | grep -v grep
ps -ef | grep bam_server1 | grep -v grep
ps -ef | grep ess_server1 | grep -v grep
ps -ef | grep wsm_server1 | grep -v grep

Likewise, if AdminServer is down, it should also return nothing:

ps -ef | grep AdminServer | grep -v grep

Finally, the same applies to Node Manager. No output should be returned if Node Manager is truly down:

ps -ef | grep NodeManager | grep -v grep

Alternatively, you can observe the last lines of the system out files to confirm whether the server is down or not.