Understanding the BC Meridian system link

The  BC Meridian system link connects the Meridian Enterprise Server to Meridian Enterprise vaults as publishing sources or destinations.

This system link is useful in several scenarios, such as:

1. A common set of documents that need to be available in multiple vaults (such as a part library at multiple sites). Changes made at one site need to be published to the other vaults.
2. Released documents need to be published to another vault that is accessible from the Internet.

Note    Be aware that when the destination vault is located outside a firewall, the firewall must be configured to allow DCOM traffic from the Meridian Enterprise Server computer to the Meridian Enterprise application server of the destination vault.

3. Documents need to be exchanged between owner and contractor vaults.
4. Renditions need to be available in the source vault.

Published documents are imported into the destination system. If the destination system is also a Meridian Enterprise vault, the following additional actions may be performed:

• Folders may be created as part of the import process.
• Redlines are published by default by the AutoVue rendering module.
• A new revision of a document is created if the document already exists.
• If a source document has hybrid parts, they are only published to the destination vault if the native document is published or if the AutoCAD rendering module is used.
• Depending on the link's configuration settings, documents are released when the publishing job has completed.

• Publishing options that are set for individual documents as described in Publishing and rendering options.

Source document properties are copied to the destination system as defined by the property mapping of the publishing job.

This l ink generates special events in the source and destination vaults before and after publishing that can be used to further customize the publishing process. For more information on these events, see VBScript reference.