Understanding Maintenance Releases
The Windchill Service Pack or a Critical Patch Set (CPS) and a regular Windchill release work in the same way, though their contents are different as mentioned in the section Maintenance Releases, Major Releases, and Patches. They contain updates for Windchill solutions, as well as a subset of the other Windchill product modules.
Recommendation on Update Tool Usage
Prior to 13.1.2.0, the Update tool was used after a maintenance release to perform code and data-related actions like applying schema changes and executing LoadNewData migrators. The following guidelines describes the update cases that require execution of the Update Tool.
• Updating from an earlier Windchill base release to a target system running at 13.1.2.0 requires execution of the Update tool.
• Updating from an earlier Windchill CPS, that is, from 13.1.0.0 CPS or 13.1.1.0 CPS release to the target system running at 13.1.3.0 requires execution of the Update tool. For example, when the source system is at 13.1.1.1 and target system is at 13.1.3.0.
• Updating from a base release , that is, from 13.1.2.0 release, to a maintenance release does not require Update Tool execution. For example, when the source system is at 13.1.2.0 and the target system is at 13.1.3.0, which is a maintenance release for 13.1.2.0.
• Updating from a base release to a Security Update Patch (SUP) for the same release does not require Update Tool execution. For example, when the source system is at 13.1.2.0 and the target system is at 13.1.2.4.
• Updating from one maintenance release to another maintenance release within the same major release does not require Update Tool execution. For example, when the source system is at 13.1.3.0 and the target system is a later maintenance release such as 13.1.x.0.
As mentioned in Using Both Test and Production Systems, PTC recommends that you use the separate test system to prepare and validate the updates before installing them into production. This will help ensure minimal downtime during the installation into the production system. It is also advisable to perform a backup of the product installation directory prior to performing the installation.
When you execute the PTC Solution Installer, it first determines which files should be installed onto your system. It does this by locating the directories that contain the Windchill products to be updated. After you select an installation to update, the installer determines which products are installed and what datecode versions are already present. This results in the following behavior:
• If the selected installation contains products for which there are no updates, no updates are installed.
• If the PTC Solution Installer detects that the current release of a Windchill product has already been partially installed in a selected installation, by default the installer does not reinstall the updated files; however, you are presented with an option to recover the installation.
• The installer only updates locale-specific resources on your system if it finds that those locales were previously installed and registered through an installation of the Windchill MultiLanguage Pack.
These features are intended to minimize the time it takes to install the maintenance release or point release. In particular, this avoids re-installing updates to site-modified files when you have previously incorporated those changes, or reinstalling updates to Windchill products that have already been completed. To ensure that the latest site-modified files are used, the files in the siteMod directory are redeployed each time you run the PTC Solution Installer using Update Existing Installation.
 |
Depending on what products have been installed and how they are deployed across your computer network, you may need to run the installer against multiple directories on the same computer or on multiple computers.
|
The following sections provide more details about installing the release in specific directories.