Enabling traces and Checking logs in websphere portal

Enabling traces and checking logs and configuration file information:

1. Access the WebSphere Application Server administrative console using http://hostname:port_number/ibm/console.
2. Go to Troubleshooting --> Logs and Traces --> Diagnostic Trace, and select the application server for your portal (WebSphere_Portal).
3. Click Diagnostic Trace --> Change log detail levels (make sure that the Enable Trace checkbox is selected).
4. Specify the required trace settings as follows:

Enable the following traces based on requirement

For issues with personalization in WebSphere Portal ( rules, campaigns, application objects ):
com.ibm.websphere.personalization.*=all:com.ibm.websphere.query.*=all

For issues with personalization and security:
com.ibm.webshere.personalization.=finest:
com.ibm.icm.ci.query.impl.ResultSetProcessor=finest:
com.ibm.icm.ci.query.impl.QueryProcessor=finest:com.ibm.wps.services.puma.=finest:
com.ibm.wps.puma.*=finest

For issues with personalization and Web Content Management (WCM):
com.ibm.websphere.personalization.*=all:com.ibm.websphere.query.*=all:
com.ibm.workplace.wcm.pzn.*=all:com.ibm.workplace.wcm.services.pzn.*=all

For issues with personalization and JCR:
com.ibm.websphere.personalization.*=all:com.ibm.websphere.query.*=all:
com.ibm.icm.*=finest:com.ibm.icm.ci.schema.impl.SchemaService=info

For issues with personalization authoring performance:
com.ibm.websphere.personalization.*=all:com.ibm.wps.caf.*=all

For issues with personalization runtime performance:
com.ibm.websphere.personalization.*=all

For issues with personalization publishing:
com.ibm.websphere.personalization.*=all

For configuration issues with personalization authoring environment
(Navigator Portlet, Editor Portlet, and List Portlet):
com.ibm.websphere.personalization.*=all:com.ibm.wps.caf.*=all

5. Save your updates.
6. Restart Portal.
a) Stop the Portal server.
b) Archive and delete the contents of the <WP_profile_root>/logs/WebSphere_Portal directory.
c) Start Portal.
7. Recreate the reported issue.
8. To disable tracing, specify the trace string, *=info, and restart Portal.

In the event that either the Trace.log or systemOut.log wrap, then increase the number of historical trace files to 20 and the number of historical systemOut.log files to 10.

To increase the number of historical files:

• Access the WebSphere Server administrative console using http://hostname:port_number/ibm/console.
• Navigate to Troubleshooting --> Logs and Traces --> WebSphere_Portal>Diagnostic Trace, and update the maximum number of historical files to 20.
• Navigate to Troubleshooting --> Logs and Traces --> WebSphere_Portal>JVM Logs, and update the maximum number of historical files to 10.
• Save the changes and restart.

Temporary tracing through the WebSphere Portal administration portlet:

Traces can be set for a temporary period by using the Enable Tracing administration portlet or the WebSphere Server administrative console. Use the following steps to set traces using the portlet:

1. Log into Portal as an administrator.
2. Go to Administration --> Portal Analysis --> Enable Tracing.
3. Type the required trace string into the "Append these trace settings" field as follows:
com.ibm.wps.caf.*=all: com.ibm.websphere.personalization.*=all
4. Click Add to update the "Current trace settings" field.

NOTE: Restarting Portal will remove traces that were set using the Enable Tracing Administration portlet.

To disable tracing:

1. Select the current trace settings and click Remove. In the example above, the current setting is
com.ibm.wps.caf.*=all: com.ibm.websphere.personalization.*=all=enabled

2. Type the trace string, *=info, into the "Append these trace settings" field and click Add. This trace string overwrites all settings listed under "Current trace settings" and resets to the default.