Checking version and history of WebSphere Application Server V5
 Technote (troubleshooting)
 
Problem(Abstract)
How to check the version and history information of your WebSphere® Application Server V5 environment.
 
Resolving the problem
  1. How do you check which version of WebSphere Application Server you are running?
    1. Look in the SystemOut.log file of the specific installation:

      Base:
      Install_Root/logs/nodeagent/SystemOut.log

      Deployment Manager:
      Install_Root/logs/dmgr/SystemOut.log

      The file contains content similar to the following, which is from a node agent SystemOut.log file:

      *******Start Display Current Environment *******
      WebSphere Platform 5.0 [BASE 5.0.0 m0232.11 ][ND 5.0.0
      m0232.11 ] running with process name Net1Network \Net1_JH
      Net1_JH and process id 1912
      Host Operating System is Windows 2000,version 5.0
      Java version =J2RE 1.3.1 IBM Windows 32 build cn131-20020731
      (JIT enabled:jitc),Java Compiler =jitc,Java VM name =Classic
      VM
      ...
      ...

      *******End Display Current Environment**********

    2. Execute the versionInfo command from the /bin directory of the specific installation:

      Install_Root/bin>versionInfo.bat/sh

      The output is similar to the following:

      ------------------------------------------------
      IBM WebSphere Application Server Version Report
      ------------------------------------------------
      Platform Information
      ------------------------------------------------
      Name:IBM WebSphere Application Server
      Version:5.0
      Product Information
      ------------------------------------------------
      ID:BASE
      Name:IBM WebSphere Application Server
      Build Date:8/14/02
      Build Level:m0232.11
      Version:5.0.0
      Product Information
      ------------------------------------------------
      ID:ND
      Name:IBM WebSphere Application Server for Network Deployment
      Build Date:8/14/02
      Build Level:m0232.11
      Version:5.0.0
      -------------------------------------------------
      End Report


      This tells us that the BASE and ND installations are both at the V5.0.0 level.

      Note: When this is run from the Deployment Manager /bin directory, versionInfo lists only the Deployment Manager version details. If this is run from the /bin directory of any of the nodes, both the local node and the Deployment Manager version details are listed.

  2. How do you check the Java™ Development Kit (JDK™) version?

    To figure out which version of the JDK you have installed in your environment, use one of the following options:
    1. Look in the SystemOut.log file:

      Base:
      Install_Root/logs/nodeagent/SystemOut

      Deployment Manager:
      Install_Root
      /logs/dmgr/SystemOut

    2. Execute java -version from the command line:

      Install_Root/java/bin/>java -version

      Result:

      java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
      Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build
      cn131-20030618 (JIT enabled: jitc))

      Execute java -fullversion from the command line:

      Install_Root/java/bin/>java -fullversion

      Result:

      java full version "J2RE 1.3.1 IBM Windows 32 build cn131-20030618"

      Note: For Unix® you might need to use the following commands:

      ./java -version

      OR

      ./java -fullversion

  3. How do you check the Object Request Broker (ORB) version?

    Using simple java commands:

    Example 1:
    Install_Root/java/bin/>java com.ibm.CORBA.iiop.Version

    Result:

    IBM Java ORB build cn131-20030618 version 1310:5

    Example 2:
    Install_Root/java/bin/>java -classpath Install_Root\lib\iwsorb.jar com.ibm.ws.orb.ORBInfo

    Result:

    RMI-IIOP (runtime) : IBM Java ORB build cn131-20030618 using native library JRE vendor/version : IBM Corporation, version: 1.3.1

    Note: Example 1 and Example 2 call the java command from the Install_Root/java/bin/ directory. This might not mean that the java command in that directory is used, depending on your PATH setting; for example, whether ./ is at the beginning, and so forth. You might want to be more explicit and use Install_Root/java/jre/bin/java directly . It is also possible that the bootclasspath might cause this to occur, since that's how the base ORB is loaded.

    Example 3:
    Enable ORB trace for any server (for example: server1)

    SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.

    SECJ0240I: Security service initialization completed successfully
    6554ceb1 ORBRas  d com.ibm.rmi.util.Version logVersions:110 P=306232:O=0:CT IBM Java ORB build
    orbsol131-20030329 6554ceb1 ORBRas  d com.ibm.rmi.util.Version logVersions:117 P=306232:O=0:CT J2RE 1.3.1 IBM Windows 32 build cn131-20030329 (JIT enabled: jitc)

    Important: The com.ibm.CORBA.iiop.ORBInfo class was valid only in V4.0 and previous releases. In release V5.0, it moved to the package com.ibm.ws.orb. If you use this package to check the version, you receive a NoClassDefFoundError.

    Install_Root/java/bin/>java com.ibm.CORBA.iiop.ORBInfo

    Result:

    Exception in thread "main" java.lang.NoClassDefFoundError: com/ibm/CORBA/iiop/ORBInfo

  4. How do you check the IBM® HTTP Server version?

    To check the version of your IBM HTTP Server or Apache Web server, perform the following:
    • On Windows® platforms, run the apache -v command:

      $IHS_HOME>apache.exe  -v

      For example: D:\IBM HTTP Server\>apache.exe -v

      Result:

      Server version:IBM_HTTP_SERVER/1.3.24 Apache/1.3.24 (Win32)Server built:Jun 12 2002 16:30:01

    • On UNIX® platforms, run the httpd -v command:

      $IHS_HOME>httpd  -v

  5. How to check the DB2® version?

    To check your DB2 version, execute the following command:

    $DB2_HOME\SQLLIB\BIN>db2level

    Result:

    DB21085I  Instance "DB2" uses DB2 code release "SQL07025" with level identifier "03060105" and informational tokens "DB2 v7.1.0.68", "n020616" and "WR21311".



Additional Information
  • Appendix A
    Product version and history information

    WebSphere Application Server provides the ability to generate two types of reports about the data in the files, Version reports and History reports.

    The following report-generation scripts are available in the Install_Root/bin directory.

    Product version reports
    The following report generation scripts extract data from XML data files in the properties/version folder.
    1. versionInfo.bat and versionInfo.sh

      Lets you use parameters to create a version report.Do not use the versionInfo command while installing or uninstalling the product, or while installing or uninstalling an interim fix or fix pack.

      Parameter
      Description
      -? or /? (Windows only) Displays command syntax.
      -components Adds a list of installed components to the report.
      -componentDetail Adds details about installed components to the report.
      -efixes Adds a list of applied interim fixes to the report.
      -efixDetail Adds details about applied interim fixes to the report.
      -file <fileName> Specifies the output file name. The report goes to standard output (stdout) by default.
      -format TEXT | HTML Selects the format of the report. The default is TEXT.
      -help or /help (Windows only) Displays command syntax.
      -long Creates the long version of the report.
      -ptfDetail Adds details about applied fix packs to the report.
      -ptfs Adds a list of applied fix packs to the report.
      -usage Displays command syntax.
    2. Generates the versionReport.html report file in the bin directory. The report includes the list of components, fixes, and fix packs.

    Product history reports

    The following report generation scripts extract data from XML data files in the properties/version/history folder.
    1. historyInfo.bat and historyInfo.sh

      Lets you use parameters to create a history report of installed and uninstalled fixes and fix packs.You can also specify a component name to create a report that shows the history for that component.
      Parameter
      Description
      -format TEXT | HTML Selects the format of the report. The default is TEXT.
      -file <fileName> Specifies the output file name. The report goes to standard output (stdout) by default.
      -updateID <ID> Specifies the ID of an interim fix or fix pack update. When specified, the product history report displays events for only the specified update. When not specified, the report displays events for all updates.
      -component <componentName> Specifies the name of a component. When specified, the product history report displays events for only the named component. When not specified, the report displays events for all components.
    2. genHistoryReport.bat and genHistoryReport.sh

      Generates the historyReport.html report file in the \bin directory. The report includes all updates and components. For more information, read the section Product version and history information in the V5.0 Information Center.

  • Appendix B
    CORBA Information

    Use com.ibm.CORBA.iiop.ORBInfo to see more information about the ORB.

    For example:

    Install_Root/java/bin/>java -classpath  Install_Root\lib\iwsorb.jar  com.ibm.ws.orb.ORBInfo

    Result:

    =========================================================
    RMI-IIOP (runtime) : IBM Java ORB build cn131-20030618 using native library JRE vendor/version : IBM Corporation, version: 1.3.1

    General Rules for Trace Properties
    ------------------------------------
    To write ORB messages to the log, set "com.ibm.CORBA.Debug=message".
    To write ORB trace information to the log, set
    "com.ibm.CORBA.Debug=trace".
    To write both ORB trace and message information to the log, set "com.ibm.CORBA.Debug=<anything_else>".
    To enable communication message trace (Comm trace), set "com.ibm.CORBA.CommTrace=true".
    Note: Comm trace information is an addition to the trace log, so "com.ibm.CORBA.Debug" must also be set to put Comm trace into the log.

    Enabling Comm Trace on Servers (Application Servers, NodeAgent Servers)
    ----------------------------------------------
    A. Through Administrative Console
       1. Traverse to the Configuration page for the server
          to be traced.
       2. Select "ORB Service" under "Additional Properties".
       3. Enable the checkbox for "ORB tracing" under
          "General Properties".

    B. Through "server.xml"
       1. Edit 'server.xml' file of the server to be traced.
         e.g. for a single-server installation, the file is
         at config/cells/<cellName>/nodes/<nodeName>/servers/server1/server.xml

       2. Search for "orb:ObjectRequestBroker". That should
          lead you to the ORB service section.
       3. Edit (or add) the 'commTraceEnabled' attribute and
          set it to "true". e.g. commTraceEnabled="true"

    Server Comm trace output goes into the trace file for the respective server.

    Enabling Comm Trace on Java Clients
    -----------------------------------
    1. Start the client program with '-D' arguments to
       specify the trace settings:
       e.g. java -Dcom.ibm.CORBA.Debug=true
            -Dcom.ibm.CORBA.CommTrace=true <program_name>

    2. Trace output are captured in unique trace files with
       names "orbtrc.<timestamp>.txt".

    Other ORB Properties
    --------------------
    -  com.ibm.CORBA.FragmentSize=<integer> ('0' == disabled)
       Size of fragments into which GIOP messages are
       fragmented.
    =========================================================

  • Appendix C
    Collector summary option

    WebSphere Application Server products include an enhancement to the collector tool beginning with Version 5.0.2, known as the collector summary option.

    The collector summary option helps you communicate with WebSphere Application Server technical staff at IBM Support. Run the collector tool with the -Summary option to produce a lightweight text file and console version of some of the information in the Java archive (JAR) file that the tool produces without the -Summary parameter. You can use the collector summary option to retrieve basic configuration and prerequisite software level information when starting a conversation with IBM Support.

    The collector summary option produces version information for the WebSphere Application Server product and the operating system as well as other information.

    Note: The collector summary option stores the information in the Collector_Summary.txt file and writes it to the console.

    You can use the information to answer initial questions from IBM Support or you can send the Collector_Summary.txt file directly to IBM Support.

    To run the collector summary option, start from a temporary directory outside of the WebSphere Application Server product installation root directory and enter the following command:

    C:\temp>C:\WebSphere\50X\Base\bin\collector.bat -summary

    Result:
    The result of above command is placed in the working directory; in this case:

    C:\temp\Collector_Summary.txt.

    Sample Collector_Summary.txt

    Hostname: Test   Nodename: testManager
    ----------------------------------------
    IBM WebSphere Application Server Product Installation Status Report
    ---------------------------------------------------------

    Report at date and time 2004-02-25T10:19:10-05:00

    Installation
    ---------------------------------------------------------
    Product Directory   C:\WebSphere\50X\ND
    Version Directory   ${product.dir}\properties\version
    DTD Directory       ${version.dir}\dtd
    Log Directory       C:\WebSphere\50X\ND\logs\update
    Backup Directory    ${version.dir}\backup
    TMP Directory       C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp

    Installation Platform
    ---------------------------------------------------------
    Name           IBM WebSphere Application Server
    Version        5.0

    Technology List
    ---------------------------------------------------------
    ND             installed

    Installed Product
    ---------------------------------------------------------
    Name           IBM WebSphere Application Server for
                   Network Deployment
    Version        5.0.2.3
    ID             ND
    Build Level    cf30403.04
    Build Date     01/23/2004

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

    Java Full Version:
    J2RE 1.3.1 IBM Windows 32 build cn131-20030618 (JIT enabled: jitc)

    Operating System: Windows 2000, 5.0

    Name:        WebSphere MQ
    Version:     530.4  CSD04
    CMVC level:  p530-04-030617
    BuildType:   IKAP - (Production)
    StdErr: 'wempsservice' is not recognized as an internal or external command,
    StdErr: operable program or batch file.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1166037
IBM Group: Software Group
Modified date: Sep 10, 2004