[[:en:v2:vistraxadmin:systemmenue|NEXT]] \\ \\ \\ ====== CHAPTER 1: Basic Operation ====== ===== vistrax Database Structure ===== 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. ===== Installation ===== **You have to install a database instance before a login is possible. You find detailed instructions in the [[en:v2:installationshilfe:voraussetzungen|Setup Guide.]] ** ===== Login ===== 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. **MSOLEDBSQL is only available for selection if the driver is installed on the workstation. Information about the download and installation can be found [[en:v2:installationshilfe:voraussetzungen#vistrax database instance|here.]] ** * **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. **If the installation information remains unchanged, the instance name comprises the computer name followed by “\VISTRAX”. For example “MyComputer\VISTRAX”.** * **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. **Do not change the packet size unless you are certain that it will improve performance. For most applications, the default packet size is best.** * **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 instance * Microsoft SQL servers: Authentication via a database login (default). * Windows integrated security: Authentication via a Windows domain user. **If the installation information is unchanged select the authentication mode “Microsoft SQL Server”.** * **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 ** If the installation information remains unchanged, the standard database login is “sa” and the standard password “VxAdmin4DB!”.** **The database login must possess administration permissions. ** * **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). ** To use an encrypted connection, the Microsoft SQL instance must be configured accordingly. See also: [[https://docs.microsoft.com/de-de/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15&redirectedfrom=MSDN&viewFallbackFrom=sql-server-2014|Enable Encrypted Connections to the Database Engine.]] If a self-signed certificate will be used, this must be added on the client computer as a trusted root certificate. ** \\ ===== Overview ===== The overview shows the vistrax main database and gives an overview of the created mandator databases. Settings cannot be altered in this menu item. ===== vistrax Main Database ===== 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”. ** For the subsequent creation and/or editing of mandator databases it is essential that a main database is set up or that a connection to an existing database has been established.** ===== Mandator Databases ===== 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. ===== Database Login ===== 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. **These are not logins for the vistrax system. The login data to log on vistrax is configured within the vistrax user administration. ** You have the possibility of creating a new database login and duplicating or deleting a existing one. ==== Account Type ==== * “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. **If, when creating a new database login, the database login in question already exists in your SQL instance but has not yet been allocated to the vistrax databases, you will receive a notification message. ** **Please be aware that deleting an database login completely removes that database login from your SQL instance. The database login will thereafter no longer be usable as a login for any other database login. ** **If a database login is added manually (e.g. with Microsoft SQL Management Studio), the appropriate rights and roles within the vistrax databases must also be set: The roles "db_datareader", "db_datawriter" and the right to execute "stored procedures" are required. Ensure that the database login can access the main database and all mandator databases. ** ===== Maintenance ===== 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”. **Before migrating a database you should create a backup copy of the existing databases to avoid data loss in the event of a problem. This should be arranged with your administrator. Backup an restore of the database can be performed for example with the Microsoft SQL Management Studio. For more information, see the following links: [[https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server?redirectedfrom=MSDN&view=sql-server-ver15| Create a Full Database Backup (SQL Server), Restore a Database Backup (SQL Server Management Studio)]] ** 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. **Before you perform the function “Reset Record Locks”, you must ensure that all vistrax clients are closed.** \\ \\ [[:en:v2:vistraxadmin:systemmenue|NEXT]]