Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Upgrade

This chapter describes the process of upgrading from previous versions of Plumtree Content Server and AquaLogic Interaction Publisher to the current version.

 

Upgrade Paths

This section describes the paths that are available to upgrade to Publisher 6.5.

Note: All upgrade paths are between two systems of the same operating system brand, but not necessarily the same operating system version. Check current hardware and software requirements and make any required upgrades to operating system or database software prior to proceeding with the Publisher upgrade.
Upgrade Path
Upgrade References
Content Server 6.1, Publisher 6.2, Publisher 6.3, or Publisher 6.4 to Publisher 6.5
Follow the procedure described in Upgrading from Publisher (Content Server) 6.1, 6.2, 6.3, or 6.4 to Publisher 6.5.
Content Server 6.0 to Publisher 6.5
Follow the procedures in described in Upgrading from Content Server 6.0 to Publisher 6.5

 

Upgrading from Publisher (Content Server) 6.1, 6.2, 6.3, or 6.4 to Publisher 6.5

To upgrade from Content Server 6.1, Publisher 6.2, Publisher 6.3, Publisher 6.4 to Publisher 6.5:

  1. Run the Publisher installer. For details, see Running the Installer During Upgrade.
  2. If you are upgrading from Content Server 6.1, upgrade the Workflow database. For details, see Upgrading the Workflow Database.
  3. Import the Publisher migration package. For details, see Importing the Publisher Migration Package.
  4. Start Publisher and verify the installation. For details, see Starting and Verifying the Installation.
  5. Upgrade the default Publisher portlet templates. For details, see Importing the Published Content Portlets Migration Package.
    6. Note: If you have customized the object properties, such as the name or description, of the default portlet templates, make copies of the portlet templates before importing the published content portlets migration package. These customizations will be overwritten and will need to be reapplied. Customizations to the Publisher settings will not be overwritten.
  6. If your published content is located on the Publisher host machine and deployed by the Publisher application server, update the publishing targets to reflect any changes from your previous installation. For details, see Updating Publishing Targets.
    7. Note: If you are upgrading from Publisher 6.4, this step does not apply unless you install Publisher 6.5 to a directory different than that of the Publisher 6.4 installation.
  7. Re-index Publisher objects by performing one of the following:
    • Republish all content items that you want to be included in the search index.
    • Republish all content folders that contain content items that you want to be included in the search index.
    • Republish the entire Publisher hierarchy.
      • Note: When you republish the entire Publisher hierarchy, all Publisher objects will be included in the search index. This includes objects that were not published and indexed before upgrading to Publisher 6.5.

      For details on publishing, see Administrator Guide for AquaLogic Interaction Publisher.

 

Upgrading from Content Server 6.0 to Publisher 6.5

To upgrade from Content Server 6.0 to Publisher 6.5:

  1. Run the Publisher installer. For details, see Running the Installer During Upgrade.
  2. (Oracle only) Upgrade the Workflow database. For details, see Upgrading the Workflow Database.
  3. Import the Publisher migration package. For details, see Importing the Publisher Migration Package.
  4. Start Publisher and verify the installation. For details, see Starting and Verifying the Installation.
  5. Upgrade the default Publisher portlet templates. For details, see Importing the Published Content Portlets Migration Package.
    6. Note: If you have customized the object properties, such as the name or description, of the default portlet templates, make copies of the portlet templates before importing the published content portlets migration package. These customizations will be overwritten and will need to be reapplied. Customizations to the Publisher settings will not be overwritten.
  6. If your published content is located on the Publisher host machine and deployed by the Publisher application server, update the publishing targets to reflect any changes from your previous installation. For details, see Updating Publishing Targets.

 

Running the Installer During Upgrade

To run the installer during upgrade:

  1. Back up the existing Portal, Publisher and Workflow databases.

    2. This allows you to recover your data if there is a problem during installation. For more information, see your database documentation.

  2. For Content Server 6.1 and higher:
    1. Stop the Publisher (Content Server) service, Search service, Automation Service and Document Repository Service.
    2. Clear the application server’s work directory. By default, this directory is located in:
Note: Unix: <install_dir>/common/container/tomcat/<version>/work
Note: Windows: <install_dir>\common\container\tomcat\<version>\work
  1. For Content Server 6.0:
    1. Stop the application server that hosts Content Server.
    2. Stop the Workflow Server service.
    3. If you installed the published content directory in the default location, \plumtree\ptcs\publishedcontent, back up your published content directory.
    4. Uninstall the existing version of Content Server. Verify that the application is removed from the application server after uninstall.
      5. Note: If you want to continue running Publisher on the same port that the legacy application server was on, change the port used by the application server to avoid a port conflict.
    5. If your published content is deployed on the same application server as Content Server and you want to deploy it to the new Publisher application server, undeploy it from the legacy application server.
      6. Note: If you will not use the legacy application server for published content, then disable the service or set it to start manually.
  2. Copy the installer file to the directory where you installed the previous version of Publisher.

    3. This allows the installer to use the silent properties file created by previous installations. For more information on using the silent properties file, see Installer Properties File.

  3. Install the Publisher components as described in Installing the Publisher Components.
    4. Note: Non-Linux Systems Only) If you are installing Publisher on the same computer on which AquaLogic Interaction 6.5 is installed, you must install Publisher into a different installation folder than the AquaLogic Interaction installation folder. For example, if the AquaLogic Interaction installation folder is /opt/bea/alui, install Publisher into a folder that is different than /opt/bea/alui, such as /opt/bea/alui_other.
  4. (Windows only) When the installer prompts you, reboot the machine. If you do not reboot, certain PATH environment variable changes might not take effect, and you will get errors when you try to deploy and start the applications.

    5. You do not need to reboot a Unix machine.

 

Upgrading the Workflow Database

This table describes the steps to upgrade an existing Workflow database to Publisher 6.5 specifications.

Table 4-1 Workflow Database Upgrade Instructions
Existing Configuration
Workflow Database Upgrade Instructions
Content Server 6.x; no existing Workflow database.
  • Create a Workflow database and user with the information you entered in the installer. Refer to Creating and Configuring the Databases for full details on database and user creation for the database you are using.
  • As the Workflow database user, run the script appropriate to your database: <install_dir>\ptworkflow\6.5\sql\mssql\create_schema.sql <install_dir>\ptworkflow\6.5\sql\oracle9.2\create_schema.sql <install_dir>\ptworkflow\6.5\sql\oracle10\create_schema.sql
Content Server 6.0 and 6.1; existing Workflow database
  • As the Workflow database user, run the script appropriate to your database:
    <install_dir>\ptworkflow\6.5\sql\mssql\upgrade_schema6.2.sql <install_dir>\ptworkflow\6.5\sql\oracle9.2\upgrade_schema6.2.sql
    <install_dir>\ptworkflow\6.5\sql\oracle10\upgrade_schema6.2.sql
Publisher 6.2, 6.3, or 6.4
  • No upgrade scripts are necessary.

 

Updating Publishing Targets

Note: This section applies only to installations in which published content is deployed by the Publisher application server or located in the Publisher installation directory on the Publisher host machine.

After upgrading from earlier versions of Content Server or Publisher, it may be necessary to modify the publishing targets to reflect a new published content URL or file system location.

  1. If your published content is located on the same host as Publisher, copy or move your published content from the old location to the new installation directory structure.

    2. If you have accepted all defaults, the old location is:

    \plumtree\ptcs\publishedcontent

    and the new location is:

    \bea\alui\ptcs\publishedcontent

  2. Point Publisher to the new published content location. From Publisher Explorer, right-click on the root node and select Publishing Target.
    1. Update the publishing target:
      • On the Publish tab, update the Transfer Path to point to the new published content location.
      • If your Publisher port has changed, update the Browser Path to reflect the new port number.
      • Click Test Publish Target to verify the new publishing target.
    2. Update the preview target:
      • On the Preview tab, update the Transfer Path to point to the new published content location.
      • If your Publisher port has changed, update the Browser Path to reflect the new port number.
      • Click Test Preview Target to verify the new preview target.
    3. Click Finish to save your changes.
  3. Change the gateway URL prefixes for the Publisher Web services:
    1. In the Admin Objects Directory, open the folder in which the Publisher Web services were created.
    2. Edit the Published Content Web service:

      3. On the HTTP Configuration page, under Gateway URL Prefixes, update the publish and preview URLs to the correct values.

      Example:

      http://<publisher_host>:<port>/publishedcontent/publish http://<publisher_host>:<port>/publishedcontent/preview

      Note: The URL prefix is ignored if the value in the text box begins with “http://” or https://.
    3. Edit the Publisher Administration Web service:

      4. On the HTTP Configuration page, under Gateway URL Prefixes, update the preview URL to the correct values.

      Example:

      http://<publisher_host>:<port>/publishedcontent/preview

      Note: The URL prefix is ignored if the value in the text box begins with “http://” or https://.
  4. Republish your existing published content. To republish the entire directory, right-click on the root node in Publisher Explorer and select Publish.

 

Additional Information for Content Server 6.0 Upgrades

The following are important differences between Publisher 6.5 and versions of Content Server prior to Content Server 6.1:


  Back to Top       Previous  Next