Useful commands for WebSphere Application Server:

Finding what versions are running:
  

While version information is available from the admin console, it is also available for most IBM products in the source file product.xml .Beginning with WebSphere Application Server Version 4.0.x, this file will also include information on eFixes that have been installed. Access this file for WebSphere Application Server using these commands:

            1]   AIX

 

cat /usr/WebSphere/AppServer/properties/com/

ibm/websphere/product.xml

 

2] Solaris/Linux

 

cat /opt/WebSphere/AppServer/properties/com/

ibm/websphere/product.xml

 

            

        3] Windows

 

c:\WebSphere\AppServer\properties\com\ibm

\websphere\product.xml

 

 

4] Java JDK

 

java -version

 

5] IBM HTTP Server:

 

Solaris/Linux

 

/opt/HTTPServer/bin/httpd -v

 

         Windows

 

c:\Program Files\IBM HTTP Server\

 

6] Location of WebSphere code:

 

Solaris/Linux

 

/opt/WebSphere/AppServer

 

May also have alias: 

 

/opt/WebAS

 

Windows: 

c:\WebSphere\AppServer

 

* Emptying the log files:

 

On UNIX, new log files may be automatically generated on a regular basis, such as daily or each
time a process is started. After a newer log file has been generated, older empty log files can be
deleted with this command:

find $WAS_HOME/logs -size 0 -exec rm {} \; 

 

* Finding what processes are running:

  ps -ef|grep java

 

What to backup:

When backing up files for WebSphere Application Server, be absolutely sure the files and information listed here are included your backup:
•The XMLConfig -export command will document the current configuration in the repository.

•The files admin.config(or server-cfg.xml for WebSphere Application Server Advanced Single Server Edition) and setupCmdLine.sh/setupCmdLine.bat document the environment settings required to connect to the repository.

•The files obj.conf/httpd.conf and appropriate SSL files, if used (e.g.*.sth, *.kdb),document the webserver's configuration.

• Beginning with WebSphere Application Server Version 4.0, all user applications are delivered as EAR, WAR or JAR files. These should be backed up as well, but that is actually done outside of WebSphere. The same is true for static Web pages written by users and served by the Web server.