The Vertec.ini – File

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

Default value is 10000.

Please refer to the article Firebird Pages and Buffersize .

• 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
  
  
  
  

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

Data Source=MYSERVER\Instance Name

BI API

From Vertec 6.4.0.14. Turns off the BI API (Application Programming Interface) for querying 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

This allows you to define the time window in which the BI data is to 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 the dice: Base on the start time, the quantity of minutes to the end time is determined. A random number from 0 to the quantity of minutes is then rolled, and this value is added to the start time. This results in the CRON expression for determining the next execution, see also Schedule Tasks.

Certificate Name

Excluded Protocols

HSTS Max Age

Login Max Failures

Starting with Vertec 6.2. Brute-force prevention mechanism to prevent numerous unsuccessful login attempts as used in brute-force authentication attacks.

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

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

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

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

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

These settings are independent and work even if the Authentication via LDAP Server is carried out.

Login Ban Minutes

Management Port

Management Port Exposed

From version 6.1.0.10.

By default, access to the Management Console is only possible via Localhost address to prevent that the Management Console, which does not require a login, can be easily accessed 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 shared accordingly and it must be ensured that the port cannot be accessed from the outside.

Monitoring

Monitoring Ban Minutes

Notif Server

The Notif Server can be explicitly disabled with 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

Enables/disables the Outlook app to operate 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 in again. The value entered must be greater than 0 and less than 2147483647.

[CloudServer]
Outlook app Session Timeout=75

Phone app Server

From version 6.2. Enable/disable the Phone app for operation with this Cloud Server instance.

[CloudServer]
Phone app Server=True

For more information, see Enable Cloud Server Services individually.

Phone app Session Timeout

Starting with 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 switched off Token Lifetime : Enable enough session time, otherwise the user will have to re-login 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 makes the start / login process shorter for the client.

See also Cloud Server Management Console.

Restricted filesystem access

Starting with 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 saved on the client side (analogous to Word-generated reports, which are always executed on the client anyway)
• No storage of reports in the web app (not even on the server), only download
• Error message when executing a report with a configured save path via Web app. In that case, no document can be saved and no activity can be created.

Restricted scripting

Starting with version 6.1.0.9. Restricts scripting when accessing via cloud clients. For detailed information, see Restrict scripting for cloud sessions.

Restricted Session Process

• The Vertec Session Process runs as a Low Integrity Process.
• The Vertec Session process may not start any further 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:\Programs\Vertec\DB\VertecDemo.fdb
• File path (invalid): ServerName=C:\Programs\Vertec\DB\VertecDemo.fdb

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

(In case of LogFileFolder is set, but no write access exists, no log is written.)

This setting is automatically enabled in the Vertec Cloud Suite.

From version 6.6.0.7 onward, 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 demo.vertec-cloud.com) is used by the Desktop App to generate the Vertec URL (vertec://...) and for the Python function vtcapp.getvertecserveraddress() used.

The logic is implemented as follows:

• If Server Address already contains a port, do not add one.
• 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 default port).

Server port

Show Error Call Stack

Show License Dialog

Opening the license dialog via Settings > Change license... can be deactivated by pressing Show License Dialog=False is set.

[CloudServer]
Show License Dialog=False

SSH Remote Host

SSH remote port

SSH User

SSH Password

Token Lifetime

Trusted Certificate

Task Scheduler

Controls whether Task Scheduling is active or not. If not, no scheduled tasks are executed.

If this parameter is not specified, the default is True.
If you do not want to execute scheduled tasks with a Cloud Server Section, this can be disabled with Task Scheduler=False .
When operating: Multiple Cloud Server only one of them is applied to run tasks. For all others, this parameter must be set to False.

Task Scheduler Polling Minutes

Task Scheduler Concurrent Tasks

Task Scheduler Max Minutes

Starting with Vertec 6.4.0.8. If a Vertec.Taskrunner process does not complete correctly, it persists and unnecessarily blocks memory on the server.

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

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 this is turned off, these clients cannot be used.

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 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 available for the Vertec 6.4.0.14 BI API used.

XML Server

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

[CloudServer]
XML Server=True

For more information, see Enabling CloudServer Services Individually.

Servers

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 installing the Cloud app, the Cloud app Installer automatically sets the settings to True set.

If the setting is missing from the Vertec.ini file or if it is set to 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 (add-ins and protocol handlers are stored locally).

The local client installation has the following advantages:

• App loading times are shorter when installed locally
• The protocol handler needed to properly resolve the URL must be installed locally (see ?3.4)
• Fewer problems with security features in Windows that block executables from outside your own computer or treat 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.

LogFile

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

Unlike the default 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, it 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 log files are not to be stored in Programdata or Appdata, an alternative folder path can be specified here. All log files are then written to this folder.

• It must be ensured that the process has write permissions to the directory. If this is not the case, no log is created (and therefore no log of related errors)
• This parameter applies to all new apps (Desktop App / Cloud app / Session / Cloudserver)

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 for logging various operations in Vertec. To find out which Debugcategories are relevant to you, please contact your Vertec adviser.

If a value is specified in the registry under HKLM\SOFTWARE\Vertec\DebugCategories, it 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.

LogglyToken

Starting with 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