IBM Support

MustGather: IBM FileNet P8 Content Search Services (CSS) for Content Based Retrieval

Troubleshooting


Problem

Customer-provided background information (also known as "MustGather" data) helps in problem determination and shortens the time to resolution for customer cases. This technote provides a description of the background information IBM® Support needs to diagnose CSS related problems.

Diagnosing The Problem

Tab navigation

 
 
 
 

Collect MustGather data before opening a case to help IBM® Support quickly determine the root cause of the problem. With this information, Support can determine whether:

  1. This case concerns a known problem (rediscovery).
  2. This case describes a nondefect problem that can be identified and resolved.
  3. This case describes a known defect for which a workaround was developed.
  4. This case concerns a new problem and a fix is required.


If you already contacted support, continue on to the CBR (Content Based Retrieval) MustGather information. Otherwise, click MustGather: Read first for FileNet Content Engine



Content Based Retrieval MustGather information

This list describes the required troubleshooting information for Content Based Retrieval problems when using FileNet Content Search Services.
 
  1. Content Engine Server trace file (p8_server_trace.log.N or ce_traceN.log) with Error tracing and CBR tracing set at the Summary level. Collect tracing only when the problem occurs (you must clear the Moderate and Detail checkboxes to reduce the logging verbosity). We might come back and request logs at the Detail tracing level later, but for the first analysis Summary is sufficient. See FileNet Content Engine Server tracing for details on how to collect this information.
  2. All of the information described in MustGather: Read first for FileNet Content Engine
  3. Locate the Content Search Services installation location (the default location is typically \IBM\Content Search Services\CSS Server).
    1. From the \config folder, send these files:
        • *.xml
        • key.txt
        • *.properties
    2. From the config\defaults\ folder, send these files:
      • collection.xml
      • parser_config.xml
    3. From the config\defaults\ folder, send the file binary_recognizer_config.xml
    4. From the \log folder, send all the log files generated by CSS, that is, trace*.log, error*.log, monitor*.csv, serverconfiguration.log, and so on. If the default location for any of the logs was changed in the config files, then obtain the .log files from those locations as well. The logging locations are customized in the ecmts_logging.properties or ecmts_config_logging.properties in the \config folder.
  4. From either the web-based IBM Administration Console for Content Platform Engine or the Windows-MMC-based Content Engine FileNet Enterprise Manager, take screen shots of:
    1. All of the property tabs from each of the search server configurations that are listed on the IBM Search Servers tab in the P8 domain properties
    2. The Text Search Subsystem tab from the P8 domain properties
    3. The Text Search tab from the Object store properties
    4. The main properties tab of each CSS IndexArea from each object store that is CBR enabled

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Component":"Content Search Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.2.x;5.5.x","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Type":"MASTER","Line of Business":{"code":"","label":""},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS8K6B","label":"IBM Content Search Services"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
28 April 2023

UID

swg21472995

Page Feedback