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
If you select a non-JRE installation option, you must ensure that your Java package includes Java
Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy les to enable registration of the
Endpoint Operations Management agent. If you select a non-JRE option and your Java package does not
include Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy les, you receive these
error messages Server might be down (or wrong IP/port were used) and Cannot support
TLS_RSA_WITH_AES_256_CBC_SHA with currently installed providers.
Configuring JRE Locations for Endpoint Operations Management Components
Endpoint Operations Management agents require a JRE. The platform-specic
Endpoint Operations Management agent installers include a JRE. Platform-independent
Endpoint Operations Management agent installers do not include a JRE.
If you select a non-JRE installation option, you must ensure that your Java package includes Java
Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy les to enable registration of the End
Point Operations Management agent. For more information , see “Java Prerequisites for the Endpoint
Operations Management Agent,” on page 45.
Depending on your environment and the installation package that you use, you might need to dene the
location of the JRE for your agents. The following environments require JRE location conguration.
n
Platform-specic agent installation on a machine that has its own JRE that you want to use
n
Platform-independent agent installation
How the Agent Resolves its JRE
The agent resolves its JRE based on platform type.
UNIX-like Platforms
On UNIX-like platforms, the agent determines which JRE to use in the
following order:
1 HQ_JAVA_HOME environment variable
2 Embedded JRE
3 JAVA_HOME environment variable
Linux Platforms
On Linux platforms, you use export HQ_JAVA_HOME=
path_to_current_java_directory to dene a system variable.
Windows Platforms
On Windows platforms, the agent resolves the JRE to use in the following
order:
1 HQ_JAVA_HOME environment variable
The path dened in the variable must not contain spaces. Consider using
a shortened version of the path, using the tild (~) character. For
example,c:\Program Files\Java\jre7 can become
c:\Progra~1\Java\jre7. The number after the tild depends on the
alphabetical order (where a = 1, b =2, and so on) of les whose name
begins with progra in that directory.
2 Embedded JRE
You dene a system variable from the My Computer menu. Select Properties
> Advanced > Environment Variables > System Variables > New.
vRealize Operations Manager vApp Deployment and Configuration Guide
46 VMware, Inc.