In addition to connecting non-discoverable endpoints to Intigua 3.7 in the Intigua Console, the following alternative methods are available.
Grant API permission to an Intigua user.
where the above parameters are as in the table below.
Alternatively, if you have a copy of the client (intigua_rest_cmd_client.py) on another machine, you can run it remotely from there, in which case you need to adjust the path to the client accordingly, and the command needs to include: --url https://<server>/vmanage-server/rest/rest-api/ , where <server> is the IP address or resolvable hostname of the Intigua server.
Optionally, you could incorporate the command in a script, such as for adding multiple machines.
You can locally install the Intigua connector on any endpoint server. This is useful for connecting servers which are not otherwise accessible to the Intigua management server, and also for adding the Intigua connector to a base image that will be used to spawn multiple servers later.
Make sure organizational firewalls allow HTTPS (port 443) communication from the endpoint to the Intigua 3.7 server.
<hostIP> is the IP address (not name) of the Intigua 3.7 server host.
If the endpoint is already listed in the Intigua Console endpoint list, and you still need to locally install the connector (for example, there is a temporary access problem), you must add to the above command: -coreid "<ID>" , replacing <ID> with the ID displayed in the endpoint's Server core ID column in the endpoint list (some of the ID may be hidden; to get the whole string, triple-click it and copy).
The connector is installed, and initiates communication with Intigua 3.7.