Administrating WebSphere : Start/Stop/Status, Kill Sessions

Check Server Status:

$WAS_HOME/profiles/Profile01/Node01/bin/serverStatus  server1(JVM NAME)
serverStatus -all (returns status for all defined servers)
serverStatus -trace (produces the serverStatus.log file)

Stop WebSphere :

ps -eaf | grep java
i.e. Dmgr ,nodeagent, prod_server_member2,prod_server_member4

sudo -u %was_user% -i
cd /opt/IBM/WebSphere/AppServer/profiles/Profile01/Nodes/bin
./stopServer.sh prod_server_member2
./stopServer.sh prod_server_member4
./stopNode.sh

cd /opt/IBM/WebSphere/AppServer/profiles/Profile01/Dmgr/bin
./stopServer.sh Dmgr

Start WebSphere : Check to see if java processes do not exist

cd /opt/IBM/WebSphere/AppServer/profiles/Profile01/Dmgr/bin
./startServer.sh Dmgr

cd /opt/IBM/WebSphere/AppServer/profiles/Profile01/Nodes/bin
./startNode.sh
./startServer.sh prod_server_member2
./startServer.sh prod_server_member4

ps -eaf | grep java (check to see if java processes do not exist)
i.e. Dmgr, nodeagent, prod_server_member2, prod_server_member4

To get just pid for killing processes use $ ps -ef | grep java | grep dev_server_member2 | awk ‘{print $2}’
8867
8880

Using apachectl commands to start IBM HTTP Server

$sudo -u was61 -i
/opt/IBM/HTTPServer/bin/apachectl start
/opt/IBM/HTTPServer/bin/apachectl stop

$sudo /opt/IBM/HTTPServer/bin/apachectl start

To list all the jvm process that websphere is running..

1. ps-ef | grep <path to websphere java>
ps -ef | grep /<was_root>/java
wasadm 18445 18436 0 13:48:33 pts/9 0:00 grep <was_root>/java
wasadm 9959 1 0 Feb 18 ? 4:17 <was_root>/java/bin/java -XX:MaxPermSize=256m -Dwas.status.socket=49743 -X
wasadm 9927 1 0 Feb 18 ? 5:10 <was_root>/java/bin/java -XX:MaxPermSize=256m -Dwas.status.socket=49611 -X

2. pgrep -f -u $WASUSER $ENVPATH

Log File locations

Httpd Logs : /opt/IBM/HTTPServer/logs

WAS logs :
[was61@bin]$ ls -l $WAS_HOME/profiles/Profile01/Node01/logs
total 2092
-rw-r–r– 1 was61 web 2097152 Jan 12 10:28 activity.log
drwxr-xr-x 2 was61 web    4096 Jan 12 09:55 dev_server_member1
drwxr-xr-x 2 was61 web    4096 Jan 11 16:20 dev_server_member2
drwxr-xr-x 2 was61 web   28672 Jan 12 10:10 ffdc
drwxr-xr-x 2 was61 web    4096 Jan  8 16:31 nodeagent

$WAS_HOME/profiles/Profile01/Node01/logs/nodeagent/:
total 1116
-rw-r–r– 1 was61 web      83 Jan 11 16:57 monitor.state
-rw-r–r– 1 was61 web   11534 Jan 11 16:57 native_stderr.log
-rw-r–r– 1 was61 web   11400 Jan  8 16:31 native_stdout.log
-rw-r–r– 1 was61 web       0 Jan  8 16:31 nodeagent.pid
-rw-r–r– 1 was61 web   12288 Jan  8 16:31 startServer.log
-rw-r–r– 1 was61 web   15491 Jan  8 16:24 stopServer.log
-rw-r–r– 1 was61 web   11400 Jan  8 16:31 SystemErr.log
-rw-r–r– 1 was61 web 1048525 Jan  8 15:26 SystemOut_10.01.08_15.27.29.log
-rw-r–r– 1 was61 web   17125 Jan 11 16:57 SystemOut.log