https://docs.protegrity.com/protectors/10.0/docs/datawarehouse_protector/dwp_trino/Recent content in Trino Data Warehouse Protector onHugoenhttps://docs.protegrity.com/protectors/10.0/docs/datawarehouse_protector/dwp_trino/dwp_trino_understand_arch/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/protectors/10.0/docs/datawarehouse_protector/dwp_trino/dwp_trino_understand_arch/<p>The architecture for the Trino Data Warehouse Protector is depicted in the image below. <img src="https://docs.protegrity.com/protectors/10.0/docs/images/bdp/dwp_trino_architecture.png" alt="" title="Trino Architecture"></p> <table> <thead> <tr> <th>Component</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>RPAgent</td> <td>Is a daemon running on each node that downloads the policy package from the ESA over a TLS channel using the installed Certificates.</td> </tr> <tr> <td>Log Forwarder</td> <td>Is a daemon running on each node that routes the audit logs and application logs to the ESA/Audit Store.</td> </tr> <tr> <td>config.ini</td> <td>Is a file on each node containing the set of configuration parameters to modify the protector behavior.</td> </tr> <tr> <td>Protector Layer</td> <td>Contains the Trino Protector UDFs and APIs.</td> </tr> <tr> <td>JcoreLite</td> <td>Is the JNI library that provides a Java API layer to the Core libraries.</td> </tr> <tr> <td>Core</td> <td>Is the set of various libraries that provide the Protegrity Core functionality.</td> </tr> </tbody> </table>https://docs.protegrity.com/protectors/10.0/docs/datawarehouse_protector/dwp_trino/dwp_trino_sys_req/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/protectors/10.0/docs/datawarehouse_protector/dwp_trino/dwp_trino_sys_req/<p>Ensure that the following prerequisites are met, before installing the Trino Protector:</p> <ul> <li>The Trino cluster is installed, configured, and running.</li> <li>The ESA appliance, version 10.0.x or v10.1.x, is installed, configured, and running.</li> <li>The ports that are configured on the ESA and the nodes in the cluster, which will run the Trino Protector, are listed in the following table:</li> </ul> <table> <thead> <tr> <th>Destination Port</th> <th>Protocol</th> <th>Source</th> <th>Destination</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>8443</td> <td>TLS</td> <td>RPAgent on the Big Data Protector cluster node</td> <td>ESA</td> <td>The RPAgent communicates with the ESA through port<br>8443 to download a policy.</td> </tr> <tr> <td>9200</td> <td>TLS</td> <td>Log Forwarder on the Trino Protector Cluster node</td> <td>Protegrity Audit<br>Store appliance</td> <td>The Log Forwarder sends all the logs to<br>the Protegrity Audit Appliance through port 9200.</td> </tr> <tr> <td>15780</td> <td>TCP</td> <td>Protector on the Trino Protector<br>cluster node</td> <td>Log Forwarder<br>on the Trino<br>Protector cluster<br>node</td> <td>The Trino Protector writes Audit Logs to<br>localhost through port 15780. The Application<br>Logs are also written to localhost through<br>port 15780. The Log Forwarder reads the logs from that<br>socket.</td> </tr> </tbody> </table>