Upgrading for Maintenance Releases

This topic assumes that you have developed and deployed a compact installation of Arbortext Editor at your site for a major Arbortext Editor release. An example of a major release is 7.1 F000.

A new version of the Arbortext Editor Deployment Kit is released with each Arbortext Editor maintenance release. An example of a maintenance release is 7.1 M010.

To upgrade the compact installation of Arbortext Editor on your users’ systems, you must add a new directory to your Deploy Directory for the maintenance release. You must also develop and deploy a new compact installation program for the maintenance release.

If you are upgrading an existing compact installation of Arbortext Editor, then you cannot change the features defined in the manifest.txt file for the existing installation. If you want to change the features included in the compact installation for a maintenance release, your users must first uninstall the existing installation of Arbortext Editor. You can then distribute the compact installation program for the maintenance release that contains the new feature set.

Follow these steps to develop a compact installation program to upgrade an existing compact installation of Arbortext Editor:

1. Download the release file for the maintenance release version of the Arbortext Editor Deployment Kit from the PTC support site and unzip the contents to a directory on your system.

To download a release file, go to the PTC support site at www.ptc.com/en/support and select Download Software.

The zip file for the 64–bit version of the Arbortext Editor Deployment Kit is available when you select Arbortext Editor from the product list.

3. Enter the same Deploy Directory in the Deploy Directory field that you are using for the existing compact installation.

Use whatever value you desire in the Installer Output File field and click the Create Installer button to create the upgrade installation program.

4. Create a new subdirectory in your Deploy Directory for the maintenance release and add the same files from the maintenance release of the Arbortext Editor Deployment Kit that you used for the existing release.

For example, suppose your existing Deploy Directory contained the following directories and files:

In this case, you would add a subdirectory for the maintenance release that contains the exact same files from the maintenance release of the Arbortext Editor Deployment Kit:

site\
siteprefs.xml
custom.zip
7.1F000\
manifest.txt
java.cab
help_center_de.cab
help_center_en.cab
help_center_es.cab
help_center_fr.cab
help_center_it.cab
help_center_ja.cab
help_center_ko.cab
help_center_zh_CN.cab
help_center_zh_TW.cab
7.1M010\
manifest.txt
java.cab
help_center_de.cab
help_center_en.cab
help_center_es.cab
help_center_fr.cab
help_center_it.cab
help_center_ja.cab
help_center_ko.cab
help_center_zh_CN.cab
help_center_zh_TW.cab

Note that you do not need to change the site directory in your Deploy Directory, as it will automatically be used by the upgraded Arbortext Editor.

6. Test the new upgrade installation program on a system that has the existing compact installation of Arbortext Editor.

Make sure the features and site customizations you expect are present in the upgraded version of Arbortext Editor.

7. Distribute the upgrade compact installation program to your users and tell them to download and execute it to upgrade their existing release of Arbortext Editor to the maintenance release.

Note that your Deploy Directory now supports two releases of Arbortext Editor. If a user ran the compact installation application for the F000 version of Arbortext Editor, then that version would be installed on their system. A Deploy Directory can support multiple versions of the compact installation application.

Once you are certain that no users at your site will need to install the previous version of Arbortext Editor, you can remove the directory for that version from your Deploy Directory. The compact installation application for a maintenance release can perform a full installation of Arbortext Editor, as well as upgrading an existing installation.