6.2

Managing RMI Communication in
vRealize Operations for Horizon 2
The vRealize Operations for Horizon components communicate by using Remote Method Invocation (RMI).
The Horizon adapter exposes RMI services that can be called by an external client. The Horizon adapter acts
as a server and the broker and desktop agents act as clients. You can change the default ports for these RMI
services.
For detailed descriptions of the vRealize Operations for Horizon components, see the
VMware vRealize Operations for Horizon Installation document.
For detailed descriptions of the vRealize Operations for Horizon components, see GUID-2F4628D5-
A8C0-44A3-ADED-077F5B24B004#GUID-2F4628D5-A8C0-44A3-ADED-077F5B24B004.
This chapter includes the following topics:
n
“RMI Services,” on page 7
n
“Default Ports for RMI Services,” on page 8
n
“Changing the Default RMI Service Ports,” on page 8
n
“RMI Considerations for Remote Collector Use,” on page 9
RMI Services
The Horizon adapter exposes the following RMI services.
RMI registry service
The broker and desktop agents initially connect to the RMI registry service
and request the address of a specific RMI server. Because the RMI registry
service is used only for lookup and no sensitive data is transmitted to it, it
does not use an encrypted channel.
Desktop message
server
The desktop agents connect to the desktop message server and use it to send
desktop performance data to the Horizon adapter. The desktop message
server uses an SSL/TLS channel to encrypt the data that is sent from the
desktop agents.
Broker message server
The broker agent connects to the broker message server and uses it for
sending Horizon inventory information to the Horizon adapter. The broker
message server uses an SSL/TLS channel to encrypt the data that is sent from
the broker agent.
Certificate management
server
The broker agent connects to the certificate management server during the
certificate pairing process. The certificate management server does not use an
encrypted channel. Certificates are encrypted by using the server key during
the certificate pairing process. For information, see “Certificate Pairing,” on
page 21.
VMware, Inc. 7