This section discusses how to install Pathways components.
Launching the Pathways Installer
To launch the Pathways installer:
Log in to the remote server host computer as the local administrator (on Windows) or a user with directory write privileges (on UNIX).
Copy the installer to the disk location from which you plan to launch it.
Launch the Pathways installer:
On a Windows host, run ALPathways_v1-0.exe.
On a UNIX host, run ALPathways_v1-0.
Completing the Installer Wizard Pages
Complete the installation wizard pages as described in the following table.
If you want to install all components on one computer, select Complete from the Install Set drop-down list. Otherwise, select Custom, then select the check box for each component that you want to install. The installer wizard pages that appear vary according to the selections you choose.
Table 4-1 Pathways Installer Wizard Pages
Wizard Page
Description
Introduction
This installer wizard page provides a brief description of the installer and describes how to run the installer in silent mode.
License Agreement
Read and accept the license agreement.
Choose Components
You can choose the Pathways components you want to install. Each component can be installed on a separate server depending on your configuration.
The Pathways components are:
Pathways Web UI: The core set of Web UI components that comprise the Pathways application.
Analytics Events for Pathways: Sends Analytics user activity data to Pathways. Install this component on the computer hosting Analytics services.
Pathways Rank Engine: Calculates the ActivityRank for each object in your system.
Portal Files: The necessary files to enable communication between the portal and Pathways. Install this component on the portal server.
Image Service Files: The necessary images, styles, user interface controls, Java applets, and online help for Pathways. Install this component on the computer hosting the computer hosting the Image Service.
Search Service: Installs the Windows service called the BEA ALI Search Service, which facilitates communication with the portal’s Search server.
Security and Directory Service: Installs the Security and Directory Service.
Note:
Do not install the Security and Directory Service if it is already installed in your environment. If you have installed AquaLogic Ensemble, you might have already installed the Security and Directory Service.
After you have chosen the components you want to install, click Next.
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)
Existing License Update
This page appears if a license.bea file exists in the location specified in the License Directory page.
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.
Select Leave Alone to leave the existing license.
For more complete details on license types and combining license keys, see Licensing.
Configuration Manager - Port and Password
Type the port number on which you want Configuration Manager to service Pathways 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/cm/login.jsf.
Also type and confirm the Administrator password that you will use to log into Configuration Manager. The password is case-sensitive.
Choose Install Folder
The default installation folder is:
C:\bea\alui (Windows)
/opt/bea/alui (UNIX)
Note:
In the rest of this guide, the Pathways installation folder is referred to as install_dir.
After you have entered the required information or accepted the default, click Next.
Path to Image Service Files
Install Image Service files on the computer on which the Image Service is installed. The path should lead to the directory where the Image Service is installed.
C:\bea\alui\ptimages (Windows)
/opt/bea/alui/ptimages (UNIX)
Before clicking Next, verify that security for the Image Service directory is appropriately configured to allow for installation of the Image Service files.
After you have entered the required information, click Next.
Path to Portal Files
Install portal files on the portal server. The path should lead to the directory where the portal is installed.
C:\bea\alui\ptportal\6.1 (Windows)
/opt/bea/alui/ptportal/6.1 (UNIX)
Note:
After installing portal files, you must restart the portal application server and, if you are running on Java, redeploy your portal.war and portal.ear files. For details, see Restarting the Portal Application Server.
Path to Analytics Files
Install Analytics files on the computer on which Analytics 2.1 is installed. The path should lead to the directory where Analytics 2.1 is installed.
C:\bea\alui\ptanalytics\2.1 (Windows)
/opt/bea/alui/ptanalytics/2.1 (UNIX)
Install Complete
This screen appears after the installer has finished. It includes the URL you use to launch the Configuration Manager. You must reboot the system before continuing to the next procedure.
After you have made a selection, click Yes, restart my system.
Restarting the Portal Application Server
Note:
This step is required after you install portal files on the portal server.
To restart the application server, 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 IIS.
Running the Security and Directory Service (SDS) Database Script
The Security and Directory Service (SDS) requires additional tables in the AquaLogic Interaction portal database.
Caution:
If you have installed Analytics 2.1, Ensemble 1.0, or any other product that utilizes the SDS, and the SDS tables are already created in the ALI portal database, do not run the create tables script. It will drop and re-create the SDS tables along with the data, potentially breaking other applications.
Instructions for updating the ALI portal database for Pathways and the SDS vary slightly depending on the type of database you have and whether or not the SDS has already been installed by another product.
To create the Pathways database on SQL Server 2000:
Copy the scripts from install_dir\pathways\1.0\sql\mssqlserver to the database host computer.
Create the Pathways database user, configuring the Pathways database user to use SQL Server Authentication.
Create the Pathways database.
Make sure to configure the size of the Pathways database. The growth of the database is directly correlated to the number of objects present in the system. Objects include such things as tags, user preferences, and saved searches. Estimate 10 MB of growth per 100,000 objects. For example, if the Pathways database stores roughly 100,000 new objects per day, you should anticipate growth of 3.65 GB per year.
Grant the Pathways database user the public and db_owner roles for the Pathways database.
On the Pathways database Properties | Permissions tab, grant the Pathways database user all permissions to the Pathways database.
As the Pathways database user, run the create_pathways_schema.sql script for the Pathways database, located in the install_dir\pathways\1.0\sql\mssqlserver\ folder.
Run the install_pathways_seeddata.sql script for the Pathways database, located in the install_dir\pathways\1.0\sql\mssqlserver\ folder.
Creating the Pathways Database on SQL Server 2005
To create the Pathways database on SQL Server 2005:
Copy the scripts from install_dir\pathways\1.0\sql\mssqlserver to the database host computer.
Create the Pathways database user, configuring the Pathways database user to use SQL Server Authentication.
Create the Pathways database with the following properties:
Configure the size of the Pathways database. The growth of the database is directly correlated to the number of objects present in the system. Objects include such things as tags, user preferences, and saved searches. Estimate 10 MB of growth per 100,000 objects. For example, if the Pathways database stores roughly 100,000 new objects per day, you should anticipate growth of 3.65 GB per year.
Change the default database for the Pathways database user to the Pathways database.
Grant the Pathways database user the db_owner role for the Pathways database.
Create the Pathways database schema. Specify the Pathways database user as the schema owner.
As the Pathways database user, run the create_pathways_schema.sql script for the Pathways database, located in the install_dir\pathways\1.0\sql\mssqlserver folder.
Run the install_pathways_seeddata.sql script for the Pathways database, located in the install_dir\pathways\1.0\sql\mssqlserver folder.
Creating the Pathways Database on Oracle
To create the Pathways database on Oracle:
Copy the oracle directory frominstall_dir\pathways\1.0\sql\oracle\windows or install_dir/pathways/1.0/sql/oracle/unix to the Pathways database’s host computer. This folder contains the scripts that you will use to set up and configure the Pathways Database.
Log on to the host computer for the Pathways database as owner of the Oracle system files.
Execute the following steps as the system user in your Oracle database.
Run the script create_pathways_tablespaces.sql for your platform. This file is located in a platform specific subdirectory within the oracle directory that you copied in Step 1.
Note:
Before running the script, determine the name of the SID used in your portal database. If necessary, edit the script so that all SID name instances in the script match the SID name used for the portal database.
Run the script create_pathways_user.sql.
Execute the following steps as the pathways user that you just created.
Run the script create_pathways_schema.sql. This script creates all of the tables and indexes that are necessary to run Pathways. The create_pathways_schema.sql script is located in the oracle directory that you copied in Step 1.
Run the script install_pathways_seeddata.sql. This script adds all of the initial seed data that are necessary to run the Pathways product. The install_pathways_seeddata.sql script is located in the oracle directory that you copied in Step 1.
Run your database’s analysis tool on the portal database to increase the efficiency of the database.
Creating the Rank Engine Database
This section describes how to create and set up the Rank Engine database. It contains the following sections:
Creating the Rank Engine Database on SQL Server 2000
To create the Rank Engine database on SQL Server 2000:
Copy the scripts from install_dir\rankengine\1.0\sql\mssqlserver to the database host computer.
Create the Rank Engine database user, configuring the Rank Engine database user to use SQL Server Authentication.
Create the Rank Engine database with the following properties:
Make sure to configure the size of the Rank Engine database. The growth of the database is directly correlated to the number of objects present in the system to which an ActivityRank is assigned. Estimate 10 MB of growth per 100,000 objects. For example, if the Rank Engine database stores roughly 100,000 new objects per day, you should anticipate growth of 3.65 GB per year.
Grant the Rank Engine database user the public and db_owner roles for the Rank Engine database.
On the Rank Engine database Properties | Permissions tab, grant the Rank Engine database user all permissions to the Rank Engine database.
As the Rank Engine database user, run the create_rankengine_schema.sql script for the Rank Engine database, located in the install_dir\rankengine\1.0\sql\mssqlserver folder.
Creating the Rank Engine Database on SQL Server 2005
To create the Rank Engine database on SQL Server 2005:
Copy the scripts from install_dir\rankengine\1.0\sql\mssqlserver to the database host computer.
Create the Rank Engine database user, configuring the Rank Engine database user to use SQL Server Authentication.
Create the Rank Engine database with the following properties.
Configure the size of the Rank Engine database. The growth of the database is directly correlated to the number of objects present in the system to which an ActivityRank is assigned. Estimate 10 MB of growth per 100,000 objects. For example, if the Rank Engine database stores roughly 100,000 new objects per day, you should anticipate growth of 3.65 GB per year.
Change the default database for the Rank Engine database user to the Rank Engine database.
Grant the Rank Engine database user the db_owner role for the Rank Engine database.
Create the Pathways database schema. Specify the Pathways database user as the schema owner.
As the Rank Engine database user, run the create_rankengine_schema.sql script for the Rank Engine database, located in the install_dir\rankengine\1.0\sql\mssqlserver folder.
Creating the Rank Engine Database on Oracle
To create and set up the Rank Engine database on Oracle:
Copy the oracle directory from install_dir\rankengine\1.0\sql\oracle\windows orinstall_dir/rankengine/1.0/sql/oracle/unix tothe Rank Engine database’s host computer. This folder contains the scripts that you will use to set up and configure the Rank Engine Oracle Database.
Log on to the host computer for the Rank Engine database as owner of the Oracle system files.
Execute the following steps as the system user in your Oracle database.
Run the script create_rankengine_tablespaces.sql for your platform. This file is located in a platform specific subdirectory within the oracle directory that you copied in Step 1.
Note:
Before running the script, determine the name of the SID used in your portal database. If necessary, edit the script so that all SID name instances in the script match the SID name used for the portal database.
Run the script create_rankengine_user.sql for your platform. This file is located in a platform specific subdirectory within the oracle directory that you copied in Step 1.
When running this script, you will be prompted to create the username and password for the Rank Engine database user. You will need to enter these values into Configuration Manager when configuring Rank Engine database settings.
Create the Rank Engine database user, including its username and password.
As the Rank Engine database user that you just created run the script create_rankengine_schema.sql.
This script creates all of the tables and indexes that are necessary to run the Rank Engine. The create_rankengine_schema.sql script is located in the oracle directory that you copied in Step 1.
Run your database’s analysis tool on the portal database to increase the efficiency of the database.
Configuring Pathways
You must use the Configuration Manager to configure database and connectivity settings on every computer on which you have installed Pathways components.
Access Configuration Manager by using the following URL: https://localhost:port_ number/cm/login.jsf. Replace port_number with the port number used by Configuration Manager.
By default, Configuration Manager uses port number 12345. If you specified a port number other than 12345 on the Configuration Manager - Port and Password installation wizard page, use the port number that you specified.
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 Windows, the Configuration Manager runs as the BEA AL Configuration Manager(port_number) service.
In Configuration Manager, enter the database and connectivity settings that you provisioned when you completed the Pathways Installation and Configuration Worksheets document. Online help is available in the Configuration Manager user interface.
Note:
(Oracle only) When completing the Rank Engine Database component of Configuration Manager, make sure to follow these guidelines when completing the Index Tablespace configuration for Oracle: By default, this tablespace is named RANKENGINEINDEX. The name that you specify must match the value of the IDX_TBSP variable in the create_rankengine_tablespaces.sql script, located in install_dir/rankengine/version/sql/database/ .
Starting the Portal
Start portal-related services. For information on starting the portal, see AquaLogic Interaction Installation and Upgrade Guide.
Note:
Do not start the BEA ALI Search Service or BEA ALI Security and Directory Service yet. You will start these services after you register Pathways with the portal.
Registering Pathways with the Portal
To register the Pathways 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 Pathways host is: install_dir\pathways\1.0\serverpackages\pathways.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 installing Pathways on a different server or to use a different port than previous installations, 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.
Note:
You need to log out of the portal, then log back in for the Pathways Administration option to appear in the Select Utility menu.
Starting the Security and Directory Service (SDS) and Search Service
This section provides information on starting the Security and Directory Service (SDS) and Search Service. Perform the procedure that is appropriate to your operating system.
Starting the SDS and Search Service on Windows
To start the SDS and Search Service on Windows:
From the Windows Control Panel, click Administrative Tools | Services.
Right-click the BEA ALI Security and Directory Service.
Choose Start.
Right-click the BEA ALI Search Service.
Choose Start.
Starting the SDS and Search Service on UNIX
To start the SDS and Search Service on UNIX, run the following commands from the command line:
To start the BEA ALI Security and Directory daemon:install_dir/securityservice/1.0/bin/securityserviced.sh start
To start the BEA ALI Search daemon: install_dir/searchservice/1.0/bin/searchservice.sh start
Starting Pathways
This section provides information on starting Pathways-related services. Perform the procedure that is appropriate to your operating system.
Starting Pathways on Windows
To start Pathways on Windows:
From the Windows Control Panel, click Administrative Tools | Services.
Right-click the BEA AL Pathways service.
Right-click the BEA AL Pathways Rank Engine service.
Choose Start.
Starting Pathways on UNIX
To start Pathways on UNIX, run the following commands from the command line:
To start the BEA AL Pathways daemon:install_dir/pathways/version/bin/pathwaysserverd.sh
To start the BEA AL Pathways Rank Engine daemon:install_dir/rankengine/version/bin/rankEngineService.sh
Seeding the SDS Database with Pathways Roles and Capabilities
To seed the Security and Directory Service database with Pathways roles and capabilities, you only need to access Pathways Administration the first time after installation. To do so:
Log in to the portal.
Click Administration.
From the Select Utility menu, choose Pathways Administration.
Performing this step automatically creates Pathways capabilities and default roles.
Installing and Configuring the Auto-Tag External Operation
If you want the Auto-Tag Engine to run periodically as an Automation Service job, you must install the Auto-Tag external operation on the Automation Service host.
Note:
This procedure is optional. If you do not perform this procedure, you can manually run the Auto-Tag Engine by clicking Start on the Tags tab, Auto-Tagging page in Pathways Administration. For details, see AquaLogic Pathways Online Help.
To install and configure the Auto-Tag external operation:
Log in to the Automation Service host computer as the local administrator (on Windows) or as a user with directory write privileges (on UNIX).
Copy the installer to the disk location from which you plan to launch it.
Launch the Pathways installer:
On a Windows host, run ALPathways_v1-0.exe.
On a UNIX host, run ALPathways_v1-0.
Complete the installer wizard pages:
Choose to perform a custom installation.
Choose to install the Pathways WebUI component only.
Note:
You only need to install the Pathways WebUI component to install the Auto-Tag external operation, which is included in the Pathways WebUI component. You do not need to use the Pathways user interface on the Automation Service host computer.
Launch Configuration Manager and enter database and connectivity settings into the Pathways application sections (you do not need to enter settings for the Rank Engine section). For details on launching and using Configuration Manager, see Configuring Pathways.
On the Automation Service host computer, copy the scripts located in install_dir\pathways\1.0\scripts to the following location: install_dir\ptportal\6.1\scripts.
Log in to the portal as a user with administrative privileges.
In Administration, use the migration utility to import the pathways_autotags_extop.pte migration package, located in install_dir\pathways\1.0\serverpackages on the Pathways host.
Edit the Pathways Auto-Tag external operation, located in the Pathways administrative folder.
In the Operating System Command box, perform the following:
(UNIX only) Change the extension of the PathwaysAutotag.bat file by replacing .bat with .sh.
If your API Service does not use the 11905 default port number, replace 11905 in <localhost:11905> with the correct port number.
If your API Service is not installed on the same computer as the Automation Service that will be assigned to execute the external operation job, replace localhost in <localhost:11905> with the fully-qualified domain name.
You can now use the Automation Service utility to schedule a job that periodically runs the Auto-Tag Engine.
Adding Pathways Navigation Tags to the Portal Banner
Pathways is delivered with navigation tags that you can add to your portal banner to make Pathways' functionality more easily accessible. Using these navigation tags, you can add the following elements to the portal banner:
Pathways search box
Pathways search button
A tab that navigates to the Pathways home page from the Directory tab
Note:
This procedure is optional; you do not need to add Pathways navigation tags to complete the installation of Pathways.
To install Pathways portlet samples in your portal environment, import the pathways_navigation_samples.pte file included with the Pathways installation.
Making the Pathways User Profile Portlet Available to Users
The Pathways User Profile portlet lets users view:
Items that a user has submitted to the Knowledge Directory or uploaded to a Collaboration project
Discussion messages that a user has posted to a Collaboration discussion
Note:
This procedure is optional. If you do not want any of your users to view the data in this portlet, you do not need to perform this procedure. Note, however, that you can make this portlet available to some of your users by performing this procedure, then editing this portlet’s security to specify the users and groups that can access this portlet. For details on managing portlet security, see AquaLogic Interaction Online Help.
Note:
Object security is respected in the Pathways User Profile portlet. Users are only allowed to see items and discussion messages that they have access to.
To make the Pathways User Profile portlet available to end users, you must use the User Profile Manager to add the portlet to the General Information (Home) page. After you perform this procedure, users can view their own Pathways User Profile portlet by clicking My Account, then clicking View User Profile.
To make the Pathways User Profile portlet available to users, perform the following:
Navigate to Administration.
The Admin Objects Directory appears.
From the Select Utility menu, select User Profile Manager.
The User Profile Manager appears.
Click General Information (Home) page.
The Edit Page: General Information page appears.
Click Add Portlets.
The Add Portlets: General Information page appears.
Select Pathways User Profile Portlet.
Click Finish.
You are returned to the Edit Page: General Information page.
Click Finish.
You are returned to the User Profile Manager.
Click Finish.
You are returned to the Admin Objects Directory.
For more information on the Pathways User Profile portlet, see AquaLogic Pathways Online Help.
Accessing Pathways Administration Online Help
This section discusses how to access Pathways Administration online help.
Note:
This section is for your information only; you do not need to access Pathways Administration online help to complete the installation of Pathways.
AquaLogic Pathways is delivered with three separate online help systems. One online help system exists for each user interface: Simple Mode, Enhanced Mode, and Pathways Administration.
Online help launched from Pathways pages in Simple Mode describes how to use Pathways in Simple Mode only. Online help launched from Pathways pages in Enhanced Mode describes how to use Pathways in Enhanced Mode only.
For the purposes of maintaining security, online help for Pathways Administration is only accessible from the Pathways Administration utility. When you launch online help from Pathways Administration pages, all content is displayed for Simple Mode and Enhanced Mode, in addition to Pathways Administration. The purpose of this is to provide you with details about using all of Pathways' functionality in one online help system.
To access online help from Pathways Administration:
Navigate to the Pathways Administration utility.
Click ? on any of the Pathways Administration pages.
The appropriate Pathways Administration help topic appears.
Configuring Content Upload for the Pathways Submit Page
The Aqualogic Pathways Submit page allows users to upload new content manually to the Aqualogic Interaction Knowledge Directory. This page enables you to tag a document as it is submitted, rather than submitting the document through the Knowledge Directory’s user interface and then finding the document using Pathways search and tagging it.
By default, the Submit page allows uploads only through the built-in WWW Content Source (“World Wide Web” option). This section describes how to configure Pathways to allow users to submit documents from their local file system as well, using the Content Upload Content Source.
This section contains the following task subsections, in the order in which you should perform them: