If you performed a new (non-upgrade) install of AquaLogic Interaction and installed the Content Upload Service, import the Content Upload migration package. For details, see Importing the Content Upload Migration Package.
This section describes how to install the AquaLogic Interaction components. The AquaLogic Interaction components are:
Image Service
Search
Document Repository Service
Administrative Portal
Automation Service
API Service
Portal Server
Content Upload Service
When performing a clean install, you can install the AquaLogic Interaction components in any order; however, you should not start any of the components until all components are installed. If you want to test components as you install them, the order in which they are listed above is recommended.
The AquaLogic Interaction components can be installed on different hosts. For details on provisioning hosts for the various AquaLogic Interaction components, see the Deployment Guide for BEA AquaLogic User Interaction.
Note:
The portal database must be scripted and running prior to starting the Administrative Portal.
Launching the AquaLogic Interaction Installer on Unix
The AquaLogic Interaction installer is a graphical, X-Windows client when run in interactive mode. If you are running the installer on a remote terminal, make sure your DISPLAY is set appropriately.
To launch the AquaLogic Interaction installer on a Unix host:
Copy the installer to a temporary location and run it as follows:
$ ./AquaLogicInteraction_v6-1_mp2
Complete the installation wizard pages according to the settings you planned when you completed the configuration worksheets.
Completing the Installer Wizard Pages on Unix
The following tables describe the AquaLogic Interaction 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 your Web application server or to the AquaLogic Interaction components you are installing, the installer does not display the wizard page.
Table 4-1 AquaLogic Interaction Installer Wizard Pages for Unix
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.
Installation Folder
Accept the default installation folder or select a different folder in which to install AquaLogic Interaction.
Default: /opt/bea
Upgrade Information
Indicates previously installed versions of portal products.
Upgrade Option
Select either Upgrade or New Install. If you select Upgrade, the installer skips subsequent configuration pages and instead uses values from a previous installation to fill in the information. The XML configuration file structure is also changed.
Note:
If you choose to upgrade the portal, the installer upgrades all of the components it detects needing an upgrade. If you want to install a specific component on a machine with multiple portal components, you should perform a New Install.
Choose Install Set
Select either Complete or Custom. If you select Complete, a full set of AquaLogic Interaction components is installed. If you select Custom, you can select individual portal components to install according to your deployment plan.
Fully Qualified Domain Name and Ports
Enter the fully qualified domain name and port numbers for the portal server. Do not include the “http://” prefix.
Example domain name: portal.mycompany.com
Example HTTP port: 80
Example HTTPS port: 443
Content Upload Service - Application Port
Indicate either http or https.
Enter the port that the Content Upload Service should use to handle requests.
API Service - Application Port
Indicate either http or https.
Enter the port that the API Service should use to handle requests.
External Portal URL
Enter the URL to the portal server that browsers outside of the local network would use.
Example: http://portal.mydomain.com:80/portal
API Service URL
Enter the URL to the API Service including the port number.
Example: http://wsserver.mydomain.com:80
Image Service URL
Enter the URL for the Image Service, including the port number if it is not 80 or 443:
Enter the host name and port for the AquaLogic Interaction Search node through which the portal initiates contact with the Search Cluster.
Example host name: back-end-services.portal.com
Example port: 15250
Click Help for further details on this installer wizard page.
Stand-alone or Cluster
Select whether you would like to install a Single Stand-alone Search Node or add/replace a Search Cluster Node. Selecting to install the stand-alone search node installs a single node on the local machine. If you want to support failover, select to add/replace nodes for a search cluster.
Search Nodes
Select to add a new search node or replace an existing node.
Note:
Selecting to replace an existing node removes all information about the node that you are replacing from the system.
Adding New Search Node
Enter the name and port number of the new search node.
The search node is installed into /opt/bea/alui/ptsearchserver/6.1.
Search Cluster Files
Select the location of the search cluster files. You must have permission to access and write to the location where you want to install these files. Search cluster files are only installed if they do not already exist in the location that you select.
Enter the port that the Search Cluster Manager will use.
Example: 15300
Default Automation Service Computer
Enter the host name for the host computer for the default Automation Service. This runs administrative jobs by default.
Example: back-end-services.portal.com
Automation Service Port
Enter the Automation Service port for the automation service being installed.
Example: 7777
Portal Database Connection Information
Specify connection information, such as host name, port, database name or service name, and administrative user information.
Document Repository Service - Application Port
Enter the port for the Document Repository Service being installed.
Example: 8020
Document Repository Service Host and Port
Enter the host name and port for the host computer for the Document Repository Service.
Example host name: back-end-services.portal.com
Example port: 8020
Pre-Installation Summary
Review the list of components to be installed.
Click Install.
Install Complete
Click Done.
Launching the AquaLogic Interaction Installer on Windows
To launch the AquaLogic Interaction installer on a Windows host:
Log into the Windows host as the local Administrator.
Copy the AquaLogicInteraction_v6-1_mp2.exe installer to a temporary location.
Close all unnecessary windows and applications.
Double-click AquaLogicInteraction_v6-1_mp2.exe to launch the installer.
Complete the installation wizard pages according to the settings you planned when you completed the configuration worksheets.
Completing the Installer Wizard Pages on Windows
The following tables describe the AquaLogic Interaction 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 your Web application server or to the AquaLogic Interaction components you are installing, the installer does not display the wizard page.
Table 4-2 AquaLogic Interaction Installer Wizard Pages for Windows
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.
Installation Folder
Accept the default installation folder or select a different folder in which to install AquaLogic Interaction.
Default: C:\bea\alui
Upgrade Information
Indicates previous installed versions of portal products.
Upgrade Option
Select either Upgrade or New Install. If you select Upgrade, the installer will automatically upgrade all of the components it detects needing an upgrade. The installer will skip most subsequent pages and request only the settings that cannot be extracted from the previous installation (for example, the type of install (.NET or Java) and the API Service information). The XML configuration file structure is also changed.
Note:
If you want to install a newer version of specific components on a machine with multiple portal components, you should perform a New Install. If you select New Install, you will proceed with the full set of appropriate installer pages.
Note:
If you choose to upgrade the portal, the installer upgrades all of the components it detects needing an upgrade. If you want to install a specific component on a machine with multiple portal components, you should perform a New Install.
Choose Install Set
Select either Complete or Custom. If you select Complete, a full set of AquaLogic Interaction components are installed. If you select Custom, you can select individual portal components to install according to your deployment plan.
Web Application Environment: .NET or Java
Select .NET (IIS) or Java.
Auto-Deployment to a Java Web Application Server
Select a web application server type to enable auto-deployment of the Portal, or select Manual to manually deploy the Portal to a web application server.
Tomcat Deployment Information
Enter the directory in which Web application configuration files reside.
Enter the WebLogic home directory, domain home, host name, port, domain, server, administrator user and administrator user password.
Note:
WebLogic domain and server names are case-sensitive. If the letter casing you enter does not match the running WebLogic domain and server, auto-deployment fails.
Click Help for further details on this installer wizard page.
Specify WebSphere Deployment Information
Enter the WebSphere home directory, host name, SOAP port and application server name.
Note:
If you change the default host or application server, the host and application server you enter must already exist.
Image Service: Auto-Deployment to Apache
Select Apache to have the Image Service automatically deployed to Apache. Select Manual if you prefer to use a Web server other than Apache.
Apache Deployment Information
Enter the Apache configuration directory.
Example directory: C:\Program Files\Apache Group\Apache2\conf\
Enter the Apache Windows service name.
Example name: Apache2
Select IIS Web Site
Select Use Default Web Site if you want the component or components being installed deployed to port 80, the default HTTP port.
Select Use another Web site if using port 80 would mean sharing the port with other applications and you do not want to do this.
Specify IIS Web Site Information
If you choose to deploy the portal to a Web site other than the default Web site, enter the IIS Web site name, HTTP and HTTPS ports you want to use for accessing the portal.
Example Web site name: ALI
Example HTTP port: 8082
Example HTTPS port: 9092
Note:
If the name you enter is not the name of an existing IIS Web site, a new Web site is created. If the Web site already exists, the secure and non-secure ports will be changed to the entries made in the installer.
Image Service Compression on IIS
The Enable Image Service HTTP Compression checkbox is selected by default. Deselect the checkbox if you do not wish to use HTTP compression.
Fully Qualified Domain Name and Ports
Enter the fully qualified domain name and port numbers for the Portal. Do not include the “http://” prefix.
Example domain name: portal.mycompany.com
Example HTTP port: 80
Example HTTPS port: 443
Content Upload Service - Application Port
Indicate either http or https.
Enter the port that the Content Upload Service should use to handle requests.
Example port: 11910
API Service - Application Port
Indicate either http or https.
Enter the port that the API Service should use to handle requests.
Example port: 11905
External Portal URL
Enter the URL to the portal that browsers outside of the local network would use.
Example: http://portal.mydomain.com:80/portal
API Service URL
Enter the URL to the API Service including the port number.
Example: http://wsserver.mydomain.com:11905
Image Service URL
Enter the URL for the Image Service, including the port number if it is not 80 or 443:
Enter the host name and port for the AquaLogic Interaction Search node through which the portal initiates contact with the Search Cluster.
Example host name: back-end-services.portal.com
Example port: 15250
Click Help for further details on this installer wizard page.
Stand-alone or Cluster
Select whether you would like to install a Single Stand-alone Search Node or add/replace a Search Cluster Node. Selecting to install the stand-alone search node installs a single node on the local machine. If you want to support failover, select to add/replace nodes for a search cluster.
Search Nodes
Select to add a new search node or replace an existing node.
Note:
Selecting to replace an existing node removes all information about the node that you are replacing.
Adding New Search Node
Enter the name and port number of the new search node.
The search node is installed into C:\bea\alui\ptsearchserver\6.1.
Search Cluster Files
Select the location of the search cluster files. You must have permission to access and write to the location where you want to install these files. Search cluster files are only installed if they do not already exist in the location that you select.
Enter the Windows user name that the search node will run as. This user must be in the Domain\User format and must have write access to the search cluster specified on the search cluster location that you specified on the Search Cluster Files installer wizard page.
Note:
The installer does not validate the user information that you specify.
Search Cluster Manager Port
Enter the port that the Search Cluster Manager will use.
Example: 15300
Default Automation Service Computer
Enter the host name for the host computer for the default Automation Service.
Example: back-end-services.portal.com
Automation Service Port
Enter the Automation Service port.
Example: 7777
Portal Database
Select SQL Server or Oracle.
Portal Database Connection Information
Specify connection information, such as host name, port, database name or service name, and administrative user information.
Document Repository Service - Application Port
Indicate either http or https.
Specify the port that the Document Repository’s Web components should use to handle requests.
Example: 8020
Document Repository Service Host and Port
Enter the host name and port for the host computer for the Document Repository Service.
Example host name: back-end-services.portal.com
Example port: 8020
Pre-Installation Summary
Review the list of components to be installed.
Click Install.
Install Complete
Choose to restart the system now or restart it manually. The system must be restarted to complete the installation.
Click Done.
Deploying the Image Service
Note:
This step is unnecessary if you installed AquaLogic Interaction for .NET, or if you instructed the installer to autodeploy the Image Service to Apache.
The Image Service is a collection of static, non-secure files that should be served by an HTTP server, such as Apache HTTP Server. The Image Service files are located in <PT_HOME>/ptimages/imageserver.
This directory should be aliased in your HTTP server configuration so that the URL specified for the Image Service when the installer was run is correct. For example, if you were running an Apache HTTP Server on port 8082, and you had specified http://webserver:8082/imageserver as your Image Service URL, you might configure Apache HTTP server as follows:
Note:
This is only an example. In a production environment the imageserver directory should be aliased to the Web server by a knowledgeable Web server administrator.
In a text editor, open the file
<APACHE_HOME>/conf/httpd.conf
Alias your <PT_HOME>/ptimages/imageserver directory to /imageserver/ on the Web server by adding the following:
Alias /imageserver/ “<PT_HOME>/ptimages/imageserver/”
Create a Directory entry for the imageserver directory:
<Directory “<PT_HOME>/ptimages/imageserver”> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory>
Save httpd.conf and exit the text editor.
(Unix only) Verify /opt/bea/alui/ptimages/imageserver is readable by Apache HTTP Server:
When Apache HTTP Server is restarted, http://webserver:8082/imageserver/ should point to <PT_HOME>/ptimages/imageserver/.
Scripting the Database
This section describes how to create the AquaLogic Interaction portal database. The procedure involves reviewing, editing, and executing SQL scripts against an Oracle 9i or 10g, or Microsoft SQL Server database. It is expected that the person setting up the AquaLogic Interaction database has a strong understanding of database system administration.
To set up the AquaLogic Interaction portal database, follow the steps in the subsection appropriate to your environment:
Creating and Configuring the Portal Database on Microsoft SQL Server 2000
To set up the Portal database on Microsoft SQL Server 2000:
Create the Portal database:
Set the Portal database name to the name you specified for the Portal database when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Verify that the initial size of the Portal database is sufficient for your AquaLogic Interaction deployment. For a relatively small installation, configure a database that is at least 100 MB. For a large enterprise with as many as 20,000 users, configure a database that is as large as 1 GB.
Create the Portal database user:
Create the Portal database user with the user name you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Configure the Portal database user to use SQL Server Authentication.
Set the Portal database user password to the password you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Set the Portal database user’s default database to the Portal database.
Grant the Portal database user the public and db_owner roles for the Portal database.
On the Portal database Properties | Permissions tab, grant the Portal database user all permissions on the Portal database.
Creating and Configuring the Portal Database on Microsoft SQL Server 2005
To set up the Portal database on Microsoft SQL Server 2005:
Configure the SQL Server instance to use SQL Server and Windows Authentication mode.
Create the Portal database:
Set the Portal database name to the name you specified for the Portal database when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Verify that the initial size of the Portal database is sufficient for your AquaLogic Interaction deployment. For a relatively small installation, configure a database that is at least 100 MB. For a large enterprise with as many as 20,000 users, configure a database that is as large as 1 GB.
Configure the Portal database to use SQL Server 2000 (80) compatibility level.
Create the Portal database user:
Create the Portal database user with the user name you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Configure the Portal database user to use SQL Server Authentication.
Set the Portal database user password to the password you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction 6.1 MP2.
Set the Portal database user’s default database to the Portal database.
Grant the Portal database user the sysadmin server role.
Scripting the Portal Database
Run the portal database scripts as the sa user on the portal database created above.
Note:
When database objects are created by the sa user, objects are owned by dbo. See Knowledge Base article DA_319052 for a discussion of the benefits of dbo object ownership.
To delete previous tables (if they exist) and create the tables required for the new portal components, run the <PT_HOME>\ptportal\6.1\sql\mssql\create_tables_mssql.sql script.
To create the portal objects required by the portal, run the <PT_HOME>\ ptportal\6.1\sql\mssql\load_seed_info_mssql.sql script.
To create the stored procedures required by the portal, run the <PT_HOME>\ptportal\6.1\sql\mssql\stored_procs_mssql.sql script.
To set configuration information required by the portal, run the <PT_HOME>\ptportal\6.1\sql\mssql\postinst_mssql.sql script.
Scripting an Oracle 9i Database on Unix
This section describes how to script an Oracle 9i database on Unix.
Setting Oracle Environment Variables
The following environment variables need to be set:
ORACLE_BASE: ORACLE_BASE should be set to the root directory of your Oracle installation. For example,
$ export ORACLE_BASE=/opt/oracle
ORACLE_HOME: ORACLE_HOME should be set to the home directory of your Oracle installation. For example,
$ export ORACLE_HOME=$ORACLE_BASE/ora92
ORACLE_SID: ORACLE_SID should be set to the system ID (SID) of your database instance. The default SID expected in the SQL scripts is PLUM on Oracle 9i. If you use a SID other than the default, the scripts will need to be edited. To set ORACLE_SID on Oracle 9i:
$ export ORACLE_SID=PLUM
These variables can be set automatically when your Oracle user logs in by modifying the .profile script for your Oracle user. For more information, consult your system administrator.
Copying SQL Scripts
When you install the Portal Server or Administrative Portal, the installer generates Oracle 9i scripts for creating and populating the database in the following directory:
<PT_HOME>/ptportal/6.1/sql/oracle_unix9.2
It is recommended that the scripts for your version of Oracle are copied to the following directory:
Create the PLUM10 directory under $ORACLE_BASE/oradata:
$ mkdir -p $ORACLE_BASE/oradata/PLUM
Create a link to initPLUM10.ora in $ORACLE_HOME/database
$ cd $ORACLE_HOME/database $ ln -s $ORACLE_BASE/admin/PLUM/plumtreescripts/initPLUM.ora
If this is a re-creation of a database or a retry of a prior failed attempt, delete the old database file. Verify that the database is not running, and then:
$ rm $ORACLE_BASE/oradata/$ORACLE_SID/*.*
From $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts, start sqlplus:
$ cd $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts $ sqlplus /nolog
Your prompt will change to SQL>.
Run the crdb1_oracle_unix.sql script to create and start the new database instance:
SQL> @crdb1_oracle_unix.sql
This script should generate no errors. The database should now be running. When the script completes, verify the following data files have been created in $ORACLE_BASE/oradata/$ORACLE_SID:
systPLUM.dbf
undo1A.dbf
temp1A.dbf (single disk installation only.)
Output from the script is saved in the file crdb1.lst in the plumtreescripts directory.
From sqlplus, run the crdb2_oracle_unix.sql script to create tablespaces, create the portal database user, and perform low level database tuning.
SQL> @crdb2_oracle_unix.sql
This script can take a significant amount of time to complete. The following errors may be generated:
ORA-00942 table or view does not exist ORA-1432/ORA-1434 public synonym to be dropped does not exist
These errors are acceptable. Any other errors are not acceptable.
When the script completes, verify the following data files have been created in $ORACLE_BASE/oradata/$ORACLE_SID:
PLUMtbl1.dbf
PLUMtmp1.dbf
PLUMidx1.dbf
Output from the script is saved in the file crdb2.lst in the plumtreescripts directory.
Connect to your database as a user with sysdba rights. From $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts, start sqlplus:
$ cd $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts
$ sqlplus /nolog
Your prompt will change to SQL>.
SQL> conn / as sysdba
Run create_ali_tablespace_unix.sql to create the ALUI tablespaces:
SQL> @create_ali_tablespace_unix.sql
Run create_ali_user_oracle.sql to create the schema user the portal will use:
SQL> @create_ali_user_oracle.sql
Scripting the Portal Database
The following steps initialize the new portal database:
Run the init_ali_db_oracle.sql script to create ALUI tables, indexes, and stored procedures. Exit sqlplus and log back in as the portal database user you just created. You should still be in the $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts directory:
$ sqlplus portal_database_user/password
The prompt should be SQL>. Now, run the init_ali_db_oracle.sql script:
SQL> @init_ali_db_oracle.sql
Output from the script is saved in the following files in the plumtreescripts directory:
create_tables_oracle.lst
stored_procs_oracle.lst
load_seed_info.lst
postinst.lst
If desired, create an Oracle SPFILE. Refer to Oracle documentation for the benefits of using an SPFILE.
Exit sqlplus and log back in using the /nolog parameter:
$ sqlplus /nolog
The prompt should be SQL>. Now, run the create_spfile_oracle_unix.sql script:
SQL> @create_spfile_oracle_unix.sql
Scripting an Oracle 9i Database on Windows
This section discusses how to script an Oracle 9i database on Windows.
Setting Oracle Environment Variables
The following environment variables need to be set:
ORACLE_BASE: ORACLE_BASE should be set to the root directory of your Oracle installation. For example, c:\oracle
ORACLE_HOME: ORACLE_HOME should be set to the home directory of your Oracle installation. For example, c:\oracle\ora92
ORACLE_SID: ORACLE_SID should be set to the system ID (SID) of your database instance. The default SID expected in the SQL scripts is PLUM on Oracle 9i. If you use a SID other than the default, the scripts will need to be edited.
After setting the environment variables, initialize the environment variables by rebooting the operating system.
Copying SQL Scripts
When you install the Portal Server or Administrative Portal, the installer generates Oracle 9i scripts for creating and populating the database in the following directory:
<PT_HOME>\ptportal\6.1\sql\oracle_nt9.2
It is recommended that the scripts for your version of Oracle are copied to the following directory:
Run the RegisterSIDPLUM.reg registry script. The script is found in the scripts directory you created in Copying SQL Scripts, and can be run from the command line:
> regedit RegisterSIDPLUM.reg
Create a directory PLUM under %ORACLE_BASE%\oradata.
Copy initPLUM.ora to %ORACLE_HOME%\database.
Run the CreateService.bat script with your SID and the portal database user password as arguments:
> CreateService.bat PLUM <password>
From %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts, start sqlplus with the /nolog flag:
> cd %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts
> sqlplus /nolog
Your prompt will change to SQL>.
Run the crdb1_oracle_nt.sql script:
SQL> @crdb1_oracle_nt.sql
This script should generate no errors.
When the script completes, make sure the following data files have been created in %ORACLE_BASE%\database:
systPLUM.dbf
undo1A.dbf
temp1A.dbf (single disk installation only)
Output from this script is saved in the file crdb1.LST.
Run the crdb2_oracle_nt.sql script:
SQL> @crdb2_oracle_nt.sql
This script may take a significant amount of time to complete, and may generate the following errors:
ORA-00942 table or view does not exist ORA-1432/ORA-1434 public synonym to be dropped does not exist
Any other errors are not acceptable.
When the script completes, verify the following data files have been created in %ORACLE_HOME%\database:
plumdata1.dbf
plumidx1.dbf
plumtmp1.dbf
Output from this script is saved in the file crdb2.LST.
Connect to your database as a user with sysdba rights. From %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts, start sqlplus:
> cd %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts
> sqlplus /nolog
Your prompt will change to SQL>.
SQL> conn / as sysdba
Run create_ali_tablespace_nt.sql to create the ALUI tablespaces:
SQL> @create_ali_tablespace_nt.sql
Run create_ali_user_oracle.sql to create the schema user the portal will use:
SQL> @create_ali_user_oracle.sql
Scripting the Portal Database
The following steps initialize the new portal database:
Run the init_ali_db_oracle.sql script to create ALUI tables, indexes, and stored procedures. Exit sqlplus and log back in as the portal database user you just created. You should still be in the %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts directory:
> sqlplus portal_database_user/password
The prompt should be SQL>. Now, run the init_ali_db_oracle.sql script:
SQL> @init_ali_db_oracle.sql
Output from the script is saved in the following files in the plumtreescripts directory:
create_tables_oracle.lst
stored_procs_oracle.lst
load_seed_info.lst
postinst.lst
If desired, create an Oracle SPFILE. Refer to Oracle documentation for the benefits of using an SPFILE.
Exit sqlplus and log back in using the /nolog parameter:
> sqlplus /nolog
The prompt should be SQL>. Now, run the create_spfile_oracle_nt.sql script:
SQL> @create_spfile_oracle_nt.sql
Starting the Oracle Listener for the Portal Database
Verify that the Oracle Listener has been started for the portal database.
Scripting an Oracle 10g Database on Unix
This section describes how to script an Oracle 10g Database on Unix.
Caution:
For installations of AquaLogic Interaction on HP-UX, it is necessary to adjust Oracle’s recommended kernel settings. The value of shmseg must be set higher than 300 to prevent Oracle memory allocation issues when search repair is run or multiple jobs are executed concurrently.
Setting Oracle Environment Variables
The following environment variables need to be set:
ORACLE_BASE: ORACLE_BASE should be set to the root directory of your Oracle installation. For example,
$ export ORACLE_BASE=/opt/oracle
ORACLE_HOME: ORACLE_HOME should be set to the home directory of your Oracle installation. For example,
ORACLE_SID: ORACLE_SID should be set to the system ID (SID) of your database instance. The default SID expected in the SQL scripts is PLUM10 on Oracle 10g. If you use a SID other than the default, the scripts will need to be edited.
To set ORACLE_SID on Oracle 10g:
$ export ORACLE_SID=PLUM10
These variables can be set automatically when your Oracle user logs in by modifying the .profile script for your Oracle user. For more information, consult your system administrator.
Copying SQL Scripts
When you install the Portal Server or Administrative Portal, the installer generates Oracle 10g scripts for creating and populating the database in the following directory:
<PT_HOME>/ptportal/6.1/sql/oracle_unix10
It is recommended that the scripts for your version of Oracle are copied to the following directory:
Create the PLUM or PLUM10 directory under $ORACLE_BASE/oradata:
$ mkdir -p $ORACLE_BASE/oradata/PLUM10
Create a link to initPLUM.ora in $ORACLE_HOME/database
$ cd $ORACLE_HOME/database $ ln -s $ORACLE_BASE/admin/PLUM10/plumtreescripts/initPLUM10.ora
If this is a re-creation of a database or a retry of a prior failed attempt, delete the old database file. Verify that the database is not running, and then:
$ rm $ORACLE_BASE/oradata/$ORACLE_SID/*.*
From $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts, start sqlplus:
$ cd $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts $ sqlplus /nolog
Your prompt will change to SQL>.
Run the crdb1_oracle_unix.sql script to create and start the new database instance:
SQL> @crdb1_oracle_unix.sql
This script should generate no errors. The database should now be running. When the script completes, verify the following data files have been created in $ORACLE_BASE/oradata/$ORACLE_SID:
systPLUM10.dbf
undo1A.dbf
temp1A.dbf (single disk installation only.)
Output from the script is saved in the file crdb1.lst in the plumtreescripts directory.
From sqlplus, run the crdb2_oracle_unix.sql script to create tablespaces, create the portal database user, and perform low level database tuning.
SQL> @crdb2_oracle_unix.sql
This script can take a significant amount of time to complete. The following errors may be generated:
ORA-00942 table or view does not exist ORA-1432/ORA-1434 public synonym to be dropped does not exist
These errors are acceptable. Any other errors are not acceptable.
When the script completes, verify the following data files have been created in $ORACLE_BASE/oradata/$ORACLE_SID:
PLUM10tbl1.dbf
PLUM10tmp1.dbf
PLUM10idx1.dbf
Output from the script is saved in the file crdb2.lst in the plumtreescripts directory.
Connect to your database as a user with sysdba rights. From $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts, start sqlplus:
$ cd $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts
$ sqlplus /nolog
Your prompt will change to SQL>.
SQL> conn / as sysdba
Run create_ali_tablespace_unix.sql to create the ALUI tablespaces:
SQL> @create_ali_tablespace_unix.sql
Run create_ali_user_oracle.sql to create the schema user the portal will use:
SQL> @create_ali_user_oracle.sql
Scripting the Portal Database
The following steps initialize the new portal database:
Run the init_ali_db_oracle.sql script to create ALUI tables, indexes, and stored procedures. Exit sqlplus and log back in as the portal database user you just created. You should still be in the $ORACLE_BASE/admin/$ORACLE_SID/plumtreescripts directory:
$ sqlplus portal_database_user/password
The prompt should be SQL>. Now, run the init_ali_db_oracle.sql script:
SQL> @init_ali_db_oracle.sql
Output from the script is saved in the following files in the plumtreescripts directory:
create_tables_oracle.lst
stored_procs_oracle.lst
load_seed_info.lst
postinst.lst
If desired, create an Oracle SPFILE. Refer to Oracle documentation for the benefits of using an SPFILE.
Exit sqlplus and log back in using the /nolog parameter:
$ sqlplus /nolog
The prompt should be SQL>. Now, run the create_spfile_oracle_unix.sql script:
SQL> @create_spfile_oracle_unix.sql
Scripting an Oracle 10g Database on Windows
Setting Oracle Environment Variables
The following environment variables need to be set:
ORACLE_BASE: ORACLE_BASE should be set to the root directory of your Oracle installation. For example, c:\oracle
ORACLE_HOME: ORACLE_HOME should be set to the home directory of your Oracle installation. For example, c:\oracle\ora10
ORACLE_SID: ORACLE_SID should be set to the system ID (SID) of your database instance. The default SID expected in the SQL scripts is PLUM10 on Oracle 10g. If you use a SID other than the default, you will need to edit the scripts.
After setting the environment variables, initialize the environment variables by rebooting the operating system.
Copying SQL Scripts
When you install the Portal Server or Administrative Portal, the installer generates Oracle 10g scripts for creating and populating the database in the following directory:
<PT_HOME>\ptportal\6.1\sql\oracle_nt10
It is recommended that the scripts for your version of Oracle are copied to the following directory:
Run the RegisterSIDPLUM10.reg registry script. The script is found in the scripts directory you created in Copying SQL Scripts, and can be run from the command line:
> regedit RegisterSIDPLUM10.reg
Create a directory PLUM10 under %ORACLE_BASE%\oradata.
Copy initPLUM10.ora to %ORACLE_HOME%\database.
Run the CreateService.bat script with your SID and portal database user password as arguments:
> CreateService.bat PLUM10 <password>
From %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts, start sqlplus with the /nolog flag:
> cd %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts
> sqlplus /nolog
Your prompt will change to SQL>.
Run the crdb1_oracle_nt.sql script:
SQL> @crdb1_oracle_nt.sql
This script should generate no errors.
When the script completes, make sure the following data files have been created in %ORACLE_BASE%\database:
systPLUM.dbf
undo1A.dbf
temp1A.dbf (single disk installation only)
Output from this script is saved in the file crdb1.LST.
Run the crdb2_oracle_nt.sql script:
SQL> @crdb2_oracle_nt.sql
This script may take a significant amount of time to complete, and may generate the following errors:
ORA-00942 table or view does not exist ORA-1432/ORA-1434 public synonym to be dropped does not exist
Any other errors are not acceptable.
When the script completes, verify the following data files have been created in %ORACLE_BASE%\database:
plumdata1.dbf
plumidx1.dbf
plumtmp1.dbf
Output from this script is saved in the file crdb2.LST.
Connect to your database as a user with sysdba rights. From %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts, start sqlplus:
> cd %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts
> sqlplus /nolog
Your prompt will change to SQL>.
SQL> conn / as sysdba
Run create_ali_tablespace_nt.sql to create the ALUI tablespaces:
SQL> @create_ali_tablespace_nt.sql
Run create_ali_user_oracle.sql to create the schema user the portal will use:
SQL> @create_ali_user_oracle.sql
Scripting the Portal Database
The following steps initialize the new portal database:
Run the init_ali_db_oracle.sql script to create ALUI tables, indexes, and stored procedures. Exit sqlplus and log back in as the portal database user you just created. You should still be in the %ORACLE_BASE%\admin\%ORACLE_SID%\plumtreescripts directory:
> sqlplus portal_database_user/password
The prompt should be SQL>. Now, run the init_ali_db_oracle.sql script:
SQL> @init_ali_db_oracle.sql
Output from the script is saved in the following files in the plumtreescripts directory:
create_tables_oracle.lst
stored_procs_oracle.lst
load_seed_info.lst
postinst.lst
If desired, create an Oracle SPFILE. Refer to Oracle documentation for the benefits of using an SPFILE.
Exit sqlplus and log back in using the /nolog parameter:
> sqlplus /nolog
The prompt should be SQL>. Now, run the create_spfile_oracle_nt.sql script:
SQL> @create_spfile_oracle_nt.sql
Starting the Oracle Listener for the Portal Database
Verify that the Oracle Listener has been started for the portal database.
Starting and Verifying the Installation
This section describes how to start AquaLogic Interaction and verify operation.
Starting AquaLogic Interaction Services and Search
Start the AquaLogic Interaction services and Search in the following order. All services may not be applicable to your portal installation.
To start AquaLogic Interaction services and Search on Unix:
Start the Search daemon:
cd to /opt/bea/alui/ptsearchserver/6.1/bin
run ./searchserverd.sh start
Start the Search Cluster Manager daemon:
cd to /opt/bea/alui/ptsearchserverl/6.1/adminui/bin
run ./clusterui.sh start
Start the Automation daemon:
cd to /opt/bea/alui/ptportal/6.1/bin
run ./automationserverd.sh start
Start the Document Repository daemon:
cd to /opt/bea/alui/ptdr/6.1/bin
run ./drserverd.sh start
Start the Content Upload daemon:
cd to /opt/bea/alui/ptupload/6.1/bin
run ./contentuploadd.sh start
Start the API daemon:
cd to /opt/bea/alui/ptws/6.1/bin
run ./apiserviced.sh start
To start AquaLogic Interaction services and Search on Windows:
Click Start > Control Panel > Administrative Tools > Services.
Start BEA ALI Search <host_name>, where <host_name> is the name of the machine where Search is installed.
Note:
It is important that third-party virus scanners do not attempt to scan the search service archives.
Start BEA ALI Search Cluster Manager.
Start BEA ALI Automation Service.
Start BEA ALI Document Repository Service.
Start BEA ALI Content Upload Service.
Start BEA ALI API Service.
Running the Diagnostics Script
Run the Diagnostic Script before starting your portal for the first time. It tests basic portal startup functionality. If there are issues with your AquaLogic Interaction installation, the Diagnostics Script will generate a list of warnings and recommendations on how to correct the issues.
Run the Diagnostics Script, follow the recommendations, and correct any issues before starting your portal for the first time.
On Unix, the script is <PT_HOME>/ptportal/6.1/bin/diagnostic.sh.
On Windows, the script is <PT_HOME>\ptportal\6.1\bin\diagnostic.bat. The script can also be launched by clicking Start | All Programs | BEA | Portal Diagnostic.
Starting the Portal
Start the portal by browsing to the server.pt application at the external portal URL you provided the AquaLogic Interaction installer. For example:
http://myportal.domain.com:80/portal/server.pt
Log in to the portal as Administrator with no password.
Caution:
You should change the default Administrator password as soon as possible. Make sure that you document the change and/or inform the appropriate portal administrators.
Importing the Search Cluster Manager Migration Package
This section describes how to import the Search Cluster Manager migration package.
Use the Migration - Import Utility (click Administration->Select Utility->Migration - Import) to import the SearchClusterAdminUI.pte file, which is located in the following location on the Search host machine:
On Unix: <PT_HOME>/ptsearchserver/6.1/serverpackages/
On Windows: <PT_HOME>\ptsearchserver\6.1\serverpackages\
If necessary, adjust any import settings.
For details on using the Migration - Import utility, see the online help or Administration Guide for BEA AquaLogic Interaction.
Note:
You may need to log out and back in to the portal in order to see the Search Cluster Manager. It appears in the Select Utility menu.
Importing the Content Upload Migration Package
This section describes how to import the Content Upload migration package.
Note:
You only need to import the Content Upload migration package if you performed a new (non-upgrade) install of AquaLogic Interaction and installed the Content Upload Service.
Use the Migration - Import Utility (click Administration->Select Utility->Migration - Import) to import the contentupload.pte file, which is located in the following location on the Content Upload Service host machine:
On Unix: <PT_HOME>/ptupload/6.1/serverpackages/
On Windows: <PT_HOME>\ptupload\6.1\serverpackages\
If necessary, adjust any import settings.
For details on using the Migration - Import utility, see the online help or Administration Guide for BEA AquaLogic Interaction.
Preparing the Portal for General Use
When you first deploy your portal, there are a number of tasks you must complete to prepare the portal for general use. These tasks are described in the Administrator Guide for AquaLogic Interaction because they are tasks you will likely perform more than once to maintain your portal. Refer to the Administrator Guide for AquaLogic Interaction for the following set-up tasks:
Configure display, navigation, and branding for the default experience definition and any additional experience definitions.
Change the default Administrator password and delegate administrator roles.
Populate the portal with administrative users and browsing users. Configure groups, users, user profiles, and Access Control Lists (ACLs) to enable managed access.
Populate the portal with documents. Configure ACLs to manage access.
Set up automated system maintenance, such as user synchronization, search updates, document refresh, and housekeeping jobs.
