Data and database configuration

Use the Database Connection Settings in the GAPTEQ Designer to configure and manage all database connections for your repository.

In this article you will read the following content:

Connection GAPTEQ Designer to the database

Connection of your GAPTEQ application

1. connecting the GAPTEQ Designer to the database

• Double-click on the stored database in the left-hand menu tree of the GAPTEQ Designer to open the “Database connection” configuration options.
• Under “Design time connection” you can finally configure the connection of the GAPTEQ Designer to the database. 

• You can use the “Define filter” button to improve performance and clarity when importing database information.

If no further configurations are made, the connection string is also used for the runtime connection. When creating a new database connection via the wizard, the connection string is stored in the “Design time connection”.

2. connection of your GAPTEQ application

You will find the “Runtime connection” directly below the “Design time connection” and can manage and configure the connection used by your GAPTEQ application here:

• • Database authentication with the AD user of the logged-in user.
    
  • Database authentication depending on the user group membership of the GAPTEQ user.
  • Set session variables and custom role groups using database queries.
• Activate the “Use a different connection for runtime” checkbox if the GAPTEQ application should use a different database connection to the GAPTEQ Designer. The connection string can be created manually or with the wizard.

• Activate the checkbox “Impersonate directory user for connection” (integrated security) and enter the access data for an Active Directory user here. Authentication against the database then takes place with this user.
• In the “Query timeout” field, set the time (in sec) before a timeout should occur in the SQL server.
• In the “Statement timeout” field, set the time (in sec) before a timeout should occur in the SQL server.
• If you activate the checkbox “This Database requires an authenticated User”, a logged-in user is required for each page of your application. This also applies to pages for which no restrictions have been defined in the access rights (public pages).

3. Authentication to the database

Under “Map accounts”, different authentications to the database can be defined for logged-in users according to their user group affiliation. The following authentication methods are available:

• User saved in Runtime connection (user name and password from the connection string)
• Database user (database user name and password)
• Directory user (“Impersonate as User”, Active Directory user name and password)
• Logged on user (“Impersonate directory users”, authentication against the database takes place with the AD account of the logged-in user)