There are a number of steps that are required to get up and running with the vCenter Hyperic server, and in configuring it for your environment.

The method that you use to start the vCenter Hyperic server depends on how it was installed and how it will run.

You can configure global control of alert processing, including enabling and disabling alert definitions and notifications, and you can specify an hierarchical method for triggering alerts. You can also specify settings that control the metrics baselining process that influences when alerts are triggered.

You can tune vCenter Hyperic server for large deployments. The sizing profile that you select affects the server properties.

vCenter Hyperic server can be integrated with Kerberos, LDAP, and SMTP Server, and can be configured to send SNMP traps.

You can configure one or more vCenter Hyperic databases, including implementing optional properties.

To avoid interruption of vCenter Hyperic server operation in the case of failure, you can configure a cluster of vCenter Hyperic servers.

The configuration settings that vCenter Hyperic server requires to start up are included in the hq-server.conf file. For example, hq-server.conf has properties that tell the server how to connect to the database and where to listen for agent and web application communications.

You can tune the vCenter Hyperic vApp for large deployments. A large deployment is defined as one in which the vCenter Hyperic server manages more than 250 platforms.