Installing vROPS for Horizon v6.2.1 – Horizon Adapter and Connection Broker Agent

Now the cluster is installed and running, here’s how to configure the Horizon adapter and connection broker agent for v4H 6.2.1

Open you vRealize UI, click Administration and then Solutions and choose to configure the Horizon Adapter

You will be directed to the licensing page to enter your Horizon license.

Enter your license key hit validate then save

Now create a credential for the horizon adapter

Choose ‘Horizon Adapter’, ‘Pairing Credential’, give the credential a name and create a password.  You will need this password to pair the adapter with the Connection Broker

Once you have created the credential had back to the Solutions menu and again click configure the Horizon adapter.

Give the instance and adapter ID a name and choose the credential you have just created from the drop down box.

You have the option in the Advanced Options to identify a specific collector for the adapter.

Click Test

Providing the test is successful click save to save the adapter configuration.

Now the Horizon adapter is created we need to install the Connection Broker agent and configuring the binding.

You only need to install the vRealize Broker Agent on ONE of the connection servers in your Horizon Pod.

Download the installer from your VMware portal. And start the wizard, the agent requires .NET Framework v4 so you may be prompted to install that before the agent can be installed.

Click Next

Accept the License Agreement

Click Install and make sure the tick box is checked to launch the configuration utility.

Click Finish

The configuration utility should then pop up.  If not run it from Start – All Programs.

Enter the IP address or FQDN of the vRealize node running your Horizon adapter

Leave the port as 3091 unless you have specifically changed this port.

Now enter the pairing key password you created when setting up the credential in the previous steps.

Click Pair

You may see an error:

Could not pair with the adapter address

An error has occurred: could not pair with the adapter

Operation Adapter Pairing has FAILED

This generally means you do not have the required firewall rules open on your network on on the vAPP.

Check out this post

Once the firewall rules are correctly configured try the pairing again

On the next screen you will be prompted to enter your View Events database username and password.  v4H uses the events database to calculate many metrics such as session logon time and uses the alerts and warnings.  You click Test to confirm the credentials and connection.

You are also able to specify the pools you want to monitor, use the pool names and separate with a comma.

You can now choose to edit the intervals and timeouts.  Session intervals are refreshed by default every 5 minutes and full topology by default every hour.

Next choose the logging levels, default is info, but here is where you can change the logging levels for troubleshooting.  Verbose logging should only be switched on for the period of troubleshooting because the log files increase in size dramatically, although logging will halt if the disk they reside on starts reaching capacity.

Finally Start the Broker service review the changes and click Finish

Log back into the UI and check the View Adapter Self Health dashboard.  Everything should be green and the metrics should be collecting.  Ready for you to start customizing your dashboards!

Note:

If you are using vRealize Desktop Agent 6.1 or below consider upgrading the Version to 6.2 or above to get the full complement of metrics.  Some are not available in the earlier version such as session logon times.  You can install the latest desktop agent over the top of the View agent but uninstall the feature from the View Agent beforehand.

Also you will need to change the SSL protocols on the node  to receive data from the older versions. See post

http://lifeonthecloud.co.uk/2016/07/05/metrics-not-collecting-after-a-vrealize-for-horizon-upgradeinstall-to-6-2-1-or-6-3/

Leave a Reply

Your email address will not be published. Required fields are marked *