Installation Variants and Requirements
Installation variants This document is intended to provide food for thought. It describes the technical possibilities of different installation scenarios and their advantages and disadvantages. In general, a server-client installation is recommended for the classic Q-DAS Desktop products, but there may be exceptions, which will be discussed in the workshop. |
English:PDF | German:PDF |
System requirements for version 14.0.4.x. This document provides information on the system requirements for using of classic Q-DAS Desktop products. |
English:PDF | |
Details of the system requirements for using the Q-DAS Web products are part of the Web Client document. |
||
Active Directory - Windows user rights - Food for thoughts This document shows how to reasonably apply Active Directory user rights to the folder structure of Q-DAS products. |
English:PDF | German:PDF |
New Installation
Server provisioning for version 14.0.4.x For a server provisioning, the Q-DAS setup provides the installation type "Concurrent - Network Installation". The aspects to consider and how to plan, prepare and perform the installation are described here. |
English:PDF | |
Client provisioning (Setup) for version 14.0.4.x This document describes how to distribute the Q-DAS application to the user's computer using the Q-DAS Client Setup. |
English:PDF | |
ACLP installation - Client provisioning ACLP provides the ability to create an automated process for distributing clients to user computers. Especially when Q-DAS applications are to be distributed to several computers (clients), the installation effort can be reduced considerably. |
English:PDF | |
Local installation for version 14.0.4.x Although "ConCurrent - Single Installation" (local) installations should be avoided, they are sometimes necessary. Examples include the use of O-QIS monitoring or workstations with very poor network connections. |
English:PDF | |
Offline client The offline client offers the possibility to work with the Q-DAS products to their full extent without an existing connection to the server. For this purpose, a local installation is performed where the licence is "borrowed" from the server for a limited period of time. An offline client can also be installed in parallel with a normal client. This is useful if, for example, a process acceptance is being carried out at the customer's premises where a network connection is not possible. |
English:PDF | German:PDF |
Web client for version 14.0.4.x This document describes how to distribute the web-based Q-DAS application to the user's computer. The difference to the classic client installation is that the web client installation must be performed on the same server as the server provision. The document combines the system requirements for the Q-DAS Web products and the installation. |
English:PDF |
Update and Upgrade
Major upgrade to version 14 Up to version 12, all major releases were installed in parallel with a new major release. Since version 12, an automatic update is performed. Depending on the current major version, updating the databases or user-specific files and settings requires a different procedure. The aspects to consider and how to plan, prepare and perform the major upgrade are described here. |
English:PDF | German:PDF |
Major upgrade from version 11 or lower to version 13 This document explains how to transfer the available settings of the previous version to version 13 and how to apply them. Although the old versions are no longer supported, this documentation describes the upgrade process from version 11 or lower to version 13. |
English:PDF | German:PDF |
Minor upgrades This documentation describes the use of the automatic patch installation for the minor upgrades within version 14. |
English:PDF | German:PDF |
Tools and further assistance
License Management The tool for license management is "Q-DAS License". It is one of the administrative Q-DAS applications in the Q-DAS Tools Launcher. Link to Q-DAS Tools Launcher |
||
Database Management All database connections are stored in a central file (FireDAC) and can be managed with the "Database Connect" tool. It is one of the administrative Q-DAS applications in the Q-DAS Tools Launcher. Link to Q-DAS Tools Launcher |
||
Create and update databases (Static DB) The tool for manual update or creation of Q-DAS databases is "Static DB". It is one of the administrative Q-DAS applications in the Q-DAS Tools Launcher. Link to Q-DAS Tools Launcher |
||
Creating databases on a Microsoft SQL Server or Oracle |
English:PDF | German:PDF |
Scripts prepared for Oracle: SQL-Scripts_V13.zip |
||
Updating existing databases on a Microsoft SQL Server Updating the SQL databases is a process that consists of several steps using various Q-DAS administrative tools. This document explains which tools are required and in which order. The required administrative tools can be found in the Q-DAS Tools Launcher. Link to Q-DAS Tools Launcher |
Englisch:PDF |
German:PDF |
Manual adjustments after the update to V14 for working with VDA5 in the third edition
Update to VDA5 third edition. In accordance with the basic rules of the update, no customer-specific configurations or files are affected when updating from V13 to V14. This also applies to the masks and report templates for working with VDA5 as well as the standard graphics. For this reason, if you decide to switch to VDA5 in the third edition, this customisation must be carried out manually. |
English:PDF | German:PDF |
Graphic files for import for the VDA5 third edition: Uncertainty_Budget_Form_VDA5_V14.zip |
||
Mask files for the VDA5 3rd. Edition to replace the existing ones: VDA5_masks.zip |
Eligibility Statement Standards for Quality Management concretely require a confirmation for the eligibility of the applied software for the intended application, before initial use as well as for a continuous use. Link to Eligibility Statement |