Select any maintenance packages (*.pak files) that want to include in your customized installation package (CIP) using the maintenance packages panel. Maintenance packages include refresh packs, fix packs and interim fixes.
Selecting maintenance packages is optional. The types of packages to include are your choice. For example, you can skip fix packs and install an interim fix. Or you can install one refresh pack and five interim fixes.
Fix pack compressed files are bundled with the Update Installer for WebSphere® Software. Decompress the file to expose the maintenance package (*.pak) file in the /updateinstaller/maintenance directory.
Always select a *.pak file when selecting a maintenance package, such as the updateinstaller\maintenance\6.2-WS-WBI-WinX32-RP0000001.pak file.
You can select only one fix pack and one refresh pack. Fix packs are cumulative. Always select the latest available package.
Type directly into each field to identify the file path and file name of the *.pak files. In connected mode, you can instead click the Browse buttons to locate available refresh packs and fix packs.
The processing engine requires selected maintenance packages to have a valid file path and valid format. In connected mode, validation of the file path occurs when you click Next. When fix packs are validated, a dialog is displayed which displays the base WebSphere Application Server maintenance level that is required for the WebSphere ESB CIP that is being created.
In disconnected mode, the processing engine performs validation while building the customized installation package from the build definition.
The directory and valid maintenance package must exist in connected mode. In disconnected mode, remember to specify the file path and the name of the *.pak file in terms of the machine on which the processing engine machine runs. The processing engine must be able to locate the maintenance package at build time.
Maintenance packages include fix packs, refresh packs and interim fixes.
A fix pack is a cumulative package of fixes, such as Version 6.2.0.1. Fix packs install on top of a previous fix pack, such as applying Version 6.2.0.2 to Version 6.2.0.1. Fix packs are cumulative, so Version 6.2.0.2 includes all fixes in Version 6.2.0.1. Check the list of delivered fixes in the fix pack to determine which interim fixes must be reinstalled. If an interim fix is deleted, but the fix is not in the fix pack, reinstall the interim fix.
A refresh pack is a cumulative package of fixes, such as Version 6.2.1. Refresh packs install on top of a previous refresh pack, such as applying Version 6.2.2 to Version 6.2.1. Refresh Packs are cumulative, so Version 6.2.2 includes all fixes in Version 6.2.1. A refresh pack also includes the fixes from all of the intermediate fix packs. Check the list of delivered fixes in the refresh pack to determine which interim fixes must be reinstalled. If an interim fix is deleted, but the fix is not in the refresh pack, reinstall the interim fix.
An interim fix is a single published emergency fix that resolves one or more product defects.
An interim fix can be applied to a release, refresh pack, or fix pack where applicable. Interim fixes are validated by at least one customer prior to publishing.