Introduction
This article explains the component parts that make up your full HighQ URL and the processes required for your instance of the platform to be accessible.
Glossary
The items highlighted in blue denote the part of the URL that matches the definition. The domain name, resource name, and context name will be different for each instance.
Domain name - https://platformname.clientname.com/instance
Subdomain/Resource name - https:/platformname.clientname.com/instance
Context name - https://platformname.clientname.com/instance
URL - https://platformname.clientname.com/instance
CNAME - platformname.clientname.com.cn.highq.com.
Domain name
The domain name is the main realm that the platform will live under. The most common approach for our clients is to use their existing domain e.g. clientname.com. However, it is also completely possible to use an entirely different domain for the platform.
Subdomain/Resource name
If you wish to use your existing domain as the main realm for the platform you will need to add a new subdomain, this is also referred to as the resource name at HighQ. The subdomain can go to multiple levels. Most commonly a two-level subdomain is used i.e. platform.clientname.com. It is also possible to go to multiple levels but it is generally best practice to limit to the third subdomain i.e. uk.platform.clientname.com
Context name
The context name is what is shown after the ‘/’ of the platform domain, e.g. https://platformname.clientname.com/instance
The context name is directly related to the database name of the platform and it must be a unique name. This means that a lot of generic names such ‘collaborate’, ‘portal’, ‘hub’ etc cannot be used as the context name.
Please be aware that once the context name/database name is set, changing it afterwards is very complex and would likely be chargeable exercise.
CNAME
Once you have decided the resource name, the next step is to register the CNAME with your authoritative DNS provider. This provides the path to route requests to the correct instance.
The CNAME is created internally by you the customer and is not controlled by HighQ.
CNAME is the abbreviation for 'Canonical Name record', it is a type of resource record in the Domain Name System (DNS) used to specify that a domain name is an alias for another domain.
Below is the full string required for the CNAME registration. As explained earlier in the article, you will need to replace the placeholder names below with your choices for domain name, resource name and context name.
platform.clientname.com.cn.highq.com.
The dot at the end of the string must be included.
Multiple instances
If you have purchased multiple instances or you are now planning to add an additional instance, there is certain information that you should consider for the domain name and context name.
Three level subdomain
You may have chosen to obtain a second instance so that data is hosted in a different region and therefore data centre. In this scenario, it is prudent to consider presenting the HighQ instances on a three level subdomain. This would allow you to retain a common subdomain name as the key identifier (e.g. collaborate). This is a standard approach for larger companies and it is commonly understood that this normally represents the location for best connection or data centre.
Multiple context names
Again when possessing multiple instances, it is recommended that you retain similar context names so that an end-user sees as little change as possible. It is important to note the context names must still be unique.
Example
OR
-
clientnameuk
-
clientnameus
Unified URL
It is possible to use one domain or subdomain for both your Collaborate and Publisher instances. The differentiator in this scenario is the context name. Below you will notice that both of the HighQ instances have the same URL but different context names.
Collaborate - https://platformname.clientname.com/collaborate
Publisher - https://platformname.clientname.com/publisher
Certain pre-requisites must be adhered to achieve this unified URL scenario:
This does not currently work with an instance of Publisher that already exists.
