7.2

Table Of Contents
Collecting a Log File Bundle
You can collect a bundle of log files to send to VMware support. You obtain the bundle from the connector
configuration page.
The following log files are collected in the bundle.
Table 29. Log Files
Component Location of Log File Description
Apache Tomcat Logs
(catalina.log)
/opt/vmware/horizon/workspace/logs/catal
ina.log
Apache Tomcat records messages that
are not recorded in other log files.
Configurator Logs
(configurator.log)
/opt/vmware/horizon/workspace/logs/confi
gurator.log
Requests that the Configurator receives
from the REST client and the Web
interface.
Connector Logs (connector.log)
/opt/vmware/horizon/workspace/logs/conne
ctor.log
A record of each request received from the
Web interface. Each log entry also
includes the request URL, timestamp, and
exceptions. No sync actions are recorded.
Procedure
1 Log in to the connector configuration page at https://connectorURL:8443/cfg/logs.
2 Click Prepare log bundle.
3 Download the bundle and send it to VMware support.
Scenario: Configure an Active Directory Link for a Highly
Available vRealize Automation
As a tenant administrator, you want to configure an Active Directory over LDAP directory connection to
support user authentication for your highly available vRealize Automation deployment.
Each vRealize Automation appliance includes a connector that supports user authentication, although
only one connector is typically configured to perform directory synchronization. It does not matter which
connector you choose to serve as the sync connector. To support Directories Management high
availability, you must configure a second connector that corresponds to your second vRealize Automation
appliance, which connects to your Identity Provider and points to the same Active Directory. With this
configuration, if one appliance fails, the other takes over management of user authentication.
In a high availability environment, all nodes must serve the same set of Active Directories, users,
authentication methods, etc. The most direct method to accomplish this is to promote the Identity Provider
to the cluster by setting the load balancer host as the Identity Provider host. With this configuration, all
authentication requests are directed to the load balancer, which forwards the request to either connector
as appropriate.
Configuring vRealize Automation
VMware, Inc. 150