WebSphere Portal logs

 

+

Search Tips   |   Advanced Search

 

Installation log files

The WebSphere Portal installation log files are in the following directory:

The table lists each file, describes the file content and recommends when to check the file for information that might assist in troubleshooting installation problems.

Log file name Description Problem symptoms
wpinstalllog.txt Trace information generated by the installation program. Check if the WebSphere Portal installation stops before successful completion.
installmessages.txt Messages generated during installation.

The messages in this file are translated for the language specified during installation.

Check for errors generated during installation.

LocalizeTrace.*.log

Archive installation or fixup messages.

The LocalizeTrace.archive5.log file is the log most likely to contain detailed tracing information.

Check for errors generated during the archive installation or fixup.
restoreConfig.log Trace information of the preconfigured WAS profile that WebSphere Portal uses. Check for errors generated during the installation step when WebSphere Portal initializes the WAS

During a successful installation, the restoreConfig.log file may contain what looks like an error but is actually not an error.

The following message is "normal" for WebSphere Portal and does NOT require a manual correction:

ADMU7006W: The cell name contained in the backup file is not the same as the current cell name of your configuration which is "cells\<yourcellname>\". Since you specified the "-force" option, the backup file will be restored but manually correct the resulting problems.
wplaunchlog.txt Trace information about the WebSphere Portal installation program launch. Check for errors generated during the launch of the installation GUI.
cmcfgdbu.log Trace information generated during the creation of the JCR tables in WebSphere Portal's database. Check if the creation of the JCR table fails.
finalfixup.log Trace information of additional installation and fixup steps.
log.txt Trace information generated during the installation of WAS.

Located in AppServer_root/logs directory for successful installs.

Located in the temporary directory (%TEMP% on Windows or /tmp/ on UNIX) for unsuccessful installs.

Check if you have problems with the installation of WAS.
wpinstalllog_base.txt Trace information generated by the installation program.

This file contains a copy of wpinstalllog.txt prior to the launch of the installation program, which then deletes wpinstalllog.txt.

Exists when the installation and configuration is done remotely from a Window workstation.

Check if the WebSphere Portal installation onto a WAS base profile stops before successful completion.
extractArchive.log Trace information generated when extracting jar files during the installation. Check if a jar file fails to extract during the installation.
VersionInfo.log Information about the product version. Check before upgrading to verify current product version.

Windows and UNIX:

The following log files are located in the temp   directory and are used during installation. You can access the directory by typing...

...into the address field in the Explorer window.

The wpinstalllog.txt and wpsinstalllog.txt log files that are previously described begin in the temp directory and are moved to PortalServer_root/log early in the installation.

Windows users:

The temp directory is typically located in a (hidden) path named...

For example...

You might need to set your folder options appropriately in order to view hidden files and directories.

Log file name Description Problem symptoms
installtraces1.txt installtraces2.txt installtraces3.txt Trace information generated by the dependency checking function.

Output is added to installtraces1.txt until it reaches a predefined size, at which point output goes into installtraces2.txt and then into installtraces3.txt. When installtraces3.txt is full, output reverts to installtraces1.txt and overwrites previous trace information.

Check these files if there are problems with component discovery and dependency checking.


i5/OS configuration log files

If you configured WebSphere Portal using the Install and Configure option of the installation program, the complete set of WebSphere Portal configuration log files are located in the UserData path of the PortalServer_root_user/log directory. Some configuration log files may also appear in the ProdData path of the PortalServer_root_prod/log directory, but these files do not contain log information on configuration performed after installation. For complete information, refer to the configuration log files contained in the UserData path of the directory.

The following files may prove useful when troubleshooting configuration problems.

This is not a complete list of the log files available.

Log file name Description Problem symptoms
LocalizeConfigTrace.log

LocalizeConfigTrace1.log

Contain trace information on the create-all-db configuration task. Output is added to LocalizeConfigTrace.log until it reaches a predefined size, at which point output goes into LocalizeConfigTrace1.log. When LocalizeConfigTrace1.log is full, output reverts to LocalizeConfigTrace.log and overwrites previous trace information. Check these logs if you have trouble creating databases.
LocalizeTrace.log LocalizeTrace.log is a subset of LocalizeConfigTrace.log and contains actual commands entered.

This file is overwritten if the installation program is run again.

Check for errors generated during installation.


Corrupted messages in log files

Corrupted messages in log files might occur if there are different locales set on the i5/OS server and the Windows client.

For example, if a user installs WebSphere Portal from a Japanese Windows client onto an i5/OS English server, the log files are unreadable.

Whenever possible, it is strongly recommended that install from a client that has the same locale as the server in order to avoid this problem.


Parent topic:

Log and tracing