Preparing to upgrade SiteEdit to Experience Manager

If your current implementation of SDL Tridion software also includes an SDL SiteEdit implementation, some backup steps are required before you can upgrade Content Manager server.

Procedure

  1. If your instance of SDL SiteEdit is (partially) implemented in deprecated VBScript/JScript templates, decide if you want to upgrade these VBScript/JScript templates, or to migrate them.
    Upgrade

    Upgrading your existing SiteEdit-enabled VBScript/JScript templating code only requires you to add a Javascript command and republish. Do bear in mind, however, that your templating code is deprecated.

    Migration

    If you would prefer to migrate your VBScript/JScript code instead, migration would be part of a larger effort to migrate your VBScript templates to modular templating. For more general information about such a migration, refer to the documentation topics about deprecation.

  2. On the Content Manager server machine, access %TRIDION_HOME%.
  3. Navigate to the subfolder SiteEdit 2009\SiteEdit\Application\Configuration\.
  4. In this folder, back up the file SiteEdit.config to a location of your choosing.
  5. If all of the following applies:
    • You currently have SiteEdit implemented in VBScript/JScript templates
    • You want to upgrade your current implementation

    then navigate to the bin\ subfolder of the Content Manager root location. From that folder, back up the following to a location of your choosing:

    • If your SiteEdit implementation includes VBScript/JScript templates for SiteEdit 2.0 and later, back up cc_SiteEdit2.dll.
    • If your SiteEdit implementation includes VBScript/JScript templates for SiteEdit 1.3 SP2, back up cm_SiteEdit.dll.
  6. Access the section to add and remove software from your Windows Start Menu, and select to uninstall your version of SiteEdit.