Recommended Resources
Abstract
Collecting data for search-related problems with the IBM WebSphere Portal version 6.1. Gathering this information before calling IBM Support will help you understand the problem and save time analyzing the data.
Content
If you already contacted Support or you must collect data to determine the nature of a problem in WebSphere Portal regarding the Portal Search Engine (PSE) then review the following information as well as Collecting Data: Read first for WebSphere Portal.
Enable Search traces
Enable WCM Seedlist traces
Enable WCM Search traces
Enable Quickr Search traces
How to send data to IBM
Enable Search traces:
- Temporary(using the portal Admin console):
- Extended(Using the WAS Admin console):
I. Enable search traces on the portal server:
1. Go to Search Administration -> Manage Search -> Search Services
2. Select the "Edit Service" button next to "Default Portal Search Service"
3. Set the "Tracer" parameter to "on". Add this property if it does not exist.
4. Set the "DebugLevel" parameter to 50. (When disabling the trace, remember to set the parameter to zero (0) instead of a blank or <null> value.)
5. Enable the trace:
- Log in to the portal as administrator.
- From the Main Menu click Administration > Portal Analysis > Enable Tracing.
- Set the following traceString:
com.ibm.hrl.*=all:com.ibm.crawler.*=all:com.ibm.portal.search.*=all:com.ibm.lotus.search.*=all:com.ibm.siapi.search.*=all
- click Add
- Start server1 on the Portal Server node.
- Login to the Admin Console and select Servers-> Application Servers->
WebSphere_Portal > Diagnostic Trace service -> Change Log Detail Levels
- Under components section, enter this trace string:
com.ibm.hrl.*=all:com.ibm.crawler.*=all:com.ibm.portal.search.*=all:com.ibm.lotus.search.*=all:com.ibm.siapi.search.*=all
- Save changes and restart the Portal Server.
- II. Enable search traces on the remote search server:
- 1. Increase the log file size and the rotation size on the remote search server:
- a. Log into the Administrative Console of the remote search server (for example, server1).
b. Click on Servers->Application Servers -> (remote search server) -> Logging and Tracing ->JVM Logs -> Configuration.
c. Set File Size Maximum Size to 10 MB.
d. Set Maximum Number of Historical Log Files to 10.
Admin Console and select Servers-> Application Servers-> (remote search server) -> Diagnostic Trace service -> Change Log Detail Levels
Under components section, enter this trace string :
- com.ibm.hrl.*=all:com.ibm.crawler.*=all:
com.ibm.portal.search.*=all:com.ibm.lotus.search.*=all:
com.ibm.siapi.search.*=all
Enable WCM Seedlist Traces:
Use the same instructions above to enable these traces on portal server
- com.ibm.workplace.wcm.searchseed.*=finest:
com.ibm.lotus.search.providers.content.seedlist.*=finest:
com.ibm.workplace.wcm.seedlist.*=finest:
com.ibm.workplace.wcm.services.*=finest
Enable WCM Search Traces:
Use the same instructions above to enable these traces on portal server:
com.aptrix.pluto.cmpnt.*=finest:com.ibm.workplace.wcm.data.siapi.*=finest:
com.ibm.workplace.wcm.services.siapi.*=finest
Back to Top
Enable Quickr Search Traces:
1. Go to Search Administration -> Manage Search -> Search Services
2. Select the "Edit Service" button next to "Default Portal Search Service"
3. Set the "Tracer" parameter to "on". Add this property if it does not exist.
4. Set the "DebugLevel" parameter to 50. (When disabling the trace, remember to set the parameter to zero (0) instead of a blank or <null> value.)
5. Enable the trace:
- Temporary(using the portal Admin console):
- From the Main Menu click Administration > Portal Analysis > Enable Tracing.
- Set the following traceString: com.ibm.lotus.search.rcss.*=all
- click Add
- Extended(Using the WAS Admin console):
- Login to the Admin Console and select Servers-> Application Servers->
WebSphere_Portal > Diagnostic Trace service -> Change Log Detail Levels
- Under components section, enter this trace string:com.ibm.lotus.search.rcss.*=all
- Save changes and restart the Portal Server.
6. Recreate the problem.
Back to Top
After the traces are enabled and the scenario is duplicated successfully, send the following files to IBM Support for review:
Local search service files:
- 1. Collect the following files from the server:
- <WP_profile>/logs/<Portal_home>/SystemErr.log,
<WP_profile>/logs/<Portal_home>/SystemOut.log, and
<WP_profile>/logs/<Portal_home>/trace.log from the time frame of the problem.
2. Screen captures of the portlets showing the problem recreated.
Remote Search service files:
- 1. <WSAS_root>/profiles/wp_profile/log/<remote search server>/SystemErr.log
2. All <WSAS_root>/profiles/wp_profile/log/<remote search server>/SystemOut_{<timestamp>}.log
3. All <WSAS_root>/profiles/wp_profile/log/<remote search server>/trace.log
Back to Top
Send files to IBM Support by using the instructions outlined in Exchanging information with IBM Technical Support for problem determination.
Was this topic helpful?
Document Information
Modified date:
03 December 2021
UID
swg21319722