# Installation and Upgrade Guide

# Upgrading Studio

The following table summarizes possible upgrade paths and upgrade documentation.

Table 4-1 Upgrade Paths
Upgrade Path | Upgrade References
--- | ---
2.x to 2.2 MP1 | Follow the procedures in Upgrade Steps.
1.1.x to 2.2 MP1 | Follow the procedures in Upgrade Steps. Then, follow the procedure in Upgrading from 1.1.x.
1.0.x to 2.2 MP1 | Follow the procedures in the Installation and Upgrade Guide for Plumtree Studio Server, Version 1.1 to upgrade your Studio database to Version 1.1. Follow the procedures in this chapter to upgrade from Version 1.1 to the current version.

## Upgrade Steps

To upgrade Studio:

1. Read the release notes for a summary of features introduced or changed in this and all previous 2.1 releases.
2. Verify that you have completed the pre-installation steps. For details, see Pre-Installation Requirements.
3. Back up your existing Studio database and portal database.
4. If you have customized your existing PTStudioConfig.xml file (for example, C:\Program Files\plumtree\ptstudio\<version>\settings\config\PTStudioConfig.xml), save a copy in a new location. The installer overwrites previously installed files.
5. If you are running a version of Studio prior to 2.1, undeploy the ptstudio Web application from the application server. To do this in Tomcat, rename the ptstudio.xml file in the <tomcat home>/webapps folder. For Weblogic or Websphere, rename the Web application ptstudio in the administrative console of your application server.
6. Install Studio software as described in Installing Studio.

Note: | You will not be running any scripts against your database.

1. Register Studio objects with the portal. For information, see Registering the Studio Remote Portlet Package with the Portal.
2. If applicable, modify PTStudioConfig.xml to configure your customized settings:

- For Windows:
  <PT_HOME>\ptstudio\2.2\settings\config\PTStudioConfig.xml
- For UNIX and Linux: <PT_HOME>/ptstudio/2.2/settings/config/PTStudioConfig.xml

3. If you are upgrading from 1.1.x, see Upgrading from 1.1.x. If you are upgrading from 2.x, you are finished.

## Upgrading from 1.1.x

If you are upgrading from 1.1.x, log in to the portal as the administrator and delete the following portlets and Web services from your portal deployment:

- Plumtree Studio Gadget Manager
- Plumtree Studio Database Manager
- Plumtree Studio Gadget Administrator
- Plumtree Studio Template Administrator
- Plumtree Studio Bundle Manager
- Plumtree Studio Gadget Manager Web Service
- Plumtree Studio Database Manager Web Service
- Plumtree Studio Gadget Administrator Web Service
- Plumtree Studio Template Administrator Web Service
- Plumtree Studio Bundle Manager Web Service

Note: | The naming convention for the above Web services always begins with Plumtree Studio followed by the Web service name. The .pte file imports a number of templates that have only Studio at the front of the name, not Plumtree Studio.