The Vertec.ini – File

ServerName

User Name

Password

Encrypted password for identification at the database server, together with the user name.

When you set up Vertec, you will be asked for the database password and this will be automatically entered in Vertec.ini in encrypted form. If you need to enter it manually, e.g. when changing the database password, use the Verschlüsselungs-Option im Kundenportal.

Buffers

Starting with Vertec 6.5, the Firebird Buffer-Size can be overwritten:

Default value is 10000.

Please refer to the article Firebird Pages und Buffersize.

Provider

• Provider=SQLOLEDB: Default driver for the SQL connection. The driver is not installed by Vertec Setup, it is part of MDAC (Microsoft Data Access Components) or the SQL Server Client Setup.

  [Database]
  Provider=SQLOLEDB
  Data Source=MYSERVER
  ...

• Provider=SQLNCLI11: Start with Vertec 6.2.0.2, the SQL Server Native Client driver is also supported. This driver supports TLS 1.2 encryption. The prerequisite is that the driver is installed. This driver is neither installed by SQL Server Client Setup nor by Vertec Setup. It is part of SQL Server Management Studio.

  The DataTypeCompatibility=80 parameter must be specified with this driver. This is important for the ADO layer to interpret the data types correctly.

  [Database]
  Provider=SQLNCLI11
  DataTypeCompatibility=80
  Data Source=MYSERVER
  ...

• Provider=MSOLEDBSQL: Start with version 6.5.0.9 the Microsoft SQL OLE DB driver for SQL Server is also supported.

  [Database]
  Provider=MSOLEDBSQL
  DataTypeCompatibility=80
  
  

Data source

If there is more than one SQL Server instance on a server, the instance name must be appended:

Data Source=MYSERVER\Instanzname

Initial Catalog

User ID

Password

Persist Security Info

Auto Translate

Host

Port

PollInterval

The port on which the indexing server can be reached on the host.

The parameter must be specified to activate the HTTP server for indexing. If it is not specified, no search is available in the Vertec Desktop App.

The path on the server where the index should be saved. Is only used by the Vertec Cloud Server. 

If nothing is indicated, the following path is used by default: C:\ProgramData\<VertecInstanceName>-index

AI Recognition Ping Timeout

As of Vertec 6.7.0.14, for automatic receipt recognition. Timeout for the “ping” request in seconds, which is executed before each detection attempt to check if the server is available.

An adjustment should only be necessary in case of poor internet connection of the server.

AI Recognition Request Timeout

As of Vertec 6.7.0.14, for automatic receipt recognition. Timeout for analysis of the submitted posting.

An adjustment should only be necessary in case of poor internet connection of the server.

BI API

As of Vertec 6.4.0.14. Enable the BI API (Application Programming Interface) to query Bi data from external applications.

[CloudServer]
BI API=True

• The BI API can only be used if the Business Intelligence Module is licensed, otherwise an error is returned.
• The BI API can only be used after authentication. Otherwise, an error is returned.

BI Task Scheduler Range Start

BI Task Scheduler Range End

Vertec versions before 6.8. This allows you to define the time window in which the BI data should be calculated. Within this time window, the Cloud Server rolls a time in which the process is started. The start time is set by a new session at the start of the Cloud Server.

BI Task Scheduler Range Start=23:00 
BI Task Scheduler Range End=05:00 

How to roll: Start from the start time, the quantity of minutes until the end time is determined. Then, a random number from 0 to the quantity of minutes is rolled and this value is added to the start time. This yields the CRON expression used to determine the next run, see Scheduled Tasks.

As of Vertec 6.8, the parameters are called Special Task Scheduler Range Start and Special Task Scheduler Range End, since they are also valid for the plated task for full-text indexing. To maintain backward compatibility, the new names are checked first and then the old ones are checked.

Certificate Name

Excluded Protocols

HSTS Max Age

Indexing server

As of Vertec 6.8. Control whether the Vertec Cloud Server provides indexing operations and thus full- Full Text Search.

• Only needs to be set if you are working with Multiple Cloud Server instances.

• May only be used on a Vertec Cloud Server True be.

Login Max Failures

As of Vertec 6.2. Brute-force prevention mechanism to prevent many failed login attempts, as used in brute-force authentication attacks.

The authentication server remembers and counts failed attempts per login name. Once the quantity of failed attempts for a given login name reaches a threshold, authentication requests for that login name will not be processed for a specified period of time.

If a successful login occurs before the threshold is reached, the counter for this login name is reset.

The quantity of possible attempts and the time period can be configured. If nothing is specified, the default is used.

[CloudServer]
Login Max Failures=10 (Standard)
Login Ban Minutes=10 (Standard)

If one of the settings is set to 0, the Brute Force Prevention mechanism is disabled.

These settings are independent and work even if Authentication via ldap server is done via LDAP servers.

Login Ban Minutes

Management Port

Management Port Exposed

From version 6.1.0.10.

Access to the Management Console is by default only possible via Localhost address to prevent that the Management Console, which does not require login, is easily accessible from outside the computer.

The setting

[CloudServer] 
Management Port Exposed=True  

provides the Management Console on all available interfaces.

We do not recommend setting this option. The ports must be approved accordingly and it must be ensured that the port cannot be accessed from outside.

Monitoring

Monitoring Ban Minutes

Notif server

The Notif Server can be explicitly disabled using Notif Server=False in the [CloudServer] section.

[CloudServer]
Server Address=SERVER1
Server Port=8081
Management Port=8082
Notif Server=False

[Notif]
Host=SERVER1
Port=8091
PollInterval=10000

The Notif Server=xxx row is optional.

If it is not present, the behavior is equivalent to Notif Server=True.

Outlook App Server

Activates/disables the Outlook App to work with this Cloud Server instance.

[CloudServer]
Outlook App Server=True

 For more information, see Enable Cloud Server Services individually.

Outlook App Session Timeout

Time, in minutes, after which an Outlook App session expires and the user must log on again. The value entered must be greater than 0 and less than or equal to 2147483647.

[CloudServer]
Outlook App Session Timeout=75

Phone App Server

From version 6.2. Activates/disables the Phone App for operation with this Cloud Server instance.

[CloudServer]
Phone App Server=True

For more information, see Enable Activate cloud server services individually.

Phone App Session Timeout

From version 6.2. Time in minutes after which a Phone App session expires and the user must log in again. The value entered must be greater than 0 and less than 35791.

[CloudServer]
Phone App Session Timeout=75

Attention when Token Lifetime is switched off: Turn on enough session time, otherwise the user will have to log in again all the time

Portal Page

Process Limit

The default value is 0. This means that no limit is set.

Process Pool Size

If a new user logs in with a cloud client, he applies this session and a new idle session is automatically started. This reduces the start / login process for the client.

See also Cloud Server Management Console.

Restricted Filesystem Access

From version 6.1.0.9. Restrict access to the server file system when saving documents.

If this option is enabled (Cloud Suite Standard), this has the following effects:

• Vertec generated legacy word reports and Office Reports are stored on the client side (similar to Word-generated reports, which are always executed on the client anyway)
• No saving of reports in the Web App (not even on the server), only download
• Error message when running a report with a configured storage path via Web App. The document cannot be saved and an activity cannot be created.

Restrict Local IP

Restricted Scripting

Starting with version 6.1.0.9. Restrict scripting when accessed via cloud clients. For details, see Restrict scripting for cloud sessions.

For new installations, this option is set by Setup to True.

Restricted session process

• The Vertec Session process runs as a Low Integrity process.
• The Vertec Session process must not start any other subprocesses.

Restrict Session Process=True

If this setting is set, make sure that when using Firebird, the ServerName parameter in the database section contains a network path, not a file path. For example:

• Network path (valid): ServerName=MYSERVER:C:\Programme\Vertec\DB\VertecDemo.fdb
• File path (invalid): ServerName=C:\Programme\Vertec\DB\VertecDemo.fdb

The corresponding Logfile (Vertec.Session.log) can then be found (defined by Windows) under C:\WINDOWS\system32\config\systemprofile\AppData\LocalLow.

(If a Logfilefolder is set but no write access exists, no log is written.)

In the Vertec Cloud Suite, this setting is automatically activated.

As of version 6.6.0.7 it affects the saving of reports like Restrict Filesystem Access (see above).

Secure server port

Server Address

The address of the server (e.g. 192.168.1.1 or vertec.company.com) is used by the Desktop App to generate the Vertec url (vertec://...) and for the Python feature vtcapp.getvertecserveraddress().

The logic is implemented as follows:

• If Server Address already contains a port, do not add any more.
• If Server Address does not contain a port and the SSH Remote Host parameter is set, do not add a port either.
• In all other cases, add port if necessary (if not standard port).

Server port

Special Task Scheduler Range Start

Special Task Scheduler Range End

This allows you to define the time window in which the planned tasks for the BI calculations and for the Full Text Indexing may be carried out.    

Within this time window, the Vertec Cloud Server rolls a time in which the processes are started. The start time is set by a new session at the start of the Cloud Server.

Special Task Scheduler Range Start=23:00 
Special Task Scheduler Range End=05:00

How to roll: Start from the start time, the quantity of minutes until the end time is determined. Then, a random number from 0 to the quantity of minutes is rolled and this value is added to the start time. This yields the CRON expression used to determine the next run, see Scheduled Tasks.

Show Error Call Stack

Show License Dialog

The opening of the license dialog via Settings > Change license... can be disabled by using Show License Dialog=False is set.

[CloudServer]
Show License Dialog=False

SSH Remote Host

The SSH parameters are used when you make Internet your Vertec available on the Internet via a service such as the Webaccess service from spektra netcom ag.    

The information to be entered will be provided by the operator.

Once the SSH remote host (the host for the SSH tunnel) is set, SSH proxy is activated. Otherwise, it is disabled.

SSH remote port

SSH User

SSH Password

Token Lifetime

Trusted Certificate

Task Scheduler

Controls whether the task scheduling is active or not. If not, no scheduled tasks will be executed.

If the parameter is not specified, the default is True. So
if you do not want to perform scheduled tasks with a Cloud Server Section, you can disable it with Task Scheduler=False.
When running Multiple Cloud Server, only one of them may run tasks. For all others, this parameter must be set to False.

Task Scheduler Polling Minutes

Task Scheduler Concurrent Tasks

Task Scheduler Max Minutes

As of Vertec 6.4.0.8. If a Vertec.TaskRunner process does not complete correctly, it persists and blocks unnecessary memory on the server.

Therefore, under Task Scheduler Max Minutes, you can specify the maximum run time in minutes for a scheduled task. Default value is 1200 (20h). If a process runs longer than the maximum time specified here, it will be automatically completed by Cloud Server.

Completing Vertec.CloudServer also completes all started TaskRunner processes.

UISync Server

From version 6.2. The UISync server controls the interface in the full-featured clients (Cloud App, Web App). If it is switched off, it is not possible to work with these clients.

This is useful, for example, if you want to put only the Phone App or the XML Server on the Web via a Cloud Server instance.

For more information, see Enable Activate cloud server services individually.

XML Session Timeout

Time, in minutes, after which an XML session expires and the user must log in again.

[CloudServer]
XML Server=True
XML Session Timeout=10

Also used for the BI API as of Vertec 6.4.0.14.

XML Server

Activates/disables the XML Server to operate with this Cloud Server instance.

[CloudServer]
XML Server=True

For more information, see Enable CloudServer Services individually.

Server

Auto Update

Here you can set whether the local version of the cloud app is automatically updated to the latest version on the server when it is started.

When you install the cloud app, the settings of the cloud app installer are automatically set to True set.

If the setting in the Vertec.ini file is missing or False is set, no auto update takes place.

Trusted Certificate

version

WordAddin

ExplorerAddin

OutlookAddin

ExplorerAddin

ClientSetup

• Local: All required files are copied to the client computer and installed there.
• Server: The essential files remain on the server and only the shortcuts are created on the client (addins and protocol handlers are stored locally).

The local client installation has the following advantages:

• The loading times for the apps are shorter when they are installed locally
• The protocol handler needed to resolve the URL properly must be installed locally (see ?3.4)
• Less problems with security features in Windows that block executables from outside your computer or classify them as suspicious
• The client can also be removed from the LAN and Vertec can be used remotely via VPN

The default setting is Local.

LogFileName

Name of the log file. If a file is specified here, logging is done to this file instead of the standard log file Vertec.log.

Unlike the standard logfile, a logfile specified here is not deleted every time Vertec is started, but the new entries are appended.

If a value is specified in the registry under HKLM\SOFTWARE\Vertec\LogFileName, this value takes precedence. See the section on versions prior to Vertec 5.4 in the Logging article.

LogFileFolder

As of Vertec 6.1.0.7 there is the parameter LogFileFolder. If the logfiles are not to be stored in ProgramData or Appdata, an alternative folder path can be specified here. All logfiles are then written to this folder.

• It must be ensured that the process has write permissions in the directory. If this is not the case, no log will be created (and therefore no log of errors in this regard).
• This parameter applies to all new apps (desktop app / cloud app / session / cloud server)

DebugCategories

Here you can define the debug categories for which you want to generate level 10 log entries. See the article about logging.

There are a variety of built-in DebugCategories to log various operations in Vertec. To find out which DebugCategories are relevant to you, please contact your Vertec advisor.

If a value is specified in the registry under HKLM\SOFTWARE\Vertec\DebugCategories, this value takes precedence. See the section on versions prior to Vertec 5.4 in the Logging article.

SqlLogTable

With SqlLogTable=True, the log entries are written to the LOGDATA table in the database. This allows all log entries of all Vertec users to be viewed and saved centrally.

For detailed information, see article Logging.

OpenObserveUrl

Vertec 6.7.0.12 or later. Must be specified for Vertec to send Log Messages to the OpenObserve Log Server.

For detailled information see article Logging.

OpenObserveUsername

Username to OpenObserveUrl.

OpenObservePassword

Password to OpenObserveUrl.

LogglyToken

As of Vertec 6.4.0.9. If a Loggly token is specified, the log output from the server-based Vertec processes (Vertec.CloudServer, Vertec.Session) is sent to the cloud-based logger service Loggly. The desired URL can be specified with the LogglyUrl parameter.

For detailed information, see article Logging.

LogglyUrl