WebSphere Portal logs

 

+

Search Tips   |   Advanced Search

 

 

Installation log files

The WebSphere Portal installation log files are in...

 

Install Log Files

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.
wpinstalllog_base.txt Trace information generated by the installation program.

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

Check if the WebSphere Portal installation onto a WAS base profile stops before successful completion.
installmessages.txt Messages that are generated during installation. The messages in this file are translated for the language specified during installation. Check for errors generated during installation.
LocalizeTrace.archive1.log
LocalizeTrace.archive2.log
LocalizeTrace.archive3.log
LocalizeTrace.archive4.log
LocalizeTrace.archive5.log
Archive install/fixup messages. Check for errors generated during the archive install/fixup.

Not used during i5/OS installation.

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.

Not used during i5/OS installation.

 

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 %temp% into the address field in the Explorer window.

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

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

\Documents and Settings\user\Local Settings

For example...

C:\Documents and Settings\Administrator\Local Settings\Temp

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 if there are problems with component discovery and dependency checking.

 

Migration log files

Unless noted otherwise migration log files are located in...

Log file name Description Problem symptoms
MigrationMessages.log Messages that are generated by...

  • portal-pre-upgrade
  • portal-post-upgrade

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

Located in...

WP_PROFILE/PortalServer/log

If you use the WebSphere Portal V6.1 supplements CD (running on either Windows or UNIX) to do a remote migration this log file contains messages that are generated by portal-pre-upgrade, and is located as follows:

  • Windows: System Temp/
  • UNIX: /tmp/
Check if migration stops before successful completion.
MigrationTrace.log Trace information generated by the tasks...

  • portal-pre-upgrade
  • portal-post-upgrade

Located in...

WP_PROFILE/PortalServer/log

If you use the WebSphere Portal V6.1 supplements CD (running on either Windows or UNIX) to do a remote migration, this log file contains trace information that is generated by the portal-pre-upgrade task only, and is located as follows:

  • Windows: System Temp/
  • UNIX: /tmp/
Check if migration stops before successful completion.

 

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 portal_server_root_user/log. Some configuration log files may also appear in the ProdData path of the portal_server_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.

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

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 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 you install from a client that has the same locale as the server in order to avoid this problem.

 

Parent topic

Logging and tracing