appsettings.json file - appsettings.json file - You can configure the HyRSC by updating the appsettings.json file. The following is a list of the sections available in the appsettings.json file. - Perceptive Content - Perceptive Integration Server on Tomcat Installation and Setup Guide - Perceptive-Content/Perceptive-Integration-Server-on-Tomcat-Installation-and-Setup-Guide/Foundation-26.1/Perceptive-Integration-Server-on-Tomcat-Installation-and-Setup-Guide/Appendix-F-HyRCS-installation-and-configuration/appsettings.json-file - Foundation 26.1 - Foundation 26.1

Perceptive Integration Server on Tomcat Installation and Setup Guide

Platform
Perceptive Content
Product
Perceptive Integration Server on Tomcat Installation and Setup Guide
Release
Foundation 26.1
License
ft:lastPublication
2026-05-11T13:40:50.414000
ft:locale
en-US

You can configure the HyRSC by updating the appsettings.json file. The following is a list of the sections available in the appsettings.json file.

Kestrel

The Kestrel section specifies the values for the Kestrel webserver. The Kestrel webserver is used when running as a standalone application or as a windows service. You can configure the HTTP endpoint here. The default is https://0.0.0.0/5001. The 0.0.0.0 syntax specifies binding to all address on the host. For more information, see the Configure endpoints for the ASP.NET Core Kestrel web server topic on the Microsoft website. Depending on the types of certificates being used, refer to this link for the values needed for your configuration.

Note: In some applications, the size of the page file that can be rendered is limited by the MaxRequestBodySize setting. The default is 28.6 MB. If you work with files larger than the default, increase the value of this setting to allow those larger page files to render.
  "Kestrel": {
    "Endpoints": {
      "Https": {
        "Url": "https://*:5001"
      }
	},
    "Limits": {
        "MaxRequestBodySize": <size in bytes>
      }
	},
    "Certificates": {
      "Default": {
        "Path": "",
        "Password": ""
      }
    }
  },

Hyland.Logging

The Hyland.Logging section specifies the logging configuration for Hyland Rendering and Conversion Service.

  "Hyland.Logging": {
    "Routes": {
      "Console-Full": {
        "DisableIPAddressMasking": "true",
        "minimum-level": "Trace",
        "maximum-level": "Critical",
        "Console": "value"
      },
      "Http": {
        "Http": null,
        "DisableIPAddressMasking": "true",
        "minimum-level": "Trace",
        "maximum-level": "Critical"
      },
      "Example-Logs": {
        "File": "./logs/RenderingConversionService.log",
        "DisableIPAddressMasking": "true",
        "minimum-level": "Trace",
        "maximum-level": "Critical",
        "FileRollInterval": "Day",
        "FileRollOnSize": "true",
        "FileByteLimit": "100000000"
      }
    }
  },

Authentication

The Authentication section specifies the underlying authentication provider that the system uses to authenticate credentials that are passed to the Hyland Rendering and Conversion Service.

  "Authentication" : [ "ApiKey" ],  

HostOptions

The AllowedOrigin section specifies an accepted origin to make CORS (Cross Origin Resource Sharing) requests. For more information, see the Enable Cross-Origin Requests (CORS) in ASP.NET Core topic on the Microsoft website.

The MultipartBodyLengthLimit value is the max number of bytes for multipart form data used on file upload.

Note: In some applications, the size of the page files that can be rendered is limited by the MultipartBodyLengthLimit setting. The default is 128 MB. If you work with files larger than the default, increase the value of this setting to allow those larger page files to render.
  "HostOptions" : {
    "AllowedOrigins" : [
    ],
     "MultipartBodyLengthLimit": 134217728
  },

ApiKeys

The ApiKey section specifies the set of keys to allow when the Authentication configuration option contains ApiKey.

  "ApiKeys" : [],