STP Documents is implemented in a three-layer model consisting of Standard DESK, Server, and two databases (STP License Database and LEXolution.DMS Database).
Standard DESK
The Standard DESK is a .NET Framework application, meaning it's an executable application (exe) and is installed on workstations or a terminal server.
Server Services
The STP LEXolution.DMS Server service consists of the .NET server service STP LEXolution.DMS Server, which is typically installed on the database server.
Alternatively, the service can be installed on its own application server.
Databases
The Microsoft SQL Server (in the Standard or Enterprise version) is used as the database.
STP Management Console
The licenses for STP products are managed in a central STP database.
The STP Management Console is used for importing licenses, but starting with version 4.8, it is no longer used for updating the server and the STP Documents database.
STP Database
The STPDatabase stores the licensed products, their modules, and the number of licenses per module in an encrypted format.
STP Documents Database
All metadata related to documents is stored in the STP Documents Database within the database content store.
Content Store
The Content Store is where documents are stored in the Standard DESK.
STP.Updater
The STP.Updater client ensures that all workstations automatically receive the latest program version.
For more information, please refer to the installation guide.
Note
Please note that in a terminal server environment, the STP.Updater client cannot be used. Updates on the terminal server are always performed through manual installation or manual patching of files.
When using a single computer for STP Documents, all instances (Standard DESK, Server, and MS SQL Server databases) can be installed on this computer. Please refer to the system requirements for more information.
Terminal Server
On a terminal server, multiple STP Documents users can work with STP Documents simultaneously (e.g., via remote desktop session or RemoteApps/WebApps starting from Windows Server 2008).
Note
Please note that in a terminal server environment, the STP.Updater cannot be used. Updates on the terminal server are always performed through manual installation or manual patching of files.
Environment Variables
DMS_Alternative_EditPath: This variable is primarily intended for use on systems with a Windows sync of the %localappdata% folder. These are mainly terminal servers, especially those accessed via a load balancer. There can be issues with document editing in these cases. To prevent this, you can set this variable to a different path (network share) on the affected systems. Each user must have their own directory.
For example, DMS_Alternative_EditPath=\\my-file-server\DMS\{username}.
Here, the path is set to a server "my-file-server" in the "DMS" share. Another environment variable "username" is used to ensure each user has their own subdirectory. It's important to ensure that user-specific directories are isolated from each other (access permissions only for the respective user). Typically, users already have such a network drive with their own permissions.
DMS_Blocked_For_User: This variable is also intended for use on terminal servers. Often, not all users on the terminal server should use DMS (especially Office Add-Ins, OutlookDesk, and LEXolution Client Application Service). However, installation sets it up for all users. Since this can lead to significant configuration efforts with each new installation and update, you can now simply set this environment variable to "true" for the affected users. This prevents any Add-In from initializing or, for example, the LCAS from starting.
Example: DMS_Blocked_For_User=true
Note
The environment variable "DMS_Alternative_EditPath" cannot be used on laptops, as they are not always connected to the LAN, which would cause the edit path to be invalid.
Note
The environment variable "DMS_Blocked_For_User" can also be set by the admin for the affected users via group policy.
Environment variables on terminal server environments can be set through the Group Policy Management.
Related to