Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
WebSphere Portal Express logs
- Installation log files
- Migration log files
- i5/OS configuration log files
- Corrupted messages in log files
Using WebSphere Portal log files
WebSphere Portal Express 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:- Windows and Linux:
- i5/OS:
- /tmp/
- portal_server_root_prod/tmp/installshield
Files in this directory are stored only on the local System i5 machine.
You may be able to view them from a Windows machine by mapping a network drive to the System i5 machine.
- portal_server_root_prod/log
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 | Contains trace information that is generated by the installation program. | Check this log if the WebSphere Portal Express installation stops before successful completion. |
| wpinstalllog_base.txt | Contains trace information that is 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 this log if the WebSphere Portal Express installation onto a WebSphere Application Server base profile stops before successful completion. |
| installmessages.txt | Contains messages that are generated during installation.
The messages in this file are translated for the language that is specified during installation. | Check this log for errors generated during installation. |
|
LocalizeTrace.archive1.log
LocalizeTrace.archive2.log LocalizeTrace.archive3.log LocalizeTrace.archive4.log LocalizeTrace.archive5.log | Contain archive install/fixup messages. | Check this log for errors generated during the archive install/fixup.
These files are not used during an i5/OS installation. |
| log.txt | Contains trace information generated during the installation of WebSphere Application Server.
Located in app_server_root/logs directory for successful installs. Located in the temporary directory (%TEMP% on Windows or /tmp/ on UNIX) for unsuccessful installs. | Check this log if you have problems with the installation of WebSphere Application Server.
This file is not used during an i5/OS installation. |
Windows and Linux: 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. 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 | 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:- Windows and Linux:
- i5/OS:
Files in this directory are stored only on the local System i5 machine.
You may be able to view them from a Windows machine by mapping a network drive to the System i5 machine.
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 |
|---|---|---|
| MigrationTrace.log | Contains trace information that is generated by the migration process. | Check this log if migration stops before successful completion. |
| MigrationMessages.log | Contains messages that are generated during migration.
The messages in this file are translated for the language that is specified during installation. | Check this log for errors generated during migration. |
| migrationwizardlog.txt | Contains information that is generated by the migration wizard. | Check this log if the migration wizard stops before successful completion. |
i5/OS configuration log files
If you configured WebSphere Portal Express using the Install and Configure option of the installation program, the complete set of WebSphere Portal Express configuration log files are located in the UserData path of the directory...
portal_server_root_user/log
Some configuration log files may also appear in the ProdData path of the directory...
portal_server_root_prod/log
...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 this log 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 Express 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