Content Manager Enterprise Studio
The visitor seat calculation has been implemented specifically for licenses of the type MSP (Managed Service Provider). Upon installation of an MSP type license, a new button, Generate MSP Usage Report, will appear on the Content Manager Enterprise Studio license page.
This feature allows you to generate a comprehensive report of seats used, taking into consideration the visitors.
For more information, see License section in Content Manager Enterprise Studio help.
-
When the Content Manager client communicates with a WGS over TCP, it uses Kerberos/NTLM to encrypt the traffic.
-
When the Content Manager client communicates with a WGS over HTTPS, it also uses Kerberos/NTLM to encrypt the traffic, but additionally, adds a HTTPS envelope over the already encrypted traffic.
For more information, see HTTPS vs TCP for WGS communication.
Encryption can be configured by the customer by using Native Network encryption. See, Data Integrity Algorithms Support. You need to add few lines in sqlnet.ora file.
The Content Manager Document store allows encryption to protect data at rest. The Administrator should configure the encryption, (For details, see section Document Stores General settings in Content Manager Help > Administration > Document Stores ).
For encryption, AES256 algorithm is used by making use of Microsoft Windows Cryptographic Module.
The parts that combine the encryption key is the Encryption Key used by the AES256 algorithm and is generated based on a proprietary algorithm that is derived from a random salt, and other entropy.
The TLS transport security is provided by Content Manager and needs to be configured by the Administrator. Content Manager supports TLS 1.2.
Because of change in the design, this error is expected. If you do not want this error to appear, add the DisableRecordUpdateVersionCheckAtDB parameter to the TRIMMetrics.ini on the Workgroup Server and set its value to 1. The default value is 0.
[Server] ; DisableRecordUpdateVersionCheckAtDB ; Disable the record version check at database. ; Type: Boolean ; Default value: 0 DisableRecordUpdateVersionCheckAtDB = 1
There is no mechanism to spawn or restart the TrimEvent.exe process with custom scripts. The TrimWorkgroup.exe and the TrimEvent.exe are intertwined and have a parent child relationship. The TrimEvent.exe state sync will not match/or work properly if we replace TRIMWorkgroup.exe with custom made solutions.