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.

1

In the agent.properties file, properties relating to communication between the End Point Operations Management agent and the vRealize Operations Manager server are inactive by default. You must activate them.

2

The agent.properties file contains properties that you can configure to manage communication.

3

The agent uses a self-signed certificate for internal communication, and a second certificate that is signed by the server during the agent registration process. By default, the certificates are stored in a keystore that is generated in the data folder. You can configure your own keystore for the agent to use.

4

The End Point Operations Management agent configuration dialog appears in the shell when you start an agent that does not have configuration values that specify the location of the vRealize Operations Manager server. The dialog prompts you to provide the address and port of the vRealize Operations Manager server, and other connection-related data.

5

You can specify that vRealize Operations Manager override default agent properties when they differ from custom properties that you have defined.

6

Multiple properties are supported in the agent.properties file for an End Point Operations Management agent. Not all supported properties are included by default in the agent.properties file.

Start the End Point Operations Management agent.