IBM Support

Collecting Data: Searching in WebSphere Portal 7.0

Troubleshooting


Problem

Collecting troubleshooting data for search-related problems with IBM WebSphere Portal 7.0.

Resolving The Problem

If you already contacted IBM Product Support and must collect data to determine the nature of a problem in WebSphere Portal, review the information below for the available methods of data collection. Otherwise, review Collecting Data: Read first for WebSphere Portal 7.0.

Enabling Search traces

A. Enable search traces on the Portal server (Portal cluster):

    1. Clear all the logs.

    2. Increase the log file size and the rotation size for the Portal JVM:
      a. Log into the Administrative Console/ DM console of the Portal server
      b. Go to Servers --> Application Servers --> (WebSphere_Portal) --> Logging and Tracing --> JVM Logs --> Configuration.
      c. Set File Size Maximum Size to 20 MB.
      d. Set Maximum Number of Historical Log Files to 50.
    3. Enable tracing.
      • Temporary (using the Portal Admin console):
        - Log into Portal as an administrator.
        - From the menu, go to 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
          - Set the following traceString only when problem involves crawling the Portal site:
            com.ibm.lotus.search.providers.content.seedlist.retriever.portal.*=all
        - click Add.
      • Extended (uses the WebSphere Application Server Admin console):
        - Start server1 on the Portal server node.
        - Log into the Admin console and select Servers --> Application Servers --> WebSphere_Portal --> Diagnostic Trace service --> Change Log Detail Levels.
        - In the 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 the changes and restart the Portal Server.
    4. Provide the time to recreate to IBM Product Support.

B. Enable search traces on the remote search server:
    1. Clear all the logs.

    2. Increase the log file size and the rotation size on the remote search server:
      a. Log into the Admin console of the remote search server (for example, server1).
      b. Go to Servers --> Application Servers --> (remote search server) --> Logging and Tracing --> JVM Logs --> Configuration.
      c. Set File Size Maximum Size to 20 MB.
      d. Set Maximum Number of Historical Log Files to 50.

    3. Enable traces on remote search server JVM:
      a. Go to the Admin console and select Servers --> Application Servers --> (remote search server) --> Diagnostic Trace service --> Change Log Detail Levels.
      b. In the Components section, enter this trace string:
        com.ibm.hrl.*=all:com.ibm.crawler.*=all
    4. Save the changes and restart the Portal Server.

    5. Recreate the problem and provide the time to recreate to IBM Product Support.

Enabling Quickr Search Traces

    1. Clear all the logs.

    2. Increase the log file size and the rotation size for the Portal JVM:
      a. Log into the Admin console/ DM console on the Portal server.
      b. Go to Servers --> Application Servers --> (WebSphere_Portal) --> Logging and Tracing --> JVM Logs --> Configuration.
      c. Set File Size Maximum Size to 20 MB.
      d. Set Maximum Number of Historical Log Files to 50.
    3. Enable tracing.
    • Temporary (using the Portal Admin console):
      - Log into Portal as an administrator.
      - From the menu, go to Administration --> Portal Analysis --> Enable Tracing.
      - Set the following traceString:
        com.ibm.lotus.search.rcss.*=all
      - Click Add.
    • Extended (uses the WebSphere Application Server Admin console):
      - Start server1 on the Portal Server node.
      - Log into 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 the changes and restart the Portal Server.
    4. Recreate the problem and provide the time to recreate to IBM Product Support.

After tracing is enabled and you've duplicated the scenarios successfully, collect the following files to provide to IBM Support for review:
    Files from the Portal server or cluster:

    1. Collect the following files from the Portal server:
      <WP_profile>/logs/<Portal_home>/SystemErr.log,
      <WP_profile>/logs/<Portal_home>/SystemOut.log
      ,
      <WP_profile>/logs/<Portal_home>/trace.log from the time frame of the problem.
      <wp_profile_root>/PortalServer/log/VersionInfo.log

      Indicate the relevant date and time in your communications. Use specific entries from the log to illustrate the problem if necessary.
    2. Send screen captures of the portlets showing the recreated problem.

    3. Provide the time to recreate.

    Files from remote search server:

    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

    4. Provide the time to recreate.
Follow the instructions to send diagnostic information to IBM Product Support. Be sure to provide all diagnostic information captured above. This requires that a PMR be opened if not already.

Refer to the detailed instructions in "Exchanging information with IBM Technical Support for problem determination" to make the information available and to update your problem record.

Related information

[{"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Business Unit":{"code":"BU012","label":"WCE"},"Component":"Problem Determination","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.0","Edition":"Enable;Extend;Server;Express;Hypervisor Edition"}]

Document Information

Modified date:
28 August 2018

UID

swg21469683