WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Build Definition wizard: Maintenance packages panel

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.

Validation

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.

Disconnected mode affects file path specifications

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.

What are maintenance packages?

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.

The image depicts the hierarchy of maintenance packages. At the top is a box icon, denoted "Refresh packs Rp1", with a local file path of "c:\WBI_downloads\name_of_refresh_pack_1_ZIP_file.pak". Below this is a similar group for "Fix packs FP3" with a local file path which is identical except that "refresh_pack_1" is replaced by "fix_pack_3". Below this is a 3rd equivalent grouping, this time labelled "SDK, Java technology edition fix pack, SDK", and a local file path with the same structure as both the refresh and fix packs. The 4th grouping is slightly altered, now an icon of 2 pages with a paper clip is denoted "interim fixes, iFix "A" and iFix "B" ". The local file paths are shown as "c:\WBI_downloads\name_of_ifix_A_file.pak" and "c:\WBI_downloads\name_of_ifix_B_file.pak". The last element of the figure is at the bottom a large arrow pointing from left to right ends at a cell containing an icon of various tools and the words "Build definition wizard", indicating that the various maintenance packages are all brought together in the customized installation package using the build definition wizard.

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cins_if_builddef_maint.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).