Verify the Setup
The following section describes how to troubleshoot and verify your setup.
Check IDOL Configuration
When you start the IDOL Content component, it logs the following message in the application log when the document tracking module loads correctly:
Starting document tracker
IDOL logs messages about document tracking to the Index
log stream. To see these messages, set the LogLevel
parameter to Full
for this log stream.
Index Content
To test the document tracking setup, you can create an IDX document to add to the IDOL Content component. 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 UIDFieldName
.
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 IDOL Content component, for example by using a DREADD
index action:
http://idol-server:9011/DREADD?dtsample.idx&IndexUID=test
Query Your Document
Run a 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 Content to send records to your back end. After this time, if the document is not present, check the index log for SQL errors.
Clean Results
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 Event
table.
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.
NOTE: If you retire an IDOL component, Micro Focus recommends that you leave the entry in the Source
table, because existing records might refer to the source of the retired component.