The WebSphere Application Server product contains structural differences from previous versions.
The properties/version directory in the app_server_root contains important data about the product and its installed components, such as the build version and build date. This information is included in WAS.product and [component].component files.
Run the historyInfo command to create a report about installed maintenance packages. The historyInfo command creates a report on the console and also creates tracking files in the app_server_root/properties/version/history directory.
Time-stamped, detailed logs record each update process in the properties/version/log directory of the app_server_root.
This topic describes the XML data files that store product information for Version 6 WebSphere Application Server products. By default, the document type declarations (DTDs) for these files are in the properties/version/dtd folder of the app_server_root, or the server root directory. See the Directory locations section for more information.
WebSphere Application 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 app_server_root bin directory.
Update processing might also use a temporary directory if necessary. A Java property specifies this directory as described in the next section.
Product information files are located relative to the WebSphere Application Server product app_server_root, or the server root directory.
Type Family: WebSphere product family
name string required version string required
Type Detail:
The websphere file denotes the presence of WebSphere family products.
Element Detail:
websphere.name The WebSphere product family name. websphere.version The WebSphere product family version. Type Family: product File Types: product component extension File Type: product Persistence: versionDir/WAS.product Elements: id string required name string required version string required build-info complex required Type Detail: A product file is placed to denote the presence of a specific WebSphere family product. The product ID is embedded in the product file name. Element Detail: product.id The id of the product. product.name The name of the product. product.version The version of the product. product.build-info An element containing build information for the product. Element Type: build-info Elements: date date required level string required Type Detail: A build-info instance details the build of a specific installed WebSphere family product. Element Detail: build-info.date The date on which the product was build. build-info.level The level code of the product's build. File Type: component Persistence: versionDir/name.component Elements: name string required spec-version string required build-version string required build-date date required File Detail: A component file denotes the presence of a specific component. The component name is embedded in the component file name. Element Detail: component.name The name of the component. component.spec-version The specification version of the component. component.build-version The build level of the component. component.build-date The build date of the component. Type Family: update File Types: ptf ptf-applied File Type: ptf Persistence: versionDir/id.ptf Elements: id string required short-description string required build-version string required build-date date required component-name complex min=1, max=unbounded Type Detail: A ptf file denotes the presence of some portion of a specific refresh pack, fix pack, or interim fix. The id of the refresh pack, fix pack, or interim fix is embedded in the fix pack file name. A ptf file contains a listing of component updates. When installing a refresh pack, fix pack, or interim fix, you can omit certain potential component updates, but only when the corresponding component is not installed. Examine a separate application file to determine the components that a particular refresh pack, fix pack, or interim fix updates. A refresh pack or fix pack can include updates for a number of interim fixes. Element Detail: ptf.id The ID of the fix pack. ptf.short-description A short description of the fix pack. ptf.build-version The build version of the fix pack. This is distinct from the build version of component updates contained within the fix pack. ptf-build-date The build date of the fix pack. This is distinct from the build version of the component updates contained within the fix pack. ptf.component-name A list of components. File Type: ptf-applied Persistence: versionDir/id.ptfApplied Elements: ptf-id string required component-applied complex min=0, max=unbounded Type Detail: A ptf-applied collection specified what components have been updated for the refresh pack, fix pack, or interim fix as specified by the ID. Element Detail: ptf-applied.ptf-id The ID of the refresh pack, fix pack, or interim fix for which applieds are recorded. ptf-applied.component-applied The list of recorded applications. Element Type: component-applied Elements: component-name string required update-type enum required [enumUpdateType] log-name anyURL required backup-name anyURL required time-stamp date required Type Detail: An applied instance is present to indicate the application of an update for a particular interim fix, fix pack, or refresh pack to a particular component. (The particular interim fix, fix pack, or refresh pack is specified by the applied parent.) An applied provides sufficient information to undo itself. The elements of an applied are copies of values from update events. Element Detail: component-applied.component-name The name of the component which was updated. component-applied.update-type The type of the component update. component-applied.log-name The name of the log file that was generated by this application. component-applied.backup-name The name of the backup file that was generated by this application. component-applied.time-stamp The time of this application (the ending time of the corresponding update event). Enum Type: enumUpdateType Values: 0 add 1 replace 2 remove 3 patch Type Detail: An update type instance specifies the type of an update. An 'add' update adds a component into an installation. A 'replace' update replaces a particular version of a component with a different version of that component. A 'remove' update removes a component. A 'patch' update performs a limited update to a component, in particular, without changing the version of the component. When adding a component, that component may not already be present. When replacing or removing a component, that component must be present. When patching a component, that component must be present. When replacing or removing a component, or when patching a component, usually, at least one version prerequisite will be specified for the component update. Value Detail: enumUpdateType.add Specifies that an update adds a component. enumUpdateType.replace Specifies that an update replaces a component. enumUpdateType.remove Specifies that an update removes a component. enumUpdateType.patch Specifies that an update modifies a component, but does not change its version. Type Family: history File Type: event-history Persistence: historyDir/event.history Elements: update-event complex min=0, max=unbounded Type Detail: One event history is provided for a websphere product family installation. This event history contains history of update events, corresponding with the actual update events for that product family. Element Detail: event-history.update-event The list of update events for the websphere product family. The top level events are refresh pack, fix pack, and interim fix events, each containing one or more component events. Element Type: update-event Elements: event-type enum required [enumEventType] parent-id string required id string required update-type enum required [enumUpdateType] primary-content anyURI required update-action enum required [enumEventAction] log-name anyURI required backup-name anyURI required start-time-stamp dateTime required result string required update-event complex optional Type Detail: An update event denotes a single update action, applying to either a fix, a fix pack, a refresh pack, or a component, according to the set event type. Element Detail: update-event.event-type The type of this event, either a refresh pack, fix pack, or an interim fix type event, or a component type event. update-event.parent-id This element is present only for component events. The ID of the parent interim fix, fix pack, or refresh pack of this event. update-event.id The ID of the interim fix, fix pack, refresh pack, or component that was updated, interpreted according to the type of the event. update-event.update-type The type of update for an update event. update-event.update-action The type of action for this event. update-event.log-name The name of the log file that was generated for this event. update-event.backup-name The name of the backup file that was generated for this event. update-event.start-time-stamp The XML timestamp of the starting time of the event. This timestamp follows the XML timestamp format, meaning that time zone information is included. update-event.result The result of the update. update-event.update-event A collection of child events. This collection is used for interim fix and fix pack type events. This collection is empty for component type events. Type Detail: An event type instance specifies the type of an update event, which is either a refresh pack, fix pack, or interim fix (ptf) event or a component event. The interpretation of particular event elements depends on the set event type. Value Detail: EventType.ptf Specifies that an event is for a refresh pack, fix pack, or interim fix update. EventType.component Specifies that an event is for a component update. Enum Type: update-action Values: 0 Install 1 Uninstall Type Detail: An event action instance specified the operation performed by an update, which can be an install or uninstall operation. Value Detail: enumEventAction.install Specifies that an event is an install operation. enumEventAction.uninstall Specifies that an event is an uninstall operation. Enum Type: enumUpdateType Values: 0 Add 1 Replace 2 Remove 3 Patch Type Detail: An update type instance specifies the type of a component update. An 'add' update adds a component into an installation. A 'replace' update replaces a particular version of a component with a different version of that component. A 'remove' update removes a component. A 'patch' update performs a limited update to a component, in particular, without changing the version of the component. To add a new component, the component must not exist. To replace or remove a component, the component must exist. To patch a component, the component must exist. When replacing or removing a component, or when patching a component, usually, at least one version prerequisite is specified for the component update. Value Detail: enumUpdateType.add Specifies that an update adds a component. enumUpdateType.replace Specifies that an update replaces a component. enumUpdateType.remove Specifies that an update removes a component. enumUpdateType.patch Specifies that an update modifies a component, but does not change its version. Enum Type: enumEventResult Values: 0 Succeeded 1 Failed 2 Cancelled Type Detail: An event result instance denotes a particular result for an update event. The result indicates success, failure, or cancellation. Value Detail: enumEventResult.succeeded Specifies that the operation was successful. enumEventResult.failed Specifies that the operation failed. enumEventResult.cancelled Specifies that the operation was cancelled.