Administration

Valid for: enaio® version 10.0

System Roles for enaio® client

The 'Client: Undo the checkout for others' system role is new.

Users with this system role can undo checkout of other users' documents. The 'Write object' right for the document type is also required. Previously, only users with the 'Supervisor' system role could do this. This action can now be specifically enabled for specialist administrators.

'Client: Export objects' System Role

The 'Client: Export objects' system role has been split into the system roles: 'Client: Export document contents,' and 'Client: Export index data.' Users who had the 'Client: Export objects' system role will automatically get both system roles after the update.

One-Time Password

The password of new users can be created as a one-time password. Users can log in to the enaio® using this one-time password; however, they must set a new password. This mechanism does not take effect if the user's authentication is against Windows.

This feature is enabled system-wide via the enaio® enterprise-manager: Server > Server properties > Category: General > One-time password.

It then applies to all contexts in which new users are created, including new imported users. This property is not part of the export and import data.

Technical users can be created without a one-time password in the enaio® administrator via the context menu.

Kerberos

enaio® client and the administrative clients support Kerberos as an authentication service with the version 10.0.

If Kerberos is configured in the Windows domain and is to be used for client-side authentication, the enaio® server must be associated with a corresponding domain account. This account requires a service principal name (SPN) adhering to the schema 'enaio/host:port' (example: enaio/osecm.domain.de:4000). It may be necessary to change the client-side connection data in the asinit.cfg file to the qualified computer name instead of the previously possible IP notation.

The following configuration steps are necessary in the enaio® enterprise-manager:

Server properties > Category: General > Login: SSP login: Windows/Security support provider: Kerberos

Office 365

The version 10.0 can be used to integrate Office 365 for collaborative work with Word, Excel, and PowerPoint documents.

enaio® java-api

The enaio® java-api package is available for accessing the functionalities of the enaio® server from applications in the Java programming language with the version 10.0.

The previous JDL libraries were no longer adapted; in particular they do not support the TLS/SSL encryption introduced with enaio® version 9.10 for the RPC protocol. For this reason, existing Java applications need to be migrated from JDL to the enaio® java-api.

The enaio® java-api package can be used for enaio® versions 9.0 and higher.

More information can be found in the developer area.

enaio® exchange

The following requirements must be fulfilled in order to install the enaio® exchange:

  • enaio_server_communication

    You can find installations in the directory \Prerequisites\Server-Communication-Ansi for ANSI installations and Server-Communication-Unicode for Unicode installations.

  • Microsoft Visual C++ 2015-2019 Redistributable

    You can find installations in the directory \Prerequisites\Microsoft Visual C++ 2015-2019 Redistributable, depending on the operating system.

enaio® documentviewer

GraphicsMagick

enaio® documentviewer integrates with the version 10.0 instead of ImageMagick, now GraphicsMagick. No further changes to the configurations are required.

Hard Disk Monitoring

Monitoring of the cache and temp directories is enabled by default. If the amount of free space falls below the threshold of 30 MB, then the enaio® documentviewer only operates in read-only mode: No further CPB jobs are processed, no new OCR jobs are delivered, no new file jobs are processed, and no internal worker jobs are processed further.

The default settings can be adjusted via the configuration file config.properties of enaio® documentviewer:

Parameter:

system.checkDiskSpace=true
system.minFreeCacheSpaceInMB=30
system.minFreeTempSpaceInMB=30

The read-only mode is stopped automatically once there is more space available.

Page Count

As of version 10.0, the page count is only created for the specified file formats . These are specified using the parameter system.pageCountSupportedFor of the config.properties configuration file of enaio® documentviewer.

Default setting:

system.pageCountSupportedFor=application/vnd.ms, application/vnd.visio, application/vnd.openxmlformats, application/ms, text/rtf, application/vnd.oasis.opendocument, application/pdf, image/

The setting can be changed. The content type does not need to be specified in its entirety.

Determining the Cache Size

Determination of the cache size is preset to 'heuristic'; the size is calculated based on average values then. A change to an exact determination was possible, but was overwritten with each update so far. The change can now be made via the configuration file config.properties of enaio® documentviewer:

cacheCount.activeIndex=1

The value 0 is reverts to 'heuristic.'

Determining the Content Type

The configuration file extensionmapper.properties located in the directory \renditionplus\bin\custom\ for mapping the file extensions for content type now has the highest priority. This makes it possible to define user-specific content types based on file extensions and to provide targeted custom converters for these content types.

Examples:

tff=image/tiff
adf=custom/compound

Renditions from External Sources

enaio® documentviewer provides REST endpoints that external rendition creators can use to file their renditions in the Documentviewer cache, thereby reducing the load on the system:

Post/ Get: /osrenditioncache/app/api/dms/{id}/contents/renditions/{type}

Text Formats for OCR

The text formats that are to be sent to the OCR can be specified via the configuration file config.properties of enaio® documentviewer. Default:

rendition.ocrSelectionPredicate=image/tif,application/pdf

Minimum Required Text Length

The minimum required text length that is used to detect whether a text extract is valid and sent to the OCR can now be changed via the configuration file config.properties of enaio® documentviewer.

rendition.textExtraction.minTextLength=5

Logging

A new text format was introduced for logging. Logs in this format allow automatic evaluation of the logs by appropriate monitoring tools.

Logs in text format are configured with the same properties as EVN logs. The configuration must be done manually via the configuration files oxrpt.cfg of the respective directories.

'TEXT' is specified as 'Type,' and the file name gets the extension 'txt.'

Example:

[oxrpt\channels\Errors-txt]
Type=TEXT
ChannelID=8
Level=1
Suspended=0
LogFileName=err_%2_%4%6%7%5.txt

Logs in text format are always UTF-8 encoded without BOM.

Output format:

date time : level : threadid : eventid : computer : user : application : module : function : sourcefile : codeline : message

The data is output line by line and separated by the colon with leading and trailing space. The date format is 'DD/MM/YYYY hh:mm:ss,ms'. The messages are composed in English regardless of the language setting. Messages can be longer than one line.

enaio® enterprise-manager shows the server logs, offers the download options, and can provide access to the settings for TEXT logs, just as with EVN logs, as well as change them.

The axrptcfg.exe configuration tool shows the data. axprotocolcfg.exe has been discontinued.

The KRN.LogConfigGet job provides you access to the log configurations, and KRN.LogConfigSet enables you to dynamically change configurations during server runtime.

enaio® editor

Changes to the object definition: Aside from having to restart the server/server engines, you will also need to reboot enaio® appconnector and the DMS service manually to ensure the changes are loaded in enaio® webclient.

Default language: Previously, German was set as the default language in the enaio® editor and could not be changed; now you can freely select the default language. We recommend selecting a language that uses the Latin alphabet. The default language can only be changed in an empty object definition. Please define it right after installation. It is not possible to change the default language later on. However, you can add additional languages to the object definition or remove them at any time. Languages that are in use by users cannot be deleted.

User add-on: You can use a new extra entry to configure the user add-on axaddusr.dll to show only users from specified groups: EXTRAn=GROUPS=GROUP1,GROUP2.

Catalog add-on: The catalog add-on axaddxmltree.dll is only compatible with ANSI installations and will be discontinued in an upcoming release. It should not be integrated again. Instead, the new Treeview add-on axaddtreeview.dll is available. The first release featured the ability to create simple catalogs that combine properties of hierarchy and tree catalogs. As with the catalog add-on, the configuration takes place in the enaio® client. It is necessary to have the 'Start editor' system role.

An upcoming release will integrate further functions of the catalog add-on, such that it can replace it. The new Treeview add-on can be used in ANSI and Unicode installations.

Import and Export

Until now there had been restrictions for installations with more than one language. Configurations could only be edited and executed in the same language in which they were created. The internal names are also saved when you open configurations in the language in which they were created, navigate through the dialogs without making any changes, and then save them. Afterwards, the configurations can be edited and executed in all languages.

This also applies to enaio® capture configurations.

When importing and exporting Excel and Access data, it is necessary to update the Microsoft Access Database Engine.

Now configuration names must always be unique. Previously, they only needed to be unique for the same file formats.

Automatic Actions 'Subscription maintenance' and 'Follow-up maintenance'

The actions can be limited to read notifications.

Portfolios

The dialog is shown preset to 'Public portfolio' when creating portfolios in the enaio® client. This setting can be changed system-wide by adding an entry to the as.cfg configuration file located in the \etc directory of the data directory: SETNEWPORTFOLIOPUBLIC = 0

Station Names

Station names in the enaio® enterprise-manager are no longer limited to 50 characters; they can now contain up to 248 characters.

SMTP Password

The SMTP password in the enaio® enterprise-manager will be encrypted when saving and then masked when shown. It is no longer necessary to enter an encrypted string already.

Events

The document preview can be updated from the following events:

DMS: OnShow/OnClickItem/OnFocusGained /

WMS: BeforeOpen/OnClickItem/OnFocusGained.

Script Editor

The font size can be changed in the script editor using Ctrl + mouse wheel. The setting is saved for each user.