> Administrator Guide > Troubleshooting

Administrator 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

Troubleshooting

This appendix provides information on troubleshooting the Pathways in runtime. It includes the following topics:

 

Overview of Logs

This section provides the descriptions and locations of logs that you can use to troubleshoot the Pathways installation and Pathways in runtime. Individual log files are generated for each day's activity.

Runtime Logs

Table A-1 Logs Used to Troubleshoot Pathways in Runtime
Log
Description
Default Location and Platform
wrapper.log
Provides additional activity and error details for the BEA AL Pathways service, including details for these user interfaces:
  • Simple UI
  • Enhanced UI
  • Pathways Administration

Note: Wrapper.log is most useful for troubleshooting startup problems. Otherwise, we recommend that you use Logging Spy instead of wrapper.log to troubleshoot Pathways. Logging Spy is an ALI logging utility. For details, see the Logging Utilities documentation at http://download.oracle.com/docs/cd/E13174_01/alui/devtools.
  • install_dir\pathways\1.5\logs
    (Windows)
  • install_dir/pathways/1.5/logs
    (UNIX)

Individual log files are generated for each day's activity.

 

Troubleshooting Common Runtime Problems

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

Tip: To find the version number of your Pathways application, use the following URL: http://pathways_server_name:port_number/graffiti/ajax/version.do. For details on using the Pathways API to find the version number of your Pathways application, see http://download.oracle.com/docs/cd/E13183_01/en/alui/devdoc/docs6x/aluidevguide/con_pathwaysapi.html.

Table A-2 Common Runtime Problems and Solutions
Problem Description and Details
Cause and Solution
  • Problem: Users cannot submit content to the Knowledge Directory from their computers.
  • Details: Users can submit content from the Web, but not from their computers because the My Computer option is not visible.
  • Cause: You did not correctly configure Pathways to allow content submission from a local file source.
  • Solution: Correctly configure Pathways to allow content submission from a local file source. For details, see Configuring Pathways to Allow Content Submission From a Local File Source.
  • Problem: Unable to access Configuration Manager.
  • Cause 1: The Windows service for Configuration Manager is not running.
  • Solution 1: Ensure that the BEA AL Configuration Manager(port_number) service is running.
  • Cause 2: You are not accessing Configuration Manager by using the correct URL.
  • Solution 2: Access Configuration Manager by using the following URL: https://localhost:port_ number. Replace port_ number with the port number used by Configuration Manager. By default, Configuration Manager uses port number 12345. If the person who installed Pathways specified a port number other than 12345 on the Configuration Manager - Port and Password installation wizard page, use the port number that the person specified.

 

When to Use the Logging Utilities

When the Pathways portlets or the Pathways Administration UI display either an error or the Pathways diagnostic checks, the Pathways application or one or more of its required services may not be configured correctly. Use ALI Logging Utilities to help identify the specific issue by enabling Pathways and the required services as message senders within Logging Spy.

For more information about the Logging Utilities, see the Logging Utilities documentation at http://download.oracle.com/docs/cd/E13174_01/alui/devtools.


  Back to Top       Previous  Next