Understanding the Architecture

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

The architecture for the Teradata distribution of the Data Warehouse Protector is depicted in the image below.

Component Name	Description
Access Module Processor	Stores and retrieves all the protector data. It is also called as the Virtual Processor (vproc).
config.ini	Contains the set of configuration parameters to modify the protector behavior.
Core	Is the set of various libraries that provide the Protegrity Core functionality.
Log Forwarder	Forwards the protector logs to Insight.
Node	Serves as a central processing unit where the database operations are executed using a single operating system.
Resilient Package (RP) Agent	Is a daemon running on each node that downloads the Policy from the ESA over a TLS channel using the installed Certificates.
UDF Layer	Contains the Data Warehouse Protector UDFs and APIs executing in the Teradata service process.

System Requirements

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

Ensure that the following prerequisites are met, before installing the Teradata Data Warehouse Protector:

The ESA appliance, v10.0.x or higher, is installed, configured, and running.
The ports that are configured on the ESA and the nodes in the cluster, which will run the Data Warehouse Protector, are listed in the following table:

Destination Port	Protocol	Source	Destination	Description
8443	TCP	RP Agent on the Data Warehouse Protector node	ESA	The RP Agent communicates with the ESA through port 8443 to download a policy.
9200	TCP	Log Forwarder on the Data Warehouse Protector node	Protegrity Audit Store appliance	The Log Forwarder sends all the logs to the Protegrity Audit Appliance through port 9200.
15780	TCP	Protector on the Data Warehouse Protector node	Log Forwarder on the Data Warehouse Protector node	The Data Warehouse Protector writes Audit Logs to localhost through port 15780. The Application Logs are also written to localhost through port 15780. The Log Forwarder reads the logs from that socket.