Open topic with navigation
The following section describes how to troubleshoot and verify your setup.
When you start the Content component, it logs the following message in the application log when the document tracking module loads correctly:
Starting document tracker
HPE IDOL Server logs messages about document tracking to the
Index log stream. To see these messages, set the
LogLevel parameter to
Full for this log stream.
To test the document tracking setup, you can create an IDX document to add to HPE IDOL Server. Make sure that you include the configured
UIDFieldName in your IDX. Alternatively, you can use a connector to generate the IDX and index it.
The following example IDX has the UID field configured as the
dtsample.idx #DREREFERENCE sample_idx_001 #DRETITLE A document to test document tracking #DREDBNAME Default #DREFIELD UID="001" #DREFIELD Myfield1="field1" #DREFIELD Myfield2="field2" #DRECONTENT Did it work? #DREENDDOC #DREENDDATANOOP
Index this document into your HPE IDOL Server, for example by using a
DREADD index action:
select statement to query for the document in your SQL back end. For example:
You might need to wait some time (30-40 seconds) for HPE IDOL Server to send records to your back end. After this time, if the document is not present, check the index log for SQL errors.
At the end of a test run, you might want to clean the database of tracking events. It is safe to delete entries from the
You must not clear the
Source table while IDOL components are running. Stop the components before clearing the
Source table or removing any entries from it.
If you retire an IDOL component, HPE recommends that you leave the entry in the
Source table, because existing records might refer to the source of the retired component.