You do not need to perform this procedure if you installed AquaLogic Pathways 1.5 or AquaLogic Analytics 2.5. The Security database was created prior to their installation and will be used for Pages.
Import the Pages migration package into the portal. For details, see Registering Pages with the Portal. Then modify experience definitions and custom navigation in the portal. For details, see the Administrator Guide for AquaLogic Pages.
Creating the Pages Database in Microsoft SQL Server 2005
To create and set up the Pages database in Microsoft SQL Server 2005:
Open SQL Server Management Studio.
Create the Pages database user:
In the navigation pane, expand the objects to display subfolders of the Security folder.
Right-click the Logins icon; then click New Login.
In the SQL Server Login Properties dialog box, enter the user name you provisioned when you completed the Installation and Configuration Worksheets for AquaLogic Pages.
In the Authentication area, choose SQL Server Authentication and enter the corresponding password.
Confirm the password to complete the process.
Create the Pages database with the name you provisioned when you completed the Installation and Configuration Worksheets for AquaLogic Pages.
Grant the Pages database user the dbo server role.
Click OK.
Set the security for the database:
In the Object Explorer, expand the Pages database and right-click the Security folder.
Select New Schema.
In the Schema Name field, type the name of the Pages database user.
Note:
The schema name must exactly match the name of the Pages database user.
Click the Search button and browse for the name of the Pages database user.
Click OK.
In the Object Explorer, expand the Users folder, which is under the Security folder.
Right-click the Pages database user and select Properties.
In the Database User dialog box, on the User Mapping page, click the ... button to the right of the Default Schema name to launch the Select Schema dialog box.
Browse for the schema that you created; this name should match the Pages database user name.
Click OK to close the Select Schema dialog box.
Click OK to close the Database User dialog box.
Close SQL Server Management Studio.
Creating the Pages Database in Oracle
To create and set up the Pages tablespace in Oracle, run the scripts in <install_dir>\settings\sql\oracle:
Create the Pages tablespace by running create_pages_tablespace_unix.sql or create_pages_tablespace_windows.sql as appropriate for your operating system. This script assumes an Oracle SID of PLUM10.
Edit the user script create_pages_user.sql:
Change @PAGESDB_LOGIN@ to the name of the user you want created.
Change @PAGESDB_PASSWORD_UNENCRYPTED@ to the password you want to use.
Create the Pages schema user by running create_pages_user.sql.
Creating the Security Database
This section describes how to set up the Security database.
Note:
You do not need to perform this procedure if you installed AquaLogic Pathways 1.5 or AquaLogic Analytics 2.5. The Security database was created prior to their installation and will be used for Pages.
Creating the Security Database on Microsoft SQL Server
This section describes how to set up the Security database on Microsoft SQL Server.
Note:
You do not need to perform this procedure if you installed AquaLogic Pathways 1.5 or AquaLogic Analytics 2.5. The Security database was created prior to their installation and will be used for Pages.
To create and set up the Security database on Microsoft SQL Server:
Create the Security database user. Specify SQL Server Authentication.
Create the Security database.
Change the default database for the Security database user to the Security database.
Grant the Security database user the db_owner role for the Security database.
Create the Security database schema. Specify the Security database user as the schema owner.
Connect to the Security database as the Security database user, using SQL Server Authentication.
Run the create_security_tables.sql script, located in install_dir\pages\1.5\sql\mssql.
Note:
Do not start the BEA AL Pagesservice at this time.
Creating the Security Database on Oracle
This section describes how to set up the Security database on Oracle.
Note:
You do not need to perform this procedure if you installed AquaLogic Pathways 1.5 or AquaLogic Analytics 2.5. The Security database was created prior to their installation and will be used for Pages.
To create and set up the Security database on Oracle:
Log on to the host computer for the Security database as owner of the Oracle system files.
Create the Security database tablespace.
Create the Security database user.
Connect to the Security database as the Security database user.
Run the create_security_tables.sql script, located in install_dir\pages\1.5\sql\mssql.
Note:
Do not start the BEA AL Pagesservice at this time.
Installing Pages Components
There are several components involved in a Pages deployment:
Pages Application: the code needed to run the Pages application. Install this component on the computer that will host Pages.
Notification Service: the service that enables Pages to email notifications to users.
Pages Portal Extensions: the portal objects used to display and access the Pages application in the portal. Install this component on the computer that hosts the portal.
Image Service Files: the images, help, and other static files used by the Pages application. Install this component on the computer that hosts the image service files.
The components can be installed on different hosts, in any order; however, you should not start any of the components until all components are installed. For details on provisioning hosts for the various Pages components, see the Deployment Guide for BEA AquaLogic User Interaction.
Note:
In a typical deployment the Pages Application is installed on a different computer than the Pages Portal Extensions and the Image Service Files.
Launching the Pages Installer
To launch the Pages installer:
Log into the Windows host as the local administrator.
Copy the ALPages_v1-5.exe installer to a temporary location.
Close all unnecessary windows and applications.
Double-click ALPages_v1-5.exe to launch the installer.
Complete the installation wizard panels as described in Completing the Installer Wizard Pages, and according to the settings you planned when you completed the configuration worksheets.
Completing the Installer Wizard Pages
The following table describes the Pages installer wizard pages. The installer wizard pages that appear vary according to the selections you choose.
Note:
If the installer setting does not apply to the Pages components you are installing, the installer does not display the wizard page.
Table 4-1 Pages Installer Wizard Pages
Wizard Page
Description
Introduction
This page provides a brief description of the installer and describes how to run the installer in silent mode. Click Next.
Choose Install Set
In the Install Set drop-down list, select either Evaluation or Custom. If you select Evaluation, the full set of Pages components is installed. If you select Custom, you can choose from the following individual components to install according to your deployment plan:
Pages Application: The core set of Web UI components that comprise the Pages application.
Notification Service: The service that enables Pages to email notifications to users.
Pages Portal Extensions: The files necessary to enable communication between the portal and Pages.
If your AquaLogic Interaction deployment is hosted on a non-Windows platform, do not install the Pages Portal Extensions using the Pages installer. Instead follow the instructions in Installing Pages Portal Extensions on UNIX or Linux.
Image Service Files: The necessary images, styles, user interface controls, and online help for Pages. Install these files on the same computer on which the portal’s Image Service is installed.
If your Image Service is hosted on a non-Windows platform, do not install the Pages Image Service Files using the Pages installer. Instead follow the instructions in Installing Image Service Files on UNIX or Linux.
After you have chosen the components you want to install, click Next.
Note:
In a typical deployment the Pages Application will be installed on a different computer than the Pages Portal Extensions and the Image Service Files.
Installation Location
Specify where you want to install the software. The default installation folder is C:\bea\alui.
After you have specified the location, click Next.
Configuration Manager - Port and Password
Specify the port and password you want to use for the Configuration Manager (a web tool that allows you to configure properties for Pages and other ALUI products). The default port is 12345.
If you have previously installed the Configuration Manager on this computer, you can update the password and port if necessary by selecting Update password and port.
Portal Path
Specify where the portal files are installed. The default portal installation folder is C:\bea\alui\ptportal\6.5\.
After you have specified the location, click Next.
Installation Location for Image Service Files
Specify where the Image Service files are installed. The default Image Service installation folder is C:\bea\alui\ptimages.
Note:
The security for the Image Service directory must be appropriately configured to allow for installation of the Image Service files.
After you have specified the location, click Next.
Pre-Installation Summary
Confirm the installer settings (install folder, components to install, and space needed for install), and click Install to start the installation.
Launch Configuration Manager
Click the link to launch the Configuration Manager and to configure settings for Pages. Log in as Administrator with the password you entered in the installer. For information on the Configuration Manager settings, refer to Verifying the Configuration Settings.
After completing the Configuration Manager, save your settings, close Configuration Manager, and click Next.
Application Settings Confirmation
Specify whether your application settings are correct, and click Next:
If you verified that all the settings in the Configuration Manager were correct, select Yes.
If you were not able to verify all the settings, but do not want to launch Configuration Manager again now to correct them, select No, configure later.
Install Complete
When the installer has finished, this page alerts you as to whether the installer succeeded. Click Done.
Redeploying the Portal Application
If you are using WebLogic, after installing the Pages Portal Extensions, you must redeploy the portal in the WebLogic console.
To redeploy the portal:
Open the WebLogic console.
Update, or delete and re-add, the portal deployment for install_dir\webapp\portal.ear file.
Verifying the Configuration Settings
Use the Configuration Manager to verify the accuracy of the Pages settings.
If you were not able to navigate to the Configuration Manager by clicking the link in the installer, navigate to https://localhost:12345/cm/ui/cm.jsf (replacing localhost with the name of the computer that hosts the Pages application, and replacing 12345 with the port number you specified during installation).
Log in as Administrator with the password you specified during installation.
Click Pages.
Verify the accuracy of the following values:
Note:
If any of the values are incorrect, click the name of the associated page to display the editable fields. Correct the values and click Save. Embedded online help is available in the Configuration Manager’s user interface.
Under Application Settings:
HTTP Enabled: Select if non-secured HTTP should be used for the application's communication.
HTTP Port: The port number the application should listen to for non-secured requests.
HTTPS Enabled: Select if secured HTTP over SSL should be used for the application's communication.
HTTPS Port: The port number the application should listen to for secured requests.
Under AquaLogic Notification Service Client:
URL: The URL should be in the format tcp://<notification_service_host>:65156.
Host: The name of the computer that hosts the Notification Service.
Under Database:
Vendor: The database vendor used for the AquaLogic Pages database.
Host: The name of the computer that hosts the Pages database.
User Name: The name of the Pages database user. (If you have to correct the user name, you should also correct the associated password.)
Port: The port number on which the Pages database services requests (the default for SQL Server is 1433, the default for Oracle is 1521).
Database Name: The name of the Pages database (for Oracle databases, this is the SID).
Under Login Tokens:
Default token type: This should be set to ALUI.
Message authentication code seed value: The value from the ALUI portal, which can be obtained by running the following sql query on the portal database:
SELECT VALUE FROM PTSERVERCONFIG WHERE SETTINGID = 65
Under Pages Notifications:
Use ALI Image Server: This should be set to true (the checkbox should be selected).
Style and Image Base URL: The URL to the image server (for example, http://<my_server>:<port>/imageserver).
Style and Image URI: The URI fragment to the base notification image and style information (for example, /plumtree/pages/private/notifications/).
Under Security Database:
Vendor: The database vendor used for the Security database.
Host: The name of the computer that hosts the Security database.
User Name: The name of the Security database user. (If you have to correct the user name, you should also correct the associated password.)
Port: The port number on which the Security database services requests (the default for SQL Server is 1433, the default for Oracle is 1521).
Database Name: The name of the Security database (for Oracle databases, this is the SID).
Under User and Group Directory:
Host: The name of the computer that hosts the LDAP service.
Port: The port number on which the LDAP service listens for requests.
Principal: The trusted user of the LDAP service.
Credential: The password for the trusted user.
If the Notification Service has been installed on the same machine as the Pages application, verify the accuracy of the values under AquaLogic Notification Service: Administrative Credentials.
Starting the BEA AL Pages Service
Note:
The BEA ALI API Service, BEA ALI LDAP Directory, and BEA AL Notification Service must be started before starting the BEA AL Pages service. These services may be running on other machines.
To start the BEA AL Pages service:
Open the Windows Services console. Click Start Settings Control Panel Administrative Tools Services.
In the list of services, double-click BEA AL Pages.
In the Startup type drop-down list, select Automatic.
Click Start.
Click OK to exit the properties dialog box.
Close the Services console.
Installing Pages Portal Extensions on UNIX or Linux
The Pages Portal Extensions component must be manually installed when AquaLogic Interaction is hosted on a non-Windows platform. When AquaLogic Interaction is hosted on a Windows platform, use the Pages installer to install the Pages Portal Extensions component, as described in Installing Pages Components.
To install the Pages Portal Extension component to a UNIX or Linux platform:
Stop your application server.
Copy taglibPages.jar to the following portal directory: install_dir/ptportal/version/lib/java. For example, execute the following command:
Navigate to the directory that contains the portal.war and portal.ear files: install_dir/ptportal/version/webapp. For example, execute the following command:
cd /opt/bea/alui/ptportal/6.5/webapp
Update the portal.war with the taglibPages.jar file by executing the following commands:
Create a tmp directory by executing the following command:
mkdir tmp
Copy the portal.war to the tmp directory by executing the following command:
cp portal.war tmp
Extract the portal.war file by executing the following command:
jar -xvf portal.war
Copy the taglibPages.jar from install_dir/ptportal/version/lib/java to the extracted portal.war in install_dir/ptportal/version/webapp. For example, execute the following command:
Repackage portal.war with new .jar by executing the following command:
jar -cvf portal.war *
Copy new portal.war file to new location by executing the following command:
cp portal.war ../tmp
Verify the taglibPages.jar was added to the portal.war by executing the following command:
jar tf portal.war
Update the portal.ear file with the new portal.war by executing the following command:
jar uf portal.ear portal.war
Navigate to the directory that contains the CustomTags.xml file: install_dir/settings/portal. For example, execute the following command:
cd /opt/bea/alui/settings/portal
Open the CustomTags.xml file in a text editor and add the following line to the <AppLibFiles> node section:
<libfile name="taglibPages"/>
For example:
<?xml version="1.0" encoding="UTF-8"?>
<AppLibFiles>
<libfile name="testlibApp" />
<libfile name="taglibPages"/>
</AppLibFiles>
Save the changes you made to CustomTags.xml.
Copy the builderconfig.xml file to the settings directory: install_dir/settings. For example, execute the following command:
cp builderconfig.xml /opt/bea/alui/settings
Restart your application server.
Installing Image Service Files on UNIX or Linux
The Image Service Files component must be manually installed when the Image Service is hosted on a non-Windows platform. When the Image Service is hosted on a Windows platform, use the Pages installer to install the Pages Image Service Files component, as described in Installing Pages Components.
To install the Pages Image Service Files component to a UNIX or Linux platform:
Copy the imagesvr.tar file into your imageserver directory: install_dir/ptimages. For example, execute the following command:
cp imagesvr.tar /opt/bea/alui/ptimages
Navigate to this directory. For example, execute the following command:
cd /opt/bea/alui/ptimages
Extract the files by executing the following command:
Restart the web server hosting your Image Service.
Registering Pages with the Portal
You must import the Pages migration package into the portal to register Pages with the portal. To register the Pages objects with the portal perform the following steps:
Move the Pages migration package (pagesobjects.pte) from the computer that hosts Pages to the computer that hosts the portal. The migration package is located in install_dir\pages\1.5\serverpackages (for example, C:\bea\alui\pages\1.5\serverpackages\pagesobjects.pte).
If you installed the Notification Service, move the Notification Service migration package (notification.pte) from the computer that hosts Pages to the computer that hosts the portal. The migration package is located in install_dir\notification\1.5\serverpackages (for example, C:\bea\alui\notification\1.5\serverpackages\notification.pte).
Log in to the portal as a portal administrator.
Click Administration.
From the Select Utility drop-down list select Migration - Import.
Browse to select the location of the Pages migration package.
Click Load Package.
Click Finish.
The following portal objects are created when you import the migration package:
Table 4-2 Portal Objects Included in Pages Migration Package
Object
Description
Pages Objects
This folder stores all the objects included in the migration package.
Blog
This portlet enables you to add a blog portlet to a portal page.
Pages Launcher Portlet
This portlet provides access to the Pages user interface. It includes a link to the Dashboard.
Wiki
This portlet enables you to add a wiki portlet to a portal page.
Wiki w/ Comments
This portlet is the same as the Wiki portlet except that you can add comments to the wiki.
Pages Components Selector
This portlet template enables you to create a portlet from an existing page component, to display content form a page component in a portal page.
Pages Server
This remote server points to the Pages installation.
Pages Base URL Web Service
This web service is used to gateway content in Pages.
Pages Blog Web Service
This is the web service for the Blog portlet.
Pages Components Service
This web service is used to gateway components displayed in portlets.
Pages Crawler Web Service
This web service enables you to crawl Pages content into the portal.
Pages Dashboard Web Service
This web service is used to display the Dashboard.
Pages Launcher Web Service
This is the web service for the Pages Launcher Portlet.
Pages Spaces Web Service
This web service provides the list of Spaces to the Spaces menu.
Pages Wiki (w/ Comments) Web Service
This is the web service for the Wiki w/ Comments portlet.
Pages Wiki Web Service
This is the web service for the Wiki portlet.
If you installed the Notification Service, you should import the Notification Service remote server into the portal and configure it to gateway RSS feeds. If you did not install the Notification Service, you can move on to integrating Pages into the portal navigation and setting up security for Pages. For details, see the Administrator Guide for AquaLogic Pages.
Importing and Configuring the Notification Service Remote Server
If you installed the Notification Service, you need to import the Notification Service remote server into the portal and configure it:
Move the Notification Service migration package (notification.pte) from the computer that hosts Pages to the computer that hosts the portal. The migration package is located in \cns\1.0\serverpackages (for example, C:\bea\alui\cns\1.0\serverpackages\notification.pte).
Log in to the portal as a portal administrator.
Click Administration.
From the Select Utility drop-down list select Migration - Import.
Browse to select the location of the Notification Service migration package.
Click Load Package.
Click Finish.
The AquaLogic Notification Service Server remote server and the AquaLogic Notification RSS Web Service are created in the AquaLogic Notification Service folder when you import the migration package.
Open the AquaLogic Notification Service Server remote server and set the Base URL.The base URL must be the fully qualified domain name, including the port number, of the server that hosts the AquaLogic Notification Service.
Click Finish to save your change.
Next you should integrate Pages into the portal navigation and set up security for Pages. For details, see the Administrator Guide for AquaLogic Pages.
Registering Pages with AquaLogic Ensemble
You can configure Pages to be accessed through the AquaLogic Ensemble proxy. This provides you more control over the appearance of Pages URLs and allows you to take advantage of Ensemble’s integration with AquaLogic Interaction Analytics.
To register Pages with Ensemble, register Pages as a resource. For instructions on registering resources in Ensemble, see the Administrator Guide for AquaLogic Ensemble.
For the Internal URL prefix, use http://Pages_host:Pages_port/ (for example, http://pages.company.com:11990/).
For the External URL prefix, use http://Ensemble_host:Ensemble_port/identifier/ (for example, http://ensemble.company.com:8080/pagesproxy/). The identifier can be any string you want to use to identify the resource. Users will access Pages by navigating to http://Ensemble_host:Ensemble_port/identifier/pages/ (for example, http://ensemble.company.com:8080/pagesproxy/pages/).
