Essential configuration files for Document Automation Server

This section lists the different configuration files we have in Nutrient Document Automation Server (DAS), along with their uses.

Autobahn.config

The Nutrient DAS configuration file Autobahn.config can be found in the config directory of Nutrient DAS. This file allows the user to make some backend changes to the way Nutrient DAS works. Below are the contents of the file.

We strongly advise users not to change any undocumented settings.

These settings are important for Nutrient DAS to function properly and should never be changed unless guided by the Nutrient support team.

<configuration\>

<appSettings file="">

<clear />

<add key="inputdelay" value="10" />

<add key="jobqueuetimeout" value="180" />

<add key="jobqueueinterval" value="10" />

<add key="mergeflag" value="" />

<add key="trigger1001" value="" />

<add key="triggerlevel" value="" />

<add key="allowlongfilename" value="" />

</appSettings\>

</configuration\>

The input delay

This in an integer value that represents the number of seconds a file must exist in the input folder before Nutrient DAS attempts to process it. The default value is 0; to change this, update the value of the inputdelay key:

<add key="inputdelay" value="10" />

The value is in seconds.

Multicore throttle settings

Refer to the guide on multicore throttling for more information:

<add key="jobqueuetimeout" value="180" />

<add key="jobqueueinterval" value="10"/>

The value of jobqueuetimeout is in seconds.

Output trigger files

This feature makes Nutrient DAS copy a file (trigger file) to the output folder after the job completes and successfully copies the processed files to the output folder. This file can be used to trigger a post-processing workflow.

The keys below can be used to control the way this feature acts.

The setting below will copy test.csv to the top-level output folder of a job with job ID 1001:

<add key="trigger1001" value="test.csv" />

<add key="triggerlevel" value="top" />

The merge flag feature

This feature is used to give the user a certain level of control over which folders to be included in the merge operations (e.g. Merge Tiffs, Merge PDF, Merge Tiffs to PDF, and Extended Merge Tiffs to PDF). It provides the user with a mechanism of flagging folders to include for processing.

To use this feature, follow the steps below:

• Choose a name you want to set as the flag name. For instance, _ready.

• Open the Autobahn.config file located at <InstallDirectory>\Autobahn DX\config\.

• Change the value of <add key="mergeflag" value="" /> to <add key="mergeflag" value="ready.adx.merge" />.

The file extension must be .adx.merge for this to work.

• Next, create the zero-size byte file named _ready.adx.merge, and copy and paste in each folder that requires processing.

• Restart the service to load the new configuration.

Restarting the service will cause all jobs that are running through the job manager to terminate.

Allow long file names

Starting in Windows 10 and Windows Server 2016, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions. However, you must opt in to the new behavior. Refer to the file name length guide for more details on how to enable this setting.

After enabling support for long file names in the registry, set the value of the allowlongfilename key to true.

Allow users to disable SSL in email steps

SSL is a security feature that helps establish secure connections when sending emails. However, sometimes emails are only sent internally, in which case an SSL certificate may not be required (or available).

Though we recommend keeping SSL enabled in most cases, it can now be disabled by setting the secureoption configuration option to None. It’s set to Auto by default.

<add key="secureoption" value="Auto" />

tiffjunction.exe.config

The TIFF Junction configuration file tiffjunction.exe.config can be found in the distribution\tj\bin directory of Nutrient DAS. It allows the user to make some backend changes to the way TIFF Junction works. Below are the contents of the file:

<?xml version="1.0"?>

<configuration>

<appSettings>

<add key="DetailedValidation" value="false" />

<add key="CompatabilityMode" value="false" />

<add key="DateFormat" value="MM dd yyyy" />

<add key="AllowErrorTiffFiles" value="false" />

<add key="UseLibTiff4JPEG" value="false" />

<add key="OrderByInt" value="false" />

<add key="ConvertToTIFFThreshold" value="50" />

<!--Extensions in lower case -->

<add key="AcceptedImages" value=".jpeg,.png,.bmp,.wbmp,.tif…" />

</appSettings>

</configuration>

It’s important to pay attention to the element within the appSettings tags. The table below gives a more detailed explanation of each setting.

pj.exe.config

The PDF Junction configuration file pj.exe.config can be found in the distribution\pj\bin directory of Nutrient DAS. This file allows the user to make some backend changes to the way PDF Junction works. Below are the contents of the file:

<?xml version="1.0"?>

<configuration>

<startup useLegacyV2RuntimeActivationPolicy="true">

</startup>

<appSettings>

<add key="OrderByInt" value="true"/>

<add key="ValidatePDFa" value="true"/>

<add key="RemoveDuplicateFontFiles" value="true"/>

<add key="DateFormat" value="MM dd yyyy"/>

<add key="DateFormat" value="MM dd yyyy" />

</appSettings>

</configuration>

Pay attention to the element within the appSettings tags. The table below gives a more detailed explanation of what each setting.

Other configuration files