Understanding the Architecture

Mon, 01 Jan 0001 00:00:00 +0000

The architecture for the Oracle Database Protector is depicted in the image below.

Component	Description
RPAgent	A daemon running on each node that downloads the package from the ESA over a TLS channel using the installed Certificates.
Log Forwarder	A daemon running on each node that routes the audit logs and application logs to the ESA/Audit Store.
config.ini	A file on each node containing the set of configuration parameters to modify the protector behavior.
DBP Layer	Contains the Database Protector UDFs and APIs.
Core	The set of various libraries that provide the Protegrity Core functionality.

System Requirements

Mon, 01 Jan 0001 00:00:00 +0000

Ensure that the following prerequisites are met:

The Oracle Database is installed and configured.
The Enterprise Security Administrator (ESA) is installed, configured, and running.
The IP address or host name of the ESA is noted.
Ensure that Policy Management (PIM) has been initialized on the ESA. The initialization of PIM ensures that cryptographic keys for protecting data and the policy repository have been created.
Download and save the Oracle Database Protector, DatabaseProtector_<operating_system>-<arch>_<Oracle_version>-64_<version>.tgz, made available by Protegrity.