JetAgent is installed within the customer’s organizational network, and is accessed via a web interface. JetAgent is available either as RPMs to be installed on CentOS or RHEL, or as a virtual appliance running on CentOS (compatible with Red Hat Enterprise Linux). The virtual appliance can be patched like any other such Linux, and can be protected with standard management tools.
The JetAgent server uses an external PostgreSQL database, which can be clustered. A high-availability solution for the JetAgent server itself is also available.
JetAgent connects directly to VMware vSphere, AWS EC2, and MS Azure environments for endpoint discovery.
Upon initial deployment to each endpoint, JetAgent establishes a channel to the endpoint by deploying the JetAgent connector client service via SMB (Windows) or SSH (Linux).
For ongoing agent provisioning, registration, control, and monitoring, JetAgent communicates with endpoints and management servers via HTTPS sessions from the endpoints to JetAgent; If HTTPS communications are unavailable, JetAgent falls back to using SMB or SSH for these ongoing operations as well. In accordance with commands from JetAgent the connector on endpoints runs, stops, and monitors managed agents, and the connector on third-party management servers performs per-endpoint registration and configuration tasks.
When preferred protocols are unavailable, JetAgent can communicate with vCenter VMs via the hypervisor channel (supported for vSphere 5.1 and above). In that case, for ongoing communications JetAgent continues to periodically try HTTPS at gradually increasing intervals up to a maximum interval of 24 hours. This default behavior is configurable.