Configuring the Meridian Project Portal Publishing Service

Configuring the Meridian Project Portal 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 Meridian Enterprise Server database for publishing.

To configure the Meridian Project Portal File Publishing Service:

On the computer where you copied the files as described in Installing components on a Meridian Project Portal server, locate the file KronodocService.exe.config and open it in any text editor.

Locate and configure the settings described in the following table:

Meridian Project Portal Publishing Service settings
Setting	Description
PublisherServicesAddress	Set the <value> element to the Meridian Enterprise Server web services URL, for example, http://<ServerName>/Publisher.
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.
MonitorSources	The <value> element is a collection (ArrayOfString element) of <string> elements that each specify a job name and a starting ID to monitor. Specify the value using the syntax <JobName>;<StartID>, for example, 45E2E0;0. You can find the job name for each publishing job in its definition. You may specify multiple job name/starting ID pairs. One job name may be associated with multiple folders and one folder may be associated with multiple job name . 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 Enterprise Server 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.

Meridian Project Portal Publishing Service settings

Setting

Description

PublisherServicesAddress

Set the <value> element to the Meridian Enterprise Server web services URL, for example, http://<ServerName>/Publisher.

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.

MonitorSources

The <value> element is a collection (ArrayOfString element) of <string> elements that each specify a job name and a starting ID to monitor. Specify the value using the syntax <JobName>;<StartID>, for example, 45E2E0;0. You can find the job name for each publishing job in its definition. You may specify multiple job name/starting ID pairs. One job name may be associated with multiple folders and one folder may be associated with multiple job name .

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 Enterprise Server 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:

<userSettings> <BlueCieloECM.Publisher.KronodocService.Properties.Settings> <setting name="MonitorSources" serializeAs="Xml"> <value> <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <string>FC1A22;0</string> <string>1E9967;0</string> </ArrayOfString> </value> </setting> </BlueCieloECM.Publisher.KronodocService.Properties.Settings> </userSettings> <applicationSettings> <BlueCieloECM.Publisher.KronodocService.Properties.Settings> <setting name="PublisherServicesAddress" serializeAs="String"> <value>http://localhost/Publisher/</value> </setting> <setting name="MonitorSecondsPeriod" serializeAs="String"> <value>60</value> </setting> <setting name="PreventDuplicate" serializeAs="String"> <value>True</value> </setting> </BlueCieloECM.Publisher.KronodocService.Properties.Settings> </applicationSettings>

Save your changes and close the file.

Start the Meridian Project Portal Publishing Service as described in Running the Meridian Project Portal Publishing Service.

Related concepts

Understanding the Meridian Project Portal system link

Configuring the BlueCielo File Publishing Service

Configuring a SharePoint server

Configuring a Meridian Enterprise Server cluster

Related information

Security privilege descriptions


	BlueCielo Meridian Enterprise Server 2013 Administrator's Guide \| BlueCielo ECM Solutions