Configuring DNS for the Web interface
Who is this article for?
IT Administratorsperforming an installation of IQM 7 Web interface.
Windows infrastructure knowledge is recommended.
Quality Management offers a web-based version of the solution which allows you to access and use the system without the need to install a local client. Before your users can access it, you need to install and configure several components.
This article is part of a series of articles covering the Web client installation process and outlines how to set up the DNS settings.
We recommend consulting the hardware and software requirements for the interface to ensure the systems used within your organisation will support it.
1. Configuring the DNS
To configure the DNS record, make sure it points to the IP address of the server. This is to ensure that the site resolves when the sub-domain is created by the interface.
If you have multiple databases listed on your login screen, you will need to create a corresponding DNS record for each one, pointing to the IP address of the server. This ensures that the site resolves when the sub-domain is created by the client.
Example
I have a Live and Training database, so I would have to create the following sub-domain records in DNS:
- Live.YourServerName
- Training.YourServerName
If you choose to use SSL to secure your connection, you will need a wildcard certificate to secure each database.
Depending on your setup, you may require a wildcard certificate that secures two levels.
Example
My fully qualified domain name is qpulse.ideagen.com and I have a Live and Training database, so I would need a wildcard certificate that can secure the following URLs:
- live.qpulse.ideagen.com
- training.qpulse.ideagen.com
I can achieve this with a wildcard for the qpulse level:
- *.qpulse.ideagen.com
Are you on v7.9 (or later)?
Starting wtih v7.9, the database name is passed as a query parameter rather than as a sub-domain. This means that you don't have to set up extra DNS entries due to how the URLs are formatted.