# Installation and Upgrade Guide

# Installation

This chapter describes how to install Publisher. If you are upgrading Publisher, refer to Upgrade.

To install Publisher:

1. Verify that you have completed the installation prerequisites. For details, see Installation Prerequisites.
2. Install the Publisher components. For details, see Installing the Publisher Components.
3. Create the Workflow database schema. For details, see Creating the Workflow Database Schema.
4. Import the Publisher migration package. For details, see Importing the Publisher Migration Package.
5. Start and verify the Publisher installation. For details, see Starting and Verifying the Installation.
6. Import the Published Content Portlets migration package. For details, see Importing the Published Content Portlets Migration Package.

## Installing the Publisher Components

This section describes how to install the Publisher components. The Publisher components are:

- Image Service files
- Publisher

Note: | If you want to install the Image Service on a machine other than the Publisher host machine, you must also run the installer on that machine. Select Custom when the installer wizard asks you to choose components to install. Install the Publisher component on the Publisher host machine. Install the Image Service component on the machine hosting the Image Service.

Note: | You must create and configure the Publisher database and perform all post-installation steps before starting Publisher.

### Launching the Publisher Installer on Unix

The Publisher installer is a graphical X-Windows client when run in interactive mode. If you are running the installer on a remote terminal, verify that your DISPLAY is set appropriately.

To launch the Publisher installer on a Unix host:

1. Log in to the Unix host as the local administrator.
2. Copy the installer to a temporary location and run it as follows:

    $ ./ALIPublisher_v6-4

Complete the installation wizard pages according to the settings you planned when you completed the configuration worksheets provided in the Installation Worksheet for AquaLogic Interaction Publisher 6.4.

#### Completing the Installer Wizard Pages on Unix

The following table describes the Publisher installer wizard pages. The wizard pages that appear vary according to the selections you choose.

Note: | If the installer setting does not apply to the Publisher components you are installing, the installer does not display the wizard page.
Table 3-1 Publisher Installer Wizard Pages for Unix
Wizard Page | Description
--- | ---
Introduction | This installer wizard page provides a brief description of the installer.
License Agreement | Read and accept the license agreement.
Choose components | Select either Complete or Custom. A custom installation allows you to install Publisher and Image Service files on separate computers. Workflow and Publisher Search Libraries are automatically installed with Publisher.
Configuration | Select Full Configuration or Published Content Configuration. Full Configuration installs all Publisher functions on the current machine. If you want to load-balance published content, you can have one server host Publisher administrative functions and published content while additional servers host only published content. To do this, select Full Configuration for the administrative host machine and Published Content Configuration for each machine hosting only published content. For more information on setting up a Publisher instance for redirecting to published content, see Clustering.
Installation Folder | Accept the default installation folder or select a different folder in which to install Publisher. Default: `/opt/bea/alui`
License Directory | Enter the path to the location where you want to store the license.bea file. This location must be in $BEA_HOME$. Default: `$HOME/bea`
Existing License Update |
Note: | This panel appears if a license.bea file exists in the location specified in the License Directory panel.
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 places 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.
Application Host and Port | Enter the fully qualified domain name and port number that Publisher web components will use to handle requests. Indicate whether the components should use http or https. Example host: `publisher.mycompany.com` Example port: `7087`
Publisher Database Connection Information | Enter connection information for the Publisher database, such as host name, port, database service name, and administrative user information.
Workflow Database Connection Information | Enter connection information for the Workflow database, such as host name, port, database service name, and administrative user information.
Portal Database Connection Information | Enter connection information for the portal database. These are the database host name, port, service name, and database administrative user information that were created for the portal database when AquaLogic Interaction was installed.
Specify Image Service Folder | Enter the path to the Image Service folder. Example location: `/opt/bea/alui/ptimages`
Published Content | Select whether to use Defaults or Custom Configuration for published content.
Custom Published Content Configuration |
Note: | This panel appears if you selected Custom Configuration in the Published Content panel.
Publisher uses the Published Content URL to access published content. The Published Content Folder stores content published by Publisher. Default Published Content URL: `http://<machine_name>:<port>/publishedcontent` Default Published Content Folder: `<PT_HOME>/ptcs/publishedcontent`
Document Repository Service | Enter the fully qualified domain name and port number for the portal Document Repository Service. Example host: `doc-repository.mycompany.com` Example port: `8020`
Search Service | Enter the fully qualified domain name and port number for the Search Service. Example host: `searchhost.mycompany.com` Example port: `15250`
SMTP Notification Settings | Enter the name of the SMTP server and the notification email address that will be used for Workflow notification emails. Example host: `mail.mycorp.com` Example email address: `portaladmin@mycorp.com`
Authentication Information | Specify the authentication ID and password for the portal to use when it connects to Publisher. Default Authentication ID: `authenticationid`
Default Language | Select the language for searching Publisher objects.
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.

### Launching the Publisher Installer on Windows

To launch the Publisher installer on a Windows host:

1. Log in to the Windows host as the local Administrator.
2. Copy the ALIPublisherv6-4.exe installer to a temporary location.
3. Close all unnecessary windows and applications.
4. Double-click ALIPublisher6-4.exe to launch the installer.

Complete the installation wizard pages according to the settings you planned when you completed the configuration worksheets provided in the Installation Worksheet for AquaLogic Interaction Publisher 6.4.

#### Completing the Installer Wizard Pages on Windows

The following table describes the Publisher installer wizard pages. The wizard pages that appear vary according to the selections you choose.

Note: | If the installer setting does not apply to the Publisher components you are installing, the installer does not display the wizard page.
Table 3-2 Publisher Installer Wizard Pages for Windows
Wizard Page | Description
--- | ---
Introduction | This installer wizard page provides a brief description of the installer.
License Agreement | Read and accept the license agreement.
Choose components | Select either Complete or Custom. A custom installation allows you to install Publisher and Image Service files separately. Workflow and Publisher Search Libraries are automatically installed with Publisher.
Configuration | Select Full Configuration or Published Content Configuration. Full Configuration installs all Publisher functions on the current machine. If you want to load-balance published content, you can host Publisher administrative functions on one server and published content on another server or servers. To do this, select Full Configuration for the administrative host machine and Published Content Configuration for each machine serving only published content. For more information on setting up a Publisher instance for redirecting to published content, see Clustering.
Installation Folder | Accept the default installation folder or select a different folder in which to install Publisher. Default: `C:\bea\alui`
License Directory | Enter the path to the location where you want to store the license.bea file. This location must be in %BEA_HOME%. Default: `C:\bea`
Existing License Update |
Note: | This panel appears if a license.bea file exists in the location specified in the License Directory panel.
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 places 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.
Application Host and Port | Enter the fully qualified domain name and port number that Publisher web components will use to handle requests. Indicate whether the components should use http or https. Example host: `publisher.mycompany.com` Example port: `7087`
Publisher Database | Select either SQL Server or Oracle as the database Publisher will use.
Publisher Database Connection Information | Enter connection information for the Publisher database, such as host name, port, database service name, and administrative user information.
Workflow Database | Select either SQL Server or Oracle as the database Workflow will use.
Workflow Database Connection Information | Enter connection information for the Workflow database, such as host name, port, database service name, and administrative user information.
Portal Database | Select either SQL Server or Oracle as the database used by the portal.
Portal Database Connection Information | Enter connection information for the portal database, such as host name, port, database service name, and administrative user information.
Specify Image Service Folder | Enter the path to the Image Service folder. Example location: `c:\bea\alui\ptimages`
Published Content | Select whether to use Defaults or Custom Configuration for published content.
Custom Published Content Configuration |
Note: | This panel appears if you selected Custom Configuration in the Published Content panel.
Publisher uses the Published Content URL to access published content. The Published Content Folder stores content published by Publisher. Default Published Content URL: `http://<machine_name>:<port>/publishedcontent` Default Published Content Folder: `<PT_HOME>\ptcs\publishedcontent`
Document Repository Service | Enter the fully qualified domain name and port number for the portal Document Repository Service. Example host: `doc-repository.mycompany.com` Example port: `8020`
Search Service | Enter the fully qualified domain name and port number for the Search Service. Example host: `searchhost.mycompany.com` Example port: `15250`
SMTP Notification Settings | Enter the name of the SMTP server and the notification email address that will be used for Workflow notification emails. Example host: `mail.mycorp.com` Example email address: `portaladmin@mycorp.com`
Authenticaion Information | Specify the authentication ID and password for the portal to use when it connects to Publisher. Default Authentication ID: `authenticationid`
Default Language | Select the language for searching Publisher objects.
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.

## Creating the Workflow Database Schema

This section describes how to create the Workflow database schema on Oracle or Microsoft SQL Server. It is expected that the person setting up the Workflow database has a strong understanding of database system administration.

To create the Workflow database schema, follow the steps in the subsection appropriate for your environment:

- Creating the Workflow Database Schema on Microsoft SQL Server.
- Creating the Workflow Database Schema on Oracle.

There are no post-installation configuration steps for the Publisher database.

### Creating the Workflow Database Schema on Microsoft SQL Server

To create the Workflow schema on Microsoft SQL Server:

1. Copy the <PT_HOME>\ptworkflow\6.4\sql\mssql\create_schema.sql script from the Publisher host machine to the Workflow database host machine.
2. As the Workflow database user, run the create_schema.sql script on the Workflow database. For information on the Workflow database and database user, see the database creation section appropriate for your version of Microsoft SQL Server:

Creating and Configuring Databases on Microsoft SQL Server 2000 or

Creating and Configuring Databases on Microsoft SQL Server 2005.

### Creating the Workflow Database Schema on Oracle

To create the Workflow schema on Oracle:

1. Locate the appropriate version of the create_schema.sql script on the Publisher host machine:

<PT_HOME>/ptworkflow/6.4/sql/oracle9.2/create_schema.sql

<PT_HOME>/ptworkflow/6.4/sql/oracle10/create_schema.sql

2. Copy the create_schema.sql script to the Workflow database host machine.
3. As the Workflow database user, run the create_schema.sql script on the Workflow tablespace. For information on the Workflow database and database user, see Creating and Configuring Tablespaces on Oracle.
4. Increase the open cursors on the Workflow tablespace to 10,000.

## Importing the Publisher Migration Package

This section describes how to import the Publisher migration package. Importing the Publisher migration package creates portal objects such as Web services, content sources, and intrinsic portlets used by Publisher.

To import the Publisher .pte file:

1. Verify that AquaLogic Interaction Search is running.
2. From the Administration Select Utility drop-down list, use the Migration - Import utility to import the publisher.pte file, which is located in the following location on the Publisher host machine:

- On Unix: <PT_HOME>/ptcs/6.4/serverpackages/
- On Windows: <PT_HOME>\ptcs\6.4\serverpackages\

Select Overwrite Remote Servers. If necessary, adjust other import settings.

For details on using the Migration - Import utility, see Administration Guide for BEA AquaLogic Interaction.

## Starting and Verifying the Installation

This section describes how to start Publisher and verify operation.

### Starting Publisher

Note: | Verify that AquaLogic Interaction Search and the AquaLogic Interaction Document Repository are running before starting Publisher.

To start Publisher:

- On Unix: From the command line, run $ <PT_HOME>/ptcs/6.4/bin/service.sh start.
- On Windows, there are two options:

- From Services, select and start the BEA AquaLogic Publisher service.
- From the command line, run <PT_HOME>\ptcs\6.4\bin\service.bat start.

### Running the Diagnostic Utilities

To verify Publisher operation, run the diagnostic utilities included in the Publisher installation:

1. Browse to the Publisher diagnostics page:
   `http://<publisher_host>:<port>/ptcs/console/index.jsp`

Enter the authentication ID and password you created during installation in the authentication challenge box.

2. If you are licensed for and plan to use Workflow, browse to the Workflow diagnostics page:
   `http://<publisher_host>:<port>/wfconsole`

Enter the authentication ID and password you created during installation in the authentication challenge box.

Note: | If you are licensed for Publisher only to support portal branding, you do not need Workflow and may disable it. For information on disabling Workflow, see Knowledge Base article DA_222501, “Enabling and Disabling Workflow Server.”

Use the error messages to correct any configuration problems. For additional troubleshooting information, see Troubleshooting.

## Importing the Published Content Portlets Migration Package

This section describes how to import the published content migration package. Importing the published content migration package creates templates that you can use to create Publisher portlets.

To import the Published Content Portlets migration package:

1. Verify that Publisher is running.
2. From the Administration Select Utility drop-down list, use the Migration - Import utility to import the published_content_portlets.pte file, which is located in the following location on the Publisher host machine:

- On Unix: <PT_HOME>/ptcs/6.4/serverpackages/
- On Windows: <PT_HOME>\ptcs\6.4\serverpackages\

If necessary, adjust any import settings.

For details on using the Migration - Import utility, see Administration Guide for BEA AquaLogic Interaction.

After the migration is complete, a new folder called “Portlet Templates” appears in Publisher Explorer containing the Publisher objects that comprise the default portlet templates. If you are upgrading from 6.0 or higher, this folder is called “Portlet Templates (2).” You can delete the old “Portlet Templates” folder and reapply any customizations to the new objects in “Portlet Templates (2).” Default templates in the old “Portlet Templates” folder are no longer used, but existing portlets created from them will continue to work.