Note: For clarity, only the Linux
and UNIX(R) versions of commands and file paths are shown
below.
The properties/version/history directory
in the install_root directory 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 install_root directory.
The following
information describes the XML data files that store product information
for WebSphere Process Server. By default, the document type declarations
(DTDs) for these files are in the properties/version/dtd folder
of the install_root directory, or the server
root directory. For more information, see the Directory locations section.
Product information files
The following
XML files in the
properties/version directory
represent installed items and installation events such as product
edition, version, component, and build information:
- WBI.product
One
file whose existence indicates the particular WebSphere Process
Server product that is installed. The type of product installed
is indicated by the <id> tag. Data in the file
indicates the version, build date, and build level. An example follows.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE product PUBLIC "productId" "product.dtd">
<product name="IBM WebSphere Process Server">
<id>WBI</id>
<version>6.0.0.0</version>
<build-info date="6/10/05" level="o0523.34"/>
</product>
- component-name.component
Any number of component files that each indicate the presence
of an installed component, which is part of the product. Data in
the file indicates the component build date, build version, component
name, and product version. An example follows.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE component PUBLIC "componentId" "component.dtd">
<component build-date="6/10/05" build-version="o0523.34"
name="relationshipManager"
spec-version="6.0.0.0"/>
- extension.id.extension
Any number of extension files that each indicate the presence
of an extension that you install as a user extension, as part of
a service engagement, or as installed by a third party product.
The extension.id.extension files
are not created, logged, or removed by WebSphere Process Server.
- fix-id.efix
Any number of interim fix files that each indicate the presence
of an installed fix.
- ptf-id.ptf
Any number of files, that each indicate the presence of an installed
refresh pack or fix pack.
The following XML files in the properties/version/history directory
describe fixes and fix packs that are currently installed. These
XML files are related to installation items by the primary ID information,
which is shown in the following examples as italicized text.
- event.history
Lists update events that have occurred. An update event is an
operation that installs or uninstalls an interim fix or a fix pack.
The file is sorted by the date and time of the events that are listed.
- fix-id.efixDriver
Interim fix-driver defining information
- fix-id.efixApplied
Interim fix installation details
- pft-id.pftDriver
Fix pack-driver defining information
- pft-id.pftApplied
Fix pack installation details
Reports
WebSphere Process Server provides the ability to generate version
reports and History reports from the data in the files. The following
report-generation scripts are available in the install_root/bin directory.
The following report generation scripts extract data from XML
data files in the
properties/version directory:
- versionInfo script
Lets you use parameters to create a version report on Linux,
UNIX, or Windows platforms. For more information about the versionInfo
command, see versionInfo command in the
WebSphere Application Server Network Deployment, version 6.0 information
center.
- genversionReport script
Generates the versionReport.html report
file in the bin directory on Linux, UNIX, or
Windows platforms. The report includes the list of components and
installed and uninstalled maintenance packages. For more information
about the genversionReport command, see genversionReport command in
the WebSphere Application Server Network Deployment, version 6.0
information center.
The following report generation scripts extract data from XML
data files in the
properties/version/history directory:
- historyInfo script
Lets you use parameters to create a history report on Linux,
UNIX, or Windows platforms. For more information about the historyInfo
command, see the historyInfo command in the
WebSphere Application Server Network Deployment, version 6.0 information
center.
- genHistoryReport script
Generates the historyReport.html report file in the bin directory
on Linux, UNIX, or Windows platforms. The report includes the list
of components and a history of installed and uninstalled maintenance
packages. For more information about the genHistoryReport command,
see genHistoryReport command in
the WebSphere Application Server Network Deployment, version 6.0
information center.
Logs and component backups
WebSphere Process Server products use two other directories when
performing update operations, for logging and backups:
- install_root/logs/update,
the logs directory for product updates.
The location of log files that describe events that occur during
the use of the update installer program.
- install_root/properties/version/backup,
the product updates backup directory.
WebSphere Process Server backs up components before applying
interim fixes and fix packs. If you uninstall an interim fix or
fix pack, WebSphere Process Server restores the backed-up component
JAR file.
File naming convention:
- Time stamp: YYYYMMDD_HHMMSS
For example: 20050324_211832 is 24-Mar-2005,
9:18:32 pm, GMT. All time stamps are in GMT.
- ID: Interim fix ID or fix pack ID
For example: apar6789c is an interim fix ID;
PTF_1 is a fix pack ID.
- Operation: install | uninstall
- Interim fix log file names: timeStamp_fixId_operation.log
For example, the update installer program creates these logs: install_root/logs/update/20050324_211832_apar6789c_install.log and install_root/logs/update/ 20050324_211912_apar6789c_uninstall.log
- Interim fix component log file names: timeStamp_fixId_componentName_operation.log
For example, the update installer program creates these logs: install_root/logs/update/20050324_211832_apar6789c_ras_install.log and install_root/logs/update/ 20050324_211912_apar6789c_ras_uninstall.log
- Fix pack log file names: timeStamp_ptfId_operation.log
For example, the update installer program creates these logs: install_root/logs/update/20050924_211832_was60_fp1_install.log and install_root/logs/update/ 20050924_211912_was60_fp1_uninstall.log
- Fix pack component log file names: timeStamp_ptfId_componentName_operation.log
The update installer program creates these logs: install_root/logs/update/20050324_211832_was60_fp1_ras_install.log and install_root/logs/update/20030325_211912_was60_fp1_ras_uninstall.log
- Backup JAR file names: timeStamp_ptfId_componentName_undo.jar or timeStamp_fixId_componentName_undo.jar,
for example: 20020924_211832_apar6789c_ras_undo.jar
Do not delete a backup JAR file. You cannot remove a component
update if the corresponding backup JAR file is not present.
Update processing might also use a temporary directory, if necessary.
A Java property specifies this directory as described in the next
section.