# Installation and Upgrade Guide

# Quickstart Overview

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

This chapter is divided into two major sections:

- Installation. This section covers installing and configuring the Analytics components, creating and scripting the database, creating the ALUI Security database, and starting and verifying the installation. The organization of this section maps directly to detailed instructions in Chapter 4, “Installation”.
- Upgrade. This section covers upgrading version of Analytics to the latest version. The organization of this section maps directly to detailed instructions in Chapter 5, “Upgrade”.

## Installation

Before you install Analytics, ensure that you have completed pre-installation steps. For details, see Installation Prerequisites

### Installing the Analytics Console Component

This section describes how to install the Analytics console and the BEA AL Analytics service. For more complete details on performing this task, see Installing the Analytics Console Component.

To install the Analytics Console Component:

1. Log in to the remote server host computer as the local administrator (on Windows) or a user with directory write privileges (on UNIX or Linux).
2. Copy the installer to the disk location from where you plan to launch it.
3. Launch the Analytics Installer.

- Windows: ALAnalytics_ALI_v2-5_mp1.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5_mp1

4. Choose to install the Analytics Console component.
5. Complete all installation wizard pages according to the settings you planned when you completed the Analytics Console Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document

After the installer has copied all files to the installation directory, the Launch Configuration Manager installation wizard page appears.

6. Do not configure Analytics Console settings in Configuration Manager at this time. First, configure the Analytics and ALUI Security databases. For details see Configuring the Analytics Database and Configuring the ALUI Security Database.
7. After configuring the Analytics and ALUI Security databases, configure all settings for all of the Analytics Console application components using the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.

### Configuring the Analytics Database

Perform one of the following procedures that is appropriate to your database platform:

- Creating the Analytics Database on Microsoft SQL Server
- Creating the Analytics Database on Oracle

#### Creating the Analytics Database on Microsoft SQL Server

For more complete details on performing this task, see Creating the Analytics Database on Microsoft SQL Server.

To set up the Analytics database on Microsoft SQL Server:

1. On the machine to which you installed the Analytics Console component, copy the scripts from install_dir\ptanalytics\2.5\sql\mssql to the database host computer.
2. In SQL Server Management Studio, access the database engine’s properties.
3. Configure the database engine to use SQL Server and Windows Authentication mode.
4. Restart the database engine.
5. Create the Analytics database user:

1. Create the Analytics database user with the user name you provisioned when you completed the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
2. Configure the Analytics database user to use SQL Server Authentication.
3. Set the Analytics database user password to the password you designated when you completed the Analytics Installation and Configuration Worksheets document.

6. Create the Analytics database with the following properties:

- Create a database with the name you provisioned when you completed the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
- Configure the size of the database.
- Change the default database for the Analytics database user to the Analytics database.

7. Grant the Analytics database user the db_owner role for the Analytics database.
8. Create the Analytics database schema. Specify the Analytics database user as the schema owner.
9. Connect to the Analytics database as the Analytics database user, using SQL Server Authentication.
10. Run the setup scripts for the database, located in the install_dir\ptanalytics\2.5\sql\mssql\ folder, in the following order (make sure that you are running the scripts on the Analytics database):

1. create_analytics_schema.sql
2. install_analytics_data.sql

#### Creating the Analytics Database on Oracle

For more complete details on performing this task, see Creating the Analytics Database on Oracle.

To create and set up an Oracle database:

1. On the machine to which you installed the Analytics Console component, copy the oracle directory from install_dir\ptanalytics\2.5\sql to the Analytics database’s host computer.
2. Log on to the host computer for the Analytics database as owner of the Oracle system files.
3. Execute the following steps as the system user in your Oracle database.

1. Determine the name of the SID that you will be using for this installation. If you changed the SID from the default when you installed the portal, you need to update create_analytics_tablespaces.sql to reflect the SID that you used, substituting all occurrences of the default SID name with your SID name. The default SID name is BEAS.

If you are creating a new SID, configure AL32UTF8 as the database character set and AL16UTF16 as the national character set.

2. Run the script create_analytics_tablespaces.sql for your platform.
3. Run the script create_analytics_user.sql.

Note: | If you do not want the script to use the defaults when creating the Oracle database user and password, edit the script. The default user is analyticsdbuser; the default password is analyticsdbuser.

4. Add the Oracle database user and password values into the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document (you will enter these values into Configuration Manager when configuring Analytics database settings).

4. Execute the following steps as the analytics user that you just created.

1. Run the script create_analytics_schema.sql.
2. Run the script install_analytics_data.sql.

5. Run your database’s analysis tool on the portal database to the efficiency of the database.

### Configuring the ALUI Security Database

(Optional) This section describes how to set up the ALUI Security database.

Note: | You do not need to perform this procedure if Pathways 1.5 is installed. Installing Pathways 1.5 requires creating the ALUI Security database.

This section contains the following sections:

- Creating the ALUI Security Database on Microsoft SQL Server
- Creating the ALUI Security Database on Oracle

#### Creating the ALUI Security Database on Microsoft SQL Server

(Optional) For more complete details on performing this task, see Creating the ALUI Security Database on Microsoft SQL Server.

Note: | You do not need to perform this procedure if Pathways 1.5 is installed. Installing Pathways 1.5 requires creating the ALUI Security database.

To create and set up the ALUI Security database on Microsoft SQL Server:

1. On the machine to which you installed the Analytics Console component, copy the scripts from install_dir\ptanalytics\2.5\sql\mssql to the ALUI Security database host computer.
2. In SQL Server Management Studio, access the database engine’s properties.
3. Configure the database engine to use SQL Server and Windows Authentication mode.
4. Restart the database engine.
5. Create the ALUI Security database user:

1. Create the ALUI Security database user with the user name you provisioned when you completed the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
2. Configure the ALUI Security database user to use SQL Server Authentication.
3. Set the ALUI Security database user password to the password you designated when you completed the Analytics Installation and Configuration Worksheets document.

6. Create the ALUI Security database with the name you provisioned when you completed the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
7. Change the default database for the ALUI Security database user to the ALUI Security database.
8. Grant the ALUI Security database user the db_owner role for the ALUI Security database.
9. Create the ALUI Security database schema. Specify the ALUI Security database user as the schema owner.
10. Connect to the ALUI Security database as the ALUI Security database user, using SQL Server Authentication.
11. Run the create_security_tables.sql script, located in the folder that you copied in Step 1.

#### Creating the ALUI Security Database on Oracle

(Optional) For more complete details on performing this task, see Creating the ALUI Security Database on Oracle.

Note: | You do not need to perform this procedure if Pathways 1.5 is installed. Installing Pathways 1.5 requires creating the ALUI Security database.

To create and set up the ALUI Security database on Oracle:

1. On the machine to which you installed the Analytics Console component, copy the oracle directory from install_dir\ptanalytics\2.5\sql to the ALUI Security database’s host computer.
2. Log on to the host computer for the ALUI Security database as owner of the Oracle system files.
3. Create the ALUI Security database tablespace.
4. Create the ALUI Security database user.
5. Add the ALUI Security database user and password values into the Configuration Worksheet, which is included in the Analytics Installation and Configuration Worksheets document (you will enter these values into Configuration Manager when configuring Analytics database settings).
6. Connect to the ALUI Security database as the ALUI Security database user.
7. Run the create_security_tables.sql script, located in the folder that you copied in Step 1.
8. Run your database’s analysis tool on the ALUI Security database to the efficiency of the database.

### Registering Portal Events

You must register portal events if you want Analytics to report on events that occur in the portal. To register portal events, run the following from the command line on the Analytics host machine:

- Windows:

- .. PTANALYTICS_HOME\bin\AnalyticsLoadEvents.bat
  ..\settings\config\analytics-core-event-def.xml
- .. PTANALYTICS_HOME\bin\AnalyticsLoadEvents.bat
  ..\settings\config\analytics-ali-event-def.xml

- UNIX/Linux:

- .. PTANALYTICS_HOME/bin/AnalyticsLoadEvents.sh
  ../settings/config/analytics-core-event-def.xml
- .. PTANALYTICS_HOME/bin/AnalyticsLoadEvents.sh
  ../settings/config/analytics-ali-event-def.xml

### Registering Collaboration Events

To register Collaboration events, perform the following:

1. Navigate to the following file on the Collaboration host machine: install_dir\ptcollab\4.5\settings\config\analytics-collab-event-def.xml
2. Copy the analytics-collab-event-def.xml file on the Collaboration host machine to the following location on the Analytics host machine:

install_dir\ptanalytics\2.5\settings\config\

3. Run the following from the command line on the Analytics host machine:

- .. PTANALYTICS_HOME\bin\AnalyticsLoadEvents.bat
  ..\settings\config\analytics-collab-event-def.xml (Windows)
- .. PTANALYTICS_HOME/bin/AnalyticsLoadEvents.sh
  ../settings/config/analytics-collab-event-def.xml (UNIX/Linux)

### Registering Ensemble Events

(AquaLogic Ensemble integration only) To register Ensemble events, run the following from the command line on the Analytics host machine:

- .. PTANALYTICS_HOME\bin\AnalyticsLoadEvents.bat
  ..\settings\config\analytics-ensemble-event-def.xml (Windows)
- .. PTANALYTICS_HOME/bin/AnalyticsLoadEvents.sh
  ../settings/config/analytics-ensemble-event-def.xml (UNIX/Linux)

### Installing the Analytics Collector Component and Clustering the BEA AL Analytics Collector Service

This section includes the following topics:

- Installing the Analytics Collector Component
- Clustering the BEA AL Analytics Collector Service

#### Installing the Analytics Collector Component

This section describes how to install the Analytics Collector component, which includes the BEA AL Analytics Collector service. For more complete details on performing this task, see Installing the Analytics Collector Component.

Note: | If you want to cluster the BEA AL Analytics Collector service, we recommend that you install each node in the cluster on a separate machine (one installation of the Analytics Collector component is one instance of the BEA AL Analytics Collector service). One instance of the BEA AL Analytics Collector service operates as one node in the cluster).

To install the Analytics Collector component:

1. Log in to the remote server host computer as the local administrator (on Windows) or a user with directory write privileges (on UNIX or Linux).
2. Copy the installer to the disk location from where you plan to launch it.
3. Launch the Analytics Installer.

- Windows: ALAnalytics_ALI_v2-5_mp1.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5_mp1

4. Choose to install the Analytics Collector component.
5. Complete all installation wizard pages according to the settings you planned when you completed the Analytics Collector Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
6. After the installer has copied all files to the installation directory, the Launch Configuration Manager installation wizard page appears.
7. In Configuration Manager, configure all settings for all of the Analytics Collector application components using the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.

#### Clustering the BEA AL Analytics Collector Service

(Optional) A BEA AL Analytics Collector service cluster consists of multiple BEA AL Analytics Collector service nodes running simultaneously and working together to provide increased scalability and reliability. One instance of the BEA AL Analytics Collector service operates as one node in the cluster.

Note: | You do not need to perform these steps if you do not want to cluster the BEA AL Analytics Collector service.

For more complete details on performing this task, see Clustering the BEA AL Analytics Collector Service.

To cluster the BEA AL Analytics Collector service:

1. Configure AquaLogic Interaction to send events to the BEA AL Analytics Collector service cluster. For details, see Configuring AquaLogic Interaction to Send Events to the Cluster.
2. Configure the nodes in the BEA AL Analytics Collector service cluster. For details, see Configuring Nodes in a Cluster.

##### Configuring AquaLogic Interaction to Send Events to the Cluster

To configure AquaLogic Interaction to send events to the BEA AL Analytics Collector service cluster:

1. Access Configuration Manager on the machine on which AquaLogic Interaction is installed.
2. Configure the following settings in the Analytics Communication component:

- Confirm that the Enabled check box is selected in the Enable area.
- Click Enabled in the Use Clustering area.
- Configure the following settings in the Cluster Communication area: Cluster name, Cluster node timeout period, Broadcast listening port.

Online help for these settings is available in the Configuration Manager application.

##### Configuring Nodes in a Cluster

This section discusses how to configure nodes in a BEA AL Analytics Collector service cluster.

If you are configuring nodes of the BEA AL Analytics Collector service to use broadcast mode, IP broadcast packets are not automatically forwarded from one subnet to another. For this reason, you should configure each instance of the BEA AL Analytics Collector service to be in the same subnet as the application from which it receives events. This configuration ensures that the event-generating applications can successfully receive broadcast messages from the Collector service cluster. If you use virtualization software, we recommend that you configure nodes of the BEA AL Analytics Collector service to use broadcast mode.

Note: | Perform this procedure for each node in the cluster.

To configure a node in a BEA AL Analytics Collector service cluster:

1. Ensure that you have installed the Analytics Collector component on each machine that will host a node in the cluster.

Note: | We recommend that each instance of the BEA AL Analytics Collector service exist on a separate machine.

For installation instructions, see Installing the Analytics Collector Component.

2. Access Configuration Manager on the BEA AL Analytics Collector service host.
3. Click the + symbol next to the Analytics Collector application name to view its components.
4. Configure the settings in the Analytics Database component.
5. Configure the settings in the Clustering component.

Note: | The value for the Cluster name field should match the value set for the Cluster name field in the Portal Service application, Analytics Communication component of Configuration Manager on the portal host. You configured this setting when you performed the procedure Configuring AquaLogic Interaction to Send Events to the Cluster.

6. Configure the settings in the Logging component.

Online help for these settings is available in the Configuration Manager application.

### Installing the Interaction Analytics Component

The Interaction Analytics component facilitates communication between Analytics and the portal. For more complete details on performing this task, see Installing the Interaction Analytics Component.

Note: | You must reinstall the Interaction Analytics component after each time you upgrade AquaLogic Interaction.

To install the Interaction Analytics component:

1. Log in to the portal host computer as the same user that installed AquaLogic Interaction.
2. If you are running on Java, shut down the application server.
3. Copy the installer to the disk location from where you plan to launch it. The installer file is one of the following:

- Windows: ALAnalytics_ALI_v2-5_mp1.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5_mp1

4. Choose to install the Interaction Analytics Component.
5. Complete all installation wizard pages according to the settings you planned when you completed the Interaction Analytics Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
6. After the installer has copied all files to the installation directory, the Launch Configuration Manager installation wizard page appears.
7. In Configuration Manager, configure all settings for all of the Analytics Communication application components using the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.
8. After the installation is complete, perform one of the following:

- If you are running on Java, restart the application server. Then redeploy your portal.war or portal.ear file to your portal application server.
- If you are running on IIS, restart the application server. For instructions, see your application server’s documentation.

### Installing the Image Service Component

For more complete details on performing this task, see Installing the Image Service Component.

To install the Image Service component:

1. Log in to the Image Service host computer as the local administrator or the ALI user created during installation of AquaLogic Interaction.
2. Copy the installer to the disk location from where you plan to launch it.
3. Launch the Analytics Installer.

- Windows: ALAnalytics_ALI_v2-5_mp1.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5_mp1

4. Choose to install the Image Service Component.

### Installing the Analytics Automation Jobs Component

For more complete details on performing this task, see Installing the Analytics Automation Jobs Component

To install the Analytics Automation Jobs component:

1. Log in to the Automation Service host computer as the local administrator or the ALI user created during the installation of AquaLogic Interaction.
2. Copy the installer to the disk location from where you plan to launch it.
3. Launch the Analytics Installer.

- Windows: ALAnalytics_ALI_v2-5_mp1.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5_mp1

Note: | Ensure that you copy the installer for the same platform that the Automation Service runs on. For example, if the Automation Service runs on Solaris, copy the Solaris installer.

4. Choose to install the Analytics Automation Jobs component.
5. Complete all installation wizard pages according to the settings you planned when you completed the Analytics Automation Jobs Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
6. After the installer has copied all files to the installation directory, the Launch Configuration Manager installation wizard page appears.
7. In Configuration Manager, configure all settings for all of the Analytics Jobs application components using the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.

### Starting Analytics and Analytics Collector Services

For more complete details on performing this task, see Starting Analytics and Analytics Collector Services.

To start the Analytics and Analytics Collector services, perform one of the following:

- On Windows, ensure the BEA AL Analytics service has been started in Windows NT Services. Then ensure the BEA AL Analytics Collector service has been started.
- On UNIX and Linux, ensure the BEA AL Analytics service has been started by using the following command:

install_dir/ptanalytics/2.5/bin/analyticsd.sh start

Then ensure the BEA AL Analytics Collector service has been started by using the following comment:

install_dir/ptanalytics/2.5/bin/collectord.sh start

You can also start and stop these services using Configuration Manager. Log in to Configuration Manager using the user name Administrator and the password you specified during installation. Follow the instructions in Configuration Manager to start the Analytics Console and Analytics Collector applications.

### Registering Analytics with the Portal

This section describes how to register the Analytics Console, remote server, web service, and portlet objects. For more complete details on performing this task, see Registering Analytics with the Portal.

To register the Analytics application, remote server, web services, and portlets with the portal, use the migration utility to import the migration package analytics.pte.

### Adding Analytics Jobs to the Automation Service

This section describes how to add all Analytics jobs to the Automation Service. Once Analytics jobs are added to the Automation Service, the Automation Service runs them automatically. For more complete details on performing this task, see Adding Analytics Jobs to the Automation Service.

To add Analytics jobs to the Automation Service:

1. Log into the portal as a user with administrative privileges.
2. In Administration, choose Automation Service.
3. Ensure that the Automation Service is online.
4. Under Edit Automation Services, click the name of the computer on which the Analytics Jobs component is installed.

The Register Folders window appears.

5. Click Add Folder.

The Add Job Folder window appears.

6. Expand the Analytics folder.
7. Select the Analytics Jobs folder.
8. Click OK to close the Register Folders window.
9. Click Finish.

The Automation Service runs the Analytics jobs. If other Automation Service jobs were in queue or running when you added the Analytics jobs to the Automation Service, the Automation Service runs the Analytics jobs after these other jobs have completed.

10. At an appropriate time, ensure that the Analytics jobs have completed successfully. If any Analytics jobs failed, schedule these jobs to run again.

## Upgrade

### Upgrade Paths

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

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

Note: | We do not support upgrades from Analytics 1.x to 2.5 MP1. 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 MP1.

### Upgrading Analytics

This section discusses:

- Upgrading Analytics from Version 2.1 to 2.5 MP1
- Upgrading Analytics from Version 2.0 to 2.5 MP1

#### Upgrading Analytics from Version 2.1 to 2.5 MP1

This section describes how to upgrade from Analytics 2.1 to Analytics 2.5 MP1. For more complete details on performing this task, see Upgrading Analytics from Version 2.1 to Analytics 2.5 MP1.

To upgrade from Analytics 2.1 to Analytics 2.5 MP1:

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.
3. Install the Analytics Console component. For details, see Installing the Analytics Console Component.

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

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 and configure Analytics Collector settings in Configuration Manager. For details, see Installing the Analytics Collector Component.
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:

install_dir\ptanalytics\2.5\sql\database\upgrade_2.1_to_2.5.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, use Configuration Manager to configure all settings for all Analytics Console application components.
14. (Oracle only) Run your database’s analysis 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 portal 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 either Pathways 1.5 or the Remote Portlets component of AquaLogic Interaction 6.5 is installed. Performing a clean (non-upgrade) install of Pathways 1.5 or installing the Remote Portlets component requires creating the ALUI Security database. Additionally, 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 .

#### Upgrading Analytics from Version 2.0 to 2.5 MP1

To upgrade from Analytics 2.0 to Analytics 2.5 MP1:

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 Analytics Services, using the tool of your choice.
3. Install the Analytics Console component. For details, see Installing the Analytics Console Component.

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

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 and configure Analytics Collector settings in Configuration Manager. For details, see Installing the Analytics Collector Component.
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, configure all Analytics Console settings in Configuration Manager.
15. (Oracle only) Run your database’s analysis 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 portal 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 either Pathways 1.5 or the Remote Portlets component of AquaLogic Interaction 6.5 is installed. Performing a clean (non-upgrade) install of Pathways 1.5 or installing the Remote Portlets component requires creating the ALUI Security database. Additionally, 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 .