This chapter provides brief, high level instructions for the installation of Pathways. It is intended to quickly guide experienced administrators through the installation procedure. It covers installing the Pathways components, scripting the databases, and starting and verifying the installation. The organization of this section maps directly to detailed instructions in Chapter 4, “Installation”.
Installation
Before you install Pathways, verify that you have completed the pre-installation steps. For details, see Installation Prerequisites.
Installing Pathways Components
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
The installer wizard pages that appear vary according to the selections you choose. For more complete details on performing this task, see Completing the Installer Wizard Pages.
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
Caution:
If you have installed Analytics 2.1, Ensemble 1.0, or any other product that utilizes the Security and Directory Service (SDS), and the SDS tables have been created in the ALI portal database, do not run the create tables script.
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.
If the SDS has not already been installed by another product, run the SDS create tables script:
On SQL Server, run create_tables_mssql.sql as the portal database user. The script is located in install_dir\securityservice\1.0\sql\mssql\.
On Oracle, run create_tables_oracle.sql as the portal schema user. The script is located in install_dir\securityservice\1.0\sql\oracle\.
If the SDS was installed by Analytics 2.1, run the SDS update tables script:
On SQL Server, run update_tables_mssql.sql as the portal database user. The script is located in install_dir\securityservice\1.0\sql\mssql\.
On Oracle, run update_tables_oracle.sql as the portal schema user. The script is located in install_dir\securityservice\1.0\sql\oracle\.
If the SDS was installed by Ensemble 1.0, the SDS database tables do not require any updates. Do not run either of the SDS database scripts.
This section describes how to create the Pathways database on SQL Server 2000, SQL Server 2005, and Oracle. For more complete details on performing this task, see Creating the Pathways Database.
Creating the Pathways Database on SQL Server 2000
To create the Pathways database on SQL Server 2000:
Copy the scripts frominstall_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.
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.
As the Pathways database user, 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 frominstall_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, assigning the Pathways database as the default database for the Pathways database user.
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.
As the Pathways database user, 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 (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.
Log on to the host computer for the Pathways database as owner of the Oracle system files.
Run the following scripts against your Oracle database as sysdba:
Run the script create_pathways_tablespaces.sql.
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, 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_pathways_schema.sql.
Run the script install_pathways_seeddata.sql.
Creating the Rank Engine Database
This section describes how to create the Rank Engine database on SQL Server 2000, SQL Server 2005, and Oracle. For more complete details on performing this task, see Creating the Rank Engine Database.
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.
Configure the Rank Engine database user to use SQL Server Authentication.
Create the Rank Engine database.
Assign the Rank Engine database as the default database for the Rank Engine database user.
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. Configure the Rank Engine database user to use SQL Server Authentication.
Create the Rank Engine database, assigning the Rank Engine database as the default database for the Rank Engine database user.
Grant the Rank Engine database user the db_owner role for the Rank Engine database.
Create the Rank Engine database schema. Specify the Rank Engine 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 the Rank Engine database on Oracle:
Copy the oracle directory from install_dir\rankengine\1.0\sql\oracle\windows or install_dir/rankengine/1.0/sql/oracle/unix to the Rank Engine database’s host computer.
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 create_rankengine_tablespaces.sql script.
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 create_rankengine_user.sql script.
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.
Run the script create_rankengine_schema.sql as the Rank Engine database user that you just created.
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.
On Windows, the Configuration Manager runs as the BEA AL Configuration Manager(port_number) service.
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 when you installed Configuration Manager for the first time, either with Pathways, Ensemble, or Pages.
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/your_database_type/ .
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
This section describes how to register Pathways with the portal. For more complete details on performing this task, see Registering Pathways with the Portal.
To register Pathways objects with the portal, use the migration utility to import the migration package pathways.pte.
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
To seed the Rank Engine database with initial data, choose Pathways Administration from the Select Utility menu. 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. For more complete details on performing this task, see Installing and Configuring the Auto-Tag External Operation.
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.
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
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
To make the Pathways User Profile portlet available to end users, use the User Profile Manager to add the portlet to the General Information (Home) page. For more information on performing this task, see Making the Pathways User Profile Portlet Available to Users.
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 the 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.
Accessing Pathways Administration Online Help
For the purposes of maintaining security, online help for Pathways Administration is accessible only 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
To enable users to submit documents from their local file system using the Pathways Submit page, you must configure Pathways to use the Content Upload Content Source.
