CHAPTER 1: Basic Operation

All information within the vistrax system is managed in multiple databases.

A vistrax installation’s database system always includes at least two databases:

1. vistrax Main database
All system-wide information and settings are managed in the main database. These include user data and connection information to all associated mandator databases.

2. Mandator database
All mandator-specific information and settings are managed in the main database. These include master data and visit data amongst other information.

A separate mandator database is set up for every further mandator. This means that all mandator-specific information is kept isolated in its respective database.

To log in, enter the following data into the login dialog “vistrax Admin Login”:

• Driver

Here you can choose the database driver:

• Microsoft OLE DB Provider for SQL Server (SQLOLEDB): Supports TLS v1.0 only (default).
• Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL): Supports TLS v1.0 and newer, as well as self-signed certificates.

• Name
  This entry corresponds with the information entered during the installation of the database instance and/or the path to an existing instance of Microsoft SQL.

• Port
  Port, to connect to the Microsoft SQL instance (default: 1433).

• Packet Size
  The network packet size in bytes which is used for the database connection. The value must be between 512 and 32767. The maximum network packet size for encrypted connections is 16383. The default network packet size is 4096.

• Data Base
  Select either “VISTRAX” if you have not yet set up a main database, or the database name of an existing vistrax main database

• Authentication Mode

Select the mode to be used for login to the SQL instan

• Microsoft SQL servers: Authentication via a database login (default).
• Windows integrated security: Authentication via a Windows domain user.

• Database Login and Password
  Here you should use the data entered during installation of the database instance, or the login data of an existing database login

• Encrypted Database Connection

Select the mode to be used to encrypt the database connection:

• Disabled: An unencrypted connection is used (default).
• Automatic (encryption preferred): If an encrypted connection can be established, it will be used. Otherwise, an unencrypted connection is used.
• Forced: An encrypted connection is always used.
• Forced: All server certificates are accepted for the encrypted connection (including self-signed ones; MSOLEDBSQL is required).

The overview shows the vistrax main database and gives an overview of the created mandator databases. Settings cannot be altered in this menu item.

In this input dialog you can see the current version number of the vistrax main database currently connected to vistrax. If the main database given during login is not yet available, you have the option of creating a the main database by clicking on “Create”.

vistrax’s architecture enables it to work with multiple mandators. This means, for example, that several companies can share the system. The data of each individual mandator (master data, visitor data etc) is managed in a separate database for each mandator.

You have the possibility of creating a new mandator, duplicating an existing mandator, editing and deleting. When creating a new database, only the mandator name and the name of the database being set up are required. You may, however, also save master data at this stage. The data entered can also be edited later.

Please be aware that duplicating an existing mandator also duplicates all existing data (master data, visitor data, visit history etc.).

When a mandator is deleted, all data is also irrevocably deleted. This process cannot be undone.

In this input dialog you can manage the database logins of the vistrax databases. These database logins are required by vistrax and vistraxWelcome to connect to the database instance in order to retrieve and save data. As a rule only one database login is required, whose access data is then saved in the connection settings of vistrax and vistraxWelcome.

You have the possibility of creating a new database login and duplicating or deleting a existing one.

• “SQL Account” (recommended): Select this option for a database login.
• “Windows User Group” or “Windows Login”: Select this option if you use LDAP / ADS authentication in your database.

The user administration allows vistrax users to be managed and settings regarding the allocation of mandators and user roles to be undertaken.

The following points should be noted:

• Authentication

Here you can choose the desired form of authentication:

• Database: The password is managed in the vistrax database.
• LDAP / Active Directory: Links the user to a LDAP / active directory: If using a windows domain, the user name corresponds to the domain name. If connecting to a LDAP directory, the user name corresponds to the distinguished name Further information on configuration can be found in Chapter 9 in the “LDAP / ADS Authentication” section.

• Access: If you wish to temporarily deactivate a user account, you can prohibit access.

A user role embodies the permissions and properties a user in vistrax has. Access permissions are grouped in categories.

After the device registration (see vistrax Self Input: Register Devices ), the device needs to be authorized. To do this, select the “Devices” menu item.

There you select the registered device and assign a user to it. Then authorize the device by clicking the “Grant access” button.

The application offers the possibility to present visitors with hints and information about your upcoming stay as part of the self-registration.

One file role can be assigned to the device per mandator.

Select the needed device in the overview and press the “Revoke access” button.

This input dialog allows you to carry out required database migrations. A migration is necessary when the database structure changes (e.g. for a new version of the software). When updating to a new version, a migration of an existing database may be required in order to use this data.

The status field will display whether a migration is necessary. To begin a migration, press the button “Migrate Databases”.

Use the “Synchronize Database Logins” button to force a synchronization of the user's master data in vistrax main database with all mandator databases. Synchronization may be required if mandator databases or individual user master data have been manually created, modified, imported or restored, e.g. through external access to the SQL databases.

With the button “Reset Record Locks” you have the possibility to reset all database record locks. This may be necessary if, for example, vistrax was not closed properly. The record locks are always reset on the main database and the selected mandator databases. The selection of the mandator databases takes place after pressing the button.