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.

The default parameters associated with this test are as follows:

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

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• In the PORT text box, specify the port number at which the host listens.

• 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.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box 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.