> Installation and Upgrade Guide > Quickstart Overview

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

Quickstart Overview

This chapter provides brief, high-level instructions for the installation and upgrade of AquaLogic Interaction, and is intended to quickly guide experienced administrators through the installation or upgrade procedure.

This chapter is divided into two major sections:

 

Installation

Installing the AquaLogic Interaction Components

  1. Launch the AquaLogic Interaction installer.

    2. On a Unix host, run the installer as the user created in Unix User and Group Requirements.

    On a Windows host, run the installer as the local administrator.

    The installer prompts you for specific information about your system and configuration. For more information, see Installing the AquaLogic Interaction Components.

  2. Deploy the Image Service.
    3. Note: This step is unnecessary if you installed AquaLogic Interaction for .NET, or if you instructed the installer to autodeploy the Image Service to Apache.

    In your HTTP server configuration, alias the Image Service directory to the URL specified for the Image Service when the AquaLogic Interaction installer was run. Image Service files are located in <PT_HOME>/ptimages/imageserver.

    By default, PT_HOME is:

Scripting the Database

Refer to the section that applies to your database vendor and version:

Scripting a Microsoft SQL Server 2000 Database

  1. Create and configure the portal database and portal database user:
    1. Create the portal database with the portal database name you provided the AquaLogic Interaction installer.
    2. Create the portal database user with the user name and password you provided the AquaLogic Interaction installer.
    3. Configure the portal database user to use SQL Server Authentication.
    4. Set the portal database user’s default database to the portal database.
    5. Grant the portal database user the public and db_owner roles for the portal database.
    6. Grant the portal database user all permissions on the portal database.

      7. For more information on these steps, see Creating and Configuring the Portal Database on Microsoft SQL Server 2000.

  2. Script the portal database:

    3. We recommend that you run the following scripts as the sa user, so that all objects created are owned by dbo. Scripts are found in %PT_HOME%\6.1\sql\mssql\.

    Run the scripts in this order:

    1. create_tables_mssql.sql
    2. load_seed_info_mssql.sql
    3. stored_procs_mssql.sql
    4. postinst_mssql.sql

      5. For more information, see Scripting the Portal Database.

Scripting a Microsoft SQL Server 2005 Database

  1. Create and configure the portal database and portal database user:
    1. Configure the SQL Server instance to use SQL Server and Windows Authentication mode.
    2. Create the portal database with the portal database name you provided the AquaLogic Interaction installer.
    3. Configure the portal database to use SQL Server 2000 (80) compatibility level.
    4. Create the portal database user with the user name and password you provided the AquaLogic Interaction installer.
    5. Configure the portal database user to use SQL Server Authentication.
    6. Set the portal database user’s default database to the portal database.
    7. Grant the portal database user the sysadmin server role.

      8. For more information on these steps, see Creating and Configuring the Portal Database on Microsoft SQL Server 2005.

  2. Script the portal database:

    3. We recommend that you run the following scripts as the sa user, so that all objects created are owned by dbo. Scripts are found in %PT_HOME%\6.1\sql\mssql\.

    Run the scripts in this order:

    1. create_tables_mssql.sql
    2. load_seed_info_mssql.sql
    3. stored_procs_mssql.sql
    4. postinst_mssql.sql

      5. For more information, see Scripting the Portal Database.

Scripting an Oracle 9i Database on Unix

  1. Set Oracle environment variables.

    2. Verify that the ORACLE_BASE, ORACLE_HOME, and ORACLE_SID environment variables are set correctly.

    Note: For Oracle 9i, the portal database scripts expect ORACLE_SID to be set to PLUM. If you use a different SID, you will need to edit the scripts.

    For more information, see Setting Oracle Environment Variables in Scripting an Oracle 9i Database on Unix.

  2. Copy SQL scripts.

    3. Copy SQL scripts from $PT_HOME/ptportal/6.1/sql/oracle_unix9.2 on the portal host to $ORACLE_HOME/admin/PLUM/scripts on the Oracle host.

    For more information, see Copying SQL Scripts in Scripting an Oracle 9i Database on Unix.

  3. Create the portal database.
    4. Note: These steps create a new, dedicated portal database. If you are creating the portal tablespace within an existing database, skip to step 4.
    1. Create the sys password:
      2. $ $ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/database/orapwPLUM password=password
    2. Create a directory PLUM under $ORACLE_BASE/oradata.
    3. Create a link to initPLUM.ora in $ORACLE_HOME/database.
    4. Start SQL*Plus using the /nolog flag and run crdb1_oracle_unix.sql. This script should generate no errors.
    5. Run crdb2_oracle_unix.sql. This script may take a significant amount of time to complete, and may generate the following errors:
      ORA-00942 table or view does not exist
      ORA-1432/ORA-1434 public synonym to be dropped does not exist

      Any other errors are not acceptable.
    6. Go to step 5.

      7. For more information, see Creating the Portal Database in Scripting an Oracle 9i Database on Unix.

  4. Create the portal tablespace and database user.
    5. Note: These steps assume you are installing the portal database in an existing, running database instance. If you created the portal database in step 3, skip this step. The tablespace and database user have already been created.
    1. Use SQL*Plus to connect to your database as a user with sysdba rights.
    2. Run create_ali_tablespace_unix.sql. This script should generate no errors.
    3. Run create_ali_user_oracle.sql. This script should generate no errors.

      4. For more information, see Creating the Portal Tablespace and Database User in Scripting an Oracle 9i Database on Unix.

  5. Script the portal database.
    1. Use SQL*Plus to connect to your database using the portal database user you created in step 3 or step 4.
    2. Run init_ali_db_oracle.sql. This script should generate no errors.

      3. For more information, see Scripting the Portal Database in Scripting an Oracle 9i Database on Unix.

Scripting an Oracle 9i Database on Windows

  1. Set Oracle environment variables.

    2. Verify that the ORACLE_BASE, ORACLE_HOME, and ORACLE_SID environment variables are set correctly.

    Note: For Oracle 9i, the portal database scripts expect ORACLE_SID to be set to PLUM. If you use a different SID, you will need to edit the scripts.

    For more information, see Setting Oracle Environment Variables in Scripting an Oracle 9i Database on Windows.

  2. Copy SQL scripts.

    3. Copy SQL scripts from %PT_HOME%\ptportal\6.1\sql\oracle_nt9.2 on the portal host to %ORACLE_BASE%\admin\PLUM\plumtreescripts on the Oracle host.

    For more information, see Copying SQL Scripts in Scripting an Oracle 9i Database on Windows.

  3. Create the portal database.
    4. Note: These steps create a new, dedicated portal database. If you are creating the portal tablespace within an existing database, skip to step 4.
    1. Update the registry with the RegisterSIDPLUM.reg script.
    2. Create a directory PLUM under %ORACLE_BASE%\oradata.
    3. Copy initPLUM.ora to %ORACLE_HOME%\database.
    4. Run CreateService.bat with the arguments PLUM and <password>

      > CreateService.bat PLUM <password>
    5. Start SQL*Plus using the /nolog flag and run crdb1_oracle_nt.sql. This script should generate no errors.
    6. Run crdb2_oracle_nt.sql. This script may take a significant amount of time to complete, and may generate the following errors:

      ORA-00942 table or view does not exist
      ORA-1432/ORA-1434 public synonym to be dropped does not exist

      Any other errors are not acceptable.
    7. Go to step 5.

      8. For more information, see Creating the Portal Database in Scripting an Oracle 9i Database on Windows.

  4. Create the portal tablespace and database user.
    5. Note: These steps assume you are installing the portal database in an existing, running database instance. If you created the portal database in step 3, skip this step. The tablespace and database user have already been created.
    1. Use SQL*Plus to connect to your database as a user with sysdba rights.
    2. Run create_ali_tablespace_nt.sql. This script should generate no errors.
    3. Run create_ali_user_oracle.sql. This script should generate no errors.

      4. For more information, see Creating the Portal Tablespace and Database User in Scripting an Oracle 9i Database on Windows.

  5. Script the portal database.
    1. Use SQL*Plus to connect to your database using the portal database user you created in step 3 or step 4.
    2. Run init_ali_db_oracle.sql. This script should generate no errors.

      3. For more information, see Scripting the Portal Database in Scripting an Oracle 9i Database on Windows.

  6. Start the Oracle Listener for the portal database.

    7. For more information, see Starting the Oracle Listener for the Portal Database in Scripting an Oracle 9i Database on Windows.

Scripting an Oracle 10g Database on Unix

Caution: For installations of AquaLogic Interaction on HP-UX, it is necessary to adjust Oracle’s recommended kernel settings. The value of shmseg must be set higher than 300 to prevent Oracle memory allocation issues when search repair is run or multiple jobs are executed concurrently.
  1. Set Oracle environment variables.

    2. Verify that the ORACLE_BASE, ORACLE_HOME, and ORACLE_SID environment variables are set correctly.

    Note: For Oracle 10g, the portal database scripts expect ORACLE_SID to be set to PLUM10. If you use a different SID, you will need to edit the scripts.

    For more information, see Setting Oracle Environment Variables in Scripting an Oracle 10g Database on Unix.

  2. Copy SQL scripts.

    3. Copy SQL scripts from $PT_HOME/ptportal/6.1/sql/oracle_unix10 on the portal host to $ORACLE_BASE/admin/PLUM10/plumtreescripts on the Oracle host.

    For more information, see Copying SQL Scripts in Scripting an Oracle 10g Database on Unix.

  3. Create the portal database.
    4. Note: These steps create a new, dedicated portal database. If you are creating the portal tablespace within an existing database, skip to step 4.
    1. Create the sys password:
      2. $ $ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/database/orapwPLUM10 password=password
    2. Create a directory PLUM10 under $ORACLE_BASE/oradata.
    3. Create a link to initPLUM10.ora in $ORACLE_HOME/database.
    4. Start SQL*Plus using the /nolog flag and run crdb1_oracle_unix.sql. This script should generate no errors.
    5. Run crdb2_oracle_unix.sql. This script may take a significant amount of time to complete, and may generate the following errors:

      ORA-00942 table or view does not exist
      ORA-1432/ORA-1434 public synonym to be dropped does not exist

      Any other errors are not acceptable.
    6. Go to step 5.

      7. For more information, see Creating the Portal Database in Scripting an Oracle 10g Database on Unix.

  4. Create the portal tablespace and database user.
    5. Note: These steps assume you are installing the portal database in an existing, running database instance. If you created the portal database in step 3, skip this step. The tablespace and database user have already been created.
    1. Use SQL*Plus to connect to your database as a user with sysdba rights.
    2. Run create_ali_tablespace_unix.sql. This script should generate no errors.
    3. Run create_ali_user_oracle.sql. This script should generate no errors.

      4. For more information, see Creating the Portal Tablespace and Database User in Scripting an Oracle 10g Database on Unix.

  5. Script the portal database.
    1. Use SQL*Plus to connect to your database using the portal database user you created in step 3 or step 4.
    2. Run init_ali_db_oracle.sql. This script should generate no errors.

      3. For more information, see Scripting the Portal Database in Scripting an Oracle 10g Database on Unix.

Scripting an Oracle 10g Database on Windows

  1. Set Oracle environment variables.

    2. Verify that the ORACLE_BASE, ORACLE_HOME, and ORACLE_SID environment variables are set correctly.

    Note: For Oracle 10g, the portal database scripts expect ORACLE_SID to be set to PLUM10. If you use a different SID, you will need to edit the scripts.

    For more information, see Setting Oracle Environment Variables in Scripting an Oracle 10g Database on Windows.

  2. Copy SQL scripts.

    3. Copy SQL scripts from %PT_HOME%\ptportal\6.1\sql\oracle_nt10 on the portal host to %ORACLE_BASE%\admin\PLUM10\plumtreescripts on the Oracle host.

    For more information, see Copying SQL Scripts in Scripting an Oracle 10g Database on Windows.

  3. Create the portal database.

    4. These steps create a new, dedicated portal database. If you are creating the portal tablespace within an existing database, skip to step 4.

    1. Update the registry with the RegisterSIDPLUM10.reg script.
    2. Create a directory PLUM10 under %ORACLE_BASE%\oradata.
    3. Copy initPLUM10.ora to %ORACLE_HOME%\database.
    4. Run CreateService.bat with the argument PLUM10 <password>:

      > CreateService.bat PLUM10 <password>
    5. Start SQL*Plus using the /nolog flag and run crdb1_oracle_nt.sql. This script should generate no errors.
    6. Run crdb2_oracle_nt.sql. This script may take a significant amount of time to complete, and may generate the following errors:

      ORA-00942 table or view does not exist
      ORA-1432/ORA-1434 public synonym to be dropped does not exist

      Any other errors are not acceptable.
    7. Go to step 5.

      8. For more information, see Creating the Portal Database in Scripting an Oracle 10g Database on Windows.

  4. Create the portal tablespace and database user.
    5. Note: These steps assume you are installing the portal database in an existing, running database instance. If you created the portal database in step 3, skip this step. The tablespace and database user have already been created.
    1. Use SQL*Plus to connect to your database as a user with sysdba rights.
    2. Run create_ali_tablespace_nt.sql. This script should generate no errors.
    3. Run create_ali_user_oracle.sql. This script should generate no errors.

      4. For more information, see Creating the Portal Tablespace and Database User in Scripting an Oracle 10g Database on Windows.

  5. Script the portal database.
    1. Use SQL*Plus to connect to your database using the portal database user you created in step 3 or step 4.
    2. Run init_ali_db_oracle.sql. This script should generate no errors.

      3. For more information, see Scripting the Portal Database in Scripting an Oracle 10g Database on Windows.

  6. Start the Oracle Listener for the portal database.

    7. For more information, see Starting the Oracle Listener for the Portal Database in Scripting an Oracle 10g Database on Windows.

Starting and Verifying the Installation

  1. Start the Automation Service, Document Repository Service, and Search.
    2. Note: It is important that third-party virus scanners do not attempt to scan the search service archives. For more information, see the note in Starting AquaLogic Interaction Services and Search.
  2. Run the diagnostics script and resolve any issues it finds.

    3. On Unix, the script is <PT_HOME>/ptportal/bin/diagnostic.sh.

    On Windows, the script is <PT_HOME>\ptportal\bin\diagnostic.bat. The script can also be launched by clicking Start | All Programs | BEA | Portal Diagnostic.

    For more information, see Running the Diagnostics Script.

  3. Start the portal.

    4. Start the portal by browsing to the server.pt application at the External Portal URL you provided the AquaLogic Interaction installer. For example: 

    http://myportal.domain.com/portal/server.pt
  4. Log in to the portal as Administrator with no password.
    5. Caution: You should change the default Administrator password as soon as possible. Make sure that you document the change and/or inform the appropriate portal administrators.

Importing the Search Cluster Manager Migration Package

Import the SearchClusterAdminUI.pte file, which is located in the following location on the Search host machine:

Windows: <PT_HOME>\ptsearchserver\6.1\serverpackages\

Unix: <PT_HOME>/ptsearchserver/6.1/serverpackages/

For details, see Importing the Search Cluster Manager Migration Package.

Note: You may need to log out and back in to the portal in order to see the Search Cluster Manager appear in portal administration’s Admin Utilities drop-down menu.

Importing the Content Upload Migration Package

Note: You only need to import the Content Upload migration package if you performed a clean (non-upgrade) install of AquaLogic Interaction and installed the Content Upload Service.

Import the contentupload.pte file, which is located in the following location on the Content Upload Service host machine:

Windows: <PT_HOME>\ptupload\6.1\serverpackages\

Unix: <PT_HOME>/alui/ptupload/6.1/serverpackages/

For details, see Importing the Content Upload Migration Package.

Preparing the Portal for General Use

When you first deploy your portal, there are a number of tasks you must complete to prepare the portal for general use. These tasks are described in the Administrator Guide for AquaLogic Interaction because they are tasks you will likely perform more than once to maintain your portal. Refer to the Administrator Guide for AquaLogic Interaction for the following set-up tasks:

  1. Configure display, navigation, and branding for the default experience definition and any additional experience definitions.
  2. Change the default Administrator password and delegate administrator roles.
  3. Populate the portal with administrative users and browsing users. Configure groups, users, user profiles, and Access Control Lists (ACLs) to enable managed access.
  4. Populate the portal with documents. Configure ACLs to manage access.
  5. Set up automated system maintenance, such as user synchronization, search updates, document refresh, and housekeeping jobs.

 

Upgrade

This section provides brief, high level instructions for the process of upgrading versions of Plumtree Corporate Portal and Plumtree Foundation to the latest version of the portal (AquaLogic Interaction).

Upgrade Paths

This section provides the paths that are available to upgrade your portal to AquaLogic Interaction 6.1.

Notes:

Upgrading from AquaLogic Interaction 6.1 to an AquaLogic Interaction 6.1 Maintenance Pack

To upgrade from AquaLogic Interaction 6.1 to an AquaLogic Interaction 6.1 Maintenance Pack:

  1. Important: Stop the Search service on all Search nodes before starting the upgrade. Do not restart any upgraded Search services until all nodes have been upgraded.
  2. Install the AquaLogic Interaction 6.1 MP2 Administrative Portal and Search components. For details on launching the installer and completing its screens, see Installing the AquaLogic Interaction Components.
  3. Complete the AquaLogic Interaction component installation. For details, see Completing the AquaLogic Interaction Component Upgrade

Upgrading from Foundation 6.0 to AquaLogic Interaction 6.1

To upgrade from Foundation 6.0 to AquaLogic Interaction 6.1:

  1. Install the AquaLogic Interaction 6.1 Administrative Portal and Search components. For details on launching the installer and completing its screens, see Installing the AquaLogic Interaction Components.
  2. Run the 6.0 to 6.1.sql database script. For details, see Running the 6.0 to 6.1 Database Upgrade Script.
  3. Start the AquaLogic Interaction 6.1 Administrative Portal and verify the installation. For details, see Starting and Verifying the Installation.
  4. Import the Search Cluster Manager migration package. For details, see Importing the Search Cluster Manager Migration Package.
  5. Rebuild the Search Index. For details, see Rebuilding the Search Index.
  6. Complete the AquaLogic Interaction component installation. For details, see Completing the AquaLogic Interaction Component Upgrade.

Running the 6.0 to 6.1 Database Upgrade Script

To run the 6.0 to 6.1 database upgrade script:

  1. Back up the portal database.
  2. Locate the upgrade6.0to6.1_<your_database_type>.sql script in the installation folder of the version 6.1 Administrative Portal server.
  3. Run the database upgrade script.

Upgrading from Corporate Portal 5.0.x to AquaLogic Interaction 6.1

To upgrade from Corporate Portal 5.0.x to AquaLogic Interaction 6.1:

  1. Install the AquaLogic Interaction 6.1 Administrative Portal and Search components. For details on launching the installer and completing its screens, see Installing the AquaLogic Interaction Components.
  2. Upgrade the portal database from Corporate Portal 5.0.x to Foundation 6.0 specifications. For details, see Upgrading the Database from Corporate Portal 5.0.x to Foundation 6.0 Specifications.
  3. Run the 6.0 to 6.1 SQL database script. For details, see Running the 6.0 to 6.1 Database Upgrade Script.
  4. Start the AquaLogic Interaction 6.1 Administrative Portal and verify the installation. For details, see Starting and Verifying the Installation.
  5. (Optional) Resolve missing mandatory portlets. Perform this step only if you upgraded your portal from 5.0.x to 6.1 and mandatory portlets are not appearing properly in your 6.1 portal. For details, seeResolving Missing Mandatory Portlets.
  6. Import the Search Cluster Manager migration package. For details, see Importing the Search Cluster Manager Migration Package.
  7. Rebuild the Search Index. For details, see Rebuilding the Search Index.
  8. Complete the AquaLogic Interaction component installation. For details, see Completing the AquaLogic Interaction Component Upgrade.

Upgrading the Database from Corporate Portal 5.0.x to Foundation 6.0 Specifications

This section describes the procedure for upgrading the portal database to AquaLogic Interaction 6.x specifications. For a detailed explanation of the database upgrade procedure, see Upgrading the Database from Corporate Portal 5.0.x to Foundation 6.0 Specifications.

To upgrade the database from Corporate Portal 5.0.x to Foundation 6.0 specifications:

  1. Upgrade database software.

    2. 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, verify that the new database character set is UTF8 and the new database national character set is AL16UTF16.
  2. Run the duplicate names database script.

    3. On Oracle databases, the following scripts may need to be run to fix duplicate portal document names:

  1. Run the database upgrade tool.

    2. On a Unix portal, the database upgrade tool is located at <PT_HOME>/ptportal/6.1/bin/dbupgradetool.sh. The tool is a command line utility and needs to be run twice. The first time it is run it collects parameters for the upgrade. The second time it is run it performs the upgrade.

    On a Windows portal, the database upgrade tool is located at <PT_HOME>\ptportal\6.1\bin\dbupgradetool.bat. If you have a .NET portal, a GUI upgrade utility will be launched. If you have a Java portal, a command line utility will be launched. The command line utility needs to be run twice. The first time it is run it collects parameters for the upgrade. The second time it is run it performs the upgrade.

    For details on using the database upgrade tool, see Running the Database Upgrade Tool.

  2. Export data from the database.

    3. Export the data from the portal schemas using tools provided by your database vendor.

  3. Create the new database schema.

    4. On Oracle databases:

    1. Drop and recreate the portal schema owner.
    2. Grant connect, resource, and dba rights on the portal tablespaces to the newly created portal schema owner.
    3. Run the create_tables_oracle.sql script. The script is located in <PT_HOME>/ptportal/6.1/sql, under the directory appropriate to your operating system and version of Oracle.

      4. On SQLServer databases:

    4. Create a new database. This database can be your new portal database, or it can serve as a temporary store for portal data.
    5. Script the new database with the portal schema. To do this, run <PT_HOME>/ptportal/6.1/sql/mssql/create_tables_mssql.sql
  4. Import data to the database.

    5. Using tools provided by your database vendor, import the data you exported in step 4 into the newly scripted database.

    Note: On SQLServer databases, the portal data will now be in a new database. You must now 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 step 5, and then exporting the data from the temporary database to the original database.
  5. Update stored procedures and system-specific parameters.

    6. Run the following two scripts against the portal database. The scripts are located in <PT_HOME>/ptportal/6.1/sql, under the directory appropriate to your operating system and database version.

    On Oracle, run:

    1. stored_procs_oracle.sql
    2. postinst_oracle.sql

      3. On SQLServer, run:

    3. stored_procs_mssql.sql
    4. postinst_mssql.sql

Resolving Missing Mandatory Portlets

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)

Rebuilding the Search Index

In portal administration’s Search Service Manager, schedule the next search repair to occur either in the past or in the very near future. Then, in the administrative folder that contains the search update agents that are registered with the Automation Service, schedule one of the search update agents to run in the past or in the very near future. 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.

Completing the AquaLogic Interaction Component Upgrade

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.


  Back to Top       Previous  Next