why doesnt serverStatus.sh work

websphere 6.1  aix 537  
on my dev box serverstat.sh returns the correct results but only if the integrated console is running. on prod it doesnt return the running server1 application server even if the console is running.  where should I look for differences in this regard?
jessesch01Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

woolmilkporcCommented:
Hi,
first, you should make sure that all fixes are applied to both of your servers.
Here is the list of recommended fixes -
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980#ver61
Good luck!
wmp
 
0
gheistCommented:
check "oslevel -r" on both servers and install them with same ML package that exceeds minimum level required for websphere. Also install websphere maintenance fixes.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HonorGodSoftware EngineerCommented:
The serverStatus command script needs to communicate with something in order to determine the status.  In a federated, or clustered environment, the communication would be directed towards the Deployment Manager (DM), which in turn, needs to communicate with the nodeagents (NAs) to determine the status of the managed nodes.

So, if your DM, or any of the NAs are down, for some reason, they will be unable to determine the status of an Application Server, even if it is still active.

Does that help any?
0
jessesch01Author Commented:
The solution was to run the server status from the appropriate profile directory instead of the default directory which only picks up the Deployment manager .   Thanks to all of course patches are a first step but we are already on a higher level than when that issue was reported.  It was basically my misunderstanding of the websphere config
0
HonorGodSoftware EngineerCommented:
Additionally, you could execute the script from the default bin directory, and specify the

-profileName Dmgr01

with the appropriate profilename..

Thanks for the assist & the points.

Good luck & have a great day
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.