Synchronizing a repository

Synchronizing a repository imports the document and object definitions and metadata from the source vaults into the repository using the settings of a publishing job.

Repository synchronization is performed by the Publisher command-line program Dex.exe. By default, the program:

• Runs in unattended mode
• Begins synchronization immediately
• Displays progress during synchronization (in interactive mode)
• Closes when synchronization has completed

This program can be found in the folder where Meridian Enterprise was installed.

The Data Library can help you to select synchronization options and run Dex.exe immediately or to schedule synchronization for a later time.

To synchronize a repository:

1. In the Data Library configuration tree, select BlueCielo Publisher 2012\<JobName>. The synchronization options appear.
2. Perform one of the following actions:

• Click the Run now hyperlink to run Dex.exe immediately.
• Click the Schedule execution hyperlink to schedule Dex.exe to run at a later time or on a periodic schedule.
• Copy the text in Command line to the Clipboard and paste it in a Command Prompt window or elsewhere.

Note    The account that is used to run Dex.exe must have Read, Write, and Create Table permissions in the repository database.

The Dex.exe command-line arguments are described in the following table.

/RUN:"<JobCode>[:<Option>]"

/User

Note    Initializing synchronization may take several minutes for a large Meridian Enterprise vault.

Synchronizing a repository should be carefully integrated into all of the other nightly Meridian Enterprise server maintenance tasks that may be scheduled:

• Prepare for Backup
• Vault recovery logs
• Tape backup
• Vault content indexing
• Vault archiving
• Repository synchronization
• Repository content indexing
• Repository thumbnail generation

In general, the tasks should be scheduled in the preceding order and each task scheduled to run only after the previous task has completed. The amount of time required for synchronization depends on numerous factors but is approximately one second per document.

When the synchronization of a specific document fails, an error will appear on the Errors tab if Dex.exe is run in interactive mode. Detailed information about the error will also be written to the DexTrace.log file. This file can be viewed as described in Viewing the Publisher trace logs.

When synchronization has completed, the repository is ready to use.