Configure a Publishing Job

The read-only, internal identifier used by Publisher to refer to the job regardless of the value of Display Name.

Type a description of the job (500 characters maximum) as you want it to appear to users.

Type a descriptive name as you want it to appear in the Administration Console and elsewhere.

The sources of the documents to publish.

The types of the systems are shown in italic text. The display names of the systems are shown in bold text. These are shown for users to select a specific destination from when the user publishes documents with a job that has multiple destination systems configured. The connection names of the systems are shown in normal text and link to the source system definition.

If multiple destination systems are selected for a job, only the property definitions of the first system are shown for property mapping as described in Configure the Mappings. The property definitions of the other systems are assumed to be identical, at least for the properties that will be mapped.

When the EnableFQDNS registry value is set to:

• 0: If the full computer name is less than or equal to 15 characters, old rendering and profile jobs can work with DNS An Accruent portable document package. A briefcase is a single file in an archive format that may contain multiple discrete documents. Briefcases may be in open standard formats such as ZIP and RAR, the Accruent BRC format, or custom formats. A briefcase may also contain document metadata in a data file and, in the Accruent BRC format, document redlines. names. If the full computer name is greater than 15 characters, you must re register the vault with the full name and recreate all rendering profiles and jobs.

• 1: you must enter all names for the source system, rendering profiles, and computer (cluster node) in FQDN The Meridian Enterprise Server data access and business services running on a server computer. May also be used to refer to the server hosting the services. format. If this is not done, the job might produce undesirable results or not work at all.

To change the sources:

1. Click Edit.

   The Source Systems dialog box appears and lists the current source systems.

2. To add another source system:

   1. Type a computer name in the text box or select a server from the list.

      Exclude the domain name or rendition jobs might not appear in Administration Console.

   2. Click the connect icon or the browse icon , depending on the configured source type.

      The systems that are available on the specified server appear in the list. For file systems, the Browse dialog box appears.

   3. Select the systems that you want.

      For a file system, navigate to the parent of the folder that you want to select, select the child folder, and then click OK. The path of the selected folder appears in the dialog box.

3. To remove a system, clear the check box next to its name.

4. Click OK.

To change the display names of the systems to be more user-friendly:

1. Click Display Name.

   The Edit Display Name dialog box appears. The name is limited to 50 characters.

2. Edit the text in the Display Name column and then click Change.

   The names are updated.

To check whether the systems that are listed are online and available:

• Click Check Availability.

  Publisher connects to each system, confirms its availability, and shows the results.

A Microsoft Excel (2003 or higher) file that contains document metadata to publish to the destination system. Available only for file system sources.

The format of the metadata must be:

• In the first worksheet in the workbook.

• Column A of row 2 and higher must contain the paths of the documents to publish. The paths must be relative to the source folder.

• Column B and higher of row 1 must be named PropertyName1, PropertyName2, and so on to the last column of metadata properties.

To select the file, click Browse.

The destination of the documents to publish.

The types of the systems are shown in italic text. The display names of the systems are shown in bold text. These are shown for users to select a specific destination from when the user publishes documents with a job that has multiple destination systems configured. The connection names of the systems are shown in normal text and link to the source system definition.

To change or check the destination systems, perform the tasks described for the Source systems option.

By default, document metadata is published to an XML file named <DateTimeStamp>_<JobName>.xml (for example, 2013-10-04_07-30-35_BA5586.xml) and located in the destination folder. All of the properties mapped as described in Configure the Mappings are output to the file.

Enabling this option stores the document metadata in a database instead of in a file on disk. The database connection parameters are specified in the following options. Available only for file system destinations.

If the job publishes packages from a Meridian Explorer repository, the URI where the packages should be uploaded. Following are examples:

C:\Packages
\\ServerName\ShareName\Packages
ftp://ServerName/Packages

https://ServerName:444/Packages/

• In addition to the package file (.zip), a manifest file (.xlsx) is also uploaded for use by destination systems that must validate the package before processing it.

• HTTP and HTTPS destination URIs must end with a trailing slash character.

• IIS destinations should be configured to use authentication and the credentials configured as described in the following options.

• IIS destinations require WebDAV authoring rules be configured.

If the Connection string option is specified, a user account name with rights to connect to the database specified in Connection string.

If the job publishes packages from a Meridian Explorer repository, a user account with rights to the path specified for Destination systems and for Package destination URI.

The password for the account specified in User name.

If the Connection string option is specified, to test the current connection credentials:

• Click Test Connection/Test Package URI.

Creates one sub-folder for each recipient specified in the package. Supported only for UNC paths. For other types (for example, FTP, HTTP, HTTPS), the sub-folders must already exist.