The creation of Tombstones for AssemblyLines and Config Instances is configured by means of check boxes in a number of screens in the Configuration Editor (CE), as well as a number of options in the global.properties or solution.properties files.
Once configured, your Configs contain the following switches:
Checking Create Tombstones cause tombstones to be generated for this AssemblyLine when runs, even when the master switch for AssemblyLines is disabled.
When AssemblyLine Tombstones are disabled using the Configuration option shown above, tombstone generation can still be enabled individually per AssemblyLine by using the appropriate option in the AssemblyLine configuration screen, Create Tombstones.
A sample tombstone record could look like this:
|Component Type ID||1|
|Event Type ID||0|
|add||Total number of entries the AssemblyLine has added (performed by Connectors in AddOnly mode)|
|mod||Total number of entries the AssemblyLine has modified (performed by Connectors in Update mode)|
|del||Total number of entries the AssemblyLine has deleted. (performed by Connectors in Delete mode)|
|get||Total number of entries the AssemblyLine has retrieved (performed by Connectors in Iterator mode)|
|request||Total number of requests accepted when there is a Server mode Connector in the AssemblyLine|
|callReply||Total number of Call/Reply operations the AssemblyLine has executed (performed by Connectors in CallReply mode)|
|err||Total number of errors encountered|
|skip||Total number of entries the AssemblyLine has skipped entries|
|lookup||Total number of Lookup operations the AssemblyLine has executed (performed by Connectors in Update/Delete/Lookup mode)|
|ignore||Total number of entries the AssemblyLine has ignored (performed by Connectors in Update/Delta mode)|
|reconnect||Total number of times the AssemblyLine has attempted to reconnect to another client|
|exception||The exception text if the AssemblyLine terminated with an exception|
|getTries||Total number of times the AssemblyLine has attempted to retrieve an entry (performed by Connectors in Iterator mode)|
|getclientTries||Total number of times the AssemblyLine has attempted to get the next connected client (performed by Connectors in Server mode)|
|nochange||Total number of entries the AssemblyLine processed but left unchanged|
|branchtrue||Total number of Branch components executed by the AssemblyLine because their expression evaluated to true|
|branchfalse||Total number of Branch components skipped by the AssemblyLine because their expression evaluated to false|
|loopstart||Total number of Loop components executed by the AssemblyLine|
|loopcycles||Total number of cycles executed for all Loop components that had more than one cycle in an AssemblyLine|
|reconnectTime||Time in ms after last reconnect was attempted by the AssemblyLine|
The Tombstone Manager monitor the number of tombstone records at runtime and delete old records as per the values of the com.ibm.di.tm.autodel.age, com.ibm.di.tm.autodel.records.trigger.on, com.ibm.di.tm.autodel.records.max configuration properties (see Tombstone Manager).
A possible AssemblyLine tombstone lifecycle could look like:
In order for the Tombstone Manager to function, the Server API must be switched on; that is, the property api.on must be set to true.
The relevant properties are:
The default value for this property is false.
The logic for tombstone record deletion is triggered on TDI Server startup and once a day on a long running TDI Server.
The default value for this property is 0.
The default value for this property is 10000.
The default value for this property is 5000.
The automatic cleanup logic determined by the com.ibm.di.tm.autodel.age property is independent of the automatic cleanup logic determined by the com.ibm.di.tm.autodel.records.trigger.on and com.ibm.di.tm.autodel.records.max properties.
The Tombstone Manager uses the TDI logging framework and logs its messages in the TDI Server main log.
com.ibm.di.tm.on=true com.ibm.di.tm.autodel.age=90 com.ibm.di.tm.autodel.records.trigger.on=50000 com.ibm.di.tm.autodel.records.max=25000 com.ibm.di.tm.create.all=false
This set of configuration properties specifies that: The Tombstone Manager is turned on. Tombstones older than 90 days are automatically deleted. Also when the total number of tombstone records reaches 50000, the oldest 25000 tombstone records is automatically deleted.