Archiving and purging of data events

After processing, data events which have processed successfully are purged. The system can be configured to archive these events.

Technical architecture overview

You will need to understand the technical architecture for archiving and purging events.

Configuration tables

The configuration tables hold the staging information for data events and jobs and the configuration parameters for the data events handling application.

Configuration properties

Configuration parameters are set for the purge events application to process. This configuration should only be changed to match the server configuration.

Configuring tables for the CONFIG schema

Tables need to be configured in the Relational Replication database CONFIG schema for multi-server purging.

Configuring tables for the multi-server artefacts

Tables need to be configured in the Relational Replication database CONFIG schema for multi-server artefacts.

Configuring tables for data type mapping

A new table needs to be created in the RR database CONFIG schema for data type mapping.

Configuring tables for late commit changes

The system has to check and correct for late commit changes. You must configure the files it uses to achieve this.

Overriding STANDARD.SELECTION values

Tables in Relation Replication are created based on the schema definition in STANDARD.SELECTION from the XSD event. The field lengths and datatypes of tables created in Relational Replication can be overridden using the RR.OVERRIDE.PARAMETER table.