If you choose to use external Audit tables, a new datastore with the name "AuditPlus" will be created in the target environment. Also, dataviews will be created for each AuditPlus transaction. In this new datastore you can define the schema where auditing tables will be created.
The information in the new datastore and information in dataviews will be used to navigate audited data and also, it will be used to create the audit database triggers.
As you can see another schema is selected (auditplus), so auditing tables will be generated in this schema.
In order to create audit triggers in the database, AuditPlus will consider the following information:
- Database name
- Can be set either in the dataview or the datastore
Database connection can also be customized using the procedure 'AuditPlusGetDatastoreParms' .
In this procedure, the user can decide which database and which schema will be used for each datastore and table.
This can be used to create and deploy audit reorganization programs for different deployments.
You should consider the following restrictions:
- DBMS does not support different schemas in one database
- AuditPlus does not support different databases for audit tables. Audit tables and application tables must be in the same database in order to work.