Development/Java & J2EE/Websphere 1 Related Topics: ---- ~~[Development/Java & J2EE/Websphere/Portal]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/TAM]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/WEBSeal]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/WASConsole]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/IBM HTTP Server]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/Versions]&nbsp;&nbsp;|&nbsp;&nbsp; [Development/Java & J2EE/Websphere/Java 2 Security]~~\\ ---- 1 Sever Starting/Stopping from command line Login to the machine that the server is on as the wasadmin user. {code} source /opt/WebSphere/AppServer/bin/setupCmdLine.sh first, then: /opt/WebSphere/AppServer/bin/startServer.sh <SEVERNAME> or /opt/WebSphere/AppServer/bin/stopSever.sh <SEVERNAME> eg. /opt/WebSphere/AppServer/bin/stopSever.sh WAS01 {code} 1 Node Agent Starting/Stopping For Network Deployment manager to be able to manage or get any information about a node, the Node Agent on that machine needs to be started. To do so, need to login as wasadmin on the machine where the node is to be started and {code} source /opt/WebSphere/AppServer/bin/setupCmdLine.sh first, then: /opt/WebSphere/AppServer/bin/startNode.sh or /opt/WebSphere/AppServer/bin/stopNode.sh {code} 1 Network Deployment Manager Starting/Stopping Need to login as wasadmin onto the ND Box (where the WASConsole is), and {code} source /opt/WebSphere/DeploymentManager/bin/setupCmdLine.sh first, then: /opt/WebSphere/DeploymentManager/bin/startManager.sh and /opt/WebSphere/DeploymentManager/bin//stopManager.sh {code} 1 Killing Server Processes Sometimes a server or node may not respond to a stop command. In this case if may be necessary to kill all the java processes on the box. If this is done, we need to ensure to also clean up the transaction and recovery logs for the server. 1.1 Killing the server As root: {code} killall -9 java {code} 1.1 Cleaning up transaction and recovery logs Delete all files from on the Portal Hosts under: ? /opt/Websphere/Appserver/translogs and \\ ? /opt/Websphere/Appserver/recoverylogs.\\ As wasadmin: {code} cd /opt/Websphere/Appserver/translogs rm ?rf * cd /opt/Websphere/Appserver/recoverylogs rm ?rf * {code} See [Development/Java & J2EE/Websphere/WASConsole] ND/WASConsole info. 1 DumpNameSpace To get the JNDI on a websphere box (port is found through wasconsole-server-endpoints-bootstrap) {code} $WAS_HOME/bin/dumpNameSpace.sh -host localhost -port 9811 {code} (username/password is the wasconsole one) 2006-10-25 15:39:34.0 2006-01-19 17:42:10.0