https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/Recent content in Teradata Data Warehouse Protector onHugoenhttps://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_teradata_arch/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_teradata_arch/<p>The architecture for the Teradata distribution of the Data Warehouse Protector is depicted in the image below.</p> <p><img src="https://docs.protegrity.com/protectors/10.1/docs/images/dwp/dwp_teradata_architecture.png" alt="Teradata Protector Multi-node Architecture"></p> <table> <thead> <tr> <th>Component Name</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>Access Module Processor</td> <td>Stores and retrieves all the protector data. It is also called as the Virtual Processor (vproc).</td> </tr> <tr> <td>config.ini</td> <td>Contains the set of configuration parameters to modify the protector behavior.</td> </tr> <tr> <td>Core</td> <td>Is the set of various libraries that provide the Protegrity Core functionality.</td> </tr> <tr> <td>Log Forwarder</td> <td>Forwards the protector logs to Insight.</td> </tr> <tr> <td>Node</td> <td>Serves as a central processing unit where the database operations are executed using a single operating system.</td> </tr> <tr> <td>Resilient Package (RP) Agent</td> <td>Is a daemon running on each node that downloads the Policy from the ESA over a TLS channel using the installed Certificates.</td> </tr> <tr> <td>UDF Layer</td> <td>Contains the Data Warehouse Protector UDFs and APIs executing in the Teradata service process.</td> </tr> </tbody> </table>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_teradata_sys_req/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_teradata_sys_req/<p>The following table lists the minimum hardware configuration for the Data Warehouse Protector on Teradata distribution.</p> <table> <thead> <tr> <th>Hardware Components</th> <th>Configuration</th> </tr> </thead> <tbody> <tr> <td>CPU</td> <td>Depends on the application.</td> </tr> <tr> <td>Disk Space</td> <td>400 MB on every node - Includes the Log Forwarder, RPAgent, and User Defined Functions (UDFs)</td> </tr> <tr> <td>RAM</td> <td>4 GB on every node</td> </tr> </tbody> </table> <blockquote> <p><strong>Note:</strong> In v10.0.0, the RPAgent loads the policy package into the shared memory. Every individual service process on a node that initializes the protector will load a copy of the policy package into the process heap memory. Therefore, the RAM requirement on each node depends on the policy size and the number of protector instances (number of processes).</p>