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, scripting the 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
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.
Launch the Analytics Installer.
Windows: ALAnalytics_ALI_v2-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
Choose to install the Analytics Services component.
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.
Configuring the Analytics Database
Perform one of the following procedures that is appropriate to your database platform:
To 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.
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 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.
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\ .
Copy the oracle directory from install_dir\ptanalytics\2.1\sql to the Analytics database's host computer.
Log on to the host computer for the Analytics database as owner of the Oracle system files.
Run the following scripts against your Oracle database as sysdba:
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.
Add the Oracle database user and password values into the Analytics Configurator Worksheet, which is included in the Analytics Installation and Configuration Worksheets document.
Execute the following steps as the analytics user, which you just created. The scripts that you run are located in the oracle directory that you copied in Step 1.
Run the script create_analytics_schema.sql.
Run the script install_analytics_seeddata.sql.
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 increase the efficiency of the database.
On UNIX or Linux, open http://localhost:11944/configurator/ui/start.jsf in a web browser.
Complete the 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.
An installer screen appears that summarizes your configuration. Review this screen and make changes, if necessary. Otherwise, click Update.
Registering Ensemble Events
(AquaLogic Ensemble integration only) To register Ensemble events, run the following from the command line on the Analytics host machine:
Install the Interaction component on all servers that host 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 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 a Java application server, shut down the application server.
Launch the Analytics Installer.
Windows: ALAnalytics_ALI_v2-1.exe
UNIX/Linux: ALAnalytics_ALI_v2-1
Choose to install the Interaction component.
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.
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.
Launch the Analytics Installer.
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.
Choose to install the Automation Service component.
To start Analytics and portal 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:
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.
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. For more complete details on performing this task, see Importing the Ensemble Migration Package.
To register the Ensemble application, use the migration utility to import the migration package analytics_ensemble.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:
Log into the Administrator Portal.
In Administration, choose Automation Service.
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.
Upgrade
Upgrade Paths
The following table summarizes the supported database upgrade paths for Analytics.
Table 3-1 Upgrade Paths
Upgrade Path
Upgrade References
2.0 to 2.1
Follow the procedures in this chapter.
1.2 to 2.1
Follow the procedures in this chapter.
Note:
We do not support upgrades from Analytics 1.1 to 2.1. To do so, you must first upgrade Analytics 1.1 to either 1.2 or 2.0, then perform the appropriate upgrade to Analytics 2.1.
This section describes how to upgrade from Analytics 2.0 to Analytics 2.1.
To upgrade from Analytics 2.0 to Analytics 2.1:
Delete the Analytics folder beneath the install_dir\common\container\tomcat\5.0.28\work directory.
Back up the installation directory of the previously-installed version of Analytics Services, using the tool of your choice.
Install Analytics Services. For details, see Installing Analytics Services. If you are choosing the same location as the existing software, accept the default installation directory location when prompted.
Back up the Analytics database using the tool of your choice.
Upgrade the Analytics database by running the upgrade_2.0_to_2.1.sql script: install_dir\ptanalytics\2.1\sql\database\upgrade_2.0_to_2.1.sql
Reconfigure Analytics by running the Analytics Configurator. For details, see Configuring Analytics
(AquaLogic Ensemble integration only) Register Ensemble events by running the following from the command line on the Analytics host machine:
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.
This section describes how to upgrade from Analytics 1.2 to Analytics 2.1.
Note:
You must upgrade your portal from Plumtree Foundation 5.x to BEA AquaLogic Interaction 6.x before upgrading Analytics from 1.2 to 2.1.
To upgrade from Analytics 1.2 to Analytics 2.1:
Delete the Analytics folder beneath the install_dir\common\container\tomcat\5.0.28\work directory.
Back up the installation directory of the previously-installed version of Analytics Services, using the tool of your choice.
Install Analytics Services. For details, see Installing Analytics Services. If you are choosing the same location as the existing software, accept the default installation directory location when prompted.
From the Scheduled Tasks, delete the Sync job from the Analytics 1.2 installation.
Back up the Analytics database, using the tool of your choice.
Upgrade the Analytics database by running the upgrade_1.x_to_2.0.sql script: install_dir\ptanalytics\2.1\sql\database\upgrade_1.x_to_2.0.sql
Upgrade the Analytics database by running the upgrade_2.0_to_2.1.sql script: install_dir\ptanalytics\2.1\sql\database\upgrade_2.0_to_2.1.sql
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_database.sql script on the portal database to create these tables. The script is located in install_dir\ptanalytics\2.1\sql\database\
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\database\ .
Reconfigure Analytics by running the Analytics Configurator. For details, see Configuring Analytics
(AquaLogic Ensemble integration only) Register Ensemble events by running the following from the command line on the Analytics host machine:
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.
