Restarting WebSphere (WAS) after a reboot

To restart the Websphere (WAS) infrastructure services after a reboot, the following credentials are necessary for the four stages :




-username wasadmin

-password your_password

Red Hat Linux

-username root

-password your_password

1. Start the deployment manager

The deployment manager is a central administrative console that provides a single point of control for the administrative functions of an environment. After SSH-ing into the server, you navigate to the directory containing the script to start the deployment manager.

Ssh into the server using the Red Hat credentials above and type:

 cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin

This will have given you access to the WAS console; you’ll then need to start the nodeagents from the command line before you can talk to the WAS application servers.

2. Start the nodeagent on the first node

In WebSphere, a nodeagent provides the runtime environment for application server processes and performs node-level administrative operations. The procedure indicates how to start the nodeagent for the first node.

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/

3. Start the nodeagent on the second node

Similar to the previous step but likely intended for a second node (though the paths provided are the same, which might be an oversight).

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/

4. Start the application servers from the WAS console

Application servers are the runtime environments where your applications run. This step describes two methods: starting them from the command line or from the WAS console.

If you do need to start them from the command line, it’s just…

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/       
./ server_name_you_want_to_start

Or, on the WAS console, go to Servers, then Application servers and select the checkbox for each server and click on the start button for each application server that needs starting.

*** NB you need to start the Dmgr before the nodeagents and the nodeagents before the application servers…

Deployment Manager -> Node Agents -> Application Servers.

Elsewhere On TurboGeek:  Configure Time with NTP and Chronyd


Richard Bailey, a seasoned tech enthusiast, combines a passion for innovation with a knack for simplifying complex concepts. With over a decade in the industry, he's pioneered transformative solutions, blending creativity with technical prowess. An avid writer, Richard's articles resonate with readers, offering insightful perspectives that bridge the gap between technology and everyday life. His commitment to excellence and tireless pursuit of knowledge continues to inspire and shape the tech landscape.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *