6.3
Table Of Contents
- vRealize Operations Manager vApp Deployment and Configuration Guide
- Contents
- About vApp Deployment and Configuration
- Preparing for Installation
- Creating the Master Node
- Scaling Out by Adding a Data Node
- Adding High Availability
- Gathering More Data by Adding a Remote Collector Node
- Continuing With a New Installation
- Connecting to Data Sources
- VMware vSphere Solution
- Endpoint Operations Management Solution
- Endpoint Operations Management Agent Installation and Deployment
- Prepare to Install the Endpoint Operations Management Agent
- Supported Operating Systems for the Endpoint Operations Management Agent
- Selecting an Agent Installer Package
- Install the Agent on a Linux Platform from an RPM Package
- Install the Agent on a Linux Platform from an Archive
- Install the Agent on a Windows Platform from an Archive
- Install the Agent on a Windows Platform Using the Windows Installer
- Installing an Endpoint Operations Management Agent Silently on a Windows Machine
- Java Prerequisites for the Endpoint Operations Management Agent
- Configuring JRE Locations for Endpoint Operations Management Components
- System Prerequisites for the Endpoint Operations Management Agent
- Configure the Endpoint Operations Management Agent to vRealize Operations Manager Server Communication Properties
- Activate Endpoint Operations Management Agent to vRealize Operations Manager Server Setup Properties
- Specify the Endpoint Operations Management Agent Setup Properties
- Configure an Endpoint Operations Management Agent Keystore
- Configure the Endpoint Operations Management Agent by Using the Configuration Dialog
- Overriding Agent Configuration Properties
- Endpoint Operations Management Agent Properties
- Encrypt Endpoint Operations Management Agent Property Values
- Adding Properties to the agent.properties File
- agent.keystore.alias Property
- agent.keystore.password Property
- agent.keystore.path Property
- agent.listenPort Property
- agent.logDir Property
- agent.logFile Property
- agent.logLevel Property
- agent.logLevel.SystemErr Property
- agent.logLevel.SystemOut Property
- agent.proxyHost Property
- agent.proxyPort Property
- agent.setup.acceptUnverifiedCertificate Property
- agent.setup.camIP Property
- agent.setup.camLogin Property
- agent.setup.camPort Property
- agent.setup.camPword Property
- agent.setup.camSecure
- agent.setup.camSSLPort Property
- agent.setup.resetupToken Property
- agent.setup.unidirectional Property
- agent.startupTimeOut Property
- autoinventory.defaultScan.interval.millis Property
- autoinventory.runtimeScan.interval.millis Property
- http.useragent Property
- log4j Properties
- platform.log_track.eventfmt Property
- plugins.exclude Property
- plugins.include Property
- postgresql.database.name.format Property
- postgresql.index.name.format Property
- postgresql.server.name.format Property
- postgresql.table.name.format Property
- scheduleThread.cancelTimeout Property
- scheduleThread.fetchLogTimeout Property
- scheduleThread.poolsize Property
- scheduleThread.queuesize Property
- sigar.mirror.procnet Property
- sigar.pdh.enableTranslation Property
- snmpTrapReceiver.listenAddress Property
- Managing Agent Registration on vRealize Operations Manager Servers
- Securing Communications with the Server
- Launching Agents from a Command Line
- Managing an Endpoint Operations Management Agent on a Cloned Virtual Machine
- Understanding Agent Uninstallation and Reinstallation Implications
- Install Multiple Endpoint Operations Management Agents Simultaneously
- Roles and Privileges
- Registering Agents on Clusters
- Manually Create Operating System Objects
- Managing Objects with Missing Configuration Parameters
- Mapping Virtual Machines to Operating Systems
- Endpoint Operations Management Agent Upgrade for vRealize Operations Manager 6.3
- Endpoint Operations Management Agent Installation and Deployment
- Installing Optional Solutions
- Migrate a vCenter Operations Manager Deployment into this Version
- Post-Installation Considerations
- Updating Your Software
- Index
Table 1‑1. Effect of Deployment Conditions on Complexity (Continued)
Complexity Level
Current or New Deployment
Condition Additional Notes
Red Your current
vRealize Operations Manager
deployment required a Professional
Services engagement to install it.
If your environment was complex
enough to justify a Professional
Services engagement in the previous
version, it is possible that the same
conditions still apply and might
warrant a similar engagement for this
version.
Red Professional Services customized
your vRealize Operations Manager
deployment. Examples of
customization include special
integrations, scripting, nonstandard
congurations, multiple level
alerting, or custom reporting.
If your environment was complex
enough to justify a Professional
Services engagement in the previous
version, it is possible that the same
conditions still apply and might
warrant a similar engagement for this
version.
vRealize Operations Manager Cluster Nodes
All vRealize Operations Manager clusters consist of a master node, an optional replica node for high
availability, optional data nodes, and optional remote collector nodes.
When you install vRealize Operations Manager, you use a vRealize Operations Manager vApp deployment,
Linux installer, or Windows installer to create role-less nodes. After the nodes are created and have their
names and IP addresses, you use an administration interface to congure them according to their role.
You can create role-less nodes all at once or as needed. A common as-needed practice might be to add nodes
to scale out vRealize Operations Manager to monitor an environment as the environment grows larger.
The following node types make up the vRealize Operations Manager analytics cluster:
Master Node
The initial, required node in vRealize Operations Manager. All other nodes
are managed by the master node.
In a single-node installation, the master node manages itself, has adapters
installed on it, and performs all data collection and analysis.
Data Node
In larger deployments, additional data nodes have adapters installed and
perform collection and analysis.
Larger deployments usually include adapters only on the data nodes so that
master and replica node resources can be dedicated to cluster management.
Replica Node
To use vRealize Operations Manager high availability (HA), the cluster
requires that you convert a data node into a replica of the master node.
The following node type is a member of the vRealize Operations Manager cluster but not part of the
analytics cluster:
Remote Collector Node
Distributed deployments might require a remote collector node that can
navigate rewalls, interface with a remote data source, reduce bandwidth
across data centers, or reduce the load on the vRealize Operations Manager
analytics cluster. Remote collectors only gather objects for the inventory,
without storing data or performing analysis. In addition, remote collector
nodes may be installed on a dierent operating system than the rest of the
cluster.
Chapter 1 Preparing for vRealize Operations Manager Installation
VMware, Inc. 11