A key component of the Connection Broker is its database. 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. Connection Broker version 5.0 uses Microsoft SQL Server® 2005 database software.
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 the CBDataBaseTest, administrators can periodically monitor the availability and responsiveness of the local and remote databases, be proactively alerted to anomalies, and avert adversities in time. This page depicts the default parameters that need to be configured for the CBDataBaseTest.

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

• By default, SSL 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.

• In the TIMEOUT textbox specify the duration (in seconds) within which the test should timeout. The default duration is 30 seconds.

• Once the necessary value has been been provided, click on the Update button to register the changes made.

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.