JetPatch Agent Manager is installed within the customer’s organizational network, and is accessed via a web interface. JetPatch Agent Manager 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 JetPatch Agent Manager server uses an external PostgreSQL database, which can be clustered. A high-availability solution for the JetPatch Agent Manager server itself is also available.
JetPatch Agent Manager connects directly to VMware vSphere, AWS EC2, and MS Azure environments for endpoint discovery.
Upon initial deployment to each endpoint, JetPatch Agent Manager establishes a channel to the endpoint by deploying the JetPatch connector client service via SMB (Windows) or SSH (Linux).
For ongoing agent provisioning, registration, control, and monitoring, JetPatch Agent Manager communicates with endpoints and management servers via HTTPS sessions from the endpoints to JetPatch Agent Manager; If HTTPS communications are unavailable, JetPatch Agent Manager falls back to using SMB or SSH for these ongoing operations as well. In accordance with commands from JetPatch 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, JetPatch Agent Manager can communicate with vCenter VMs via the hypervisor channel (supported for vSphere 5.1 and above). In that case, for ongoing communications JetPAtch continues to periodically try HTTPS at gradually increasing intervals up to a maximum interval of 24 hours. This default behavior is configurable.