Index

A  C  D  E  F  G  H  I  J  L  M  N  O  P  R  S  T  U  W  X  

---

A

• about Audit Collection Plug-ins 3.1
• about XML mapper files 2.3.5
• Action fields A.2.1
• actions and target types A.2
• agents
  • redeploying 6.4
• Agents
  • deploying 6.3
• audit collection plug-in
  • packaging 5
  • setting up development environment for 2
• audit collection plug-ins
  • types of 1.3
• audit collection Plug-ins
  • determining which to use 1.3.3
• Audit Collection Plug-ins 3.1
• AuditEventCollectorException exception 4.5.14
• AuditEventCollectorFactory 4.5.2
• audit records 1.4.1
  • storing 1.4.5
• audit trail 1.2
  • clean-up 1.5.3.6
• audit trail cleanup
  • Java-based collection plug-ins 4.7
• Audit Vault Agent
  • deploying 6.3
  • how it works 1.2
• Audit Vault and Database Firewall core fields A.1.1
• Audit Vault and Database Firewall fields A.1
• Audit Vault and Database Firewall SDK
  • downloading 2.2
• Audit Vault Server
  • how it works 1.2
• Audit Vault Server events
  • about 1.4.1
• Audit Vault Server fields
  • about 1.4.1
• av.collector.atcintervaltime 3.7
• av.collector.securedtargetversion (Mandatory) 3.7
• av.collector.timezoneoffset (Mandatory) 3.7
• avcli commands 6.2
• AVCLI commands 3.7
• AVDF extension fields A.1.4
• AVDF large fields A.1.2
• AVLogger API 4.6.5
• avpack tool
  • how to use 5.5

---

C

• checkpoint
  • of a trail 1.5.3.4
• clean-up
  • audit trail 1.5.3.6
• closing Java-based collection plug-ins 4.5.13
• CollectContext class 4.5.3
• collection concepts 1.5.3
• collection phase 1.5.3.2
• collection plug-in
  • directory structure 2.3.2
  • Java-based
    • See Java-based collection plug-in 1.3.4
  • upgrading (creating new versions) 5.4
• collection plug-in directory structure 2.3
• collection plug-in example
  • CSV C.4
  • Java file C.6
  • JSON C.3
  • JSON REST C.5
  • XML file C.2
• collection plug-in manifest file
  • CSV file C.4.2
  • JSON file C.3.2
  • JSON REST C.5.2
  • XML file C.2.2
• collection plug-in mapper file
  • CSV file C.4.1
  • JSON file C.3.1
  • JSON REST C.5.1
  • XML file C.2.1
• collection plug-ins
  • what are they? 1.3.1
• collection process
  • overview of the whole process 1.5
• collection thread 1.5.3.1
• ConnectionManager API 4.6.2
• creating a database table mapper file 3.2.3
• creating the CSV file audit collection mapper file 3.5.3
• creating the JSON file audit collection mapper file 3.4.3
• creating the JSON REST audit collection mapper file 3.6.3
• creating the XML file audit collection mapper file 3.3.3
• CSV file audit collection mapper file
  • creating 3.5.3
• CSV file collection plug-in
  • example audit trail for 3.5.2
• CSV file collection plug-in example C.4
• CSV file collection plug-in manifest file C.4.2
• CSV file collection plug-in mapper file C.4.1
  • schema B.5
• CSV file collection plug-ins 3.5
  • requirements for 3.5.1

---

D

• database table collection plug-in example C.1
• database table collection plug-in manifest file C.1.2
• database table collection plug-in mapper file B.2, C.1.1
• database table collection plug-ins 3.2
  • requirements 3.2.1
• database table mapper file
  • creating 3.2.3
• data collection
  • recovery phase 1.5.3.5
• deploying an Audit Vault Agent 6.3
• deploy plugin command 5.4
• development environment 2.3
  • directory structure 2.3.1, 2.3.2
    • Java-based collection plug-in 2.3.3
  • plugin-manifest.xml file staging 2.3.4
  • requirements 2.1
  • setting up 2.2
• directory structure
  • collection plug-in 2.3
  • collection plug-ins 2.3
  • general 2.3.1

---

E

• errors
  • exception to use 4.5.14
  • unrecoverable condition 4.5.14
• EventLog API 4.6.3
• event logs
  • Java-based collection plug-ins 4.6.3
  • Windows 4.6.3
• EventMetaData API 4.6.4
• Event Time to UTC 4.5.6.1
• example
  • database table collection plug-in C.1
• example audit trail for a CSV file collection plug-in 3.5.2
• example audit trail for a database table collection plug-in 3.2.2
• example audit trail for a JSON file collection plug-in 3.4.2
• example audit trail for a JSON REST collection plug-in 3.6.2
• example audit trail for an xml file collection plug-in 3.3.2
• exceptions
  • AuditEventCollectorException 4.5.14
  • SetAttributeException 4.5.14
  • types the collection plug-in can throw 4.5.14
• extension fields A.1.4
• external dependencies 5.3
• ezcollector plug-in mapper file
  • schema B.10

---

F

• fields, large 4.5.11
• flow of control
  • inside the collection plug-in 1.5.2
• flow of packaging 5.1

---

G

• general procedure
  • for writing collection plug-is 1.6

---

H

• handling large fields 4.5.11

---

I

• initializing the collector plug-in 4.5.4

---

J

• Java-based audit collection plug-in
  • directory structure 2.3.3
  • writing 4
• Java-Based Collection Plug-in 4.2
• Java-based collection plug-ins
  • about 4.1
  • about creating 4.5.1
  • audit trail cleanup 4.7
  • classes and interfaces, useful 4.4
  • closing 4.5.13
  • CollectContext class 4.5.3
  • collection factory 4.5.2
  • connecting 4.5.5
  • creating 4.5
  • creating markers 4.5.12
  • description of 1.3.4
  • event logs 4.6.3
  • extension fields 4.5.10
  • fetching events 4.5.5
  • flow of control process 4.3
  • how they work 4.3
  • intializing 4.5.4
  • large fields 4.5.11
  • retrieving other field values 4.5.7
  • security considerations 4.8
  • setting checkpoints 4.5.5
  • source connections 4.6.2
  • transforming source event values to Audit Vault values 4.5.6
  • utility APIs 4.6
• Java-based collector plug-ins 4.1
  • changing attributes at run time 4.5.8, 4.5.9
• Java-based file collection plug-in example C.6
• JDK requirement for Java-Based Collection Plug-in 4.2
• JDK requirements for 4.2
• JSON collector plug-in mapper file
  • schema B.9
• JSON file audit collection mapper file
  • creating 3.4.3
• JSON file collection plug-in
  • example audit trail for 3.4.2
• JSON file collection plug-in example C.3
• JSON file collection plug-in manifest file C.3.2
• JSON file collection plug-in mapper file C.3.1
  • schema B.4
• JSON file collection plug-ins 3.4
  • requirements for 3.4.1
• JSON REST audit collection mapper file
  • creating 3.6.3
• JSON REST collection plug-in
  • example audit trail for 3.6.2
• JSON REST collection plug-in manifest file C.5.2
• JSON REST collection plug-in mapper file C.5.1
  • schema B.6
• JSON REST collection plug-ins 3.6
  • requirements for 3.6.1
• JSON REST file collection plug-in example C.5

---

L

• large fields A.1.2

---

M

• mapper file
  • database table collection plug-in B.2, C.1.1
• mapper files 2.3.5
• mappings
  • from target to Audit Vault Server 1.5.3.3
• marker fields A.1.3
• markers in Java-based collection plug-ins 4.5.12

---

N

• name pattern collection plug-in mapper file
  • schema B.8

---

O

• Oracle Audit Vault and Database Firewall
  • what is it? 1.1
• Oracle AVDF marker fields A.1.3
• Oracle XML Developer’s Kit 4.6.6

---

P

• packaging 5
  • external dependencies 5.3
  • flow of 5.1
• plugin id 2.3.6
• plugin-manifest.xml file
  • about 2.3.4
  • description of 2.3.6
  • sample schema B.1
  • staging 2.3.4
• plug-in manifest file
  • database table collection C.1.2
• plug-ins
  • redeploying agent 6.4
  • requirements for testing 6.1
  • testing procedure 6.2
• pre-processing audit data 3.8

---

R

• recovery phase
  • of data collection 1.5.3.5
• requirements for CSV file collection plug-ins 3.5.1
• requirements for database table collection plug-ins 3.2.1
• requirements for JSON file collection plug-ins 3.4.1
• requirements for JSON REST collection plug-ins 3.6.1
• requirements for xml file collection plug-ins 3.3.1
• REST collector plug-in mapper file
  • schema B.7

---

S

• sample schema for a plugin-manifest.xml file B.1
• schema for CSV file collection plug-in mapper file B.5
• schema for ezcollector plug-in mapper file B.10
• schema for JSON collector plug-in mapper file B.9
• schema for JSON file collection plug-in mapper file B.4
• schema for JSON REST collection plug-in mapper file B.6
• schema for name pattern collection plug-in mapper file B.8
• schema for REST collector plug-in mapper file B.7
• schema for xml file collection plug-in mapper file B.3
• SDK
  • downloading 2.2
• security considerations
  • Java-based collection plug-ins 4.8
• SetAttributeException exception 4.5.14
• setting up development environment 2
• source attributes
  • additional 4.5.3.4
  • Java based 4.5.3.1
• source attributes, changing custom at run time 4.5.9
• source attributes, changing Oracle AVDF at run time 4.5.8
• source database
  • connections to Java-based collection plug-in 4.6.2
• source event id to source event name 4.5.6.3
• source event ID to target type 4.5.6.4
• source event name to Audit Vault event name 4.5.6.2
• source event name to target type 4.5.6.4
• source event status to Audit Vault event status 4.5.6.5
• source event values, transforming to Audit Vault event values 4.5.6
• staging
  • plugin-manifest.xml file 2.3.4
• storing audit records 1.4.5

---

T

• target 1.2
• target collection attributes 3.7
• target type 1.2
• target types A.2.2
• trail
  • checkpoint 1.5.3.4
• trail attributes
  • additional 4.5.3.4
• trail-related attributes 4.5.3.2

---

U

• undeploy plugin command 5.4
• unresolved-external tag 5.3
• upgrading
  • collection plug-ins 5.4
• utilities
  • AVLogger API 4.6.5
  • Oracle XML Developer’s Kit 4.6.6
• utility APIs
  • Java-based collection plug-ins 4.6
• utility instances 4.5.3.3

---

W

• what are collection plug-Ins? 1.3.1
• Windows
  • EventMetaData API 4.6.4
• Windows EventLog 4.6.3
• Windows EventLog API 4.6.3
• Windows Metadata Java API 4.6.4
• writing collection plug-Ins
  • general procedures for 1.6

---

X

• xml file audit collection mapper file
  • creating 3.3.3
• xml file collection plug-in
  • example audit trail for 3.3.2
• XML file collection plug-in example C.2
• XML file collection plug-in manifest file C.2.2
• xml file collection plug-in mapper file
  • schema B.3
• XML file collection plug-in mapper file C.2.1
• xml file collection plug-ins
  • requirements for 3.3.1
• XML file collection plug-ins 3.3
• XML mapper files 3.1
  • about 2.3.5