BlueCielo Meridian Enterprise 2018 Release Notes
Migrating existing synchronization jobs
After you upgrade to Meridian Enterprise 2017, the new repository synchronization engine is used for all existing jobs and for new jobs by default. Except for creating additional synchronization tasks as listed below if your business case requires them, no new configuration is necessary. As a consequence, synchronization jobs are simpler than before but they can no longer perform individual document processing like rendering.
Depending on the contents of your repository and the types of its synchronization jobs, you may also notice some of the following effects of the conversion of old synchronization jobs to the new method after the upgrade:
- Project folders that are re-synced will be converted to projects in Meridian Explorer.
- If you do not run a full synchronization, the repository will contain a mix of project folders that were converted to Meridian Explorer projects and others that are still regular folders.
- Project copy documents that reside in the root of the repository will remain there until you re-sync the document or its project.
- Project copy tags that reside in the root of the repository will remain there until you re-sync them.
The following features of synchronization jobs have been removed since the documents are not synchronized individually. For more information about configuring the alternatives, see the BlueCieloMeridian Enterprise Administrator's Guide.
| Feature | Alternative |
|---|---|
|
Rendering during synchronization |
Create a replacement Rendition type job. |
| Configurable synchronization without projects job type | No alternative. Projects are always synchronized to the Explorer repository. |
|
Copy content to Explorer repository option |
Schedule content import with the new repository option Document Content. |
|
Create thumbnails option |
Create a replacement task with the THUMBNAILS repository management tool. |
|
Enable separate options per document option |
No alternative. Document properties cannot be used to set synchronization options. |
|
Enable Meridian script events option |
No alternative. The Doc_Sync* events do not occur for source documents. |
| ExplorerSynchronization property set | No alternative. The properties are always ignored during synchronization. |
| Merged folder structures from multiple source vaults | No alternative. A separate folder tree appears in the repository for each source vault. |
A synchronization validation task should be run after upgrading to this release, which is a best practice after any upgrade. In the unlikely event that the new engine causes problems with an existing job, the old engine can be activated for compatibility. Contact BlueCielo Technical Support for more information.