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.4 MP1.
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, or Publisher 6.3 to Publisher 6.4 MP1
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.
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.
Note:
If you are upgrading from Publisher 6.3, this step does not apply unless you install Publisher 6.4 MP1 to a directory different than that of the Publisher 6.3 installation.
Upgrading from Content Server 6.0 to Publisher 6.4 MP1
To upgrade from Content Server 6.0 to Publisher 6.4 MP1:
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.
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.
Upgrading from Content Server 5.0.x to Publisher 6.4 MP1
To upgrade from Content Server 5.0.x to Publisher 6.4 MP1:
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.
(Optional) If your previous 5.0.x installation included a Branding Remote Server object, you can safely delete it from the portal after upgrading to 6.4 MP1 because it is no longer used.
Log in to the Administrative Portal.
Go to the Administration directory.
Browse to the Branding folder and delete the Branding Remote Server.
Upgrading 5.0.x Portlet Templates
In Publisher 6.4 MP1, the default portlet templates are installed under language subfolders: de, en, fr, etc. If you are upgrading from Content Server 5.0.x, your existing portlet templates are upgraded but not moved into the appropriate language folder. To make the portlet templates available under the language folder, you must delete the existing templates before importing the published_content_portlets.pte file.
Note:
In 5.0.x installs of Content Server without Branding, all six portlet templates are under the Published Content Portlets folder. In 5.0.x installs of Content Server with Branding, the Header, Footer, and ContentCanvas portlet templates are under the Content Server | Branding folder and the News, Community Directory, and Announcement portlet templates are under the Content Server | Published Content Portlets folder.
Delete the 5.0.x portlet templates:
Log in to the Administrative Portal.
Go to Administration.
Browse to the Content Server | Published Content Portlets folder.
Choose the existing default Content Server portlet templates and click Delete.
If applicable, repeat the above process for any Content Server portlet templates in Content Server | Branding.
If you have a preexisting 5.0.x portal and Content Server installation, it contains different Web services objects for the published content portlet templates (like the News Portlet Template) and branding portlet templates (like the Header, Footer, or Canvas template). Publisher 6.4 MP1 replaces these five distinct Web services with a single Web service.
As the final step of an upgrade from 5.0.x, you must run a script against the portal database that updates the Web service UUIDs for existing portlets to point to the newer Publisher Web service for published content. This script affects only the portal objects that relate directly to Publisher and Workflow portlets and portlet template integration.
To upgrade your Web Services UUIDs:
Back up the portal database.
As the portal database user, run the script appropriate to your portal database:
Stop the application server that hosts Content Server.
Stop the Workflow Server service.
If you installed the published content directory in the default location, \plumtree\ptcs\publishedcontent,back up your published content directory.
Uninstall the existing version of Content Server. Verify that the application is removed from the application server after uninstall.
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.
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.
Note:
If you will not use the legacy application server for published content, then disable the service or set it to start manually.
Copy the installer file to the directory where you installed the previous version of Publisher.
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.
(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.
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.4 MP1 specifications.
Table 4-1 Workflow Database Upgrade Instructions
Existing Configuration
Workflow Database Upgrade Instructions
Content Server 5.0.x, 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: <PT_HOME>\ptworkflow\6.4\sql\mssql\create_schema.sql<PT_HOME>\ptworkflow\6.4\sql\oracle9.2\create_schema.sql <PT_HOME>\ptworkflow\6.4\sql\oracle10\create_schema.sql
Content Server 5.0.x; existing Workflow database.
As the Workflow database user, run the script appropriate to your database: <PT_HOME>\ptworkflow\6.4\sql\mssql\create_schema.sql<PT_HOME>\ptworkflow\6.4\sql\oracle9.2\create_schema.sql <PT_HOME>\ptworkflow\6.4\sql\oracle10\create_schema.sql
Run the dbupgrade script:
On Windows: <PT_HOME>\ptworkflow\6.4\bin\dbupgrade.bat
On Unix: <PT_HOME>/ptworkflow/6.4/bin/dbupgrade.sh
Content Server 6.0, existing Workflow database
(Oracle only) Run the script appropriate to your version of Oracle: <PT_HOME>\ptworkflow\6.4\sql\oracle9.2\upgrade_schema6.1.sql <PT_HOME>\ptworkflow\6.4\sql\oracle10\upgrade_schema6.1.sql
Content Server 6.1; existing Workflow database
As the Workflow database user, run the script appropriate to your database: <PT_HOME>\ptworkflow\6.4\sql\mssql\upgrade_schema6.2.sql <PT_HOME>\ptworkflow\6.4\sql\oracle9.2\upgrade_schema6.2.sql <PT_HOME>\ptworkflow\6.4\sql\oracle10\upgrade_schema6.2.sql
Publisher 6.2 or 6.3
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.
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.
If you have accepted all defaults, the old location is:
\plumtree\ptcs\publishedcontent
and the new location is:
\bea\alui\ptcs\publishedcontent
Point Publisher to the new published content location. From Publisher Explorer, right-click on the root node and select Publishing Target.
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.
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.
Click Finish to save your changes.
Change the gateway URL prefixes for the Publisher Web services:
In the Admin Objects Directory, open the folder in which the Publisher Web services were created.
Edit the Published Content Web service:
On the HTTP Configuration page, under Gateway URL Prefixes, update the publish and preview URLs to the correct values.
The URL prefix is ignored if the value in the text box begins with “http://” or https://.
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 5.0.x and 6.0 Upgrades
The following are important differences between Publisher 6.4 MP1 and versions of Content Server prior to Content Server 6.1:
Simplified Deployment: Publisher 6.4 MP1 contains a significant change in the deployment configuration for the product. Instead of installing the product, installing a separate application server, and deploying a WAR file to the application server, Publisher 6.4 MP1 is self-contained. It includes the runtime components needed for HTTP/HTTPS processing, and no longer requires a separate application server. This change makes the product easier to install and maintain.
BEA AquaLogic Publisher Service: After you install or upgrade to 6.4 MP1, there is a single service (or daemon on Unix) that starts and stops both the Publisher and Workflow applications. The service is controlled from the Services control panel on Windows and from the command line on Unix. In versions prior to 6.1, Content Server was deployed to a separate application server, and Workflow was a standalone service. For more information on starting and stopping the Publisher Service, see Starting and Verifying the Installation.
Single port number: The BEA AquaLogic Publisher Service runs on a single port number. In versions prior to 6.1, the Content Server Web application ran on one port number, and the Workflow Server ran on a different port number. We recommend the use of port 7087 for the BEA AquaLogic Publisher Service. Version 6.4 MP1 includes a container.conf file containing any port number settings that need to be changed after installation.
