enaio® services

enaio® 11.10

enaio® services are installed during a setup. The required runtime environment is installed automatically.

The os_service-manager_setup.exe setup file can be found in the \Backend\Service-Manager directory in the installation data. The setup will install enaio® service-manager as service with the selected services.

If services are installed via the os_service-manager_setup.exe setup file later, then updates made via enaio_services_versionfix.exe are undone in the process. You will need to run the updates again afterwards.
If self-signed certificates were integrated, then they must be integrated again or the backup needs to be restored after running os_service-manager_setup.exe. The setup saves the JDK TrustStore in the backup directory of the installation of enaio® service-manager before the update.

Installation Requirements

The following requirements must be fulfilled in order to install enaio® service-manager and enaio® services:

enaio® server is installed, started, and accessible.
The names of computers on which enaio® service-manager and the services are installed may only contain letters from 'a' to 'z,' digits from '0' to '9,' and the hyphen within the name, in accordance with specifications for Internet communication and protocols (see RFC 952 and RFC 1123).

enaio® services

enaio® service-manager manages the services and must be installed once with the basic services 'admin' and 'discovery'. The basic services are not required for further installations of services with enaio® service-manager on other computers. If services are distributed, the connection between services must be configured.

Service	Function
Basic services: admin discovery	Basic services for administration, communication, and monitoring (argus).
ai-connector	Service that provides enaio® customers access to Kairos AI cloud services.
applet	Service for HTML/JS/CSS front-end components, e.g., content preview.
archive	Service for archiving
data-transfer	Service for enaio®data-transfer-ng (beta).
dms	DMS service for document management.
extraction	Service for metadata extraction. The extraction can lead to errors if the path for the temporary directory of the service is too long. You can change this directory from the \service-manager\config directory via the servicewatcher-sw.yml file: To do so, add the following entry to the extractionservice section: options: - "-Djava.io.tmpdir=<path>"
index search	Services for full-text integration. The services are configured via enaio® services-admin.
consistency check	Service for periodically checking the full-text index in projects.
migration	Service for migrating the full-text index in projects.
gateway-ng	Service for OAuth2/OIDC authentication for enaio® webclient.
license	Service for license management.
mailstorage	Service for e-mail filing.
mas-mailbox mas-smtp mas-storage	Services for e-mail transfer from Microsoft Exchange with enaio® mail-archive-service.
msteams-client msteams-actions	Service for the connection to Microsoft Teams.
office365-client office365-dashlet	Service for the connection to Office 365.
ocr	Service for OCR.
osweb	Service for enaio® webclient.
repositorymanager	This service is no longer used (EOL). Switch to the new standalone services 'repositorymanager-ilm' and 'repositorymanager-archivelink.' Review the migration guide before completing the installation.
repositorymanager-ilm	New service for the SAP® ILM connection. Review the migration guide before completing the installation if ILM was used with the previous 'repositorymanager' service.
repositorymanager-archivelink	New service for the SAP® ILM ArchiveLink connection. Review the migration guide before completing the installation if ArchiveLink was used with the previous 'repositorymanager' service.
repositorymanager-cmis	Service for the SAP® CMIS connection in the project.
restdashlet	Service for integrating enaio® coLab.
users	USERS service for user management.

This is configured via enaio® services-admin and can be accessed in the browser at the following URL:

http://<service-manager-admin-IP>:<port>

Default port: 7273

Microservices are installed with default values for the memory and port.