QEST Platform Post Install Configuration via QEST Web App
- Mark Elkomos
QEST Platform 5.0 Documentation
Applies to QEST Web App
Contents
- Initial Setup
- Database Connections
- Client URIs
- SMTP
- Notifications
- Data Integrators
- License Usage
- Logging
- QESTNet Restart
After installing QEST Platform products other than QESTLab, there are a number of configuration items that need to be completed to connect the products together and to their respective databases. These articles outline the administration and configuration functionality for QEST Platform that should be completed post-install and are accessible via the QEST Web App.
Required Post-Install Configuration
After installing the QESTNet, QEST Web API and QEST Web App products, users can configure the connections between non-QESTLab QEST Platform products as well as the database connections for these products. This post installation configuration is required in order for these products to function correctly.
| Article | Description |
|---|---|
| Initial Setup | The initial setup page that users will see upon navigating to the QEST Web App after installing the QESTNet, QEST Web API and QEST Web App products. This initial setup allows a connection to the QEST Platform database to be defined for the QESTNet product, allowing further configuration to take place. |
Definitions of the database connections that QESTNet uses for various tasks. A connection to the QEST Platform database, named QESTLab_Data, is required at minimum. Other database connections that may need to be configured here are:
| |
| Client URIs | Client URIs for various QEST Platform are provided to the QESTNet to allow products to connect to one another.
|
| SMTP | SMTP settings that will allow emails to be sent via products that utilize the QESTNet service. This includes publishing reports by email from QESTField as well as the sending of license monitoring emails to system administrators. If these settings are not completed, no emails will be able to be sent from these products. |
| Notifications | If the QESTField Scheduler is in use along with notifications to technicians, these settings allow some configuration of how notifications function. |
| Data Integrators | If specialist data integrators are being used that connect to another on-premises system to transfer data between the QEST Platform and that system, these connections are defined here. Spectra QEST will advise organizations if this configuration is necessary and provide the required values. |
| License Usage | Configuration of features related to Checking Concurrent License Use for the QEST Platform. Configuration of where licensing log files are stored, settings for the licensing warning emails (including recipients and transfer interval). |
| Logging | The QESTNet service generates log files for the purposes of aiding troubleshooting. These settings define where the log files are created as well as what level of details is included. |
| QESTNet Restart | Allows the QESTNet service to be restarted for configuration changes to take effect. Downtime and Potential Loss of Data The QESTNet service should only be restarted when there are no users actively using QEST Platform products. Restarting the QESTNet while users have active QESTField sessions will disconnect those sessions and potentially result in data loss. |
Products described on these pages, including but not limited to QESTLab®, QESTNet, QESTField, QEST Web App, Construction Hive, and associated products are Trademarks (™) of Spectra QEST Australia Pty Ltd and/or related companies. The content of this page is confidential. Do not share, duplicate or distribute without permission. © 2021 Spectra QEST® Australia Pty Ltd and/or related companies. Terms of Use and Privacy Statement
Related content
Integrity | Curiosity | Empathy | Unity
The content of this page is confidential and for internal Spectra QEST use only. Do not share, duplicate or distribute without permission.