This chapter provides brief, high-level instructions for installing AquaLogic Pages. It is intended to quickly guide experienced administrators through the installation procedure.
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.
Create the Pages database user with the name and password you provisioned when you completed the Installation and Configuration Worksheets for AquaLogic Pages. Specify SQL Server Authentication.
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.
Create a new schema with the name of the Pages database user.
In the Pages database user properties, map the Pages database user to the schema you created.
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. It contains the following sections:
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 SQLServer
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
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 the Pages Components
There are several components involved in a Pages deployment:
Pages Application: the code needed to run the Pages application
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
Image Service Files: the images, help, and other static files used by the Pages application
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.
Complete the installer wizard pages. The installer prompts you for specific information about your system and configuration. For detailed instructions on responding to the installer wizard pages, see
“Completing the Installer Wizard Pages” on page 4-6.
If you are using WebLogic, after installing the Pages Portal Extensions, you must redeploy the portal deployment in the WebLogic console. To redeploy the portal:
Open the WebLogic console.
Update, or delete and re-add, the portal deployment for the 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 in the installer.
Click Pages.
Verify the values.
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.
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.
You must import the Pages migration package into the portal to register Pages with the portal, then modify experience definitions and custom navigation in the portal.
Use the Migration - Import Utility in the portal to register the Pages objects located in the migration package. The migration package is installed on the computer that hosts Pages, in install_dir\pages\1.5\serverpackages (for example, C:\bea\alui\pages\1.5\serverpackages\pagesobjects.pte). For more information, see
“Registering Pages with the Portal” on page 4-15.