Related Topics:
Portal | TAM | WEBSeal | WASConsole | IBM HTTP Server | Versions |
Java 2 Security
Sever Starting/Stopping from command line
Login to the machine that the server is on as the wasadmin user.
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
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
source /opt/WebSphere/AppServer/bin/setupCmdLine.sh first, then:
/opt/WebSphere/AppServer/bin/startNode.sh
or /opt/WebSphere/AppServer/bin/stopNode.sh
Network Deployment Manager Starting/Stopping
Need to login as wasadmin onto the ND Box (where the WASConsole is),
and
source /opt/WebSphere/DeploymentManager/bin/setupCmdLine.sh first, then:
/opt/WebSphere/DeploymentManager/bin/startManager.sh
and
/opt/WebSphere/DeploymentManager/bin//stopManager.sh
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.
Killing the server
As root:
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:
cd /opt/Websphere/Appserver/translogs
rm ?rf *
cd /opt/Websphere/Appserver/recoverylogs
rm ?rf *
See
WASConsole ND/WASConsole info.
DumpNameSpace
To get the JNDI on a websphere box (port is found through wasconsole-server-endpoints-bootstrap)
$WAS_HOME/bin/dumpNameSpace.sh -host localhost -port 9811
(username/password is the wasconsole one)
