There are a number of steps that are required to get up and running with the vRealize Hyperic server, and in configuring it for your environment. Starting the vRealize Hyperic ServerThe method that you use to start the vRealize Hyperic server depends on how it was installed and how it will run. Configuring Metric Baselining and Alert Processing BehaviorYou 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. Scaling and Tuning vRealize Hyperic PerformanceYou can tune vRealize Hyperic server for large deployments. The sizing profile that you select affects the server properties. Integrating vRealize Hyperic Server with Other SystemsvRealize Hyperic server can be integrated with Kerberos, LDAP, and SMTP Server, and can be configured to send SNMP traps. Managing the vRealize Hyperic DatabaseYou can configure one or more vRealize Hyperic databases, including implementing optional properties. Clustering vRealize Hyperic Servers for FailoverTo avoid interruption of vRealize Hyperic server operation in the case of failure, you can configure a cluster of vRealize Hyperic servers. vRealize Hyperic Server PropertiesThe configuration settings that vRealize 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. Tuning the vRealize Hyperic vAppYou can tune the vRealize Hyperic vApp for large deployments. A large deployment is defined as one in which the vRealize Hyperic server manages more than 250 platforms.