Collecting Data: WebSphere Portal Search for version 6.1.x

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.

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:
• Temporary(using the portal Admin console):

- 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
• Extended(Using the WAS Admin console):

- 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.

6. Recreate the problem.

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.
2. Set the following traces on remote search server:
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
3. Save and restart the remote search 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

• Temporary(using the portal Admin console):

• Extended(Using the WAS Admin console):

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.
Indicate the relevant date and time to IBM Support in your communications. Use specific entries from the log to illustrate the problem if necessary.
2. Screen captures of the portlets showing the problem recreated.

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.

• Overview: WebSphere Portal Support
• Steps to getting support for WebSphere Portal
• Collecting Data: Read first for WebSphere Portal 6.1