# 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 2.1 to Analytics 2.5
- Upgrading Analytics from Version 2.0 to Analytics 2.5

## Upgrade Paths

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

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

Note: | We do not support upgrades from Analytics 1.x to 2.5. To do so, you must first upgrade Analytics 1.0/1.1 to either 2.0 or 2.1, then perform the appropriate upgrade to Analytics 2.5.

## Upgrading Analytics from Version 2.1 to Analytics 2.5

To upgrade from Analytics 2.1 to Analytics 2.5:

1. Delete the Analytics folder beneath the install_dir\common\container\tomcat\5.0.28\work directory.
2. Back up the installation directory of the previously-installed version of the Analytics Services component, using the tool of your choice.

Note: | In Analytics 2.1, the Analytics Services component installation consisted of the BEA AL Analytics service, the core Analytics application files, and the BEA AL Analytics Collector service. The default installation directory for Analytics Services was install_dir\ptanalytics (Windows) and install_dir/ptanalytics (UNIX and Linux).

Note: | In Analytics 2.5, installing the Analytics Console component installs only the BEA AL Analytics service and the core Analytics application files. Installing the Analytics Collector component installs only the BEA AL Analytics Collector service.

3. Install the Analytics Console component. For details, see Installing the Analytics Console Component.

If you are choosing the same location as the existing software, accept the default installation directory location when prompted.

Note: | At this time, do not use Configuration Manager to configure Analytics Console settings.

Note: | If you are upgrading to Analytics 2.5, you must choose Overwrite License. The installer replaces your Analytics 2.1 Production license with an Analytics 2.5 Evaluation license. Next, you must replace the Analytics 2.5 Evaluation license with an Analytics 2.5 Production license. You can obtain product licenses through elicense.bea.com or licensing@bea.com.

4. Configure the Analytics database. For details, see Configuring the Analytics Database.
5. Register portal events. For details, see Registering Portal Events.
6. Register Collaboration events. For details, see Registering Collaboration Events.
7. (AquaLogic Ensemble integration only) Register Ensemble events. For details, see Registering Ensemble Events.
8. Install the Analytics Collector component and configure Analytics Collector settings in Configuration Manager. For details, see Installing the Analytics Collector Component.

Note: | If you are upgrading to Analytics 2.5, you must choose Overwrite License. The installer replaces your Analytics 2.1 Production license with an Analytics 2.5 Evaluation license. Next, you must replace the Analytics 2.5 Evaluation license with an Analytics 2.5 Production license. You can obtain product licenses through elicense.bea.com or licensing@bea.com.

9. (Optional) If desired, cluster the BEA AL Analytics Collector service. For details, see Clustering the BEA AL Analytics Collector Service.
10. Back up the Analytics database using the tool of your choice.
11. Upgrade the Analytics database by running the upgrade_2.1_to_2.5.sql script:

- Windows: install_dir\ptanalytics\2.5\sql\database\upgrade_2.1_to_2.5.sql
- UNIX/Linux: install_dir/ptanalytics/2.5/sql\database/upgrade_2.0_to_2.1.sql

12. Run the Analytics25Update.bat file:

- Windows: install_dir\ptanalytics\2.5\bin\Analytics25Update.bat
- UNIX/Linux: install_dir/ptanalytics/2.5/bin/Analytics25Update.sh

13. On the machine on which you installed the Analytics Console component:

1. Access Configuration Manager.
2. Click the + symbol next to the Analytics Console application name to view its components.
3. Configure all Analytics Console settings.

14. (Oracle only) Run your database’s analyisis tool on both the Analytics and portal databases to increase the efficiency of the databases.
15. Back up the installation directory of the previously-installed version of the Interaction Analytics component, using the tool of your choice.
16. Install the Interaction Analytics component and configure Analytics Communication settings in Configuration Manager. For details, see Installing the Interaction Analytics Component
17. Install the Image Service component. For details, Installing the Image Service Component
18. Stop and restart Analytics and Analytics Collector services. For details, see Starting Analytics and Analytics Collector Services.
19. Install the Analytics Automation Jobs component and configure Analytics Jobs settings in Configuration Manager. For details, see Installing the Analytics Automation Jobs Component
20. Add Analytics jobs to the Automation Service. For details, see Adding Analytics Jobs to the Automation Service.
21. (Optional) Create and set up the ALUI Security database and migrate data from the portal database’s security tables to the ALUI Security database.

Note: | You do not need to perform these steps if Pathways 1.5 is installed. Performing a clean (non-upgrade) install of Pathways 1.5 requires creating the ALUI Security database. Upgrading from Pathways 1.0 to Pathways 1.5 requires creating the ALUI Security database and migrating data from the portal database’s security tables to the ALUI Security database.

1. Create and set up the ALUI Security database. For details, see Configuring the ALUI Security Database.
2. On the machine on which the previous version of the BEA AL Analytics service is installed, run the security-upgradetool.bat or security-upgradetool.sh file, located in install_dir\ptanalytics\2.5\bin .

Performing this step migrates data from the portal database’s security tables to the ALUI Security database.

## Upgrading Analytics from Version 2.0 to Analytics 2.5

To upgrade from Analytics 2.0 to Analytics 2.5.

1. Delete the Analytics folder beneath the install_dir\common\container\tomcat\5.0.28\work directory.
2. Back up the installation directory of the previously-installed version of the Analytics Services component, using the tool of your choice.

Note: | In Analytics 2.0, the Analytics Services component installation consisted of the BEA AL Analytics service, the core Analytics application files, and the BEA AL Analytics Collector service. The default installation directory for Analytics Services was install_dir\ptanalytics (Windows) and install_dir/ptanalytics (UNIX and Linux).

Note: | In Analytics 2.5, installing the Analytics Console component installs only the BEA AL Analytics service and the core Analytics application files. Installing the Analytics Collector component installs only the BEA AL Analytics Collector service.

3. Install the Analytics Console component. For details, see Installing the Analytics Console Component.

If you are choosing the same location as the existing software, accept the default installation directory location when prompted.

Note: | At this time, do not use Configuration Manager to configure Analytics Console settings.

Note: | The installer adds an Analytics 2.5 Evaluation license. You must replace the Analytics 2.5 Evaluation license with an Analytics 2.5 Production license. You can obtain product licenses through elicense.bea.com or licensing@bea.com.

4. Configure the Analytics database. For details, see Configuring the Analytics Database.
5. Register portal events. For details, see Registering Portal Events.
6. Register Collaboration events. For details, see Registering Collaboration Events.
7. (AquaLogic Ensemble integration only) Register Ensemble events. For details, see Registering Ensemble Events.
8. Install the Analytics Collector component and configure Analytics Collector settings in Configuration Manager. For details, see Installing the Analytics Collector Component.

Note: | If you are upgrading to Analytics 2.5, you must choose Overwrite License. The installer replaces your Analytics 2.0 Production license with an Analytics 2.5 Evaluation license. Next, you must replace the Analytics 2.5 Evaluation license with an Analytics 2.5 Production license. You can obtain product licenses through elicense.bea.com or licensing@bea.com.

9. (Optional) If desired, cluster the BEA AL Analytics Collector service. For details, see Clustering the BEA AL Analytics Collector Service.
10. Back up the Analytics database using the tool of your choice.
11. Upgrade the Analytics database by running the upgrade_2.0_to_2.1.sql script:

- Windows: install_dir\ptanalytics\2.5\sql\database\upgrade_2.0_to_2.1.sql
- UNIX/Linux: install_dir/ptanalytics/2.5/sql\database/upgrade_2.0_to_2.1.sql

12. Upgrade the Analytics database by running the upgrade_2.1_to_2.5.sql script:

- Windows: install_dir\ptanalytics\2.5\sql\database\upgrade_2.1_to_2.5.sql
- UNIX/Linux: install_dir/ptanalytics/2.5/sql\database/upgrade_2.0_to_2.1.sql

13. Run the Analytics25Update.bat file:

- Windows: install_dir\ptanalytics\2.5\bin\Analytics25Update.bat
- UNIX/Linux: install_dir/ptanalytics/2.5/bin/Analytics25Update.sh

14. On the machine on which you installed the Analytics Console component:

1. Access Configuration Manager.
2. Click the + symbol next to the Analytics Console application name to view its components.
3. Configure all Analytics Console settings in Configuration Manager.

15. (Oracle only) Run your database’s analyisis tool on both the Analytics and portal databases to increase the efficiency of the databases.
16. Back up the installation directory of the previously-installed version of the Interaction Analytics component, using the tool of your choice.
17. Install the Interaction Analytics component and configure Analytics Communication settings in Configuration Manager. For details, see Installing the Interaction Analytics Component
18. Install the Image Service component. For details, Installing the Image Service Component
19. Stop and restart Analytics and Analytics Collector services. For details, see Starting Analytics and Analytics Collector Services.
20. Register the Analytics application, remote server, Web services, and portlets with the portal by importing the migration package. For details, see Registering Analytics with the Portal.
21. Install the Analytics Automation Jobs component and configure Analytics Jobs settings in Configuration Manager. For details, see Installing the Analytics Automation Jobs Component
22. Add Analytics jobs to the Automation Service. For details, see Adding Analytics Jobs to the Automation Service.
23. (Optional) Create and set up the ALUI Security database and migrate data from the portal database’s security tables to the ALUI Security database.

Note: | You do not need to perform these steps if Pathways 1.5 is installed. Performing a clean (non-upgrade) install of Pathways 1.5 requires creating the ALUI Security database. Upgrading from Pathways 1.0 to Pathways 1.5 requires creating the ALUI Security database and migrating data from the portal database’s security tables to the ALUI Security database.

1. Create and set up the ALUI Security database. For details, see Configuring the ALUI Security Database.
2. On the machine on which the previous version of the BEA AL Analytics service is installed, run the security-upgrade.bat or security-upgrade.sh file, located in install_dir\ptanalytics\2.5\bin .

Performing this step migrates data from the portal database’s security tables to the ALUI Security database.