enaio® repository-manager

enaio® repository-manager • 10.10 »

You will find information about the latest service releases of enaio® repository-manager here.

Installation

Services are installed via the os_service-manager_setup.exe file in the \Backend\Service-Manager\ directory.

Service updates take place via enaio_services_versionfix.exe in the \Backend\Service-Manager-Update\ directory. Copy the directory to the computers where the microservice installations are located prior to carrying out the updates.

The current repositorymanager-app.jar can also be copied to the \service-manager\update\ directory. enaio® service-manager then automatically updates enaio® repository-manager.

enaio® repository-manager 4.3.5

A secure connection between the SAP system and enaio® repository-manager cannot be established if the certificate is available in the Windows Keystore. The certificate must be available in a PKCS12 file.

To update to version 4.3.5 with the new version of the KGS Content Server, the following steps must be carried out:

  • Save the directory \working-dir\embeddedTomcat\webapps\cs\conf\contentserver\.

  • Exit enaio® repository-manager.

  • Delete the \working-dir\ directory.

  • Update enaio® repository-manager to version 4.3.5.

  • Start enaio® repository-manager.

    The \working-dir\ directory is recreated.

  • Exit enaio® repository-manager.

  • Replace the directory \working-dir\embeddedTomcat\webapps\cs\conf\contentserver\ with the saved directory.

  • Start enaio® repository-manager.

  • Check the configuration via the KGS administration page.

Without these steps, the configuration must be recreated via the KGS administration page.

enaio® repository-manager 4.3.1

servicewatcher-sw.yml

If the upgrade to version 4.2.2 has not already been carried out, then the servicewatcher-sw.yml configuration file of enaio® service-manager must be extended.

The JDK parameter must be supplemented: jdk: jdk17

- name: repositorymanager
  type: microservice
  profiles: mq,prod,cloud,blue
  instances: 1
  memory: 1024M
  port: 8010
  path: ${appBase}/repositorymanager/repositorymanager-app.jar
  jdk: jdk17
  arch: x64

KGS Content Server

If the upgrade to version 4.2.2 has not already been carried out, then for the new version of the KGS Content Server, the \working-dir\ working directory must be emptied and the configuration recreated via the KGS administration page.

Barcode Errors

For easier troubleshooting, the object definition of the ArchiveLink cabinet can be extended by a dialog element of the 'checkbox' type with the internal name 'Barcodeprocessingerror'. The checkbox is enabled when errors occur during barcode processing.

The object definition file from the \working-dir\obj-def\ installation directory has been updated accordingly.

Connection Parameters

The connection to the DMS service and to enaio® appconnector can be made via enaio® gateway and – if enaio® gateway is configured accordingly – encrypted.

The connection parameters must be specified.

KGS GUI

The KGS GUI can now also be accessed via enaio® gateway. The configuration of enaio® gateway must also be modified:

enaio® repository-manager 4.3.2

Connection with enaio® appconnector

The connection to enaio® appconnector is established via the address http://127.0.0.1:8060/ by default. If enaio® appconnector is installed on a different host or port, or is running via HTTPS, then the address must be specified via the new enaio.app-connector.uri parameter in repositorymanager-prod.yml.

The user and password of the technical user in the application-blue.yml file of enaio® service-manager are used for the connection by default. If you want to use a different technical user, then you can specify this in the repositorymanager-prod.yml file via the enaio.dms.username parameter.

The previous parameters enaio.osrest.uri, enaio.osrest.username and enaio.osrest.password are no longer evaluated and can be deleted.

IP Filter for Management Endpoints

Access to the following endpoints can be restricted via IP filters: info, health, env, loggers, and metrics.

For this purpose, addresses that allow access are specified via the new management.trusted.ipPattern parameter in the repositorymanager-prod.yml file.

In general, IP filters can also be configured for both the management endpoints and the services.