The genHistoryReport command generates the historyReport.html report file in the current working directory, which is usually the bin directory. The report includes a list of changed components and installed or uninstalled maintenance packages. The genHistoryReport script invokes the historyInfo script specifying the correct parameters to place the information generated into an HTML file in the current directory.
The historyInfo tool displays historical data about the product and the installation and removal of maintenance packages for the product. This tool is particularly useful when working with support personnel to determine the cause of any problem.
Product history reports
app_server_root/bin/genHistoryReport
app_server_root/bin/genHistoryReport.sh
app_server_root\bin\genHistoryReport.bat
The command syntax is:
genHistoryReport
genHistoryReport.sh
genHistoryReport.bat
Issue the command from the bin directory of the app_server_root directory.
The historyInfo command generates the report. The genHistoryReport command calls the historyInfo command with a set of report parameters that reports the following information:
The genHistoryReport script creates the following information in the historyReport.html report file, which is edited to show only the first few components:
-------------------------------------------------------------------------------- IBM WebSphere Application Server History Report -------------------------------------------------------------------------------- Report at date and time: 2004-12-26 01:47:19-0500 Installation -------------------------------------------------------------------------------- Product Directory: /opt/WebSphere/AppServer Version Directory: /opt/WebSphere/AppServer/properties/version DTD Directory: /opt/WebSphere/AppServer/properties/version/dtd Log Directory: /opt/WebSphere/AppServer/logs/update Backup Directory: /opt/WebSphere/AppServer/properties/version/update/backup TMP Directory: /tmp History Directory /opt/WebSphere/AppServer/properties/version/history Installation Event -------------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Action: install Package Filename: was60_fp1_linux.pak Log File Name: /opt/WebSphere/AppServer/logs/update/was60_fp1_linux.install/updatelog.txt Backup File Name: /opt/WebSphere/AppServer/properties/version/backup/was60_fp1_linux.pak Timestamp: 2004-12-14 06:15:14-0500 Result: success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Component Name: activity Action: install Update Action: replace Timestamp: 2004-12-14 06:15:14-0500 Result: success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Component Name: activity.impl Action: install Update Action replace Timestamp: 2004-12-14 06:15:14-0500 Result: success Installation Event -------------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Action: install Package Filename: was60_fp2_linux.pak Log File Name: /opt/WebSphere/AppServer/logs/update/was60_fp2.install/updatelog.txt Backup File Name: /opt/WebSphere/AppServer/properties/version/backup/was60_fp2.pak Timestamp: 2004-12-14 10:25:34-0500 Result: partial success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Component Name: activity Action: install Update Action: replace Timestamp: 2004-12-14 10:25:34-0500 Result: partial success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Component Name: activity.impl Action: install Update Action: replace Timestamp: 2004-12-14 10:25:34-0500 Result: partial success Installation Event -------------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Action: uninstall Package Filename: was60_fp2_linux.pak Log File Name: /opt/WebSphere/AppServer/logs/update/was60_fp2.uninstall/updatelog.txt Backup File Name: not applicable Timestamp: 2004-12-18 17:29:12-0500 Result: success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Component Name: activity Action: uninstall Update Action: replace Timestamp: 2004-12-18 17:29:12-0500 Result: success Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp2 Component Name: activity.impl Action: uninstall Timestamp: 2004-12-18 17:29:12-0500 Update Action: replace Result: success Installation Event -------------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Action: uninstall Package Filename: was60_fp1_linux.pak Log File Name: /opt/WebSphere/AppServer/logs/update/was60_fp1_linux.uninstall/updatelog.txt Backup File Name: not applicable Timestamp: 2004-12-23 15:15:14-0500 Result: fail Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Component Name: activity Action: uninstall Update Action: replace Result: fail Component Installation Event ----------------------------------------------------------------------------- Maintenance Package ID: was60_fp1_linux Component Name: activity.impl Action: uninstall Update Action: replace Result: fail -------------------------------------------------------------------------------- End History Report --------------------------------------------------------------------------------
Changes are in three areas: command syntax, report information, and the event.history file.
Version 6 replaces the term updateID with maintenancePackageID to describe a specific maintenance package. This matches the terminology used in the Version 6 update installer application.