6.2
Table Of Contents
- VMware vRealize Operations for Published Applications Installation and Administration
- Contents
- VMware vRealize Operations for Published Applications Installation and Administration
- Introducing vRealize Operations for Published Applications
- System Requirements for vRealize Operations for Published Applications
- Installing and Configuring vRealize Operations for Published Applications
- Install and Configure vRealize Operations for Published Applications
- Downloading the vRealize Operations for Published Applications Installation Files
- Install the vRealize Operations for Published Applications Solution
- Open the Ports Used by vRealize Operations for Published Applications
- Adding a vRealize Operations for Published Applications License Key
- Associate XD-XA Objects with Your vRealize Operations for Published Applications License Key
- Create an Instance of the vRealize Operations for Published Applications 6.2 Adapter
- Enabling Firewall Rules for XenDesktop Delivery Controllers and PVS Server
- Install the vRealize Operations for Published Applications Broker Agent
- Configure the vRealize Operations for Published Applications Broker Agent
- Configure Broker Agent to use Non-Admin User for Citrix Desktop Delivery Controller
- Install a vRealize Operations for Published Applications Desktop Agent
- Push the vRealize Operations for Published Applications Desktop Agent Pair Token Using a Group Policy
- Install and Configure vRealize Operations for Published Applications
- Monitoring Your Citrix XenDesktop and Citrix XenApp Environments
- Managing RMI Communication in vRealize Operations for Published Applications
- Changing the Default TLS Configuration in vRealize Operations for Published Applications
- Managing Authentication in vRealize Operations for Published Applications
- Certificate and Trust Store Files
- Replacing the Default Certificates
- Certificate Pairing
- SSL/TLS and Authentication-Related Log Messages
- Create a vRealize Operations Manager Support Bundle
- Download vRealize Operations for Published Applications Broker Agent Log Files
- Download vRealize Operations for Published Applications Desktop Agent Log Files
- View Collector and vRealize Operations for Published Applications Adapter Log Files
- Modify the Logging Level for vRealize Operations for Published Applications Adapter Log Files
- Index
Default Ports for RMI Services
The RMI services use certain default ports. The default ports are left open on the firewall on cluster nodes
and remote collector nodes.
Table 6‑1. Default Ports for RMI Services
RMI Service Default Port
RMI registry 3095
Desktop message server 3096
Broker message server 3097
Certificate management server 3098
Changing the Default RMI Service Ports
You can change the default ports for the RMI registry service, desktop message server, broker message
server, and certificate management server.
RMI Service Port Properties
The RMI service ports are defined in properties in the msgserver.properties file on the server where the
vRealize Operations for Published Applications adapter is running.
Table 6‑2. RMI Service Port Properties
RMI Service Property
RMI registry registry-port
Desktop message server desktop-port
Broker message server broker-port
Certificate management server certificate-port
Change the Default RMI Service Ports
You can change the default RMI service ports by modifying the msgserver.properties file on the server
where the vRealize Operations for Published Applications adapter is running.
Prerequisites
n
Verify that you can connect to the node where the vRealize Operations for Published Applications
adapter is running.
n
Become familiar with the RMI service port properties. See “RMI Service Port Properties,” on page 36.
Procedure
1 Log in to the node where the vRealize Operations for Published Applications adapter is running.
VMware vRealize Operations for Published Applications Installation and Administration
36 VMware, Inc.