Preparing Accessories for the Tanker Accessory

In order for other DATABridge Accessories to use the filtered audit files generated by the Tanker Accessory, they must call the DBINITFILTER (filtername) entry point in the Engine. To determine the pack where the filtered audit files reside, the Engine then reads DATA/TANKER/databasename/CONTROL or DATA/TANKER/logicaldatabasename/CONTROL .

  • For any user-written Accessory, you must include the DBINITFILTER call.
  • For the Span Accessory and the Server Accessory, you can edit the PREFILTERED option in their respective parameter files. The PREFILTERED option requests that the Engine use the filtered audit files generated by the Tanker Accessory.

In either case, if the Engine cannot locate a filtered audit file, it automatically switches to using the normal audit files if the PREFILTERED option is set to PREFERRED.