How To - Responder - Adding Custom Fields Into Responder RDMS Tables.

Version 3

    Solution

     

    The following steps go through adding a new field into Responder.  Custom fields can be added into Responder but may not be populated without additional customization.

    1. Add the field into the database. Using an RDMS you are comfortable with, add the field to the table you want.  The example below is for the RX_INCIDENTS Table: 2014-06-10 10_29_15-W7USFYV37R1L_SQLEXPRESS.gis - dbo.RX_INCIDENTS - Microsoft SQL Server Management.jpgEvery table in Responder has a matching _History and _Archive table that also needs the new field added in the same format. The _Archive table may be in a different Archive schema or database depending on your configuration.
    2. Once all the fields are added you'll need to modify the triggers assigned to the active tables.  In the example above, the trigger would be the RX_INCIDENTS_TRG.  Add the new field in the same order for every event (update, delete, insert) and recompile the trigger.  Without the triggers, the fields will not be processed during the Archive process.
    3. Change the configuration files for Responder.  Responder has two files (ArchiveSchemaConfig.xml and DatabaseSchemaConfig.xml) located in the Responder\Server folder that contain the fields Responder sees in the RDMS.  Edit these files and add the new fields to each of the tables added via the RDMS tools.  You can use the other fields as examples.
    4. Restart the Responder Windows Service and the field will be ready.