Creating a resource hub

A resource hub consists of three utilities, which are typically set up in the same region as a server pool.

• Hyperstream – This is the Apporto technology that transforms Windows, Linux, or Mac screens into HTML/H264 that can be displayed in a browser.
• Filestore – This utility enables users to upload and download files from their virtual desktops.
• Load balancer – This is the RDP load-balancer used to distribute user sessions across the RDP multi-user server pools.

Use the information in this guide to learn how to:

• Create a new resource hub
  • Add a hyperstream
  • Add filestores
  • Add a load balancer

You may also visit the related article on managing resource hubs to learn about the Resource hub list page and how to update an existing resource hub.

Create a new resource hub

To begin creating a resource hub, follow the steps below.

1. Log in to the system using your credentials.
2. Click resource hubs or the  icon in the navigation panel.
3. The list of resource hubs will display. You may filter the list or adjust the displayed columns to locate records. See the article on working with lists for more information.
4. Click create resource hub. The system will direct you to the Create resource hub page.
5. Create the resource hub profile.

The first part of the resource hub configuration is the profile section.

The table below shows the values that make up a resource hub profile.

Field	Datatype	Required?	Notes
Name	String	Yes
Description	String	Yes
Cloud	Lookup value	Yes	Other – this option applies to on-premises resource hubs AWS Azure Mac Stadium
Cloud region	Lookup value	Yes	Options are dependent on cloud selection Other Hybrid AWS Canada Central Canada West Frankfurt Germany Hong Kong Ireland London Mumbai Northern California Northern Virginia Ohio Oregon Azure East US Germany West London North Central US South Central US West US Mac Stadium Atlanta Las Vegas
Capacity API	String	No	Value indicates the URL of the Capacity API service to be used by this resource hub. If the hyperstream service is deployed inside a K8S cluster, the URL will be http://hap-capacity-api.api-microservices-prod.svc:5000/hap-capacity-api/. If the hyperstream cluster is deployed as a standalone service, the URL will point to the Capacity API ingress URL. The ingress URL has the form https://{REGION_ID}-api-prod.apporto.com/hap-capacity-api/, where {REGION_ID} typically corresponds to the region ID hosting the hyperstream cluster.
Resource hub active	Boolean	Yes	By default, the desktop pool will be inactive.

 

Add a hyperstream

At the bottom of the Create resource hub page, you may view the hyperstream configuration for the resource hub. A maximum of one hyperstream can be configured for the resource hub at a time.

To add a hyperstream, follow the steps below:

1. From the “hyperstream” section, click add hyperstream.
2. The system will display the Add new hyperstream pop-up.
   
   
3. Enter the necessary values. The table below shows the values that make up a hyperstream record.
   

   Field	Datatype	Required?	Notes
   Name	String	Yes	A user-friendly name for the hyperstream service.
   Description	String	Yes	Any meaningful description that helps describe this service.
   URL	String	Yes	The public URL of the hyperstream service. This URL must be accessible by your end-users. The URL must have the following form: https://{FQDN}/hyperstream/#/client/
   Secret	String	No	The value is used for the payload validation during authentication to on-premise hyperstream deployments. The secret entered here must match the secret stored in the hyperstream services configuration. If not specified, the Apporto cloud default will be used.

4. Click add hyperstream. The system will close the pop-up.
5. The newly created hyperstream will display in the tab. Click save changes to confirm.
   
   
6. Click edit to update a hyperstream’s values or remove to delete an unwanted hyperstream. See the article on managing resource hubs for more information.

Add filestores

The second tab in the bottom section displays filestores that are assigned to the resource hub.

To add a filestore, follow the steps below:

1. From the “filestore” tab, click add filestore.
2. The system will display the Add new filestore pop-up.
   
   
3. Enter the necessary values. The table below shows the values that make up a filestore record.
   

   Field	Datatype	Required?	Notes
   Name	String	Yes
   Description	String	No
   Type	Lookup value	No	Unknown DFS NFS
   FQDN or hostname	String	Yes

4. Click add filestore. The system will close the pop-up.
5. The newly created filestore will display in the tab. Click save changes to confirm.
   
   
6. Click edit to update a filestore’s values or remove to delete an unwanted filestore. See the article on managing resource hubs for more information.

Add a load balancer

The third tab displays the load balancer configuration for the resource hub. This is the RDP Load-balancer used to distribute user sessions across the RDP multi-user server pools. A maximum of one load balancer can be configured for the resource hub at a time.

To add a load balancer, follow the steps below:

1. From the “load balancers” section, click add load balancer.
2. The system will display the Add new load balancer pop-up.
   
   
3. Enter the necessary values. The table below shows the values that make up a load balancer record.
   

   Field	Datatype	Required?	Notes
   Name	String	Yes	A user-friendly name for the RDP load-balancer endpoint
   Description	String	No	Any meaningful description that helps describe this RDP load-balancer
   FQDN or hostname	String	Yes	The FQDN or Hostname of the RDP load-balancer used by this resource hub

4. Click add load balancer. The system will close the pop-up.
5. The newly created load balancer will display in the tab. Click save changes to confirm.
   
   
6. Click edit to update a load balancer’s values or remove to delete an unwanted load balancer. See the article on managing resource hubs for more information.