versionInfo command

The versionInfo command generates reports from data it extracts from XML files in the properties/version folder.

 

Product version and history information

The /properties/version directory in the installation root contains important data about the product and its installed components, such as the build version and build date. This information is included in product.product and component.component files. The /properties/version/history directory in the installation root contains a collection of records for installed interim fixes and fix packs. This information is included in interim fixID.efixApplied, interim fixID.efixDriver, fix packID.ptfApplied, and fix packID.ptfDriver files. A driver file has useful information about the entire contents of an interim fix or fix pack. The applied file has relevant information about the interim fixes or fix packs that are currently applied. Event.history files are also present. They contain a detailed log about updates you have applied, either successfully or unsuccessfully. Time-stamped, detailed logs record each update process in the /properties/version/log directory of the installation root.

You can view product information by examining files in the properties/version directory, including the properties/version/history directory. WAS also provides the ability to generate two types of reports about the data in the files, Version reports and History reports.

Restriction: There is one restriction. Do not use the versionInfo.sh or versionInfo.bat script while installing or uninstalling the product, or while installing or uninstalling an interim fix or fix pack.

Product version reports

The following report generation scripts extract data from XML data files in the properties/version folder...

• versionInfo script

  Lets you use parameters to create a version report on Linux and UNIX-based platforms, or on Windows platforms.

• genVersionReport command

  Generates the versionReport.html report file in the bin directory on Linux and UNIX-based platforms, or on Windows platforms. The report includes the list of components, fixes, and fix packs.

 

Location of the command file

The command file is a script. On Linux and UNIX platforms, the command file is named versionInfo.sh in the $WAS_HOME/bin directory. On Windows platforms, the command file is named versionInfo.bat in the $WAS_HOME\bin directory.

 

Syntax for the versionInfo command on a Linux or UNIX-based platform

The command syntax is

versionInfo.sh [ -format text | html]
               [ -file output file]
               [ -long ]
               [ -efixes ]
               [ -efixDetail ]
               [ -ptfs ]
               [ -ptfDetail ]
               [ -components ]
               [ -componentDetail ]


versionInfo.sh [ -help | -? | /help | /? | -usage ]

Issue the command from the $WAS_HOME/bin directory.

 

Syntax for the versionInfo command on a Windows platform

The command syntax is

versionInfo [ -format text | html]
            [ -file output file]
            [ -long ]
            [ -efixes ]
            [ -efixDetail ]
            [ -ptfs ]
            [ -ptfDetail ]
            [ -components ]
            [ -componentDetail ]


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

Issue the command from the $WAS_HOME\bin directory.

 

Parameters

-? 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.

 

Logging

As the tool runs, it creates reports instead of log entries. Reports appear on the console unless directed to a file with the -file filename parameter. There is no default file name. You must specify a file name to generate a file.

 Usage scenariobinversionInfo.bat

D:\Program Files\WebSphere\DeploymentManager\bin>versionInfo
WVER0011I: WAS Release 5.0
WVER0012I: VersionInfo reporter version 1.14, dated 5/9/03

----------------------------------------------------------

IBM WAS Product Installation Status Report
----------------------------------------------------------



Report at date and time 2003-10-05T11:01:45-04:00

Installation
----------------------------------------------------------

Product Directory   D:\Program Files\WebSphere\DeploymentManager
Version Directory   ${product.dir}\properties\version
DTD Directory       ${version.dir}\dtd
Log Directory       D:\Program Files\WebSphere\DeploymentManager\logs\update
Backup Directory    ${version.dir}\backup
TMP Directory       D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp

Installation Platform
----------------------------------------------------------

Name           IBM WAS
Version        5.1

Technology List
----------------------------------------------------------

ND             installed

Installed Product
----------------------------------------------------------

Name           IBM WAS Network Deployment
Version        5.1.0
ID             ND
Build Level    b0334.18
Build Date     8/30/03

---------------------------------------------------------

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

 

See Also

Product version and history information
genVersionReport command

 

---