WebSphere Portal logs

 

+
Search Tips   |   Advanced Search

 

  1. Installation log files
  2. Configuration log files
  3. Runtime log file

 

Installation log files

The installation log files are in...

/QIBM/ProdData/PortalServer5/log

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.
wpsinstalllog.txt Trace information generated by the WebSphere Portal component during installation. Check for errors related to the WebSphere Portal component.
responselog.txt Values entered by the user when installing WebSphere Portal. This file may be used as a response file to duplicate the installation at a later time.

 

Configuration log files

The WebSphere Portal configuration log files are located in...

/QIBM/UserData/WebAS5/Base/<instance>/PortalServer5/log

If you used IBM Web Adminstration for iSeries to configure WebSphere Portal, configuration log files are instead located in...

/QIBM/UserData/WebAS5/Base/<instance>/logs/<instance>

Log files generated by configuring with IBM Web Adminstration for iSeries use the following naming convention: 

   WPSWIZARD_<timestamp>_<filename.log>

If you used the Install and Configure option when installing WebSphere Portal, some configuration log files may also appear in...

/QIBM/ProdData/PortalServer5/log

These files do not contain log information on configuration performed after installation. See the configuration log files in...

/QIBM/UserData/WebAS5/Base/<instance>/PortalServer5/log

Log file name Description Problem symptoms
addwpsinst.log Trace information on adding WebSphere Portal to the WAS instance. Check if you notice any WebSphere Portal files missing from the instance directory.
ConfigTrace.log
ConfigMessages.log
ConfigTrace1.log 		Trace information on the create-all-db and basic-config configuration task. Check these logs if you have trouble creating databases or configuring WebSphere Portal with the basic-config task.
portletinstall.log Trace information on portlet deployment. Check if any portlets fail to deploy.
responselog.txt Values entered by the user when installing and configuring WebSphere Portal. This file may be used as a response file to duplicate the installation at a later time.

 

 

WebSphere Portal runtime log file

The WebSphere Portal log file contains messages and trace information, if tracing is enabled. The default runtime log file is:

/QIBM/UserData/WebAS5/Base/<instance>/PortalServer5/log/wps_<date_time>.log

For example...

/qibm/userdata/webas5/base/WAS5Portal/PortalServer5/log

Messages and trace information are contained in the same log file. Message logging is always enabled. Trace logging is enabled by setting properties in...

/QIBM/UserData/WebAS5/Base/<instance>/PortalServer5/shared/app/config/log.properties

The default setting is that trace logging is disabled. Settings in this file are applied whenever WebSphere Portal is running. However, if you want to set logging options for the current session only, use the Enable Tracing page in the WebSphere Portal Administration pages.

The following table describes trace loggers for particular situations and problem symptoms. Enabling the trace loggers can slow down WebSphere Portal.

Component When to use Trace string Additional comments
AccessControl 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=enabled The traces are easier to evaluate while WebSphere Portal usage is low.
Authentication   com.ibm.wps.engine.commands.*=all=enabled:
com.ibm.wps.services.puma.*=all=enabled:
com.ibm.wps.puma.*=all=enabled:
com.ibm.wps.engine.servlet=all=enabled:
com.ibm.wps.sso.*=all=enabled 		 
Command Turn on all command trace loggers. com.ibm.wps.command.*=all=enabled  
Composition Enable these messages if you want to get more information on how pages are constructed, need to verify page lists displayed on WebSphere Portal for correctness, or need to isolate an error in the WebSphere Portal aggregation component. com.ibm.wps.composition.*=all=enabled The traces are easier to evaluate while WebSphere Portal usage is low.
CredentialVault   com.ibm.wps.sso.*=all=enabled:
com.ibm.wps.command.credentialvault.*=all=enabled:
com.ibm.wps.portletservice.credentialvault.*=all=enabled
 
Database Deals with generated SQL statements and the internal flow in the WebSphere Portal database layer. com.ibm.wps.datastore.*=all=enabled:
com.ibm.wps.services.datastore.*=all=enabled
Important: Enabling this logger will create very large log files.
EngineCommands Diagnose problems with logging in, enrollment, and WebSphere Portal navigation. com.ibm.wps.engine.commands.*=all=enabled  
Engine Enable all engine trace loggers. com.ibm.wps.engine.*=all=enabled  
EngineTags Diagnose problems with tags within Java Server Pages. com.ibm.wps.engine.tags.*=all=enabled  
EngineTemplates Diagnose problems with internationalization and selecting device-dependent templates. com.ibm.wps.engine.templates.*=all=enabled  
FrameworkObjectModel com.ibm.wps.model.impl.*=all=enabled:
com.ibm.wps.composition.Composition=all=enabled:
com.ibm.wps.composition.CompositionMap=all=enabled:
com.ibm.wps.model.invalidation.*=all=enabled:
com.ibm.wps.model.factory.*=all=enabled
Enables tracing for all portlets. Therefore, place the suspect portlet on a separate page for testing.
General com.ibm.wps.*=all=enabled

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=all=disabled

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.
LoggingIn com.ibm.wps.puma.*=all=enabled:
com.ibm.wps.services.puma.*=all=enabled:
com.ibm.wps.engine.commands.*:
com.ibm.wps.sso.*=all=enabled
Note: The values above have to be set in the log.properties file as one line without blanks or line feeds between the sections.
MappingURLs Diagnose problems with the user-defined mappings of URLs com.ibm.wps.mappingurl.*=all=enabled:
com.ibm.wps.command.mappingurl.*=all=enabled
 
ModelFactory com.ibm.wps.model.factory.*=all=enabled  
ModelInvalidation com.ibm.wps.model.invalidation.*=all=enabled  
Model com.ibm.wps.model.impl.*=all=enabled:
com.ibm.wps.composition.Composition=all=enabled:
com.ibm.wps.composition.CompositionMap=all=enabled
 
PageAggregation com.ibm.wps.composition.*=all=enabled:
com.ibm.wps.services.navigator.*=all=enabled
 
PortletContainer com.ibm.wps.pe.pc.*=all=enabled:
org.apache.jetspeed.portlet.Portlet=all=enabled
 
PortletEnvironment com.ibm.wps.pe.ext.*=all=enabled:
com.ibm.wps.pe.factory.*=all=enabled:
com.ibm.wps.pe.om.*=all=enabled:
com.ibm.wps.pe.util.*=all=enabled
 
PortletManager com.ibm.wps.pe.mgr.*=all=enabled:
com.ibm.wps.services.deployment.*=all=enabled:
com.ibm.wps.command.applications.*=all=enabled:
com.ibm.wps.command.portlets.*=all=enabled
 
Portlets Diagnose problems with portlets. com.ibm.wps.portlets.*=all=enabled:
org.apache.jetspeed.portlet.PortletLog=all=enabled
Enables tracing for all portlets. Therefore, place the suspect portlet on a separate page for testing.
Registration Diagnose problems with user registration and profile editing. com.ibm.wps.services.puma.*=all=enabled:
com.ibm.wps.puma.*=all=enabled
Use this logger if there are errors in self-registration, self-care and the Manage Users and Groups portlet.
ServicesDataStore Logs the transaction handling of the WebSphere Portal datastore service. com.ibm.wps.services.datastore.*=all=enabled Important: Enabling this logger will create very large log files.
ServicesDispatcher Use for observing the calling of JSPs. com.ibm.wps.services.dispatcher.*=all=enabled  
ServicesEventBroker   com.ibm.wps.services.registry.EventHandlerRegistry=all=enabled:
com.ibm.wps.services.events.*=all=enabled
 
ServicesFinder Use for debugging the resolution of filenames. com.ibm.wps.services.finder.*=all=enabled  
ServicesLoader Trace the dynamic class loading performed by this service. com.ibm.wps.services.ServiceManager=all=enabled  
ServicesLocalizer Logs the WebSphere Portal default locale during initialization. com.ibm.wps.services.localizer.*=all=enabled  
ServicesNaming Debug the look up of objects by the naming service. com.ibm.wps.services.naming.*=all=enabled  
ServicesNavigator Diagnose problems with parts of page aggregation and display. com.ibm.wps.services.navigator.*=all=enabled  
ServicesRegistry View the policies of the internal portlet object caching and watch it reload its content. com.ibm.wps.services.registry.*=all=enabled  
Services Use for switching on tracing for all services. com.ibm.wps.services.*=all=enabled  
SiteAnalyzer Trace problems with logging site analysis logging data for the portal. com.ibm.wps.services.siteanalyzer.*=all=enabled  
SSOCredentialVault   com.ibm.wps.sso.credentialvault..*=all=enabled  
SSO Turn on all SSO tracer loggers listed after this trace logger. com.ibm.wps.sso.*=all=enabled Use this logger if errors occur when use the Security Vault task on the Security page of the Portal Administration pages.
SSOVaultService   com.ibm.wps.sso.vaultservice.*=all=enabled  
UserManagement Trace problems with the user subsystem, such as problems with logging in, enrollment and access control. com.ibm.wps.services.puma.*=all=enabled:
com.ibm.wps.puma.*=all=enabled:
com.ibm.wps.command.puma.*=all=enabled
 
XMLAccess Diagnose problems with the XML import/export of WebSphere Portal configurations. com.ibm.wps.command.xml.*=all=enabled  

 

See also