Lab 1: Performance Problems with the Horizon Connection Server

Objective and Tasks
In this lab, you address performance problems with the Connection Server 01:

  1. Log In to the  Control Center
  2. Verify the Horizon Connection Server CPU and Memory
  3. View the Event Logs
  4. Confirm Java Heap Use in Logs
  5. Change the Horizon Connection Server CPU and Memory
  6. Verify the New Java Heap Size
Task 1: Log In to ControlCenter
  • In this task, you log in to the ControlCenter  to set up for the lab.
  • ControlCenter.techseals.co is your domain controller DNS server and Root CA server
  • Its also your primary landing desktop into your assigned vAPP
  1. Access the ControlCenter in the lab environment. Use these credentials:
    • User name: techseals\Administrator
    • Password: Pa$$w0rd
    • Note: Its also your primary landing desktop into your assigned vAPP
Task 2: Verify the Horizon Connection Server CPU and Memory

In this task, You would  use ControlCenter to access the infrastructure.

  1. On the ControlCenter Server
  2. Open  Chrome Browser
  3. From the Favourites bar,
  4. Once logged it to the vCenter,
  5. From the Inventory, navigate to VMs and Templates.
  6. Expand vcenter-01a.techseals.co>Region01A  Datacenter
  7. Identify the HZN-01c VM.
  8. Select the HZN-01c VM and click the Summary tab
  9. Under VM Hardware find and record the values for CPU and RAM allocated to this VM.
  10. Right-click HZN-01c VM in the left navigation pane and select Power > Restart Guest OS
    • To Confirm the Guest OS Restart, click Yes
    • Wait 2-3 minutes to allow time for the VM to reboot before continuing to the next task
      • Note
        • Regular reboots can ensure that the cache is cleared and logs are easier to navigate.
Task 3: View the Event Logs

In this task, you review the Horizon 1c Event Logs using Horizon console.

  1. From the ControlCenter Server, open a new Chrome tab and click the Horizon 1c bookmark.
  2. Log in to the Horizon Connection Server Horizon 1c admin console .
    • User name: administrator
    • Password: Pa$$w0rd
  3. From the left navigation pane, expand Monitor and select Events.
    • On the Events page, click the Filter icon to open the Event Filters page.
    • Change the Time Period to Last Week
    • From the Severity menu, select Warning and click Submit.
    • Note: A list of warning messages about the Horizon Connection Server physical memory appears.
Task 4: Confirm Java Heap Use in Logs

In this task, you confirm that Java Heap Use log entries appear in the Horizon 1c VM logs.

  1. From the ControlCenter Desktop, open an Remote Desktop > Site1
  2. Connect to HZN-01c VM using RDP icon in the folder
  3. You should automatically login as techseals\Administrator
  4. Access the Connection Server Logs
    1. Navigate to:
      • %programdata%\Omnissa\Horizon\logs
    2. Double-click the latest debug log file or right click and select to Edit with Notepad++
    3. The log file opens.
  5. Scroll to the bottom of the log file:
    1. From here, search back up through the log file, searching for the phrase java heap size
      • Record the values for xmx.
    2. You find three entries, one for Tunnel Service, one for Tomcat, and one for MessageBus. Record the values for each service.
    3. Observe that the Tomcat service and the MessageBus service have been allocated the same amount of memory.
  6. Shut down the HZN-01c VM from the RDP session.
Task 5: Change the Horizon Connection Server CPU and Memory

In this task, you correct the Horizon 1c  underresourcing issue.

  1. Return to vSphere Client Access in the chrome browser
  2. Confirm that HZN-01c is powered Off. If necessary, Login:
  3. From the vCenter Inventory, right click the Hzn-01c and select  Edit settings
  4. Observe the current values for CPU and Memory
    • Change the CPU to 4
    • Change the Memory to 10
    • click OK
  5. Power On the VM.
Task 6: Verify the New Java Heap Size

In this task, you review the new Java Heap Use log entries that appear in the Horizon 1c Connection Server

  1. From the ControlCenter Desktop, open an Remote Desktop > Site1
  2. Connect to HZN-01c VM
  3. You should automatically login as  techseals\Administrator
  4. Access the Connection Server Logs
    1. Navigate to:
      • %programdata%\Omnissa\Horizon\logs
    2. Double-click the latest debug log file or right click and select to Edit with Notepad++
    3. The log file opens.
  5. Scroll to the bottom of the log file:
    1. From here, search back up through the log file, searching for the phrase java heap size
    2. You find three entries, one for Tunnel Service, one for Tomcat, and one for MessageBus. Record the values for each service.
    3. Compare the new CPU and Memory values with their original values.
    4. The increased value for the three services indicates an increase in memory.
  6. Close the RDP session to the Horizon 1c VM but leave the VM powered on. The change in memory ensures that the Horizon Connection Server VM operates within expected parameters.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.