Multiple MTC Outbound Node Installation
In case several Multi Tenant Connector outbound nodes are to be used in the same tenant site, the RPAM MTC Installer should be executed with the MTC Outbound role on every Multi Tenant Connector machine. After that, the user needs to fill in the required data for every Multi Tenant Connector node on the Tenant Connector page of the Kron PAM Web GUI and press the SAVE button as explained in the 4th step of Section 8.1. In the end, multiple tenant connector nodes appear under the same tenant site.
If more than one Multi Tenant Connector node is active under the same tenant site, the traffic is distributed in a round-robin manner through those nodes. The Kron PAM Server keeps checking the activeness of the connector nodes by running a job called TunnelHeartbeatCheckJob. This job keeps track of the regular heartbeat messages sent by the connector nodes and sets the tunnel status as FAILED in case three consecutive heartbeat messages (this number is specified in the "connector.heartbeat.check.interval" system config parameter) do not arrive. There will be no traffic on the failed Multi Tenant Connector node unless its status turns active again.
If the TunnelHeartbeatCheckJob is not defined on the Kron PAM Server, the user should define it first.
The important point here is that the Kron PAM Server understands the status of the Multi Tenant Connector node with this job if the connector node fails. In case the connector service on the Multi Tenant Connector node goes down or the secure tunnel between the Kron PAM Server and the Multi Tenant Connector node goes down, and this job is not defined (or not run), even though in reality the Multi Tenant Connector node is not active, the Kron PAM Server thinks that it is still active and still sends the requests to this connector node.