Configure a Publishing Job

You create a publishing job as described in Create a Publishing Job. This type of job defines the options for publishing documents or creating renditions.

To configure a publishing job:

In Meridian Enterprise Server Administration Console, in the Data Exchange group, click Jobs. The All Jobs page appears and lists the existing publishing jobs. The jobs are grouped by the name of the computer (cluster node) to which they have been assigned.
Double-click the publishing job that you want to configure. The Overview page appears.
Click options or type values using the descriptions in the following table.
Click SAVE.
Configure the applicable options as described in the remaining topics in this chapter.

Note:

Some of the options in the following table are only available for specific source or destination system types.

Publishing job basic options
Option	Description
Synchronization	The read-only type of the publishing job.
Name	The read-only, internal identifier used by Publisher to refer to the job regardless of the value of Display Name.
Description	Type a description of the job (500 characters maximum) as you want it to appear to users.
Display Name	Type a descriptive name as you want it to appear in the Administration Console and elsewhere.
Source systems	The sources of the documents to publish. Note: 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. If the EnableFQDNS registry value is enabled on a Meridian Enterprise server that is a source system, the system must also be specified in FQDN format in this option. Otherwise, the job can cause undesirable results or not work at all. For more information about the registry value, see the Accruent Meridian Enterprise Administrator's Guide. To change the sources: Click EDIT. The SOURCE SYSTEMS dialog box appears and lists the current source systems. To add another source system: Type a computer name in the text box or select a server from the list. Note: Exclude the domain name or rendition jobs might not appear in Administration Console. 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. 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. To remove a system: Clear the checkbox next to its name. Click OK. To change the display names of the systems to be more user-friendly: Click DISPLAY NAME. The EDIT DISPLAY NAME dialog box appears. The name is limited to 50 characters. 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.
Properties file	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.
Destination systems	The destination of the documents to publish. Note: 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.
Computer	If a cluster is configured as described in Configure a Meridian Enterprise Server Cluster, select the node on which to run this job.
Use database for metadata storage	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.
Connection string	A valid connection string to connect to a SQL Server or Oracle database where the metadata should be stored.
Package destination URI	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/ Note: 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.
User name	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.
Password	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.
Table	The name of the table where to store the metadata. The column names and data types in this table must match the property names and data types that are mapped as described in Configure the Mappings.
Create folders for recipients	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.
Path column	The name of the column that will contain the document paths. The column must be the String data type.

Configure a Publishing Job

We’re sorry about that

Thanks for letting us know.

Great!