Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
WebSphere Portal Express run-time logs
Use WebSphere Portal Express log files
IBM® WebSphere® Portal Express has log files that are created during run time. This section describes the content of the log files and recommendations for when to check the log files.
The run-time log files are:
WebSphere Portal Express run-time log file
The WebSphere Portal Express log file contains messages and trace information, if tracing is enabled. The default run-time log file is:- Windows and Linux:
portal_server_root/log/trace.log
- i5/OS:
portal_server_root_user/log/trace.log
Messages and trace information are contained in the same log file. Refer to the topic System event logging for details on how to configure logging and for information on the grammar of the "trace string" configuration key.
The following table describes trace loggers for particular situations and problem symptoms. Enabling the trace loggers can slow down WebSphere Portal Express.
The trace strings beginning with com.ibm.wps.* are extensions in the IBM portlet API.
| Area of concern | When to use | Trace string | Additional comments |
|---|---|---|---|
| Access Control | Enable this tracer if you want permissions for resources to be explained in detail, need to verify the correctness of a permission, or need to isolate a defect in access control. | com.ibm.wps.ac.*=all |
The traces are easier to evaluate while WebSphere Portal Express usage is low.
Enabling this logger creates very large log files. |
| Authentication |
com.ibm.wps.engine.*=all: com.ibm.wps.services.puma.*=all: com.ibm.wps.puma.*=all: com.ibm.wps.sso.*=all: com.ibm.wps.services.authentication.*=all | ||
| Command | Use to turn on all command trace loggers. | com.ibm.wps.commands.*=all | |
| Composition Model | Enable these messages if you want to get more information on how pages are constructed, need to verify page lists displayed on WebSphere Portal Express for correctness, or need to isolate an error in the WebSphere Portal Express aggregation component. |
com.ibm.wps.model.*=all: com.ibm.wps.composition.*=all |
The traces are easier to evaluate while WebSphere Portal Express usage is low.
Enabling this logger creates very large log files. |
| Credential Vault |
com.ibm.wps.sso.credentialvault.*=all: com.ibm.wps.command.credentialvault.*=all: com.ibm.wps.portletservice.credentialvault.*=all: com.ibm.wps.services.credentialvault.*=all: com.ibm.portal.portlet.service.credentialvault.*=all | ||
| Database | Deals with generated SQL statements and the internal flow in the WebSphere Portal Express database layer. |
com.ibm.wps.datastore.*=all: com.ibm.wps.services.datastore.*=all |
Enabling this logger will create very large log files. |
| Engine | Use to enable all engine trace loggers. | com.ibm.wps.engine.*=all | |
| General | com.ibm.wps.*=all
If you want to use general tracing but do not want render times to be displayed for such portlets, selectively disable tracing using the following trace string: com.ibm.wps.pe.PortletRenderTimeLoggingHelper=info
| When general tracing is enabled and parallel portlet rendering is turned on, portlets that are configured to be rendered in parallel will display the render time as part of the portlet content. | |
| Mail Service | Use to diagnose problems with the Mail Service. |
com.ibm.wps.services.mail.*=all | |
| Mapping URLs | Use to diagnose problems with the user-defined mappings of URLs |
com.ibm.wps.mappingurl.*=all: com.ibm.wps.command.mappingurl.*=all | |
| Personalization |
com.ibm.websphere.personalization.*=all com.ibm.dm.pzn.ui.*=all | When Personalization is installed outside of a WebSphere Portal Express server, Personalization will log using WebSphere Application Server tracing with the same trace strings. | |
| Document Manager |
com.ibm.wps.pdm.*=all=enabled com.ibm.content.*=all=enabled com.ibm.icm.*=all=enabled | ||
| WebSphere Portal Express Search | Use to turn on all WebSphere Portal Express Search messages. | com.ibm.portal.search=all | For detailed information refer to Logging and tracing in Portal Search. |
| Enable to obtain messages about URLs that are discovered by the crawler but could not be fetched and indexed for different reasons. | com.ibm.portal.search.notIndexed=all | ||
| Enable to obtain messages about the crawling process. | com.ibm.portal.search.crawler=all | ||
| Enable to obtain messages about failures that happen during a crawl. | com.ibm.portal.search.crawler.failure=all | ||
| Enable to obtain messages about the indexing process. | com.ibm.portal.search.index=all | ||
| Enable to obtain messages about failures that happen during the indexing process. | com.ibm.portal.search.index.failure=all | ||
| Portlet Container |
com.ibm.wps.pe.pc.*=all: org.apache.jetspeed.portlet.Portlet=all javax.portlet.Portlet=all | ||
| Portlet Environment |
com.ibm.wps.pe.ext.*=all: com.ibm.wps.pe.factory.*=all: com.ibm.wps.pe.om.*=all: com.ibm.wps.pe.util.*=all | ||
| Deployment |
com.ibm.wps.pe.mgr.*=all: com.ibm.wps.services.deployment.*=all: com.ibm.wps.command.applications.*=all: com.ibm.wps.command.portlets.*=all | ||
| Portlets | Use to diagnose problems with portlets. |
com.ibm.wps.portlets.*=all: org.apache.jetspeed.portlet.PortletLog=all | Enables tracing for all portlets. Therefore, place the suspect portlet on a separate page for testing. |
| Scripting Interface | Use this trace string to diagnose problems with the Portal Scripting Interface, or with application interface scripting, and the execution of such scripts. |
com.ibm.wps.scripting.*=all: | The traces are easier to evaluate while WebSphere Portal usage is low.
Enabling this logger can create large log files fast. |
| Selfcare | Use to diagnose problems with user registration and profile editing. |
com.ibm.wps.services.puma.*=all: com.ibm.wps.puma.*=all | Use this logger if there are errors in the sign-up, Edit My Profile, and the Manage Users and Groups portlets. |
| Services: EventBroker |
com.ibm.wps.services.registry.EventHandlerRegistry=all: com.ibm.wps.services.events.*=all | ||
| Services: Finder | Use for debugging the resolution of file names. | com.ibm.wps.services.finder.*=all | |
| Services: Loader | Use to trace the dynamic class loading performed by this service. | com.ibm.wps.services.ServiceManager=all | |
| ServicesNaming | Use to debug the lookup of objects by the naming service. | com.ibm.wps.services.naming.*=all | |
| ServicesNavigator | Use to diagnose problems with parts of page aggregation and display. | com.ibm.wps.services.navigator.*=all | |
| ServicesRegistry | Use to view the policies of the internal portlet object caching and watch it reload its content. | com.ibm.wps.services.registry.*=all | |
| Services | Use for switching on tracing for all services. | com.ibm.wps.services.*=all | |
| SSO | Use to turn on all SSO tracer loggers listed after this trace logger. | com.ibm.wps.sso.*=all | Use this logger if errors occur when use the Security Vault task on the Security page of the Administration pages. |
| WSRP administration | Use to diagnose problems occurring during the administration of Web Services for Remote Portlets (WSRP) with WebSphere Portal Express. |
com.ibm.wps.command.wsrp.*=all: com.ibm.wps.wsrp.cmd.*=all | |
| WSRP Consumer | Use to diagnose problems occurring during the use of WSRP with WebSphere Portal Express as a Consumer. | com.ibm.wps.wsrp.consumer.*=all | |
| WSRP Producer | Use to diagnose problems occurring during the use of WSRP with WebSphere Portal Express as a Producer. | com.ibm.wps.wsrp.producer.*=all | |
| XML configuration interface | Use to diagnose problems with the XML import/export of WebSphere Portal Express configurations. | com.ibm.wps.command.xml.*=all |
Related information