> Installation and Upgrade Guide > Post-Installation Steps

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Post-Installation Steps

After you run the installer, complete the following steps:

Caution: Do not start the Publisher application until after you have imported the publisher.pte file in Step 2 below.
  1. Import the Workflow Database Schema into the Workflow database. For details, see Import the Workflow Database Schema.
  2. Register Publisher objects with the portal. For details, see Import the Publisher Migration Package.
  3. Start Publisher and Workflow. For details, see Start Publisher and Workflow
  4. Run the diagnostic tool to verify connectivity among Publisher components and the portal. For details, see Verify Your Publisher Installation.
  5. Import the published_content_portlets.pte file. This file provides you with templates that you can use to create portlets. For details, see Import the Published Content Portlets Migration Package.

 

Import the Workflow Database Schema

After you have installed the Publisher software, create the Workflow schema according to one of the following procedures:

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

Creating the Workflow Database Schema on SQL Server

To create the Workflow schema:

  1. Copy the <install_root>\ptworkflow\6.3\sql\mssql\create_schema.sql file from the Publisher host computer to the Workflow database host computer.
  2. On the Workflow database host computer, open the SQL Server Enterprise Manager and log into the Workflow database as the Workflow database user. For information on the Workflow database and database user, see Creating Databases and Database Users on SQL Server.
  3. Open and execute the create_schema.sql script.
  4. After the script has been run, open the Workflow tablespace and verify that the schema tables have been successfully created.

Creating the Workflow Database Schema on Oracle:

To configure an Oracle database for Workflow, create the database schema and increase the maximum number of cursors, as described in the following procedures.

To create the Workflow Server schema:

  1. Copy the script file from the host computer for Publisher to the host computer for the portal database.
  2. On the host computer for the Workflow database, open the Oracle Enterprise Manager Console.
  3. Change directory to the location of the Workflow schema scripts. <install_root>\ptworkflow\6.3\sql\oracle9.2 or <install_root>\ptworkflow\6.3\sql\oracle10
  4. Start SQLPlus.
  5. Log into the Workflow database instance as the Workflow database user. For information about the Workflow database user, see Creating Tablespaces and Database Users on Oracle.
  6. Type @create_schema.sql to execute the create_schema script.
  7. After the script has been run, open the Workflow tablespace and verify that the schema tables have been successfully created.

To increase maximum cursors:

  1. Log into the Oracle Enterprise Manager Console as a database administrator.
  2. Select your Workflow instance.
  3. Click Configuration.
  4. Click the All Initialization Parameters button.
  5. Look for open cursors and modify values from 300 to 10,000.

 

Import the Publisher Migration Package

Importing the publisher.pte file will create portal objects such as web services, content sources, and intrinsic portlets used by Publisher.

To migrate the Publisher .pte file:

  1. Make sure that the AquaLogic Interaction Administrative Portal and AquaLogic Interaction Search are running.
  2. Log into the Administrative Portal.
  3. Go to the Administration directory.
  4. From the Select Utility drop-down, choose Migration - Import.
  5. Click Browse and locate the publisher.pte file in <install root>\ptcs\6.3\serverpackages\. Click Open.
  6. Click Load Package.
  7. Select Overwrite Remote Servers.
  8. Click Finish.

 

Start Publisher and Workflow

Make sure the AquaLogic Interaction Search and Document Repository services are running before starting the Publisher service.

Starting Publisher

Windows:

From Services, select and start the BEA AquaLogic Publisher service.

Or, from the command line, run
$ <install base>\ptcs\6.3\bin\service.bat start

UNIX:

From the command line, run
$ <install base>/ptcs/6.3/bin/service.sh start

Starting Publisher as a Console Program

For debugging / troubleshooting purposes, you can start the Publisher service as a console program rather than in the background, so that startup messages (and errors if any) display directly in the console:

Windows:

From the command line, run
$ <install base>\ptcs\6.3\bin\service.bat console

UNIX:

From the command line, run
$ <install base>/ptcs/6.3/bin/service.sh console

On both Windows and UNIX, the console mode can be terminated by typing Ctrl-C in the console window.

Stoppping Publisher

To stop the Publisher ervice:

Windows:

From Services, select and stop the BEA AquaLogic Publisher Service.

From the command line, run
$ <install base>\ptcs\6.3\bin\service.bat stop

UNIX:

From the command line, run
$ <install base>/ptcs/6.3/bin/service.sh stop

 

Verify Your Publisher Installation

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

In a browser, access the Publisher diagnostics page:
http://<host>:<port>/ptcs/console/index.jsp
For example,
http://dev01.bea.com:7087/ptcs/console/index.jsp

Use the authentication ID and password you previously created. You should see no errors if there are no configuration problems and all supporting services (Search, Document Repository) are running.

You can also access the Workflow diagnostics page:
http://<host>:<port>/wfconsole
For example,
http://dev01.bea.com:7087/wfconsole

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

 

Import the Published Content Portlets Migration Package

Caution: Publisher must be running before you import this package.

In Publisher 6.3 the default portlet templates are installed under language subfolders: de, en, fr, etc. If you are upgrading from Content Server 5.x, your existing portlet templates are upgraded but not moved into the appropriate language folder. To make the portlet templates available under the language folder, you must delete the existing templates before importing the published_content_portlets.pte file.

In 5.x installs of Content Server without Branding, all six portlet templates are under the Published Content Portlets folder. In 5.x installs of Content Server with Branding, the Header, Footer, and Content Canvas portlet templates are under the Content Server | Branding folder and the News, Community Directory, and Announcement portlet templates are under the Content Server | Published Content Portlets folder.

To delete the 5.x portlet templates:

  1. Log into the Administrative Portal.
  2. Go to Administration.
  3. Browse to the Content Server | Published Content Portlets folder.
  4. Choose the existing default Content Server portlet templates and click Delete.
  5. If applicable, repeat the above process for any Content Server portlet templates in Content Server | Branding.

To import the Published Content Portlets migration package:

  1. Log into the Administrative Portal.
  2. Go to Administration.
  3. From the Select Utility drop-down choose Migration - Import.
  4. Click Browse and locate the published_content_portlets.pte file in <install root>\ptcs\6.3\serverpackages\. Click Open.
  5. Click Load Package.
  6. Click Finish.

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, 6.1, or 6.2, 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.


  Back to Top       Previous  Next