We are on windows 2003 box. Its a stand alone Appserver. What are the benefits of restarting the Nodeagents and deployment manager. Main purpose of scheduling restart is ...we are seeing some issues with CPU usage of Java.exe, so when we restart the CPU usage goes down..Its a temporary workaround untill we figure out the root cause.
So do you think its better to restart appserver , nodeagent and deployment manager for a clean and gracefull stop and start of the web sphere or only restart of app server is good.
If possible could you please help me with the steps I have to consider to pust the scripts together.
THANKS expert
Main Topics
Browse All Topics





by: HonorGodPosted on 2009-05-30 at 19:57:09ID: 24511228
What operating system?
On Unix type systems, I would use a cron job.
On Windows, you would need to use the job scheduler.
Next question.
- Are we talking about a stand alone AppServer, or a Federated AppServer, or a Cluster?
When you say you want to restart WebSphere, does this mean only the AppServer, or do you want/need to stop & restart any nodeagents, and deployment manager?
Assuming that you are talking about a stand-alone AppServer, I would have the job:
- check for the *pid (process ID) file in the appropriate AppServer log directory
and save the PID of the AppServer
- use the serverStatus script (and parse the result) to see if the AppServer is active, or stopped.
- If active, I would use the stopServer script to (gracefully) stop the AppServer
- Parse/process the output of the stopServer script to verify successful termination.
- pause/delay for a short time (10-30 seconds)
- Use the startServer script to start the AppServer, and parse the output to verify successful AppServer startup
-> If it fails... send a message to your pager. :-)