# Installation and Upgrade Guide

# Installation

This chapter describes the steps you take to install Analytics and its components:

1. Ensure you have completed pre-installation steps. For details, see Installation Prerequisites
2. Install the Analytics Console component on the remote server host computer. For details, see Installing the Analytics Console Component.
3. Configure the Analytics database. For details, see Configuring the Analytics Database.
4. Configure the ALUI Security database. For details, see Configuring the ALUI Security 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 cluster the BEA AL Analytics Collector service. For details, see Installing the Analytics Collector Component and Clustering the BEA AL Analytics Collector Service.

Note: | Installing the Analytics Collector component is required. However, clustering the BEA AL Analytics Collector service is optional.

9. Install the Interaction Analytics component on all portal servers. For details, see Installing the Interaction Analytics Component.
10. Install the Image Service component on your Image Service host. For details, see Installing the Image Service Component.
11. Install the Analytics Automation Jobs component on your Automation Service host. For details, see Installing the Analytics Automation Jobs Component.
12. Start Analytics and portal services. For details, see Starting Analytics and Analytics Collector Services.
13. Register the Analytics application, remote server, web services, and portlets with the portal. For details, see Registering Analytics with the Portal.
14. Add Analytics jobs to the Automation Service. For details, see Adding Analytics Jobs to the Automation Service.

## Installing the Analytics Console Component

This section describes how to install the Analytics Console component, which includes the Analytics user interface and the BEA AL Analytics service. The instructions are the same for installing on a Windows, UNIX, or Linux host, with slight exceptions as noted. 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. The installer file is one of the following:

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

3. Close all unnecessary applications.
4. Execute the installer file.
5. Complete the installation wizard pages as described in the following table and according to the settings you planned when you completed the Analytics Service Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.

   Table 4-1 Installation Wizard Pages - Analytics Console Component
   Wizard Page | Description
   --- | ---
   License Agreement | Read and accept the license agreement.
   Choose Components | Choose Analytics Console.
   Analytics Console - Installation Directory | The default is: install_dir\ptanalytics (Windows) install_dir/ptanalytics (UNIX and Linux)
   Note: | By default, install_dir is C:\bea\alui (Windows) and /opt/bea/alui (UNIX/Linux)
   Configuration Manager - Update | This page is displayed if an existing installation of Configuration Manager 2.0 is detected. Select if you want to update the password or port information for Configuration Manager or use the existing settings.
   Configuration Manager - Port and Password | This page is displayed if you chose to update Configuration Manager’s password and port information or if you are installing Configuration Manager for the first time. Type the port number on which you want Configuration Manager to service requests. By default, the port number is 12345. After running the installer, you will be able to access Configuration Manager by using the following URL: https://localhost:port_number. Also type and confirm the Administrator password that you will use to log into Configuration Manager. The password is case-sensitive. In Windows, the Configuration Manager runs as the BEA AL Configuration Manager(port_number) service.
   License Directory | Specify the path to the location where you want to store the evaluation version of the license.bea file. This location must be in BEA_HOME. The default location of BEA_HOME is: C:\bea (Windows) /opt/bea (UNIX/Linux)
   Note: | When Analytics is installed with an evaluation version of the license.bea file, all user-level events are reported as performed by only the Administrator user. Analytics must be installed with a Production version of the license.bea file for user-level events to be reported on all individual users.
   Existing License Update | This page is displayed if you have an existing license. Perform one of the following: Select Merge License to merge an Evaluation license with the existing license. Select Overwrite License to overwrite the existing license with an Evaluation license. The installer will place a backup of the existing license in BEA_HOME.
   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.
   Select Leave Alone to leave the existing license. If you already have a production license for Analytics, choose Leave Alone.
   Note: | When Analytics is installed with an evaluation version of the license.bea file, all user-level events are reported as performed by only the Administrator user. Analytics must be installed with a Production version of the license.bea file for user-level events to be reported on all individual users.
   For more complete details on license types and combining license keys, see Licensing.
   Pre-Installation Summary | Click Install to begin the installation. The installer copies the BEA AL Analytics service and core application files to the installation directory.
   Note: | The installer writes a log file to the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.
   Launch Configuration Manager | This installation wizard page lets you access Configuration Manager to configure settings for the core Analytics application. It is important that you perform these steps in the following order: Before launching Configuration Manager, you must configure the Analytics and ALUI Security databases, described in: Configuring the Analytics Database. Configuring the ALUI Security Database. Click the link on this installation wizard page to access Configuration Manager. The default username for logging into Configuration Manager is administrator. Use the password that you typed into the Configuration Manager - Port and Password installation wizard page. In Configuration Manager, click the + symbol next to the Analytics Console application name to view its components. Configure all settings for all of the Analytics Console components using the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document. Online Help for these settings is available in the Configuration Manager application.
   Note: | We recommend that you sync the clocks on the servers that run Analytics and the portal before proceeding with configuration. If the clocks are not aligned, some events and sync jobs behave incorrectly.
   (Optional) Click LOGOUT in Configuration Manager.
   Application Settings Confirmation | Select Yes if you have completed configuration of the Analytics settings. Select No, configure later to complete the installer without configuring the Analytics settings. You must run the Configuration Manager and configure Analytics settings before starting Analytics.
   Install Complete | Click Done to complete the Analytics Console component installation.

## Configuring the Analytics Database

This section describes how to set up the Analytics database. It contains the following sections:

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

### Creating the Analytics Database on Microsoft SQL Server

To create and 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 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. The growth of the database is directly correlated to the number of events present in the system. Events include such things as page views, portlet views, user logins, and discussion posts. Estimate 100 MB of growth per 1 million events. For example, if your portal receives roughly 1 million events per day, you should anticipate growth of 36.5 GB per year.
- 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

To create and set up the Analytics 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 Analytics database’s host computer. This folder contains the scripts that you will use to set up and configure the Analytics Oracle database.
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. This file is located in a platform specific subdirectory within the oracle directory that you copied in Step 1.
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. The create_analytics_user.sql script is located in the oracle directory that you copied in Step 1.

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. This script creates all of the tables and indexes that are necessary to run Analytics. The create_analytics_schema.sql script is located in the oracle directory that you copied in Step 1.
2. Run the script install_analytics_data.sql. This script adds all of the initial seed data that are necessary to run the Analytics product. The install_analytics_data.sql script is located in the oracle directory that you copied in Step 1.

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) This section describes how to set up 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.

This folder contains the script that you will use to configure the ALUI Security database.

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) This section describes how to set up 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.

This folder contains the script that you will use to configure the ALUI Security database.

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. The instructions are the same for installing on a Windows, UNIX, or Linux host, with slight exceptions as noted.

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). For details on clustering the BEA AL Analytics Collector service, see Clustering the BEA AL Analytics Collector Service.

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. The installer file is one of the following:

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

3. Close all unnecessary applications.
4. Execute the installer file.
5. Complete the installation wizard pages as described in the following table and 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.

   Table 4-2 Installation Wizard Pages - Analytics Collector Component
   Wizard Page | Description
   --- | ---
   License Agreement | Read and accept the license agreement.
   Choose Components | Choose Analytics Collector.
   Analytics Collector - Installation Directory | The default is: install_dir\ptcollector (Windows) install_dir/ptcollector (UNIX and Linux)
   Note: | By default, install_dir is C:\bea\alui (Windows) and /opt/bea/alui (UNIX/Linux)
   Configuration Manager - Update | This page is displayed if an existing installation of Configuration Manager 2.0 is detected. Select if you want to update the password or port information for Configuration Manager or use the existing settings.
   Configuration Manager - Port and Password | This page is displayed if you chose to update Configuration Manager’s password and port information. Type the port number on which you want Configuration Manager to service requests. By default, the port number is 12345. After running the installer, you will be able to access Configuration Manager by using the following URL: https://localhost:port_number. Also type and confirm the Administrator password that you will use to log into Configuration Manager. The password is case-sensitive.
   License Directory | Specify the path to the location where you want to store the evaluation version of the license.bea file. This location must be in BEA_HOME. The default location of BEA_HOME is: C:\bea (Windows) /opt/bea (UNIX/Linux)
   Note: | When Analytics is installed with an evaluation version of the license.bea file, all user-level events are reported as performed by only the Administrator user. Analytics must be installed with a Production version of the license.bea file for user-level events to be reported on all individual users.
   Existing License Update | This page is displayed if you have an existing license. Perform one of the following: Select Merge License to merge an Evaluation license with the existing license. Select Overwrite License to overwrite the existing license with an Evaluation license. The installer will place a backup of the existing license in BEA_HOME.
   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.
   Select Leave Alone to leave the existing license. If you already have a production license for Analytics, choose Leave Alone.
   Note: | When Analytics is installed with an evaluation version of the license.bea file, all user-level events are reported as performed by only the Administrator user. Analytics must be installed with a Production version of the license.bea file for user-level events to be reported on all individual users.
   For more complete details on license types and combining license keys, see Licensing.
   Pre-Installation Summary | Click Install to begin the installation. The installer copies BEA AL Analytics Collector service files to the installation directory.
   Note: | The installer writes a log file to the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.
   Launch Configuration Manager | Click the link to access Configuration Manager. The default username for logging into Configuration Manager is administrator. Use the password that you typed into the Configuration Manager - Port and Password installation wizard page. In Configuration Manager: Click the + symbol next to the Analytics Collector application name to view its components. Configure all settings for all of the s. Online Help for these settings is available in the Configuration Manager application. Use the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.
   Application Settings Confirmation | Select Yes if you have completed configuration of the Analytics Collector settings. Select No, configure later to complete the installer without configuring the Analytics Collector settings. You must run Configuration Manager and configure Analytics Collector settings before starting Analytics.
   Install Complete | Click Done to complete the installation.

### Clustering the BEA AL Analytics Collector Service

(Optional) A 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.

To cluster the BEA AL Analytics Collector service:

1. Configure AquaLogic Interaction to send events to the BEA AL Analytics Collector 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. Click the + symbol next to the Portal Service application name to view its components.
3. 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.

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 BEA AL Analytics Collector service 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

This section describes how to install the Interaction Analytics component. The Interaction Analytics component facilitates communication between Analytics and the portal. The installation instructions are the same for Windows, UNIX, and Linux hosts, with slight exceptions as noted.

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.exe
- UNIX/Linux: ALAnalytics_ALI_v2-5

4. Close all unnecessary applications and windows.
5. Perform one of the following:

- If you are installing on Windows, double-click the installer file.
- If you are installing on UNIX/Linux, run the installer file.

6. Complete the installation wizard pages as described in the following table and 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.

   Table 4-3 Installation Wizard Pages - Interaction Analytics Component
   Wizard Page | Description
   --- | ---
   License Agreement | Read and accept the license agreement.
   Choose Components | Choose Interaction Analytics Component.
   Configuration Manager - Update | This page is displayed if an existing installation of Configuration Manager 2.0 is detected. Select if you want to update the password or port information for Configuration Manager or use the existing settings.
   Configuration Manager - Port and Password | This page is displayed if you chose to update Configuration Manager’s password and port information. Type the port number on which you want Configuration Manager to service requests. By default, the port number is 12345. After running the installer, you will be able to access Configuration Manager by using the following URL: https://localhost:port_number. Also type and confirm the Administrator password that you will use to log into Configuration Manager. The password is case-sensitive.
   Portal Installation Directory | Browse and select the location of the portal server installation, for example: install_dir\ptportal\6.5
   Note: | The Interaction Analytics and Analytics Automation Jobs components require installation into the same directory. For this reason, you use the same wizard page for both installations.
   Pre-Installation Summary | Click Install to begin the installation. The installer copies Interaction Analytics component files to the installation directory. The installer writes a log file to the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.
   Launch Configuration Manager | Click the link to access Configuration Manager. The default username for logging into Configuration Manager is administrator. Use the password that you typed into the Configuration Manager - Port and Password installation wizard page. In Configuration Manager: Click the + symbol next to Portal Service application name to view its components. Click the Analytics Communication component. Click the Enabled check box, which appears in the Enable Analytics Communication area. Additional configuration options appear. Configure the following settings: Enable unicast Collector hostname Collector port Online Help for these settings is available in the Configuration Manager application. Use the settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.
   Application Settings Confirmation | Select Yes if you have completed configuration of the Analytics settings. Select No, configure later to complete the installer without configuring the Analytics settings. You must run the Configuration Manager and configure Analytics Communication settings before starting Analytics.
   Install Complete | Click Done to complete the Interaction Analytics Component installation.

7. 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.

Note: | The installer writes a log file in the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.

## Installing the Image Service Component

This section describes how to install the Image Service component. The instructions are the same for installing on a Windows, UNIX, or Linux host, with minor differences as noted. 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. The installer file is one of the following:

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

3. Close all unnecessary applications and windows.
4. Double-click the installer file.
5. Complete the installation wizard pages as described in the following table and according to the settings you planned when you completed the Image Service Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.

   Table 4-4 Installation Wizard Pages - Image Service Component
   Wizard Page | Description
   --- | ---
   License Agreement | Read and accept the license agreement.
   Choose Components | Choose Image Service Component.
   Image Service Component - Image Service Installation Directory | Browse and select the location where the Image Service files are installed, for example: install_dir\ptimages.
   Pre-Installation Summary | Click Install to begin the installation. The installer copies Image Service component files to the installation directory. The installer writes a log file to the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.
   Install Complete | Click Done to complete the Image Service component installation.

## Installing the Analytics Automation Jobs Component

This section describes how to install the Analytics Automation Jobs component. The instructions are the same for installing on a Windows, UNIX, or Linux host, with minor differences as noted.

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. The installer file is one of the following:

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

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.

3. Close all unnecessary applications and windows.
4. Double-click the installer file.
5. Complete the installation wizard pages as described in the following table and 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.

   Table 4-5 Installation Wizard Pages - Analytics Automation Jobs Component
   Wizard Page | Description
   --- | ---
   License Agreement | Read and accept the license agreement.
   Choose Components | Choose Analytics Automation Jobs.
   Configuration Manager - Update | This page is displayed if an existing installation of Configuration Manager 2.0 is detected. Select if you want to update the password or port information for Configuration Manager or use the existing settings.
   Configuration Manager - Port and Password | This page is displayed if you chose to update Configuration Manager’s password and port information. Type the port number on which you want Configuration Manager to service requests. By default, the port number is 12345. After running the installer, you will be able to access Configuration Manager by using the following URL: https://localhost:port_number. Also type and confirm the Administrator password that you will use to log into Configuration Manager. The password is case-sensitive.
   Portal Installation Directory | Browse and select the location of the portal server installation, for example: install_dir\ptportal\6.5.
   Note: | The Analytics Automation Jobs and Interaction Analytics components require installation into the same directory. For this reason, you use the same wizard page for both installations.
   Pre-Installation Summary | Click Install to begin the installation. The installer copies Analytics jobs to the installation directory. The installer writes a log file to the directory where it is installed (for example: C:\bea\alui\installlogs). If you encounter problems during installation, examine the error messages in the log file.
   Launch Configuration Manager | Click the link to access Configuration Manager. The default username for logging into Configuration Manager is administrator. Use the password that you typed into the Configuration Manager - Port and Password installation wizard page. In Configuration Manager: Click the + symbol next to the Analytics Jobs application name to view its components. Configure all settings for all of the Analytics Jobs components. Online Help for these settings is available in the Configuration Manager application. Use the database and connectivity settings that you provisioned when you completed the Analytics Installation and Configuration Worksheets document.
   Application Settings Confirmation | Select Yes if you have completed configuration of the Analytics Jobs settings. Select No, configure later to complete the installer without configuring the Analytics Jobs settings. You must run the Configuration Manager and configure Analytics Jobs settings before starting Analytics.
   Install Complete | Click Done to complete the Analytics Automation Jobs component installation.

## Starting Analytics and Analytics Collector Services

This section provides information on starting the BEA AL Analytics and BEA AL Analytics Collector services. Perform the procedure that is appropriate to your operating system.

### Starting Analytics and Analytics Collector Services on Windows

After you have installed all Analytics components:

- Ensure that the BEA AL Analytics service has been started. From Windows NT Services, click Administrative Tools | Services; if the Analytics service has not started, right-click it and choose Start.
- Ensure that the BEA AL Analytics Collector service has been started. From Windows NT Services, click Administrative Tools | Services; if the Collector service has not started, right-click it and choose 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.

### Starting the Analytics and Analytics Collector Services on UNIX and Linux

After you have installed all Analytics components:

- Ensure the BEA AL Analytics service has been started: install_dir/ptanalytics/2.5/bin/analyticsd.sh start
- Ensure the BEA AL Analytics Collector service has been started: install_dir/ptcollector/2.5/bin/collectord.sh start

## Registering Analytics with the Portal

This section describes how to register the Analytics Console, remote server, web service, and portlet objects.

To register the Analytics objects with the portal:

1. Log into the portal as a user with administrative privileges.
2. Click Administration.
3. From the Select Utility drop-down choose Migration - Import.
4. Browse to select the location of the migration package. If you accepted installation defaults, the location on the Analytics host is: install_dir\ptanalytics\2.5\serverpackages\analytics.pte
5. Click Load Package.
6. Perform one of the following:

- If you are importing the migration package for the first time, keep the default selections under Import Settings. The default selections are Import ACLs and Remember Dependency Settings.
- If you have previously imported the migration package and you are importing it again, keep the default selections and check the box next to Overwrite Remote Servers.

7. Click Portal Resources on the left hand side of the Migration editor.
8. Select the objects that you want to import.
9. Click Finish.

## Adding Analytics Jobs to the Automation Service

This section describes how to add all Analytics jobs to the Automation Service. Once these jobs are added, the Automation Service runs them automatically. To add Analytics jobs to the Automation Service:

1. Log into the portal as an administrator.
2. Click Administration.
3. From the Select Utility drop-down, choose Automation Service.

The Automation Service Manager appears.

4. Ensure that the Automation Service is online.
5. Under Edit Automation Services, click the name of the computer on which the Analytics Jobs component is installed.

The Register Folders window appears.

6. Click Add Folder.

The Add Job Folder window appears.

7. Expand the Analytics folder.
8. Select the Analytics Jobs folder.
9. Click OK to close the Register Folders window.
10. 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.

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