d8888 888 888      88888888888 888      d8b                                 888       888          888       .d8888b.           888                               
      d88888 888 888          888     888      Y8P                                 888   o   888          888      d88P  Y88b          888                               
     d88P888 888 888          888     888                                          888  d8b  888          888      Y88b.               888                               
    d88P 888 888 888          888     88888b.  888 88888b.   .d88b.  .d8888b       888 d888b 888  .d88b.  88888b.   "Y888b.   88888b.  88888b.   .d88b.  888d888 .d88b.  
   d88P  888 888 888          888     888 "88b 888 888 "88b d88P"88b 88K           888d88888b888 d8P  Y8b 888 "88b     "Y88b. 888 "88b 888 "88b d8P  Y8b 888P"  d8P  Y8b 
  d88P   888 888 888          888     888  888 888 888  888 888  888 "Y8888b.      88888P Y88888 88888888 888  888       "888 888  888 888  888 88888888 888    88888888 
 d8888888888 888 888          888     888  888 888 888  888 Y88b 888      X88      8888P   Y8888 Y8b.     888 d88P Y88b  d88P 888 d88P 888  888 Y8b.     888    Y8b.     
d88P     888 888 888          888     888  888 888 888  888  "Y88888  88888P'      888P     Y888  "Y8888  88888P"   "Y8888P"  88888P"  888  888  "Y8888  888     "Y8888  
                                                                 888                                                          888                                        
                                                            Y8b d88P                                                          888                                        
                                                             "Y88P"                                                           888   

All Things WebSphere

Concerns and issues relating to all versions of WebSphere Application Server

Tuesday, April 26, 2011

 

How to determine the version of WebSphere Application Server programatically

Often times it becomes critical in operational scripting or even in your application code to determine the current runtime version of WAS. The Server mbean provides exactly this facility.
Below is a set of wsadmin script commands using AdminControl that you can use to query the Server mbean.


wsadmin>set server [$AdminControl completeObjectName cell=smitaNode02Cell,node=smitaNode02,name=server1,type=Server,*]
WebSphere:name=server1,process=server1,platform=proxy,node=smitaNode02,j2eeType=J2EEServer,version=8.0.0.0,type=Server,mbeanIdentifier=cells/smitaNode02Cell/nodes/smitaNode02/servers/server1/server.xml#Server_1183122130078,cell=smitaNode02Cell,spec=1.0,processType=UnManagedProcess


wsadmin>$AdminControl getAttribute $server state
STARTED


wsadmin>$AdminControl getAttribute $server platformName
ND


wsadmin>$AdminControl getAttribute $server platformVersion
8.0.0.0


wsadmin>$AdminControl getAttribute $server serverVersion
--------------------------------------------------------------------------------
IBM WebSphere Product Installation Status Report
--------------------------------------------------------------------------------


Report at date and time April 26, 2011 3:09:10 PM EDT


Installation
--------------------------------------------------------------------------------
Product Directory        C:\WebSphere8\f1116.06
Version Directory        C:\WebSphere8\f1116.06\properties\version
DTD Directory            C:\WebSphere8\f1116.06\properties\version\dtd
Log Directory            C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs


Product List
--------------------------------------------------------------------------------
NDTRIAL                  installed


Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server Network Deployment
Version               8.0.0.0
ID                    NDTRIAL
Build Level           f1116.06
Build Date            4/19/11
Architecture          x86-64 (64 bit)
Installed Features    IBM 64-bit SDK for Java, Version 6


--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------


wsadmin>$AdminControl getAttribute $server processType
UnManagedProcess


wsadmin>


This exact same code can be written in java as well using the AdminClient interface
See http://www.ibm.com/developerworks/websphere/techjournal/0302_cundiff/cundiff.html
also http://alvinabad.wordpress.com/2009/02/15/automating-websphere-using-jmx/

With these tools in hand you can interrogate all the characteristics of your current WAS server :
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.javadoc.doc/public_html/mbeandocs/index.html


Comments:

Post a Comment

Subscribe to Post Comments [Atom]



Links to this post:

Create a Link



<< Home

Archives

December 2006   September 2008   January 2009   February 2009   March 2009   September 2009   October 2009   November 2009   December 2009   January 2010   February 2010   March 2010   April 2010   October 2010   January 2011   February 2011   April 2011   May 2011   June 2011   July 2011   August 2011   September 2011   October 2011   November 2011   December 2011   January 2012   February 2012   March 2012   April 2012   May 2012   June 2012   July 2012   August 2012   September 2012   October 2012   November 2012   January 2013   May 2013   June 2013   July 2013   September 2013   October 2013   June 2014   August 2014  

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]