iSeries Webserver Search Engine
Tracing Search Engine and Web Crawler
There are various traces that can be used to determine why errors are occurring with search or the web crawler. When you start either an Original or Apache server using STRTCPSVR with option "-vv", no information specific to search or the web crawler will be stored. However, this trace can be useful for errors related to the server configuration such as mapping or authorizations.
| Trace task |
How to start trace |
Comments |
Trace search calls and parameters
Trace crawling startup |
MKDIR '/GTRTRC' |
This trace is sent to stderr. If you are using search or crawling CL commands, run them in batch so that the trace statements will be sent to QPRINT spoolfile; otherwise trace statements are sent to the terminal session and will not be saved. If you are using the browser, set up an error log to catch the trace statements. |
| Trace a crawling sesion. |
MKDIR '/CRLTRC' |
Trace information is put into files /CRLTRC/TRCHTTPCRL.xxxxx. A new file is created for each crawling session. |
| Trace Net.Data macro processing |
See Trace Logging |
Monitor Net.Data as it is processing a macro. As Net.Data executes an HTML block, it will write out trace information that includes the functions being called, parameters being passed (both input and output), and errors that may be encountered. See note 1. |
| Trace HTTP server |
Manage HTTP Servers or STRTCPSVR with trace option |
See Run a trace on Set up logs on HTTP Server |
Note 1: To set up the trace, do the following on the green screen:
- CRTSRCPF FILE(QHTTPSVR/INI) MBR(DB2WWW) (The library specified depends on the library used for the DB2WWW.PGM.)
- Add: DTW_TRACE_MERGE_RECORDS=NO (This means that each job will have its own trace.)
| 
