Configuration of CtxGwHATest

A high availability (HA) deployment of two Citrix Cloud Gateway Connectors can provide uninterrupted operation in any transaction. With one connector configured as the primary node and the other as the secondary node, the primary node accepts connections and manages servers while the secondary node monitors the primary. If, for any reason, the primary node is unable to accept connections, the secondary node takes over.

The secondary node monitors the primary by sending periodic messages (often called heartbeat messages or health checks) to determine whether the primary node is accepting connections. If a health check fails, the secondary node retries the connection for a specified period, after which it determines that the primary node is not functioning normally. The secondary node then takes over for the primary (a process called failover).

When monitoring a Citrix Cloud Gateway Connector, you may first want to know whether the target connector has been deployed in an HA setup or not. If so, you may then want to time and again evaluate the effectiveness of the HA configuration, by checking the following:

• What is the current status of highly available node in the HA setup?

• What is the current status of target connector in the HA setup?

• Has the status of target connector changed?

This is exactly what the CtxGwHATest does.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the HOST for which this test is to be configured.

• Specify the port number at which the specified host listens in the PORT text box. By default, this is 8443.

• To monitor a Citrix Cloud Gateway Connector, the eG agent should be configured with the credentials of a user with read-only privileges to the target connector. Specify the credentials of such a user in the USERNAME and PASSWORD text boxes.

• Confirm the password by retyping it in CONFIRM PASSWORD text box.

• By default, the SSL flag is set to No indicating that the eG agent will communicate with the connector via HTTP by default. If the target connector is SSL-enabled, then set this flag to Yes to enable the eG agent to communicate with target connector via HTTPS.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.