Configure the Accruent File Publishing Service

Configuring the Accruent File Publishing Service specifies where the service will monitor for new files, how often it monitors, and where and how it will register the files in the Publisher database for publishing.

To configure the Accruent File Publishing Service:

On the computer where you copied the files as described in Install Components On a Windows File Server, locate the file WinFSService.exe.config and open it in any text editor.
Locate and configure the settings described in the following table:
Save your changes and close the file.
Start the Accruent File Publishing Service as described in Run the Accruent File Publishing Service.

Accruent File Publishing Service settings
Setting	Description
PublisherServicesAddress	Set the <value> element to the Publisher web services URL, for example, http://<ServerName>/BCEnterprise.
MonitorSecondsPeriod	Set the <value> element to the frequency in seconds at which you want the service to scan the folder for changed files. The default value is 60 seconds.
PreventDuplicate	Set the <value> element to True (default) to check for duplicate document registrations before adding a new one. If any duplicates found, the document will not be registered again.
FailOnDuplicate	Set the <value> element to True to continue a batch operation if any duplicate document registration is found. The default is False.
CommitSize	Set to the number of documents to send to the server as a single batch. If set to 0, all documents are sent in one batch. The default value is 10.
MonitorFolders	The <value> element is a collection (ArrayOfString element) of <string> elements that each specify a job name (not Display Name) and a corresponding folder to monitor. Specify the value using the syntax <JobName>;<FolderPath>, for example, 45E2E0;D:\ToPublish\. You can find the job name for each publishing job in its definition. You may specify multiple job name/folder pairs. One job name may be associated with multiple folders and one folder may be associated with multiple job names. If the publishing job has multiple source or destination systems, the following syntax must be used to specify the ordinal numbers of the systems to use. The numbers are the one-based index of the systems as defined in the publishing job. SourceNumber{JobName}TargetNumber;FolderPath SourceNumber is the index of the publishing source. It is required if the job has multiple sources configured. TargetNumber is the index of the publishing destination. If omitted, then the files will be registered for all destinations. Examples: JobName;C:\TEMP\Source – compatible with prior Publisher versions. The job must have a single source. If multiple targets are defined, then the files are published to all destinations. 2{JobName}1;C:\TEMP\Source – publish from source #2 to destination #1 JobName}1;C:\TEMP\Source – publish to destination #1. The job must have a single source 2{JobName;C:\TEMP\Source – publish from source #2 to all destinations

Following is a simple example of these settings:

<setting name="PublisherServicesAddress" serializeAs="String">
  <value>http://nkv/Publisher/</value>
</setting>
<setting name="MonitorSecondsPeriod" serializeAs="String">
  <value>60</value>
</setting>
<setting name="PreventDuplicate" serializeAs="String">
  <value>True</value>
</setting>
<setting name="MonitorFolders" serializeAs="Xml">
  <value>
    <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <string>45E2E0;D:\ToPublish\</string>
    </ArrayOfString>
  </value>
</setting>