There are various options that you can use to run a vCenter Hyperic agent. You can customize certain parameters to suit your environment requirements.

You can use the command line to initiate the vCenter Hyperic agent launcher and agent lifestyle commands.

In vCenter Hyperic, you can issue selected commands to a running vCenter Hyperic agent.

If you run a If you run an Hyperic agent on a system that does not support the Java Service Wrapper, or for other reasons prefer not to use the wrapper, you can start the agent without the wrapper.

You can configure the name, location, and logging level for vCenter Hyperic agent logs. You can also redirect system messages to the agent log, and configure the debug log level for an agent subsystem.

At startup, a vCenter Hyperic agent loads all the plug-ins in the AgentHome/bundles/agent-x.y.z-nnnn/pdk/plugins directory. You can reduce the agent's memory footprint by configuring it to load only the plug-ins that you use.

You can configure a vCenter Hyperic agent to enable a specific plug-in to perform one or more of its management functions.

You can monitor your vCenter Hyperic agents and tune them to your requirements. You can view the status of all the agents, view the metrics of a specific agent and reduce the memory footprint of an agent.

Multiple properties are support in the file for a vCenter Hyperic agent. Not all supported properties are included by default in the file.

The configuration file for the vCenter Hyperic agent;s Java service wrapper is located in AgentHome/bundles/BundleHome/conf/wrapper.conf.

The Java options that are supplied to the vCenter Hyperic agent at startup are configured in the Java Additional Parameters section of the wrapper.conf file.

You can deploy multiple vCenter Hyperic agents simultaneously, using vCenter Infrastructure Navigator. You configure the agent properties prior to deployment.