# Installation and Upgrade Guide

# Troubleshooting

This chapter provides troubleshooting tips for installing and deploying Publisher. It includes the following sections:

- Reviewing Log Files
- Starting Publisher as a Console Program
- Running the Diagnostic Utilities
- Reviewing the Database Configuration Files
- Diagnosing Unexpected Results

## Reviewing Log Files

If installation fails and you are unable to complete the installer, follow the installer error messages to correct problems with software dependencies. In addition, the installer creates four separate log files and places them in the installation folder. The generated log files are listed below:

- AquaLogic_Interaction_Publisher_InstallLog.log
- content_register.log
- workflow_register.log
- imageserver_register.log (This is created only for Image Service installations).

If you encounter problems after installation, review the <PT_HOME>\ptcs\6.4\logs\container.log and <PT_HOME>\ptcs\6.4\logs\service.log files to help diagnose and correct the problem.

## Starting Publisher as a Console Program

For debugging and troubleshooting, you can start the Publisher service as a console program rather than in the background, so that startup messages and errors are displayed directly in the console:

On Unix, run $ <PT_HOME>/ptcs/6.4/bin/service.sh console.

On Windows, run <PT_HOME>\ptcs\6.4\bin\service.bat console.

## 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 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 using 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. Review the configuration decisions you recorded on the configuration worksheets provided in Installation Worksheet for AquaLogic Interaction Publisher 6.4 MP1 and re-run the installer.

## Reviewing the Database Configuration Files

Two Publisher database configuration files are populated with information you entered in the Publisher installer. Later, these files may be modified if you must change a database configuration setting. The files database.content.properties and database.portal.properties are installed in the following directory:

<PT_HOME>\ptcs\6.4\settings\config

Similarly, there is a Workflow database configuration file that is populated with information that you entered in the Publisher installer. This file, application.conf, is installed in the following directory:

<PT_HOME>\ptworkflow\6.4\settings\config

## Diagnosing Unexpected Results

This following table provides symptom-solution interpretations for unexpected results you might encounter when you install and deploy Publisher.

Table 4-2 Troubleshooting
Symptom | Possible Solution
--- | ---
The BEA AquaLogic Interaction Publisher Service does not start. | The BEA AquaLogic Interaction Publisher Service attempts to connect to port 1098, which may already be in use. To change the port: Open <PT_HOME>\ptcs\settings\config\container.conf with a text editor. Change plumtree.container.jboss.jndi.rmi.port=1098 to indicate an unused port, for example 10098. Restart the BEA AquaLogic Interaction Publisher Service.
After starting Publisher, the portlets time out and errors are displayed. These errors are most likely to occur when you start up Publisher the first time after it is installed. | The Java Server Pages (.jsp pages) in your application server were not precompiled before you started Publisher for the first time. Refresh the page to resolve the errors.
An error occurs when trying to publish content for which the publishing target is a drive mapped to a network shared folder. | Specify a UNC path instead of a mapped drive for the publishing target. For more information, see KB article DA_130773, “Problem Publishing Content Server Content To a Mapped Drive.”
Port conflict, port in use, BindException | Port numbers for HTTP and HTTPS are configured in <PT_HOME>/ptcs/6.4/settings/config/service.conf. Edit the HTTP and HTTPS settings in service.conf to set the value to an available port. The service must be restarted to pick up changes made in the configuration file. Note that changes to a service port number require corresponding changes to any Web service or remote server settings which may reference that port number.
Memory consumption, Out of Memory Errors | The maximum amount of memory, in megabytes, that the service JVM will be allowed to use is controlled by the wrapper.java.maxmemory property, configured in the file <PT_HOME>/ptcs/6.4/settings/config/service.conf. For example, the following line shows a maximum memory setting of 1 GB: wrapper.java.maxmemory=1024 The setting corresponds directly to the -Xmx parameter used by the java executable. The default value of this setting in the config file will be adequate for most configurations. For large production configurations, especially those in which the service is installed on a dedicated host machine, this value should be set as high as possible (e.g. 1024 or 1536) but should always remain below the amount of physical RAM on the host machine.