|
|
This chapter describes the process of upgrading versions of Plumtree Corporate Portal and Plumtree Foundation to the latest version of the portal (AquaLogic Interaction).
This section provides the paths that are available to upgrade your portal to AquaLogic Interaction 6.1.
| Note: | When upgrading to an AquaLogic Interaction 6.1 maintenance pack, it is not necessary to upgrade to AquaLogic Interaction 6.1 first. Unless otherwise noted, follow the procedure for upgrading from your current version to AquaLogic Interaction 6.1, but use the installer for the maintenance pack instead of the installer for AquaLogic Interaction 6.1. |
| 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 portal upgrade.
|
To apply an AquaLogic Interaction 6.1 Maintenance Pack:
To upgrade from Foundation 6.0 to AquaLogic Interaction 6.1:
To run the 6.0 to 6.1 SQL database upgrade script:
To upgrade from Corporate Portal 5.0.x to AquaLogic Interaction 6.1:
This section describes the procedure for upgrading the portal database to AquaLogic Interaction 6.x specifications. The basic steps described in this section are:
If necessary, have your DBA upgrade database software to the currently supported version. For current database version requirements, see Software Requirements.
| Note: | When upgrading to Oracle 9i or 10g, ensure that the new database character set is UTF8 and the new database national character set is AL16UTF16. |
In earlier versions of the portal, document names were case sensitive; a document name in all caps would be considered a different document than one with the same name in all lower case. In AquaLogic Interaction 6.x, document names are case insensitive, which means document names considered unique in earlier versions of the portal may now be considered duplicates.
If there is a concern that your Oracle database contains duplicate document names, BEA provides two scripts that you scan run before you run the Database Upgrade Tool. It is important to note that running these scripts is optional and that they support Oracle databases only. The scripts are located in <PT_HOME>/ptportal/6.1/sql.
The command line Database Upgrade Tool is used to upgrade a portal database to 6.x specifications.
To successfully perform an upgrade, you must supply data needed by the upgrade process (such as the location of various files). You supply this data through a text file. This text file is the upgradedata.properties file and is created in:
[PT_HOME]/settings/portal/upgradedata.properties
The first time you run the Database Upgrade Tool, it creates the upgradedata.properties text file that contains descriptions of the required data. You edit the upgradedata.properties file in a text editor. After entering all necessary parameters, you run the Database Upgrade Tool a second time. The Database Upgrade Tool reads the parameters from the upgradedata.properties file, and performs the upgrade.
| Note: | Your system must be properly configured to run the portal in order to use this application, as it relies on your portal configuration to know how to connect to the database and complete the upgrade. |
| Note: | The Admin User Name is case sensitive. |
| Note: | File paths are in the format /directory/subdir/filename.xxx and cannot have a space at the end of the path nor quotes around the path name. A correct example would be:File_Path = /opt/plumtree/ptedir/yourfilename.pte |
| Note: | The Database Upgrade Tool modifies data regardless of whether it is also generating an SQL Script. |
| Note: | If PTGROUPMEMBERSHIP has a materialized view you may see an error regarding inability to drop a view. This can be ignored. |
| Note: | You must restore the database to its original 5.0.x state before you re-run the Database Upgrade Tool. The Database Upgrade Tool modifies the database to determine all possible errors. Therefore, even if the upgrade did not complete successfully, the database is at least partially upgraded to 6.1 specifications. |
Export the data from the portal schemas using tools provided by your database vendor.
To create the new database schema, follow the instructions appropriate for your database type.
On a Unix installation the script is located at:
<PT_HOME>/ptportal/6.1/sql/oracle_unix9.2
<PT_HOME>/ptportal/6.1/sql/oracle_unix10
On a Windows installation and Oracle 9i, the script is located at:
<PT_HOME>\ptportal\6.1\sql\oracle_nt9.2
<PT_HOME>\ptportal\6.1\sql\oracle_nt10
Using tools provided by your database vendor, import the data you exported into the newly scripted database.
| Note: | On SQLServer databases, the portal data will now be in a new database. You must either modify connection information for all servers that use the portal database, or move the portal database back to the original database by dropping the original, recreating the original using the table script in Creating the New Database Schema on a SQLServer Database, and then exporting the data from the temporary database to the original database. |
To update stored procedures and system-specific parameters in the new portal database, you must run two sql scripts. The scripts are located in <PT_HOME>/ptportal/6.1/sql under the directory appropriate to your operating system and database version.
If you upgraded your portal from 5.0.x to 6.1 and find that mandatory portlets are not appearing properly in your 6.1 portal, run the following database script on your 6.1 database to resolve the issue. If you upgraded from 5.0.x to 6.0 and mandatory portlets are appearing properly in your 6.0 portal, skip this step:
UPDATE PTPages SET TopicPos=0 WHERE TopicPos!=0 AND ObjectId IN (SELECT ObjectId FROM PTPages p, (SELECT FolderId, MIN(TopicPos) AS MinTopicPos FROM PTPages WHERE FolderId<0 GROUP BY FolderId) a WHERE p.FolderId=a.FolderId AND p.TopicPos=a.MinTopicPos)
The next search update agent that runs will rebuild the search index.
| Note: | We do not recommend clicking Run Once from the administrative folder or selecting Run Once from the Job Editor. If you click Run Once from the administrative folder, the job log will be lost after the operation completes, which may inhibit troubleshooting if the rebuild fails. If you select Run Once from within the Job Editor, the Search Update Agent will not be scheduled to run again in the future. |
Now that you have installed version 6.1 of the Administrative Portal, scripted the database and performed other necessary upgrade steps, you can complete the AquaLogic Interaction component upgrade. You do this by installing all other AquaLogic Interaction 6.1 components on their respective hosts. On each host, first stop any existing Corporate Portal 5.0.x, Foundation 6.0 or AquaLogic 6.1 services. Run the AquaLogic Interaction 6.1 installer on each host and select Custom Install to select the AquaLogic Interaction 6.1 components that you want to install. For detailed instructions on launching the installer and completing its screens, see Installing the AquaLogic Interaction Components.
If your portal deployment includes one or more AquaLogic User Interaction products (such as Collaboration, Publisher, Analytics, and so on) upgrade those products now. Refer to each product’s associated installation and upgrade guide for instructions on upgrading those products.
|