Getting Started with vFabric Hyperic v.5.7 - VMware

JSW runs as a native executable; it invokes and monitors the vFabric Hyperic Agent's JVM,based on configuration information provided to the wrapper at startup. In this way, the wrappersupports restarts of the JVM process without stopping the wrapper process itself. The JSWprocess acts as a watchdog for the JVM process, periodically pinging it for availability.For information about wrapper configuration, see Agent Java Service Wrapper Configuration.What Happens When an Agent Starts UpA vFabric Hyperic Agent needs to know how to connect to the vFabric Hyperic Server, and thevFabric Hyperic Server needs to know how to connect to the vFabric Hyperic Agent — eachcomponent needs the IP address and listen port (and other connection properties) to use toestablish a connection with the other. As described in About Agent Configuration you can definethe connection properties interactively at first agent startup, or in the agent'sagent.properties file.When you start a vFabric Hyperic Agent:5. The agent checks to see if there is a /data directory that contains the vFabric HypericServer's connection properties.o At first startup, the /data directory will not exist — it is created after the firstsuccessful connection between agent and server is established.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.6. If the agent did not find the /data directory, it looks for an agent.properties file in ahidden directory named .hq in the home directory of the user that runs the agent.o This directory will not exist unless you have previously created it. This location forthe properties file is supported to ensure configuration data is not lost in theevent that the complete agent installation is overwritten in an upgrade.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.7. If the agent did not find the agent-server connection properties in anagent.properties file in the hidden /.hq directory, it looks at theagent.properties file in its /conf directory.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.8. If the agent did not find connection properties in the agent.properties file in its/conf directory, it prompts for the properties to be supplied interactively in thecommand shell.9. Upon obtaining the agent-server connection properties, the agent attempts to connect tothe vFabric Hyperic Server.10. Once communications between agent and server have been successfully established:o The agent saves the vFabric Hyperic Server connection settings inAgentHome/data.14