+

Search Tips   |   Advanced Search

 

historyInfo command

 

The historyInfo command generates a report from data extracted from XML files in the properties/version folder and the properties/version/history folder. The report includes a list of changed components and a history of installed or uninstalled maintenance packages.

 

Product history information

The historyInfo tool displays important data about the product and its installed components, such as the build version and build date. History information for installation and removal of maintenance packages also displays in the report. This tool is particularly useful when working with support personnel to determine the cause of any problem.

Product history reports The following report generation scripts extract data from XML data files in the properties/version folder and the properties/version/history folder:

 

Location of the command file

The historyInfo command is a script.

[AIX] [HP-UX] [Linux] [Solaris] The command file is a script named historyInfo.sh in the app_server_root/bin directory.

[Windows] The command file is a script named historyInfo.bat in the app_server_root\bin directory.

 

Syntax for the historyInfo command

The command syntax is:

[AIX] [HP-UX] [Linux] [Solaris]

historyInfo.sh [ -format text | html ]
               [ -file file_name ]
               [ -maintenancePackageID ID_of_maintenance_package ]
               [ -component component_name ]

 historyInfo [ -help | /help | -? | /? | -usage ]

[Windows]

historyInfo [ -format text | html ]
            [ -file file_name ]
            [ -maintenancePackageID ID_of_maintenance_package ]
            [ -component component_name ]

 historyInfo [ -help | -? | /help | /? | -usage ]

Issue the command from the bin directory of the app_server_root directory.

 

Parameters

-? or /?

Displays command syntax.

-component component_name

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.

-file file_name

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

Displays command syntax.

-maintenancePackageID ID_of_maintenance_package

Specifies the ID of the interim fix, fix pack, or refresh pack. When specified, the product history report displays events for only the named maintenance package. When not specified, the report displays events for all maintenance packages.

-usage

Displays command syntax.

 

Report description

The historyInfo command reports the following information:

 

Installation information

Displays the following general information about the current installation:

 

Installation event information

Displays the list of installed maintenance packages (interim fix, fix pack, and refresh pack) and the following related information:

 

Component installation event information

Displays the following component-level information of the event for the current maintenance package:

 

The event.history file

The historyInfo command also generates the event.history file. This file represents the raw data of the history report information. The following example of an event.history file corresponds to the history report in the preceding example:

<!DOCTYPE event-history SYSTEM "eventHistory.dtd">
<event-history>
  <update-event
    event-type="ptf"
    id="was60_fp1_linux"
   update-action="install"
   primary-content="was60_fp1_linux.pak"
   update-type="replace"
   log-name=
      "/opt/WebSphere/AppServer/logs/update/was60_fp1_linux.install/updatelog.txt"
   backup-name=
      "/opt/WebSphere/AppServer/properties/version/backup/was60_fp1_linux.pak"
    start-time-stamp="2004-12-14 06:15:14-0500"
    result="success">
    <update-event
      event-type="component"
      parent-id="was60_fp1_linux"
      id="activity"
      update-action="install"
      update-type="replace"
      start-time-stamp="2004-12-14 06:15:14-0500"
      result="success">
   </update-event>
   <update-event
      event-type="component"
      parent-id="was60_fp1_linux"
      id=" activity.impl"
      update-action="install"
      update-type="replace"
      start-time-stamp="2004-12-14 06:15:14-0500"
      result="success">
   </update-event>
 </update-event>
 <update-event
    event-type="ptf"
    id="was60_fp2"
   update-action="install"
   primary-content="was60_fp1_linux.pak"
   update-type="replace"
   log-name="/opt/WebSphere/AppServer/logs/update/was60_fp2.install/updatelog.txt"
   backup-name="/opt/WebSphere/AppServer/properties/version/backup/was60_fp2.pak"
     start-time-stamp="2004-12-14 10:25:34-0500"
     result="partialSuccess">
    <update-event
      event-type="component"
      parent-id="was60_fp2"
      id="activity"
      update-action="install"
      update-type="replace"
     start-time-stamp="2004-12-14 10:25:34-0500"
     result="partialSuccess">
   </update-event>
   <update-event
      event-type="component"
      parent-id="was60_fp2"
      id=" activity.impl"
      update-action="install"
      update-type="replace"
      start-time-stamp="2004-12-14 10:25:34-0500"
      result="partialSuccess">
   </update-event>
 </update-event>
 <update-event
    event-type="ptf"
    id="was60_fp2"
   update-action="uninstall"
     primary-content=" was60_fp2.pak"
   update-type="replace"
   log-name=
      "/opt/WebSphere/AppServer/logs/update/was60_fp2.uninstall/updatelog.txt"
   backup-name="not applicable"
    start-time-stamp="2004-12-18 17:29:12-0500"
    result="partialSuccess">
    <update-event
      event-type="component"
      parent-id="was60_fp2"
      id="activity"
      update-action="uninstall"
      update-type="replace"
     start-time-stamp="2004-12-18 17:29:12-0500"
      result="partialSuccess">
   </update-event>
   <update-event
      event-type="component"
      parent-id="was60_fp2"
      id=" activity.impl"
      update-action="uninstall"
      update-type="replace"
     start-time-stamp="2004-12-18 17:29:12-0500"
      result="partialSuccess">
   </update-event>
 </update-event>
 <update-event
    event-type="ptf"
    id="was60_fp1_linux"
   update-action="uninstall"
     primary-content=" was60_fp1_linux.pak"
     update-type="replace"
   log-name=
      "/opt/WebSphere/AppServer/logs/update/was60_fp1_linux.install/updatelog.txt"
   backup-name="not applicable"
    start-time-stamp="2004-12-23 15:15:14-0500"
    result="faiurel">
    <update-event
      event-type="component"
      parent-id="was60_fp1_linux"
      id="activity"
      update-action="uninstall"
      update-type="replace"
      start-time-stamp="2004-12-23 15:15:14-0500"
      result="failure">
   </update-event>
   <update-event
      event-type="component"
      parent-id="was60_fp1_linux"
      id=" activity.impl"
      update-action="uninstall"
      update-type="replace"
      start-time-stamp="2004-12-23 15:15:14-0500"
      result="failure">
   </update-event>
  </update-event>
</event-history>

 

Summary of V6 changes for the historyInfo command

Changes are in three areas: command syntax, report information, and the event.history file.

 

Changes to command syntax

V6 replaces the term updateID with maintenancePackageID to describe a specific maintenance package. This matches the terminology used in the V6 update installer application.

 

Changes to report information

The following changes are in effect:

 

Changes to the event.history file

The following changes are in effect:




 

Related Reference


genHistoryReport command
Product version information

 

Related information


Use command line tools

 

Reference topic