Install the Automation Service component of the installation package on your Automation Service host and complete the Analytics Configurator pages for the Automation Service component. For details, see Installing the Automation Service Component.
This section describes how to install the core application, which includes the Analytics service and the Analytics Collector service. The instructions are the same for installing on a Windows, UNIX, or Linux host, with slight exceptions as noted. To install Analytics Services:
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).
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-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
Close all unnecessary applications.
Execute the installer file.
Complete the installation wizard pages as described in the following table and according to the settings you planned when you completed the Analytics Services Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
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)
/bea (UNIX/Linux)
Existing License Update
(Only appears if you have an existing license) Choose to either merge the evaluation license with the existing license, replace the existing license with the evaluation license, or leave the existing license alone.
If you already have an production license for Analytics, choose Leave Alone.
Application Port
Select http or https protocol. The default port is 11944. This is the port that the portal uses to query Analytics for the Analytics reports UI.
On the final Wizard page, click Install to begin the installation.
Note:
After the installer has copied all files to the installation directory, click Done. The Analytics Configurator will launch; however, do not complete the configuration at this time. First, configure the Analytics database, described in Configuring the Analytics Database. Note that the Analytics Configurator does not launch on UNIX and Linux systems if a default browser is not specified.
Note:
The installer writes a log file to the directory where it is installed (for example: C:\bea\alui). If you encounter problems during installation, examine the error messages in the log file.
Caution:
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.
Configuring the Analytics Database
This section describes how to set up the Analytics database. It contains the following sections:
Creating and Setting Up the Analytics Database on Microsoft SQL Server 2000
To create and set up the Analytics database on Microsoft SQL Server 2000:
Copy the scripts from install_dir\ptanalytics\2.1\sql\mssql to the database host computer.
Create the Analytics database user:
Create the Analytics database user with the user name you provisioned when you completed the Analytics Configurator Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Configure the Analytics database user to use SQL Server Authentication.
Set the Analytics database user password to the password you designated when you completed the Analytics Installation and Configuration Worksheets document.
Create the Analytics database with the following properties:
Create a database with the name you provisioned when you completed the Analytics Configurator 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.
Grant the Analytics database user the public and db_owner roles for the Analytics database.
On the Analytics database Properties | Permissions tab, grant the Analytics database user all permissions to the Analytics database.
Connect to the Analytics database as the Analytics database user, using SQL Server Authentication.
Run the setup scripts for the database, located in the install_dir\ptanalytics\2.1\sql\mssql\folder, in the following order (make sure that you are running the scripts on the Analytics database):
db_creation.sql
install_seeddata.sql
Connect to the portal database as the portal database user.
As the portal database user, query the portal database to check if these tables exist:
PTROLES
PTAPPLICATIONS
PTCAPABILITIES
PTUSERROLELINKS
PTGROUPROLELINKS
PTROLECAPABILITYLINKS
PTCREDENTIALPROPERTIES
PTCREDENTIALVALUES
If these tables exist, continue to the next step.
If these tables do not exist, run the create_sds_tables_mssql.sql script on the portal database to create these tables. The script is located in install_dir\ptanalytics\2.1\sql\mssql\
As the portal database user, run the install_sds_seeddata.sql setup script on the portal database. The script is located in install_dir\ptanalytics\2.1\sql\mssql\ .
Creating and Setting Up the Analytics Database on Microsoft SQL Server 2005
To create and set up the Analytics database on Microsoft SQL Server 2005:
Copy the scripts from install_dir\ptanalytics\2.1\sql\mssql to the database host computer.
Create the Analytics database user:
Create the Analytics database user with the user name you provisioned when you completed the Analytics Configurator Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Configure the Analytics database user to use SQL Server Authentication.
Set the Analytics database user password to the password you designated when you completed the Analytics Installation and Configuration Worksheets document.
Create the Analytics database with the following properties:
Create a database with the name you provisioned when you completed the Analytics Configurator 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.
Grant the Analytics database user the db_owner role for the Analytics database.
Create the Analytics database schema. Specify the Analytics database user as the schema owner.
Grant the Analytics database user the sysadmin server role.
Connect to the Analytics database as the Analytics database user, using SQL Server Authentication.
Run the setup scripts for the database, located in the install_dir\ptanalytics\2.1\sql\mssql\folder, in the following order (make sure that you are running the scripts on the Analytics database):
db_creation.sql
install_seeddata.sql
Connect to the portal database as the portal database user.
As the portal database user, query the portal database to check if these tables exist:
PTROLES
PTAPPLICATIONS
PTCAPABILITIES
PTUSERROLELINKS
PTGROUPROLELINKS
PTROLECAPABILITYLINKS
PTCREDENTIALPROPERTIES
PTCREDENTIALVALUES
If these tables exist, continue to the next step.
If these tables do not exist, run the create_sds_tables_mssql.sql script on the portal database to create these tables. The script is located in install_dir\ptanalytics\2.1\sql\mssql\
As the portal database user, run the install_sds_seeddata.sql setup script on the portal database. The script is located in install_dir\ptanalytics\2.1\sql\mssql\ .
Creating and Setting Up the Analytics Database on Oracle
To create and set up the Analytics database on Oracle:
Copy the oracle directory from install_dir\ptanalytics\2.1\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.
Log on to the host computer for the Analytics database as owner of the Oracle system files.
Execute the following steps as the system user in your Oracle database.
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.
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.
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.
Add the Oracle database user and password values into the Analytics Configurator Worksheet, which is included in the Analytics Installation and Configuration Worksheets document (you will enter these values into the Analytics Configurator during the procedure described in "Configuring Analytics").
Execute the following steps as the analytics user that you just created.
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.
Run the script install_analytics_seeddata.sql. This script adds all of the initial seed data that are necessary to run the Analytics product. The install_analytics_seeddata.sql script is located in the oracle directory that you copied in Step 1.
As the portal database user, query the portal database to check if these tables exist:
PTROLES
PTAPPLICATIONS
PTCAPABILITIES
PTUSERROLELINKS
PTGROUPROLELINKS
PTROLECAPABILITYLINKS
PTCREDENTIALPROPERTIES
PTCREDENTIALVALUES
If these tables exist, continue to the next step.
If these tables do not exist, run the create_sds_tables_oracle.sql script on the portal database to create these tables. The script is located in install_dir\ptanalytics\2.1\sql\oracle\
As the portal database user, run the install_sds_seeddata.sql setup script on the portal database. The script is located in install_dir\ptanalytics\2.1\sql\oracle\ .
Run your database's analysis tool on the portal database to the efficiency of the database.
This section describes how to configure Analytics.
Note:
Different sets of component-specific configuration pages appear, depending on the components that you just installed.
To configure Analytics:
Ensure that the following services are running:
BEA ALI API Service
BEA AL Analytics Service
Return to the browser window that launched when you completed the installer. If you have closed the browser window, you can launch the Analytics Configurator on Windows by choosing Start | Programs | BEA | Analytics Configurator. On UNIX or Linux, open the following location in a web browser: http://localhost:11944/configurator/ui/start.jsf.
Caution:
On Windows 2003, IE Security settings might prevent the configurator from completing. If this is the case, configure IE to completely trust the Analytics host computer.
Click Continue to begin the sequence of configuration pages. Complete the following configuration pages using the values you decided on when you completed the Analytics Configurator Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Table 4-2 Analytics Configurator Pages
Configuration Page
Settings
Comments
Configure Analytics Database Information
Analytics DB
Analytics DB Server Name
Does not appear if you select Use JDBC URL
Analytics DB Port
Does not appear if you select Use JDBC URL
Analytics DB Name
Does not appear if you select Use JDBC URL
Analytics DB JDBC URL
Appears if you select Use JDBC URL
Analytics DB Username
Analytics DB Password
Use JDBC URL
We recommend that you only use a JDBC URL if the standard method of configuration does not work for your environment, for example if you use Oracle RAC or a SQL Server cluster.
API Service Information
API Service URL
You can find the API Service URL in Portal Administration by selecting Portal Settings from the Select Utility drop-down list. Then click Portal URL Manager. The API Service URL is displayed in the SOAP Server URL field.
Portal Username
This user must be for a portal account that has Select rights to all communities, portlets, users, documents, and Collaboration projects. It is recommended that you enter a user that belongs to the Administrators group.
Portal Password
Configure Portal Database Information
Portal DB
Portal DB Server Name
Does not appear if you select Use JDBC URL
Portal DB Port
Does not appear if you select Use JDBC URL
Portal DB Name
Does not appear if you select Use JDBC URL
Portal DB JDBC URL
Appears if you select Use JDBC URL
Portal DB Username
The Portal DB Username must be the same as the one you used to create the portal database.
Portal DB Password
Use JDBC URL
We recommend that you only use a JDBC URL if the standard method of configuration does not work for your environment, for example if you use Oracle RAC or a SQL Server cluster.
Configure Collaboration Database Information (OPTIONAL)
BEA AquaLogic Interaction Collaboration is installed in my portal environment.
Select this option if Collaboration is installed in your portal environment.
Collab DB
Collab DB Server Name
Does not appear if you select Use JDBC URL
Collab DB Port
Does not appear if you select Use JDBC URL
Collab DB Name
Does not appear if you select Use JDBC URL
Collab DB JDBC URL
Appears if you select Use JDBC URL
Collab DB Username
Collab DB Password
Use JDBC URL
We recommend that you only use a JDBC URL if the standard method of configuration does not work for your environment, for example if you use Oracle RAC or a SQL Server cluster.
Configure Publisher Database Information
(OPTIONAL)
BEA AquaLogic Interaction Publisher is installed in my portal environment.
Select this option if Collaboration is installed in your portal environment.
Publisher DB
Publisher DB Server Name
Does not appear if you select Use JDBC URL
Publisher DB Port
Does not appear if you select Use JDBC URL
Publisher DB Name
Does not appear if you select Use JDBC URL
Publisher DB JDBC URL
Appears if you select Use JDBC URL
Publisher DB Username
Publisher DB Password
Use JDBC URL
We recommend that you only use a JDBC URL if the standard method of configuration does not work for your environment, for example if you use Oracle RAC or a SQL Server cluster.
An installer screen appears that summarizes your configuration. Review this screen and make changes, if necessary.
On the final page, click Update.
Note:
If you encounter configuration-related errors, follow the instructions in the error message or see Troubleshooting
Registering Ensemble Events
(AquaLogic Ensemble integration only): To register Ensemble events, run the following from the command line on the Analytics host machine:
This section describes how to install the Interaction and Automation Service components.
The installation instructions are the same for Windows, UNIX, and Linux hosts, with slight exceptions as noted.
Note:
You must reinstall the Interaction component after each time you upgrade AquaLogic Interaction.
To install the Interaction component:
Log in to the portal host computer as the same user that installed AquaLogic Interaction.
If you are running on Java, shut down the application server.
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-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
Close all unnecessary applications and windows.
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.
Complete the installation wizard pages as described in the following table and according to the settings you planned when you completed the Interaction Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Browse and select the location of the portal server installation, for example: C:\bea\alui\ptportal\6.1.
Note:
The Interaction and Automation Service components require installation into the same directory. For this reason, you use the same wizard page for both installations.
Analytics Services - Fully Qualified Domain Name
Specify the fully qualified domain name for the machine hosting Analytics Services (not the host computer(s) on which you installed AquaLogic Interaction).
On the final Wizard page, click Install to begin the installation.
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). 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:
Log in to the Image Service host computer as the local administrator or the ALI user created during installation of AquaLogic Interaction.
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-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
Close all unnecessary applications and windows.
Double-click the installer file.
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.
Installation Directory
Browse and select the location where the Image Service files are installed, for example: C:\bea\alui\ptimages\imageserver.
.
On the final Wizard page, click Install to begin the installation.
Note:
The installer writes a log file in the directory where it is installed (for example: C:\bea\alui). If you encounter problems during installation, examine the error messages in the log file.
Installing the Automation Service Component
This section describes how to install the Automation Service component. The instructions are the same for installing on a Windows, UNIX, or Linux host, with minor differences as noted.
To install the Automation Service component:
Log in to the Automation Service host computer as the local administrator or the ALI user created during the installation of AquaLogic Interaction.
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-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
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.
Close all unnecessary applications and windows.
Double-click the installer file.
Complete the installation wizard pages as described in the following table and according to the settings you planned when you completed the Automation Service Component Installation Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Table 4-5 Installation Wizard Pages - Automation Service Component
Wizard Page
Description
License Agreement
Read and accept the license agreement.
Choose Components
Choose Automation Service component.
Portal Installation Directory
Browse and select the location of the portal server installation, for example: C:\bea\alui\ptportal\6.1.
Note:
The Automation Service and Interaction components require installation into the same directory. For this reason, you use the same wizard page for both installations.
On the final Wizard page, click Install to begin the installation.
Note:
The installer writes a log file in the directory where it is installed (for example: C:\bea\alui). If you encounter problems during installation, examine the error messages in the log file.
When installation is complete, the Analytics Configurator launches for the machine on which you installed the Automation Service. Complete the configuration page that appears, as described in Configuring Analytics.
Starting Analytics and Portal Services
This section provides information on starting Analytics and portal services. Perform the procedure that is appropriate to your operating system.
Starting Analytics and Portal Services on Windows
After you have installed Analytics services and all Analytics components:
Ensure 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 the BEA AL Analytics Collector service has been started. From Windows NT Services, click Administrative Tools | Services; if the Analytics Collector service has not started, right-click it and choose Start.
Starting Analytics and Portal Services on UNIX and Linux
After you have installed Analytics services and all Analytics components:
Ensure the BEA AL Analytics service has been started:install_dir/ptanalytics/2.1/bin/analyticsd.sh start
Ensure the BEA AL Analytics Collector service has been started: install_dir/ptanalytics/2.1/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:
Log into the Administrator Portal.
Click Administration.
From the Select Utility drop-down choose Migration - Import.
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.1\serverpackages\analytics.pte
Click Load Package.
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.
Click Portal Resources on the left hand side of the Migration editor.
Select the objects that you want to import.
Click Finish.
Importing the Ensemble Migration Package
This section describes how to register the Ensemble application with the portal for use with Analytics. You only need to perform this procedure if you are integrating Ensemble with Analytics.
To register Ensemble with Analytics:
Log into the Administrator Portal.
Click Administration.
From the Select Utility drop-down choose Migration - Import.
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.1\serverpackages\analytics_ensemble.pte
Click Load Package.
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.
Click Portal Resources on the left hand side of the Migration editor.
Select the objects that you want to import.
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:
Log into the portal as an administrator.
Click Administration.
From the Select Utility drop-down, choose Automation Service.
The Automation Service Manager appears.
Ensure that the Automation Service is online.
Under Edit Automation Services, click the name of the computer on which Analytics Jobs are installed.
The Register Folders window appears.
Click Add Folder.
The Add Job Folder window appears.
Expand the Analytics folder.
Select the Analytics Jobs folder.
Click OK to close the Register Folders window.
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.
At an appropriate time, ensure that the Analytics jobs have completed successfully. If any Analytics jobs failed, schedule these jobs to run again.