By default, communication between JetPatch server and endpoints is based on one of three protocols: WEB, SSH, and SMB2.
The primary protocol is WEB once the connector is installed. If the primary protocol is down, then it will fall back to SSH and SMB2, depending on OS.
If you want to disable the SMB2 and SSH protocols, that can be accomplished by editing the Intigua Config XML, then restarting tomcat.
Note: there is also the VSPHERE protocol that can be used if the endpoint is discovered via vCenter Automatic Discovery.
Path of the Config file: usr/share/tomcat/default/conf/intigua.config.xml
Note: restart tomcat after making changes
Within that file, you may see the following section, if you do, edit it.
If you do not see it, add it everything highlighted in green above, after </watchdog>.
Note: priority is based on the order from top to bottom
As an example, if the intigua.config.xml is updated as below then this means that the connector's communication is solely based on the Web protocol (either http or https).
Installing the connector on a new endpoint directly from JetPatch, requires either SSH (for Linux) or SMB2 (for Windows), as these protocols are absent in this example, it will only be possible to install the connector on the endpoint using JetPatch's connector MSI or by downloading the connector installation files directly to the endpoint and running the appropriate installation command line. For more info on these techniques visit the following article: https://kc.jetpatch.com/hc/en-us/articles/360023862672-Adding-Non-Discoverable-Endpoints-and-Deploying-Connector-on-the-Endpoint-itself