# Installation and Upgrade Guide

# Upgrade

This chapter includes information on how to upgrade Analytics. It includes the following sections:

- Upgrade Paths
- Upgrading Analytics from Version 1.2 to Analytics 2.0
- Upgrading Analytics from Version 1.1 to 2.0

## Upgrade Paths

The following table summarizes the supported database upgrade paths for Analytics.

Table 5-1 Upgrade Paths
Upgrade Path | Upgrade References
--- | ---
1.2 to 2.0 | Follow the procedures in this chapter.
1.1 to 2.0 | Follow the procedures in this chapter.

This section discusses:

- Upgrading Analytics from Version 1.2 to Analytics 2.0
- Upgrading Analytics from Version 1.1 to 2.0

## Upgrading Analytics from Version 1.2 to Analytics 2.0

This section describes how to upgrade from Analytics 1.2 to Analytics 2.0.

To upgrade from Analytics 1.2 to Analytics 2.0:

1. Ensure that the Plumtree Analytics service is not running.

- Windows: From the Windows Control Panel, click Administrative Tools | Services; if the Analytics service is running, right-click it and choose Stop.
- UNIX: Use the command <PT_HOME>/ptanalytics/1.2/bin/analyticsd.sh stop

2. Ensure that the Plumtree Analytics Collector service is not running.

- Windows: From the Windows Control Panel, click Administrative Tools | Services; if the Analytics Collector service is running, right-click it and choose Stop.
- UNIX: Use the command <PT_HOME>/ptanalytics/1.2/bin/collectord.sh stop

3. Delete the Analytics folder beneath the PT_HOME\common\container\tomcat\5.0.28\work directory.
4. Install Analytics Services. For details, see Installing Analytics Services. If you are choosing the same location as the existing software, accept the default installation directory location when prompted.

Note: | The script file sync.bat is deleted. The AnalyticsRunJobs.bat file is added, and is scheduled to run automatically as an Automation Service job.

5. Upgrade the Analytics database by running the upgrade_1.x_to_2.0.sql script:

<PT_HOME>\ptanalytics\2.0\sql\<database>\upgrade_1.x_to_2.0.sql

6. Run the portal_security_service_install.sql setup script on the portal database. The script is located in <PT_HOME>\ptanalytics\2.0\sql\mssql\ .
7. Reconfigure Analytics by running the Analytics Configurator. For details, see Configuring Analytics
8. Partition the Analytics database tables by running the following script:

- AnalyticsPartition.bat (Windows)
  <PT_HOME>\ptanalytics\2.0\bin\AnalyticsPartition.bat
- AnalyticsPartition.sh (UNIX)
  <PT_HOME>/ptanalytics/2.0/bin/AnalyticsPartition.sh

The partition.log file displays partitioning progress in real-time. This log is located in:

- C:\bea\alui\ptanalytics\2.0\logs (Windows)
- /opt/bea/alui/ptanalytics/2.0/logs (UNIX/Linux)

The following table describes the approximate lengths of time that it should take to partition the Analytics database:

Table 5-2 Analytics Database Partitioning Estimates - Analytics 1.2 to 2.0
Total Number of Facts | Time to Partition
--- | ---
10 million | 12.5 minutes
20 million | 25 minutes
50 million | 62.5 minutes
100 million | 2 hours 5 minutes
500 million | 10 hours 50 minutes

9. (Oracle only) Run your database's analyisis tool on both the Analytics and portal databases to increase the efficiency of the databases.
10. Install the Interaction component. For details, see Installing the Interaction Component
11. Install the Image Service component. For details, Installing the Image Service Component
12. Stop and restart the Analytics services. For details, see Starting Analytics and Portal Services.
13. Register the Analytics application, remote server, Web services, and portlets with the portal by importing the migration package. For details on performing this task on a 6.x portal, see Registering Analytics with the Portal. For details on importing the migration package on a 5.x portal, see Administrator Guide for Plumtree Corporate Portal.
14. Install the Automation Service component. For details, see Installing the Automation Service Component
15. Add Analytics jobs to the Automation Service. For details, see Adding Analytics Jobs to the Automation Service.

## Upgrading Analytics from Version 1.1 to 2.0

This section describes how to upgrade from Analytics 1.1 to Analytics 2.0.

To upgrade from Analytics 1.1 to Analytics 2.0:

1. Ensure that the Plumtree Analytics service is not running.

- Windows: From the Windows Control Panel, click Administrative Tools | Services; if the Analytics service is running, right-click it and choose Stop.
- UNIX: Use the command <PT_HOME>/ptanalytics/1.1/bin/analyticsd.sh stop

2. Ensure that the Plumtree Analytics Collector service is not running.

- Windows: From the Windows Control Panel, click Administrative Tools | Services; if the Analytics Collector service is running, right-click it and choose Stop.
- UNIX: Use the command <PT_HOME>/ptanalytics/1.1/bin/collectord.sh stop

3. Delete the Analytics folder beneath the PT_HOME\common\container\tomcat\5.0.28\work directory.
4. Install Analytics Services. For details, see Installing Analytics Services. If you are choosing the same location as the existing software, accept the default installation directory location when prompted.

Note: | The script file sync.bat is deleted. The AnalyticsRunJobs.bat file is added, and is scheduled to run automatically as an Automation Service job.

5. Upgrade the Analytics database by running the upgrade_1.x_to_2.0.sql script: <PT_HOME>\ptanalytics\2.0\sql\<database>\upgrade_1.x_to_2.0.sql
6. Run the portal_security_service_install.sql setup script on the portal database. The script is located in <PT_HOME>\ptanalytics\2.0\sql\mssql\
7. Reconfigure Analytics by running the Analytics Configurator. For details, see Configuring Analytics

Note: | When running the Analytics Configurator during the 1.1 to 2.0 upgrade, you must re-enter the API Service URL and the passwords for all databases.

8. Partition the Analytics database tables by running the following script:

- AnalyticsPartition.bat (Windows): <PT_HOME>\ptanalytics\2.0\bin\AnalyticsPartition.bat
- AnalyticsPartition.sh (UNIX):
  <PT_HOME>/ptanalytics/2.0/bin/AnalyticsPartition.sh

The collector.log file displays partitioning progress in real-time. This log is located in:
<PT_HOME>\ptanalytics\2.0\logs\collector.log

The following table describes the approximate lengths of time that it should take to partition the Analytics database:

Table 5-3 Analytics Database Partitioning Estimates - Analytics 1.1 to 2.0
Total Number of Facts | Time to Partition
--- | ---
10 million | 12.5 minutes
20 million | 25 minutes
50 million | 62.5 minutes
100 million | 2 hours 5 minutes
500 million | 10 hours 50 minutes

9. (Oracle only) Run your database's analyisis tool on both the Analytics and portal databases to increase the efficiency of the databases.
10. Install the Interaction component. For details, see Installing the Interaction Component

Note: | Upon upgrading to Analytics 2.0 the port used to send event metrics from the portal server(s) to the Analytics Services server is modified to 31314. Ensure that this port is open between the portal server(s) and the Analytics Services server. For a list of other ports used by Analytics, see Ports Required by Analytics.

11. Install the Image Service component. For details, Installing the Image Service Component
12. Stop and restart the Analytics services. For details, see Starting Analytics and Portal Services.
13. Register the Analytics application, remote server, Web services, and portlets with the portal by importing the migration package. For details on performing this task on a 6.x portal, see Registering Analytics with the Portal. For details on importing the migration package on a 5.x portal, see Administrator Guide for Plumtree Corporate Portal.
14. Install the Automation Service component. For details, see Installing the Automation Service Component
15. Add Analytics jobs to the Automation Service. For details, see Adding Analytics Jobs to the Automation Service.