Before first agent startup, you can define the properties that enable the agent to communicate with the vRealize Operations Manager server, and other agent properties, in the agent.properties file of an agent. When you configure the agent in the properties file you can streamline the deployment for multiple agents.
If a properties file exists, back it up before you make configuration changes. If the agent does not have a properties file, create one.
An agent looks for its properties file in AgentHome/conf. This is the default location of agent.properties.
If the agent does not find the required properties for establishing communications with the vRealize Operations Manager server in either of these locations, it prompts for the property values at initial start up of the agent.
A number of steps are required to complete the configuration.
You can define some agent properties before or after the initial startup. You must always configure properties that control the following behaviors before initial startup.
When the agent must use an SSL keystore that you manage, rather than a keystore that vRealize Operations Manager generates.
When the agent must connect to the vRealize Operations Manager server through a proxy server.
Verify that the vRealize Operations Manager server is running.