'osrest.properties' Configuration File
In order to configure enaio® appconnector, edit the osrest.properties configuration file in the program directory \services\OS_Appconnector\configuration.
The 'Server: Switch job context' system role must be assigned to the technical user whose user account is used to execute enaio® appconnector.
The following settings can be configured in the configuration file:
default.pagesize | Maximum number of hits provided by enaio® appconnector. The default value is 500 hits. |
favoritesPortfolioName | A portfolio containing the favorites can be specified for versions earlier than 7.10. Specify the topic. |
notifications.skipworkflow | Disable workflow. Workflow functions are deactivated if the parameter is set to 'true.' |
metadata.defaultmappingname | Name of the configuration file in which it is defined which index data fields of the individual enaio® object types are shown, for example, in enaio® mobile. The file name has to be specified without the file extension. The file can be found in the ..\configuration\schema directory. |
osecm.default.nameschema | Specify whether internal names in the object definition must be used for index data assignment. The default value is internal_name. You can also use names and index data fields of DMS objects (name) for assignment, but the names must then follow the same rules like internal names (see 'Configuration Scripts'). |
hide.stacktrace | Switch off stacktrace logging. |
maxFilesInZip | Maximum number of files that can be exported to a ZIP archive. Default: 200 |
maxFilesInPdf | Maximum number of files that can be exported to a PDF file. Default: 200 |
base.url | Base URL of enaio® appconnector. The URL will be read automatically from the server registry and entered here. If you enter a URL yourself, the registry value will be ignored. |
fileservice.contentviewerurl | Base URL of enaio® ContentViewer. It will be read automatically from the server registry and entered here. If you enter a URL yourself, the registry value will be ignored. |
fileservice.documentviewerurl | Base URL of enaio® documentviewer. enaio® documentviewer creates the previews of enaio® objects that you can, for example, view via enaio® app. The URL will be read automatically from the server registry and entered here. If you enter a URL yourself, the registry value will be ignored. For example: https://demo.optimal-systems.org/osdocumentviewer |
services.renditioncache | URL of rendition service. The URL specified here will overwrite the corresponding value in enaio® enterprise-manager. |
services.detailsviewer | URL of enaio® detailsviewer. The URL specified here will overwrite the corresponding value in enaio® enterprise-manager. |
extractionservice.url | Base URL of enaio® extraction. If you would like to use these components (extraction of EXIF files from audio, video, and image files, XMP data from Office and PDF documents, and default properties from e-mails in MSG and EML formats), contact the OPTIMAL SYSTEMS Professional Services team. |
fileservice.osweburl | Base URL of enaio® webclient. This URL is required to edit the content of DMS objects in enaio® webclient on your mobile device, for example. These can otherwise only be viewed in enaio® app. For example: https://demo.optimal-systems.org/osweb |
admin.email | E-mail address to which app users can send error messages. In addition to the error message, the e-mail also contains the stacktrace to the error. |
welcomepage | URL of a welcome screen suitable for mobile applications. The welcome screen will be shown when starting enaio® app and when changing the server profile, provided that the user has enabled the app configuration parameter 'Always show Welcome page.' Please note that the colon in the URL must be preceded by an escape character. For example: http\://www.ecm.mobi |
Access to enaio® appconnector must always be via enaio® gateway. The osrest.properties configuration file can be used to enter an IP filter to secure access to enaio® appconnector. The default setting permits access by all IP addresses.
For example: trusted.ipPattern=127\.0\.0\.1.
authentication.useprofileuser | A profile user whose accesses occur without authentication can be used ('true'). The parameters profile.user.password and profile.user.name are then used to specify the name and password of the profile user. |
profile.user.name | Name of the profile user. This information is only required if the authentication.useprofileuser parameter was set to 'true.' |
profile.user.password | Password of the profile user. This information is only required if the authentication.useprofileuser parameter was set to 'true.' Note that the password entered here is not encrypted. You can also enter the encrypted password including # characters from the user table of the enaio® database. |
authentication.restrictaccesstogroups | enaio® user group that will receive access to the service. Use a comma to separate multiple groups. Users must always be a member of all groups specified here in order to have access to the service. |
services.pushnotification.enabled | This must be set to 'true' for the system to send push notifications to mobile devices. |
services.pushnotification.production | Internal parameter that cannot be changed. Otherwise, the push notification service will no longer work. |
services.pushnotification.version | Internal parameter that cannot be changed. Otherwise, the push notification service will no longer work. |
services.pushnotification.proxy.enabled | If a proxy is used to connect to the Internet, this must be set to 'true.' |
services.pushnotification.proxy.address | If a proxy is used to connect to the Internet, its address must be specified here. |
services.pushnotification.proxy.port | Port of the proxy server |
services.pushnotification.proxy.password | Password of the proxy user |
services.pushnotification.proxy.username | Name of the proxy user |
res.revision | Internal parameter that cannot be changed. |
More information about the configuration of the push notification service can be found here: Push Notification Service.