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


This appendix provides information on troubleshooting the installation and configuration process. It includes the following topics:


Overview of Logs

This section provides descriptions and locations of logs that you can use to troubleshoot the installation of Pages and Pages in runtime.

Installation Log

The following log file provides activity and error details for the installation of Pages: install_dir\installlogs\AquaLogic_Pages_InstallLog.log.

Runtime Log

The following log file provides activity and error details for the BEA AquaLogic Pages service: install_dir\pages\1.0\logs\wrapper.log.


Troubleshooting Common Installation Problems

The table in this section describes common installation and configuration problems and provides solutions to them.

Table C-1 Common Installation and Configuration Problems and Solutions
The BEA AquaLogic Pages service is started, but I get an error when navigating to Pages from the portal.
  1. Look at wrapper.log for any errors that occur when accessing Pages from the portal.
  2. If you do not see any errors in wrapper.log, confirm that the BEA Automation and Search services have been started; Pages relies on those services to communicate with the portal.
  3. If the services are running, log in to the portal as an administrator, click Administration, open the Pages Objects folder, display the Remote Servers, click Pages Server, confirm that the port number in the Base URL is correct (the default port is 11990).
  4. If the port number is correct, copy the base URL into a browser address bar, then type /pages/ (for example http://pages_host:11990/pages/) and press ENTER. This should enable you to access Pages, bypassing the portal.
When I open the Pages application, I do not see any navigation.
Verify that the experience definition displayed for your user uses some type of horizontal navigation. For more information on navigation in Pages, see the Administrator Guide for AquaLogic Pages.
Security and Directory Service is consuming too much CPU.
Reduce the number of calls made to the Security and Directory Service by increasing the expiration time of login tokens. To do so, change the setting for the wsserver.DefaultSessionDurationInMinutes node in serverconfig.xml as desired.

  Back to Top       Previous  Next