Connection Broker Database Test

The Connection Broker is completely self-contained and is bundled with an internal database. This database stores and maintains the following:

  • Passwords only for users that are created locally
  • Clients
  • Desktops and their environments
  • Microsoft Active Directory® user credentials: Encrypted.
  • Machine centers: Access credentials are encrypted.
  • Locations, roles, and all other operational parameters

An external database, on the other hand, is required when Connection Brokers are clustered. To handle high peak loads (such as, simultaneous logons) and failure of a Connection Broker (or its host) it is necessary to cluster Connection Brokers and run each Connection Broker on a different virtualization host. As soon as you cluster Connection Brokers virtual machines, they need an external database in order to share information. Microsoft SQL Server can be used as an external database server for the Connection Broker.

A key component of the Connection Broker is its internal and external database servers. If the internal/external database is rendered unavailable or is experiencing a significant slowdown, it can cause prolonged Connection Broker outages, deny/delay users access to critical desktops/data, and thus mar the user experience. Using this test, administrators can periodically monitor the availability and responsiveness of the local and remote databases, be proactively alerted to anomalies, and avert adversities in time.

Target of the test : A Leostream Connection Broker

Agent deploying the test : An internal agent

Outputs of the test : One set of results each for the local and remote database used by the Connection Broker.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


Specify the IP address of the Connection Broker for which the test is to be configured.


Refers to the port used by the Connection Broker is listening.


By default, this flag is set to No, indicating that by default, the test connects to the Connection Broker via HTTP. If the Connection Broker is SSL-enabled, then set this flag to Yes.


Specify the duration (in seconds) within which the test should timeout. The default duration is 30 seconds.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates whether the database is available or not.


While the value 100 indicates that the database is available, the value 0 indicates that it is not.

The internal database will be available as long as the Connection Broker is. If the external database is unavailable, it could be owing to an improper configuration of the database or a poor network connection (in case of an external database).

Response time

Indicates the time taken by the connection broker to respond to requests.


Ideally, the value of this measure should be low. A very high value indicates a marked deterioration in the performance of the database, which can be attributed to insufficient space, improper configuration, or a network congestion (in case of an external database).