JetProxy Overview - Gateway Proxy Architecture

JetProxy Use-Cases

1. JetProxy allows you to use a single JetPatch console for managing endpoints in multiple data centers
2. JetProxy simplifies the deployment of JetPatch within a perimeter network (DMZ), where a special firewall rule needs to be requested for every endpoint in order to allow it to connect to the JetPatch server

Hardware Requirements

See JetProxy hardware requirements

Network Requirements

• Ensure connectivity between JetProxy and JetPatch server using telnet over port 443.
• Ensure firewall settings allowing connection on the JetProxy over port 443/HTTPS.
• Ensure the machine can resolve the server's hostnames (if used)
• (Optional) Ensure the below requirements for WSUS server, in case it's required

Installing JetProxy

• Installing JetProxy (CentOS/RHEL)
• Installing JetProxy (Ubuntu)

Important Notes on the JetProxy Solution

• JetProxy acts as a proxy to the main JetPatch console. Once JetProxy is configured and the endpoints are pointing to the proxy server, then a user can log into the main JetPatch console in order to view and manage all endpoints, including endpoints pointing to the proxy server.
• Connector installation is not possible through the proxy solution, only upgrades and removal, since this is a web proxy not an SSH/SMB2 proxy.  For instructions on how to install the connector on the endpoint itself, see this article.
• Connector upgrade is possible through the proxy solution.  Make sure you create a connector service for your proxy endpoints, which will be important for connector upgrade and service reconfiguration.
• No agents are stored on the proxy server.