WebSphere Portal logs

 

+
Search Tips   |   Advanced Search

 

  1. Use WebSphere Portal log files
  2. Installation log files
  3. Migration log files
  4. i5/OS configuration log files
  5. Corrupted messages in log files

 

Use WebSphere Portal log files

WebSphere Portal has log files that are created during installation and run time. This section describes the content of the log files and recommendations for when to check the log files.

 

Installation log files

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

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.

This file 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 WebSphere Application Server base profile stops before successful completion.
installmessages.txt Messages generated during installation.

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

Check for errors generated during installation.
LocalizeTrace.archive1.log
LocalizeTrace.archive2.log
LocalizeTrace.archive3.log
LocalizeTrace.archive4.log
LocalizeTrace.archive5.log
Portal archive install and fixup messages. Check for errors generated during the portal archive install and fixup.

These files are not used during an iSeries installation.

log.txt Trace information generated during the installation of WAS.

For successful installs, located in...

app_server_root/logs

Located in %TEMP% (Windows) or /tmp (UNIX) for unsuccessful installs.

Check if you have problems with the installation of WAS.

This file is not used during an iSeries installation.

Windows and UNIX:

The following log files are located in the temp directory and are used during installation. We can access the directory by typing %temp% into the address field in the Explorer window. Note that the log files...

  • wpinstalllog.txt
  • wpsinstalllog.txt

...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

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

Log file name Description Problem symptoms
installtraces1.txt
installtraces2.txt
installtraces3.txt
Contain 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.

 

Migration log files

The migration log files are in the following directory:

Log file name Description Problem symptoms
MigrationTrace.log Trace information generated by the migration process. Check if migration stops before successful completion.
MigrationMessages.log Messages generated during migration. The messages in this file are translated for the language that is specified during installation. Check for errors generated during migration.
migrationwizardlog.txt Information generated by the migration wizard. Check if the migration wizard 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...

portal_server_root/log

Some configuration log files may also appear in the ProdData path of...

portal_server_root/log

...but these files do not contain log information on configuration performed after installation.

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 sent 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 Subset of...

LocalizeConfigTrace.log

...Contains actual commands entered.

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.

 

Related information

 

Parent topic:

Logging and tracing

 

Related tasks


Configure the WebSphere Portal server to recognize Lotus Domino and the Collaborative Services
Configure the WebSphere Portal server to recognize Lotus QuickPlace
Configure the WebSphere Portal server to recognize Lotus Sametime