You can install the Endpoint Operations Management agent from a RedHat Package Manager (RPM) package. The agent in the
noarchpackage does not include a JRE.
Before you begin
Verify that you have sufficient privileges to deploy an Endpoint Operations Management agent. You must have vRealize Operations Manager user credentials that include a role that allows you to install Endpoint Operations Management agents. See Roles and Privileges in vRealize Operations Manager.
If you plan to run ICMP checks, you must install the Endpoint Operations Management agent with root privileges.
To configure the agent to use a keystore that you manage yourself for SSL communication, set up a JKS-format keystore for the agent on its host and configure the agent to use its SSL certificate. Note the full path to the keystore, and its password. You must specify this data in the agent agent.properties file.
Verify that the agent keystore password and the private key password are identical.
If you are installing a non-JRE package, define the agent
Endpoint Operations Management platform-specific installers include JRE 1.8.x. Platform-independent installers do not. Depending on your environment and the installer you use, you might need to define the location of the JRE to ensure that the agent can find the JRE to use. See Configuring JRE Locations for Endpoint Operations Management Components.
If you are installing a non-JRE package, verify that you are using the latest Java version. You might be exposed to security risks with earlier versions of Java.
Verify that the installation directory for the Endpoint Operations Management agent does not contain a vRealize Hyperic agent installation.
If you are using the
noarchinstallation, verify that a JDK or JRE is installed on the platform.
Verify that you use only ASCII characters when specifying the agent installation path. If you want to use non-ASCII characters, you must set the encoding of the Linux machine and SSH client application to UTF-8.
About this task
Agent-only archives are useful when you deploy agents to a large number of platforms with various operating systems and architectures. Agent archives are available for Windows and UNIX-like environments, with and without built-in JREs.
The RPM performs the following actions:
Creates a user and group named epops if they do not exist. The user is a service account that is locked and you cannot log into it.
Installs the agent files into /opt/vmware/epops-agent.
Installs an init script to /etc/init.d/epops-agent.
Adds the init script to chkconfig and sets it to on for run levels 2, 3, 4, and 5.
If you have multiple agents to install, see Install Multiple Endpoint Operations Management Agents Simultaneously.
- Download the appropriate RPM bundle to the target machine.
RPM Bundle to Download
64bit Operating System
32bit Operating System
- Open an SSH connection using
rpm -i epops-agent-Arch-linux-version.rpmto install the agent on the platform that the agent will monitor, where Arch is the name of the archive and version is the version number.
The Endpoint Operations Management agent is installed, and the service is configured to start at boot.
What to do next
Before you start the service, verify that the
epops user credentials include any permissions that are required to enable your plug-ins to discover and monitor their applications, then perform one of the following processes.
Run service epops-agent start to start the epops-agent service.
If you installed the Endpoint Operations Management agent on a machine running SuSE 12.x, start the Endpoint Operations Management agent by running the [EP Ops Home]/bin/ep-agent.sh start command.
When you attempt to start an Endpoint Operations Management agent you might receive a message that the agent is already running. Run ./bin/ep-agent.sh stop before starting the agent.
Configure the agent in the agent.properties file, then start the service. See Activate Endpoint Operations Management Agent to vRealize Operations Manager Server Setup Properties.