Professional Documents
Culture Documents
InterplayMAM 59 SyncServiceAdministrator
InterplayMAM 59 SyncServiceAdministrator
InterplayMAM 59 SyncServiceAdministrator
User’s Guide
Version 5
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.
This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be
used in accordance with the license agreement.
This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.
This guide is protected by copyright. This guide is for your personal use and may not be reproduced or distributed, in whole or in part,
without permission of Avid. Reasonable care has been taken in preparing this guide; however, it may contain omissions, technical
inaccuracies, or typographical errors. Avid Technology, Inc. disclaims liability for all losses incurred through the use of this document.
Product specifications are subject to change without notice.
Copyright © 2017 Avid Technology, Inc. and its licensors. All rights reserved.
2
The following disclaimer is required by getElementsByAttribute:
Copyright © 2006 Robert Nyman (http://www.robertnyman.com)
3
The following disclaimer is required by jquery.jqModal:
Copyright © 2007,2008 Brice Burgess (<bhb@iceburg.net>)
The following disclaimer is required by Microsoft.Net Framework Base Class Libraries, BigRational:
Portions of this product are Copyright © Microsoft Corporation. All rights reserved.
4
The following disclaimer is required by PlainIt Works JeeGooContext:
Copyright © 2009 - 2010 by Erik van den Berg
Trademarks
Avid, the Avid Logo, Avid Everywhere, Avid DNXHD, Avid DNXHR, Avid Nexis, AirSpeed, Eleven, EUCON, Interplay, iNEWS, ISIS, Mbox,
MediaCentral, Media Composer, NewsCutter, Pro Tools, ProSet and RealSet, Maestro, PlayMaker, Sibelius, Symphony, and all related
product names and logos, are registered or unregistered trademarks of Avid Technology, Inc. in the United States and/or other countries.
The Interplay name is used with the permission of the Interplay Entertainment Corp. which bears no responsibility for Avid products. All
other trademarks are the property of their respective owners. For a full list of Avid trademarks, see: http://www.avid.com/US/about-avid/
legal-notices/trademarks.
Avid Interplay | MAM Sync Service Administrator User’s Guide v5.9 • Created 6/8/2017 • This document is distributed by
Avid in online (electronic) form only, and is not available for purchase in printed form.
5
Contents
6
Using This Guide
Congratulations on your purchase of Avid® Interplay® | Media Asset Manager, a powerful system for
archiving and managing media in a shared storage environment. This guide describes how to use
Avid Interplay | MAM Sync Service Administrator, the central tool for monitoring metadata
synchronization from MAM Data Manager to MediaCentral Index.
This guide is intended for all users charged with maintaining Interplay Media Asset Manager. This
guide contains all the task-oriented instructions and conceptual information you need to work with
Interplay MAM Sync Service Administrator.
n All tasks described in this guide can only be performed by users with administrative privileges.
c A caution means that a specific action you take could cause harm to your
computer or cause you to lose data.
w
A warning describes an action that could cause you physical harm. Follow the
guidelines in this document or on the unit itself when handling electrical
equipment.
g A user tip provides a helpful hint that can aid users in getting the most from their
system.
> This symbol indicates menu commands (and subcommands) in the order you
select them. For example, File > Import means to open the File menu and then
select the Import command.
Bold font Bold font is primarily used in task instructions to identify user interface items and
keyboard sequences.
Italic font Italic font is used to emphasize certain words and to indicate variables.
Courier Bold font Courier Bold font identifies text that you type.
Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the mouse
action. For example, Command+Option+C or Ctrl+drag.
Symbol or Convention Meaning or Action
| (pipe character) The pipe character is used in some Avid product names, such as Interplay |
MAM. In this document, the pipe is used in product names when they are in
headings or at their first use in text.
For information on courses/schedules, training centers, certifications, courseware, and books, please
visit www.avid.com/support and follow the Training links, or call Avid Sales at 800-949-AVID
(800-949-2843).
8
1 Getting Started
The following topics provide basic information to help you get started using Avid Interplay | MAM
Sync Service Administrator:
• About Interplay | MAM Sync Service Administrator
• Opening Sync Service Administrator
• Understanding the Sync Service Administrator Layout
• Quitting Sync Service Administrator
Basic Features
Starting with release 5.0, Interplay MAM systems can be accessed by using the MediaCentral | UX.
MediaCentral UX provides the capability to search in the databases of different connected systems
by using the “Central Index”. This requires data synchronization between MediaCentral and
Interplay MAM.
On MediaCentral’s side, Media Index allows users of MediaCentral UX to search using the Central
Index, which provides both data storage and a query engine. The index receives its data from the
original data sources — generally, the databases of multiple asset management systems like Interplay
MAM — and then pushes the data to the service that performs the index. This allows the index to
continuously sync to the database. Indexed search in MediaCentral UX queries a central index
synced with multiple databases and finds anything stored in the index.
On Interplay MAM’s side, the synchronization of data between the MAM system database and
Central Index is done by the SyncCentralIndex Service. It gets data from the MAM Data Manager’s
DM_SYNC table and pushes it to Central Index: The SyncCentralIndex Service detects data changes
for media and EDL objects, reads information from the Data Manager database (for metadata, all
attributes; for strata, changed segments), and sends update and delete requests to Central Index.
Before SyncCentralIndex Service can synchronize the data, it passes all Interplay MAM attribute
names and types to Central Index and converts MAM attributes to Central Index custom attributes.
This is called the initialization of the data schema.
Note the following limitations:
• All Attributes marked as “searchable” in the MAM data model are always sent to Central Index
during synchronization; attributes marked as “not searchable” are not sent to Central Index and
are not available for searches or in search-result lists.
• When using legal list attributes in Interplay MAM CBA rules, MAM allows building rules using
“>=”, “<“ for legal list values, since these values are integer values in MAM. On the Central
Index side, legal list values are treated as “ID-string,” and only comparisons like “=” or “!=” are
supported.
The SyncCentralIndex Service has a GUI called “Sync Service Administrator” that can be used by
administrators to monitor the metadata synchronization between Interplay MAM and Media Index.
The following illustration shows the services that are involved in data synchronization for Central
Index on Interplay MAM’s and MediaCentral’s side.
10
Prerequisites for Using Sync Service Administrator
To use Sync Service Administrator you must be a member of an administrator group that has the
following group rights:
• Administration/Platform_Administration
As an administrator you can review and assign these group rights in the User Manager of the
Interplay MAM Administrator. For additional information, see the “Interplay | MAM User Manager
User’s Guide” that is shipped with the software.
For additional information, see the “Interplay | MAM Configuration Settings Reference” that is
shipped with the software.
Basic Checks
To use Central Index for Interplay MAM in MediaCentral UX, check and adjust the following
settings. These settings have been configured during the installation of the
MAM.Core.MediaCentralConnection package and should already display correct values.
n If you change the setting, you need to refresh the configuration of the DataMangerWS or restart the
pool MAM_0900_DataManager in MAM Control Center’s Service Controller.
6. Select the profile SyncCentralIndex > section Settings and ensure that the value of the following
keys are set to true.
- EnableDataPropagation
- EnableCBAAssignmentsPropagationOnStart (if needed)
- SendLegalListsOnStartup (if needed)
- SendThesauriOnStartup (if needed)
11
n If you change a setting, you need to refresh the configuration of the SyncCentralIndex or restart the
pool MAM_2200_SyncCentralIndex in MAM Control Center’s Service Controller.
7. Select the profile FeatureToggles > section SyncCentralIndex and check if the value of the
following keys have the required value:
- EnableAsyncThesaurusSending:
- True: Enables sending thesaurus data asynchronously.
Recommended for new installations starting with Interplay MAM v5.6/MediaCentral
v2.7. This is the default value. See “Thesaurus Handling” on page 27.
- False: Disables sending thesaurus data asynchronously.
- EnableThesaurusCompression:
- True: Enables sending thesaurus data in compressed format if the value of the feature
toggle EnableAsyncThesaurusSending is also set to “true.”
Recommended for new installations starting with Interplay MAM v5.7/MediaCentral
v2.8. This is the default value.
- False: Disables sending thesaurus data in compressed format.
- EnableTbmdSending:
- True: Enables the new format for time-based metadata (strata segments).
Recommended for installations starting with Interplay MAM v5.6/MediaCentral v2.7 if
populating non-text metadata fields in segments is to be supported. This is the default
value.
- False: Disables the new format for time-based metadata.
- EnableSyncBatchEntriesLimit:
- True: Enables limiting bulk operations by the number of assets.
Recommended for new installations starting with Interplay MAM v5.7/MediaCentral
v2.8. This is the default value. See “Synchronizing in Bulk Operations” on page 22.
- False: Disables limiting bulk operations by the number of assets.
- EnableSyncBatchSizeLimit:
- True: Enables limiting bulk operations by the size of assets.
Recommended for new installations starting with Interplay MAM v5.7/MediaCentral
v2.8. This is the default value.
- False: Disables limiting bulk operations by the size of assets.
- EnableSendLocalizedObjectClassesLabels:
- True: Enables sending localized asset type (object class) labels to Central Index as part
of schema updates.
Recommended for new installations starting with Interplay MAM v5.8/MediaCentral
v2.9. This is the default value.
- False: Disables sending localized asset type (object class) labels to Central Index as part
of schema updates.
- EnableSegmentCalculationWithTimeCodeLeaps:
- True: Enables SyncCentralIndex to take timecode leaps information into account when
calculating segment timecode information.
Recommended for new installations starting with Interplay MAM v5.8/MediaCentral
v2.9. This is the default value.
12
- False: Disables taking timecode leaps information into account when calculating
segment timecode information.
n If you change a FeatureToggle setting, you need to restart the pool MAM_2200_SyncCentralIndex in
MAM Control Center’s Service Controller.
Area Function
Title bar The Show mapping info link provides information on attribute mapping between
Interplay MAM and Central Index. For additional information, see “Displaying
Attribute Mapping” on page 40.
13
Area Function
Monitor Monitors recent synchronization activities, displays details for each activity, and
provides controls to manually trigger synchronization on different levels. For
additional information, see “The Monitor View” on page 14.
Traffic Monitors recently synchronized objects and displays details for each object. For
additional information, see “The Traffic View” on page 16
Statistics Provides statistics on how many MAM objects of different classes were synchronized
in Central Index. For additional information, see “The Statistics View” on page 18.
MAM/CI Compare Provides statistics on the number of objects and EDLs per object class in MAM and
Central Index, and shows the difference between these numbers. For additional
information, see “The MAM / CI Compare View” on page 18.
Sync Queue Provides statistics on the create, update, and delete entries in the DM_SYNC table. For
additional information, see “The Sync Queue View” on page 19.
Errors Displays information on unsynchronized entries and provides controls to reset or purge
erroneous synchronization entries. For additional information, see “The Errors View”
on page 19.
CI Services Monitor Displays information on the runtime status of Central Index services. For additional
information, see “The CI Services Monitor View” on page 20.
Send JSON Sends JSON statements to and receives responses from MediaCentral services for
debugging and troubleshooting purposes. For security reasons, the Send JSON tab is
hidden by default. As an administrator you can show the tab by setting the value of the
key EnableMessagingDiagnostics in the Settings section of the SyncCentralIndex
configuration profile to “true.”
14
q w e r
Item Function
1 Refresh controls Sync Service Administrator updates the display of recent synchronization
activities every five seconds if the Auto refresh check box is checked. If you
uncheck the Auto refresh check box you can update the display manually by
clicking the Refresh button.
2 Recent events list Displays a configurable number of synchronization activities (default is 3,000).
For each entry the following information is shown: Time stamp (data and time
of synchronization), consecutive number, and message.
The following colors indicate the synchronization status:
• Red: indicates synchronization errors
• Orange: indicates warnings
• Black: indicates schema, CBA, legal list, and thesaurus synchronization
activities; bold style indicates index rebuild activities
For additional information, see “Monitoring Synchronization Activities in the
Monitor View” on page 33.
3 Details Displays detailed information about the entry selected in the Recent events list.
15
Item Function
4 Water mark indicator Indicates the load of the synchronization queue as a traffic light. Sync Index
Administrator checks the number of high-priority entries in the DM_Sync table
and shows a traffic light depending on water mark settings. You can update the
water mark indicator manually by clicking the Refresh button. For additional
information, see “Checking the Health Status” on page 42.
16
q w e
r
q
Item Function
1 Refresh controls Sync Service Administrator updates the display of recently synchronized
objects every five seconds if the Auto refresh check box is checked. If you
uncheck the Auto refresh check box you can update the display manually by
clicking the Refresh button.
2 Synchronized objects list Displays a configurable number of recently synchronized objects (default is
3,000). For each object the following information is shown: Time stamp (data
and time of synchronization), consecutive number, and a title consisting of an
operation type (Created, Updated, or Deleted) and the DMGUID of the object.
The following colors indicate the synchronization status:
• Red: indicates synchronization errors
• Orange: indicates failed synchronizations
• Blue: indicates successfully created or updated objects
• Light blue: indicates deleted objects
• Gray: indicates bulk synchronization activities
For additional information, see “Monitoring Synchronized Objects in the
Traffic View” on page 42.
3 Details Displays detailed information about the object selected in the Recently
synchronized objects list.
4 Filter controls Applies filters to the entries displayed in the Recently synchronized objects list.
For additional information, see “Filtering Synchronized Objects in the Traffic
View” on page 47.
17
The Statistics View
The Statistics view provides statistics on how many MAM objects of different classes were
synchronized in Central Index. The information is displayed in an overview table, as shown in the
following illustration. For each object class the number of successful and failed synchronizations is
shown for the current hour, current day, and current week. Additionally, the total number of
synchronization activities is given.
The Statistics view is for information purposes only, and does not provide controls to apply actions
on the statistics. For additional information, see “Viewing Synchronization Statistics” on page 48.
The information is displayed in an overview table, as shown in the following illustration. It shows the
number of objects for each object and EDL class in MAM and Central Index. Additionally, the
number of differing entries is given.
The MAM / CI Compare view is for information purposes only, and does not refresh automatically. It
provides a control to update the statistics. For additional information, see “Comparing the Number of
Objects between Interplay | MAM and Central Index” on page 49.
18
The Sync Queue View
The Sync Queue view provides statistics on the number of entries in the synchronization queue. The
information is displayed in an overview table, as shown in the following illustration. For each object
class, it shows the number and priority of synchronization requests, and the create, update, and delete
entries in the DM_SYNC table. Additionally, the total number of entries in the synchronization table
is given.
The Sync Queue view is for information purposes only, and does not refresh automatically. It
provides a control to update the statistics. For additional information, see “Viewing Sync Queue
Statistics” on page 50.
Function
19
Function
2 Displays the number of synchronization errors for each affected object class. Provides check boxes to
select individual or all object classes to trigger a retry or purge operation. For additional information, see
“Error Handling” on page 52.
4 Triggers the selected synchronization operation (retry or purge) for the selected object class(es).
The CI Services Monitor view is for information purposes only, and does not refresh automatically. It
provides a control to update the status information. For additional information, see “Monitoring the
Status of Central Index Services” on page 50.
20
Sync Service Administrator quits, but both Interplay MAM Control Center and Interplay MAM
Administrator remain open. You can resume working in both applications or quit.
21
2 Working with Interplay | MAM Sync Service
Administrator
The following topics provide information about the basic actions that you can perform when working
with Sync Service Administrator:
• Basic Synchronization Concepts
• Triggering Synchronization Manually
• Background Activities
• Displaying Attribute Mapping
• Monitoring Synchronization Activities in the Monitor View
• Checking the Health Status
• Monitoring Synchronized Objects in the Traffic View
• Filtering Synchronized Objects in the Traffic View
• Viewing Synchronization Statistics
• Comparing the Number of Objects between Interplay | MAM and Central Index
• Viewing Sync Queue Statistics
• Error Handling
Before version 5.2, objects were sent to Central Index one by one. Starting with version 5.2, objects
are sent to Central Index in bulk operations. This is applied when you select the following
synchronization options:
• Synchronize objects of class
• Synchronize all objects
• Synchronize all objects (low priority)
• Rebuild index for all objects
As an administrator you can specify the number of records that are retrieved from the
synchronization queue (DM_SYNC table) and limit the bulk size in Interplay MAM System
Administrator (profile SyncCentralIndex > section Settings > key BatchSize).
Bulk operations are split into chunks. Starting with Interplay MAM v5.7, you can specify the split
criteria by using “size” and “number of entries” settings. In doing so, you define the number of assets
that are sent to Central Index in one query. As an administrator you can modify the settings in
Interplay MAM System Administrator (profile SyncCentralIndex > section Settings > keys
SyncBatchSizeLimit and SyncBatchEntriesLimit. If both limitations are turned on, the one that limits
more has higher priority. Note that the settings could be disabled by the feature toggles
EnableSyncBatchEntriesLimit and EnableSyncBatchSizeLimit (see “Basic Checks” on page 11).
Example 1: There is a bulk operation with 10 assets with different operation types (Create, Update,
Delete). The feature toggles EnableSyncBatchEntriesLimit and EnableSyncBatchSizeLimit are both
disabled. The bulk example would create six chunks. The assets in each chunk are sent to Central
Index in a separate query.
Example 2: There is a bulk operation with 10 assets with different operation types (Create, Update,
Delete). With the feature toggle EnableSyncBatchEntriesLimit “enabled” and the setting
SyncBatchEntriesLimit set to “2,” the bulk example would create seven chunks. The assets in each
chunk are sent to Central Index in a separate query.
Example 3: There is a bulk operation with 10 assets with different operation types (Create, Update,
Delete). The size of each asset is 1 KB. With the feature toggle EnableSyncBatchSizeLimit “enabled”
and the setting SyncBatchSizeLimit set to “3,” the bulk example would create six chunks. The assets
in each chunk are sent to Central Index in a separate query.
23
Starting with Interplay MAM v5.7, bulk operations are handled as follows:
1. Get the number of records from the DM_SYNC table, as specified by the setting BatchSize.
2. Optimize events (merge records for the same object).
3. Split the optimized list into chunks:
a. Each chunk can contain only the same operation type (create, update, delete).
b. If EnableSyncBatchEntriesLimit is set to true, the number of assets in the chunk cannot be
greater than what is specified in the setting SyncBatchEntriesLimit.
c. If EnableSyncBatchSizeLimit is set to true, the size of the chunk cannot be greater than what
is specified in the setting SyncBatchSizeLimit.
4. Send the chunks to Central Index.
Information on bulk operations can be found in the Traffic view’s Recently synchronized objects list,
where bulk messages are shown with gray font:
• Each time SyncCentralIndex service tries to send objects to Central Index in one query, “Sending
<number> assets in one query” is shown.
If objects were successfully sent to Central Index in one query, all sent objects are listed. After
that, the message “<numbers> assets sent in one query” is shown.
• If a bulk from the synchronization queue contains several updates for one object,
SyncCentralIndex optimizes the records and sends only one asset to Central Index. The message
“<n> changes merged” is shown.
After the merged changes are successfully sent to Central Index in one query, the message “1/1
asset was sent” is shown.
• If SyncCentralIndex service fails to send objects to Central Index in one query, all failed objects
are listed in the format “Error: <dmguid>.” After that, the “Failed to send <number> assets in
one query” message is shown.
• If SyncCentralIndex service fails to send objects to Central Index in one query, it tries to send
these objects one by one. In this case, the “Sending <number> assets one by one” message is
shown. While sending objects one by one, each object is listed separately. After all objects are
processed the “<number of successfully sent>/<total number> assets were sent one by one”
message is displayed.
For bulk operations a default timeout of 600 seconds is configured. As an administrator you can
modify the timeout in Interplay MAM System Administrator (profile SyncCentralIndex > section
Settings > key BulkSyncTimeout).
If Central Index has come out of sync but still has information about most objects, it is favorable to
keep it in operation and to re-send all objects to fill up the missing objects. Re-sending all objects
into an operational Central Index by using the default “Synchronize all objects” option might block
normal operations (create, update, delete).
Using the “Synchronize all objects (low priority)” option allows you to re-send all objects with lower
priority to not disturb the ongoing operation. The aim of this mechanism is to propagate updates of
objects (on which somebody is currently working) while a huge database is imported into Central
Index.
24
If you select the “Synchronize all objects (low priority)” option, all objects are added to the
synchronization table, but existing update requests are not deleted from the table. The DM_SYNC
table is populated by “create” events, which have the value “0” in the PRIORITY column whereas
the existing events have the value “1” in the PRIORITY column. The SyncCentralIndex service takes
the different event priorities into account: For each bulk synchronization, it takes events from the
DM_SYNC table with different priorities (from 0 to 1).
Resynchronization
Compared to the “Synchronize all objects (low priority)” option, “Synchronize all objects” provides
the additional feature to delete all existing update-entries from the DM_SYNC table. If you have
many updates in the DM_SYNC table, you might want to use this option rather than the “low
priority” option, to avoid sending information twice.
If you select the “Synchronize all objects” option, all objects are added to the synchronization table
and existing update requests are deleted from the table. The DM_SYNC table is populated by
“create” events, which have the value “1” in the PRIORITY column.
Rebuild Index
If you select the “Rebuild index for all objects” option, it cleans up the DM_SYNC table, removes
the MAM system from Central Index by sending a 'reset' command, resynchronizes the data schema,
refreshes CBA rules and their assignments, and synchronizes all objects.
Starting with version 5.4, objects are synchronized with low priority (DM_SYNC entries with value
“0” in the PRIORITY column are created).
Sort Order
When the DM_SYNC table is populated sorting criteria are applied. Before version 5.2, sorting was
based on object classes. Starting with version 5.2, sorting is based on the
MODIFICATION_DATETIME attribute in descending order. This ensures that the most recent
objects are sent to Central Index before older objects.
Sorting by “modification date and time” is applied when you select the following synchronization
options:
• Synchronize object of class
• Synchronize all objects
• Synchronize all objects (low priority)
• Rebuild index for all objects
If an update fails because an object does not exist in Central Index, the entire object needs to be
recreated in Central Index. Starting with version 5.2, all object information is resent to Central Index.
This may occur if the creation of an object failed in Central Index but the SyncCentralIndex service
sends updated information for the object.
Example: There is an “update” event in the DM_SYNC table for an object. SyncCentralIndex takes
this event and tries to send the update of the object. Central Index returns the error “Document is
missing in Elastic,” because the “create” event of this object failed (for any reason).
SyncCentralIndex handles this error and re-sends all object information to Central Index.
25
Additionally, SyncCentralIndex removes any “update” events of this object from the DM_SYNC
table because having re-sent the object all data is up-to-date, so there is no reason to send the same
information twice.
Starting with version 5.3, objects that are deleted from Interplay MAM can also be deleted from
Central Index during a resynchronization operation. To achieve this, a new entry is added to the
DM_SYNC table after all resend create entries. It uses the internal asset time stamp of Central Index
(“_created_time”) which tracks when an asset was created in Central Index. Invalid objects that have
not been refreshed since the resynchronization action started (the “created in CI time stamp” is older
than the start of the resynchronization action) are deleted.
When a user synchronizes all objects or objects by class, the new technical record is added to the
DM_SYNC table (after all object synchronization rows). When SyncCentralIndex synchronizes the
objects and detects this technical record, the deleteByQuery command is called after the object
synchronization is finished.
For the deletion feature, the server times of Interplay MAM and Central Index must always be
synchronized. Therefore, the configuration key DeleteByQueryTimeLag was added to the profile
SyncCentralIndex, section Settings. It is used to compensate for possible time differences between
Interplay MAM and Central Index.
Multi-Value Attributes
For Interplay MAM v5.5/MediaCentral v2.6, the format of multi-value attributes was changed.
Previously, a multi-value attribute was sent to Central Index as a “compound” attribute with a sub-
attribute that had the same name. Now, multi-value attributes are sent as a “simple” attribute (such as
“string,” “date,” or “int”) with a “multi-value: true” flag.
Starting with Interplay MAM v5.6/MediaCentral v2.7, the new multi-value format is enabled by
default. This changes how SyncCentralIndex sends information about multi-value fields. You can
search for multi-value attributes in Indexed Search.
Updating from version MAM v5.5/MediaCentral v2.6 or earlier to MAM v5.6/MediaCentral v2.7 or
later requires rebuilding the index for all assets. If you do not rebuild the index, you will see error
messages such as “Error: Re-index failed” or “Error: Attribute’s assignment failed” in the Monitor
view.
If you work with CBA rules in your Interplay MAM installation, CBA rules and the assignment of
CBA rules to users are also subject to synchronization with Central Index. CBA rules are defined in
the data model using Interplay MAM Datamodel Administrator; the assignment of CBA rules to user
groups is defined in Interplay MAM User Manager. For additional information, see the
Interplay | MAM Datamodel Administrator User’s Guide and Interplay | MAM User Manager User’s
Guide.
• CBA rules are always sent to Central Index on start of SyncCentralIndex service and after a
changed data model is activated.
• The CBA rules assignment is sent on start of SyncCentralIndex service according to the value of
the setting EnableCBAAssignmentsPropagationOnStart (profile SyncCentralIndex > section
Settings). Default is “true.”
You can manually trigger the resynchronization of the CBA rules to user assignment.
26
• CBA updates do not require the deletion of existing CBA rules and assignments before the
update.
• Note the following limitation: When using legal list attributes in Interplay MAM CBA rules,
MAM allows building rules using “>=” and “<“ for legal list values, since these values are
integer values in MAM. On the Central Index side, legal list values are treated as “ID-string,” and
only comparisons like “=” or “!=” are supported.
If you work with legal lists in your Interplay MAM installation, legal list values and their language-
dependent labels are also subject to synchronization with Central Index. Legal lists are defined in the
data model using Interplay MAM Datamodel Administrator; legal list values and labels are defined
in Interplay MAM Legal List Administrator. For additional information, see the Interplay | MAM
Datamodel Administrator User’s Guide and Interplay | MAM Legal List Administrator User’s Guide.
• Legal list data is queried directly from the database by SyncCentralIndex service without using
Data Manager WS.
• Legal list values are sent on start of SyncCentralIndex service according to the value of the
setting SendLegalListsOnStart (profile SyncCentralIndex > section Settings). Default is “true.”
You can manually trigger the resynchronization of legal list values.
• You synchronize all legal lists — selecting individual legal lists for synchronization is not
possible.
• Legal lists are currently sent to Central Index one by one, not in bulk operations.
• Legal lists and their individual entries may be configured for multi-tenancy. Therefore
SyncCentralIndex evaluates the tenant specified in the DefaultLegallistTenant key (profile
SyncCentralIndex > section Settings) during synchronization. By default, the key is empty,
which means that all legal lists are evaluated as being “tenant-independent.”
Additionally, you can specify a fallback tenant in the FallbackTenant key (profile
SyncCentralIndex > section Settings). If no label is available for the tenant specified in the
DefaultLegallistTenant key, the label for the configured fallback tenant is synchronized. By
default, the FallbackTenant key is empty, which means that “tenant-independent” labels are
synchronized. The fallback tenant is used both for legal lists and thesauruses.
• For legal list synchronization operations a default timeout of 600 seconds is configured. As an
administrator you can modify the timeout in Interplay MAM System Administrator (profile
SyncCentralIndex > section Settings > key ThesaurusSyncTimeout).
• Regarding format changes to MAM SyncCentralIndex service thesaurus entry identifiers — to
enable full text search by structured metadata labels for MediaCentral version 2.5 — the format
of legal list entries was changed. The format is now <systemID>:legallist_<typeID>:<itemID>.
Starting with MAM v5.7/MediaCentral v2.8, only the new ID format is valid for thesauruses,
legal lists, and their labels. Updating from an earlier version requires rebuilding the index for all
assets.
Thesaurus Handling
If you work with thesauruses in your Interplay MAM installation, thesaurus values and their
language-dependent labels are also subject to synchronization with Central Index. Thesauruses are
defined in the data model using Interplay MAM Datamodel Administrator; thesaurus values and
27
labels are defined in Interplay MAM Thesaurus Administrator. For additional information, see the
Interplay | MAM Datamodel Administrator User’s Guide and Interplay | MAM Thesaurus
Administrator User’s Guide.
• Thesaurus data is queried directly from the database by SyncCentralIndex service without using
Data Manager WS.
• Thesaurus values are sent on start of SyncCentralIndex service according to the value of the
setting SendThesauriOnStart (profile SyncCentralIndex > section Settings). Default is “true.”
You can manually trigger the resynchronization of thesaurus values; you can synchronize all
thesauruses or select an individual thesaurus for synchronization.
• Starting with Interplay MAM v5.6, thesauruses can be sent asynchronously to improve the
propagation of larger thesauruses. As an administrator you can configure the new thesaurus
propagation approach in Interplay MAM System Administrator (profile FeatureToggles >
section SyncCentralIndex > key EnableAsyncThesaurusSending).
• Starting with Interplay MAM v5.7, SyncCentralIndex service does not send thesaurus data to
Central Index via the BUS. SyncCentralIndex compresses the thesaurus data in a ZIP archive,
saves the zipped file to a download directory, and sends the download URL to Central Index.
Central Index downloads the zipped thesaurus using the received download URL. The new
thesaurus handling significantly improves performance.
As an administrator you can configure the new thesaurus compression and download approach in
Interplay MAM System Administrator (profile FeatureToggles > section SyncCentralIndex > key
EnableThesauriCompression). Note that the feature toggle only works in combination with the
feature toggle EnableAsyncThesaurusSending — both need to be enabled.
• For thesaurus synchronization operations, a default timeout of 600 seconds is configured. As an
administrator you can modify the timeout in Interplay MAM System Administrator (profile
SyncCentralIndex > section Settings > key ThesaurusSyncTimeout).
If thesaurus compression and asynchronous sending are enabled, the setting is used to control
how long SyncCentralIndex waits for notifications from Central Index. Use high timeouts (such
as 9,000 seconds) in case of large thesauruses. If the timeout expires, SyncCentralIndex stops
listening for notifications from Central Index; however, that does not mean that thesaurus
synchronization has failed.
• Currently, incremental updates of thesauruses are not supported. During synchronization all
information for each thesaurus is sent with “force-flag”=true, which means that old information
is no longer valid and only the new information is valid.
• The following thesauruses are excluded from synchronization:
- Thesauruses that are not defined in the data model
- The system thesaurus STATEMACHINE
- Thesauruses that contain more terms than allowed by configuration. As an administrator you
can modify the allowed maximum number of terms in Interplay MAM System
Administrator (profile SyncCentralIndex > section Settings > key TermsLimit).
• Thesauruses and their individual terms may be configured for multi-tenancy. Therefore
SyncCentralIndex service evaluates the tenant specified in the DefaultThesaurusTenant key
(profile SyncCentralIndex > section Settings) during synchronization. By default, the key is
empty, which means that all thesauruses are evaluated as being “tenant-independent.”
28
Additionally, you can specify a fallback tenant in the FallbackTenant key (profile
SyncCentralIndex > section Settings). If no label is available for the tenant specified in the
DefaultThesaurusTenant key, the label for the configured fallback tenant is synchronized. By
default, the FallbackTenant key is empty, which means that “tenant-independent” labels are
synchronized. The fallback tenant is used both for thesauruses and legal lists.
• For MediaCentral version 2.5, the format of the thesaurus entry identifier for the MAM
SyncCentralIndex service was changed to enable the full text search by structured metadata
labels. While in version 2.4 the identifier for the term was just a number (from the MS SQL
database), in version 2.5 the format is <systemID>:thesaurus_<typeID>:<itemID>, so all label
IDs are unique. The same applies to legal list entries whose format is now
<systemID>:legallist_<typeID>:<itemID>.
Starting with MAM v5.7/MediaCentral v2.8, only the new ID format is valid for thesauruses,
legal lists, and their labels. Updating from an earlier version requires rebuilding the index for all
assets.
c During index rebuild, all objects are removed from Central Index and are not available for
searches in Central Index. Depending on the data size this can take several hours to several
days. Avid recommends using the “Rebuild index for all objects” option only in case of an
emergency.
29
2. Type a reason in the Synchronization reason text box. All synchronization options — except for
synchronizing an individual object by DMGUID — require a reason string to activate the
Synchronize button.
3. Click Synchronize.
A security prompt opens.
4. Click OK.
The number of objects marked for synchronization is shown in the Details pane (“<number>
objects will be synchronized.”). The selected synchronization option is applied. During index
rebuild, the index for the MAM system is dropped, the data schema for the MAM system is
initialized, and, finally, all MAM objects are synchronized to Central Index. See “Background
Activities” on page 30. After the synchronization is finished, invalid objects are removed from
Central Index.
Time, user name, and synchronization reason string are logged and written to the
SyncCentralIndex service’s log file for security reasons.
During data schema synchronization, all operations — except for CBA rules to user assignment
— are unavailable (the Synchronize button is disabled).
Background Activities
During data synchronization the following activities are processed in the background. For additional
information, see “Basic Synchronization Concepts” on page 22.
SyncCentralIndex start
30
7. (Option) If multi-tenancy is enabled, the tenant-based CBA rules to user assignments are sent.
8. If the “Send legal lists on start” feature is enabled by configuration, legal lists are sent
(Thesaurus service).
9. If the “Send thesauri on start” feature is enabled by configuration, thesauruses are sent
(Thesaurus service).
The following actions are performed when the data schema is initialized — for example, when a
changed data model is activated in Interplay MAM.
1. The re-indexing status is checked (Import service).
2. By default, SyncCentralIndex sends schema updates with “reindexing” parameter set to “false,”
the data schema is sent to the Import service, and no re-indexing is performed.
If an error occurs during schema synchronization, SyncCentralIndex sends a
“TYPE_CHANGE_ERROR” (“Failed to synchronize schema changes because of field(s) type
changed”) and asks for index rebuild (“Field type change requires rebuild of index”).
3. CBA rules in the data model are checked. If they are disabled in the data model, they are
removed from Central Index (Permission service).
4. CBA rules are sent.
5. (Option) If multi-tenancy is enabled, the tenant-based CBA rules are sent.
6. Localized labels of object and EDL classes are sent to Central Index as a special legal list (http://
avid.com/thesaurus/[SYSTEM_ID]:legallist_MAM_OBJECT_CLASSES (Thesaurus service).
Localizations are only sent for languages supported by Central Index.
Index rebuild
All updates are deleted from the DM_SYNC table and the table is filled with all objects in the system
with a value of 1 in the PRIORITY column. After synchronization, deleteByQuery is performed.
31
Synchronize all objects (low priority)
The DM_SYNC table is filled with all objects in the system with a value of 0 in the PRIORITY
column. Synchronization is performed in the background, with a lower priority than with normal
create or update operations. After synchronization, deleteByQuery is performed.
All updates for the selected object class are deleted from the DM_SYNC table and the table is filled
with the objects of the selected class in the system with a value of 1 in the PRIORITY column. After
synchronization, deleteByQuery is performed.
The following actions are performed when the CBA rules to user assignments are synchronized.
1. CBA rules in the data model are checked and the CBA rules to user assignments are refreshed.
2. (Option) If multi-tenancy is enabled, the tenant-based CBA rules to users assignments are sent.
The following actions are performed when legal lists are synchronized.
1. SyncCentralIndex service retrieves the legal list data from the database.
2. Using Thesaurus service, legal lists and the assignment of legal list attributes are updated in
Central Index.
Synchronize thesauruses
Create object
Update object
The object is sent to Central Index with an update request (Import service). If the object does not
exist in Central Index, it is created from scratch.
Delete object
A delete request for the given object is sent to Central Index (Import service).
32
Monitoring Synchronization Activities in the Monitor
View
Use the Monitor view to get an overview of a configurable number of recent synchronization
activities (default is 3,000) and detailed information about synchronization activities. It provides
information on synchronization time, synchronization activity, and status of the synchronization. For
additional information, see “Background Activities” on page 30.
Records for the system events history — the synchronization activities shown in the Monitor view —
are stored in the database. To perform database cleanup, SyncCentralIndex removes all records that
are older than a configurable number of days (default is 7 days). You can modify the cleanup interval
by changing the value of the key SystemHistoryCleanupPeriodInDays (profile SyncCentralIndex,
section Settings) in Interplay MAM System Administrator.
You can also modify the number of displayed synchronization activities by changing the value of the
key MonitorHistoryLength (profile SyncCentralIndex, section Settings) in Interplay MAM System
Administrator.
The Monitor view’s Details pane shows up to 2,000 lines of text by default. If this number is
exceeded, a notification “Too much detail to display. Please see the full length details in log file” is
shown. You can modify the number of displayed text lines by changing the value of the key
DetailsLength (profile SyncCentralIndex, section Settings) in Interplay MAM System Administrator.
- For the localization of object classes that is sent as part of schema synchronization activities,
the following entries are shown.
33
- For thesaurus download activities, the following entries are shown.
- For legal list and thesaurus activities, the following entry is displayed after a finished
propagation activity, if, for example, the affected attribute is defined in the data model but
marked as “not searchable.”
- For index rebuild activities, and legal lists and thesauruses start activities, the corresponding
action is displayed in bold, black font, as shown in the following illustration.
- For warnings, such as if a thesaurus is not going to be synchronized, “Warning” and a reason
string is displayed in orange font.
- For synchronization errors, such as if the re-indexing status cannot be obtained from Central
Index, the synchronize of the data schema failed, or the legal list attribute assignment failed,
the reason string is displayed in red font.
Activity Details
Startup For startup activities, such as “Service startup” no detailed information is displayed.
Synchronization For each synchronization request, the name of the requesting user or service and the reason string
requests is shown.
34
Activity Details
Schema For a schema synchronization request, the name of the requesting user or service and the reason
synchronization string is shown.
For schema synchronization started and finished entries, system information and the synchronized
attributes are displayed, as shown in the following example for “Schema synchronization finished.”
For a “Failed to syn schema. Index rebuild required” error, a reason string and the Response
message are displayed, as shown in the following example.
35
Activity Details
CBA rules and CBA CBA rules: the request message sent to the Permission service (for “CBA rules propagation
rules assignments started”) and the response message (for “CBA rules propagation finished”) are shown.
Assignment of CBA rules to users: the request message sent to the Permission service (for “Trying
to send CBA rules’ assignments”) and the response message (for “Sending of CBA rules
assignments finished successfully”) are shown.
36
Activity Details
Legal lists For “Legal lists to be synchronized,” the IDs and names of all legal lists that are to be synchronized
are shown.
For propagation of legal list <name> entries, the request message sent to the Thesaurus service (for
“Started propagation for <legal list name>”) and the response message (for “Propagation finished
“) are shown.
For “Assignment of attributes finished,” statistics about the name and ID of the legal list and the
number of its assigned attributes are shown.
37
Activity Details
Thesauruses For “Next thesauri are going to be sent,” the names of all thesauruses that are to be synchronized
are shown (thesauruses that are defined in the data model and belong to the tenant specified in the
configuration profile SyncCentralIndex).
For propagation of thesaurus <name> entries, the request message sent to the Thesaurus service
(for “Started propagation for <thesaurus name>”) and the response message (for “Propagation
finished”) are shown.
For “Started assignment of attributes,” the request sent to Thesaurus service is shown.
For “Assignment of attributes finished,” statistics about the name and ID of the thesaurus and the
number of its assigned attributes are shown.
38
Activity Details
Re-index activities For Re-indexig activities, different types of information are shown in the Details pane.
• For “Index rebuild started,” “Cleared DM_SYNC table,” “Removed system from Central
Index,” and “Index status checking,” no detailed information is displayed.
• Waiting for re-indexing results
• Re-index in progress
• Re-index is complete
39
Activity Details
• The thesaurus is not synchronized because it contains more terms than allowed by
configuration.
Error For “Error” entries, information about the reasons for failure are provided. The following example
shows what is displayed for the error “Cannot obtain re-indexing status from CI.”
If you have administrator privileges for MediaCentral, you can sign in to MediaCentral UX and view
the complete mapping information in the Media | Index > Indexes view.
Base Information
The following table describes how Media Index categorizes Interplay MAM base information:
Type Prefix.ClassName.
The prefix is “sequence” for EDL classes and “asset” for object classes (such
as sequence.EDL and asset.VIDEO).
Id {DMGUID}
systemID SYSTEMID
Common Attributes
The following table describes how Media Index categorizes some common Interplay MAM
attributes:
40
Media Index Field Interplay MAM Attribute
Name MAINTITLE
GlobalAssetID DMGUID
Creator REGISTRATION_USERLOGIN
Modifier MODIFICATION_USERLOGIN
Created REGISTRATION_DATETIME.
If REGISTRATION_DATETIME is empty, the values of the
REGISTRATION_DATE and REGISTRATION_TIME attributes are
combined.
Modified MODIFICATION_DATETIME.
If MODIFICATION_DATETIME is empty, the values of the
MODIFICATION_DATE and MODIFICATION_TIME attributes are
combined.
ThumbnailURL /api/mam/proxy/forresource?id=interplay-
mam:{SYSTEMID}:1|thumb|{DMGUID}
Description DESCRIPTION
durationTC SYSTEM_DURATION_TC
The value is taken from the attribute SYSTEM_DURATION_UNITS or
SYSTEM_DURATION (as fallback). Every time
SYSTEM_DURATION_UNITS or SYSTEM_DURATION are changed,
SYSTEM_DURATION_TC is set.
Custom Attributes
All other MAM attributes are sent as Custom attributes with prefix “com.avid.mam.” followed by the
MAM attribute name in Central Index (for example, com.avid.mam.asset_type).
41
Checking the Health Status
The Monitor view provides a health indicator that indicates the load of the Synchronization queue. It
checks the number of high-priority entries in the Synchronization queue and displays a warning
when the number of entries in the DM_Sync table exceeds a configurable water mark. The view
automatically updates the health indicator status every 60 seconds.
The water marks depend on the indexing performance and can be configured in MAM System
Administrator, in the profile SyncCentralIndex, section Settings, keys WatermarkLevel1 and
WatermarkLevel2. Default values are 5,000 for WatermarkLevel1 and 50,000 for WatermarkLevel2.
2. (Option) Position the mouse pointer over the health indicator icon to show information that
explains the status and the current water mark settings.
3. (Option) Click the Refresh button to update the health indicator manually.
Records for the traffic history — the synchronization activities shown in the Traffic view — are
stored in the database. To perform database cleanup, SyncCentralIndex removes all records that are
older than a configurable number of days (default is 7 days). You can modify the cleanup interval by
changing the value of the key TrafficHistoryCleanupPeriodInDays (profile SyncCentralIndex, section
Settings) in Interplay MAM System Administrator.
You can also modify the number of displayed objects by changing the value of the key
TrafficHistoryLength (in the profile SyncCentralIndex, section Settings) in Interplay MAM System
Administrator.
42
To monitor synchronized objects:
1. (Option) Click the Refresh button to update the list of synchronized objects.
2. Scroll through the Recently synchronized objects list to get an overview of the recently
synchronized objects. List entries are numbered sequentially and are time-stamped (data and
time of synchronization). Additionally, it shows:
- Each time SyncCentralIndex gets rows from the DM_SYNC table, “<n> rows fetched from
synchronization queue” is displayed to indicate that SyncCentralIndex is processing items
from the synchronization queue.
- For bulk activities, the corresponding action is displayed in gray font, as shown in the
following illustration.
- For each successfully synchronized object, a title is displayed that includes the operation
type (Created, Deleted, Updated) and DMGUID of the object — created and updated objects
in blue font, deleted objects in light blue font.
If a bulk from the synchronization queue contains several updates for one object,
SyncCentralIndex optimizes and merges the updates. This is indicated by a “<n> changes
merged” postfix.
- For deletion of invalid assets, “missed objects” strings are displayed in black font.
- For synchronization errors, “Error <DMGUID of object>” is displayed in red font. An object
is in error state if the synchronization requests have failed for a configurable number of
attempts (default is 10).
43
Activity Details
Startup For startup activities, such as “Waiting for objects,” no detailed information is displayed.
Sending assets / bulk For sending asset activities, the following details are shown:
operations
• For “Sending x assets in one query” and “x/x assets were sent” entries, information about the
number of assets and the operation type (Index, Update, or Delete) is given.
• For finished bulk operations (“x assets sent in one query”), base, common, and custom data for
each object in the bulk operation sent to Central Index are listed; additionally, statistics about
the result set (received, indexed, updated, deleted, failed, and rejected assets) are shown.
44
Activity Details
Objects For successfully created and updated objects, base, common, and custom data sent to Central Index
are listed, as shown in the following illustration for a “create” activity.
45
Activity Details
Missed Objects Invalid objects — objects that have not been refreshed in Central Index since the resynchronization
action started — are removed from Central Index by using the “deleteByQuery” command, based
on the “_created_time” time stamp.
For “Removing missed objects from CI,” the following is shown.
If no objects are removed (“There were no missed objects in CI”), the following is shown.
If objects are removed from Central Index, “<number> objects were deleted” is shown. If invalid
objects are deleted but not all objects were updated in Elasticsearch at the time of deletion, a
Version Conflict Error is shown.
46
Activity Details
Warning / Error For “Warning” and “Error” entries, information about the reasons for failure are provided. The
following example shows what is displayed for the warning “Failed to synchronize object.”
3. Deselect the check boxes of the entries you want to hide from the Recently synchronized objects
list:
- Created: Shows “object created” synchronization information.
- Updated: Shows “object updated” synchronization information.
47
- Deleted: Shows “object deleted” synchronization information.
- Warning: Shows warning messages.
- Error: Shows error messages.
- Info: Shows system messages.
- Bulk: Shows bulk synchronization information.
The filter is applied to the entries shown in the Recently synchronized objects list. If no entry of
the selected type can be found, the list shows the “No events found” message.
4. Select the check boxes of the entries you want to show in the Recently synchronized objects list.
5. (Option) Click the blue Activate button so it turns black.
The Filters check boxes are disabled. The Recently synchronized objects list shows all objects
and activities again.
n All information refers to the current runtime of the SyncCentralIndex service — if the service is
rebooted, all statistics are reset to 0.
The view shows synchronization statistics in an overview table. For each object class, the
number of successful and failed synchronization requests (create, update, and delete) to Central
Index is shown for the current hour, current day, and current week. An object is listed in the
Failed column if it could not be synchronized after a configurable number of tries (default is 10).
The total number of synchronization activities is shown in the last column.
2. (Option) Do one of the following:
t Select the Auto refresh check box to refresh the statistics display every five seconds.
48
t Click the Refresh button to update the statistics display manually.
The view shows synchronization statistics in an overview table. For each object and EDL class, it
shows the number of objects in MAM and Central Index, and the difference between them. The
total numbers are shown in the last column.
If the Search service is unavailable, the Central Index is reset, or an error occurs while
information is collected, the CI object count is set to 0 and an error message is displayed below
the table, as shown in the following illustration.
2. Click the Refresh button to query the object count from both systems and update the statistics
display.
49
Viewing Sync Queue Statistics
The Sync Queue view provides statistics on the number of entries in the DM_SYNC table. It shows
all requests for normal operations (create/update/delete) and for resynchronization (split into low-
and high-priority level).
n Re-indexing can be one reason for many entries in a queue, but not the only one — an increased load
due to many create/update requests can also generate a long queue (caused by many users, through
third-party integrations, or ongoing data migrations into the Interplay MAM database).
The view shows synchronization queue statistics in an overview table. For each object class the
following is shown:
- The number of synchronization requests, split into high- and low-priority requests
- The number of create, update, and delete entries in the DM_SYNC table
The total number of entries in the synchronization table is shown in the last column.
2. Click the Refresh button to query the current status of the DM_SYNC table and update the
statistics display.
The CI Services Monitor view is shown by default. As an administrator you can hide the view by
setting the value of the key EnableServicesStatuses in the Settings section of the SyncCentralIndex
configuration profile to “false.”
50
To monitor the status of Central Index services:
1. Open the CI Services Monitor view.
The status information is refreshed and displayed in an overview table. It shows the status of
each service indicated by an icon and status message, the name of the service, and its version
number (if it exists). Additionally, the host name is given as header.
Not registered Indicates that the service is not registered on the BUS (for example, because it
is stopped).
Suspended Indicates that the service cannot work correctly due to a non-service related
issue.
Warning Indicates that the service is still fully functional but may want to warn users of
issues (for example, high memory usage).
Error Indicates that the service is not working as expected and needs intervention to
fix issues.
51
2. Click the Refresh button to query the status of all services and update the status display.
If an error occurs while the status information is retrieved, an error message is displayed, as
shown in the following example.
Check the SyncCentralIndex log file to get additional information on the error reason.
Error Handling
The Errors view provides statistics on synchronization errors and provides controls to reset or purge
erroneous synchronization entries in Central Index. Technically, the view shows the count of “failed
to sync” rows in the DM_SYNC database table, grouped by object classes.
52
2. Do one of the following:
t Select the Object class check box to select all object classes shown in the table.
t Select the check box of individual object classes.
3. Do one of the following:
t Select the Clear error flag option button to reset the error count for the entries that have
exceeded the threshold — that is, retry the synchronization. Technically this means that the
ERROR_COUNT column value for the selected object classes will be set to 0.
t Select the Remove synchronization entries with errors option button to remove entries where
the error count has exceeded the threshold — that is, purge and ignore the errors.
Technically this means that the ERROR_COUNT column value for the selected object
classes will be deleted.
4. Click Submit.
A security prompt opens.
5. Click OK.
The selected option is applied. The Errors view is refreshed and the fixed object class is removed
from the Errors table. If the Retry option was applied, for each resynchronized object an update
event is listed in the Monitor view’s Recently synchronized objects list.
53
Index
A E
Activate button 47 Error 33, 40, 42
Auto refresh 14, 16 ERROR COUNT 19, 52
Automatic fix of update errors 22 ErrorCountThreshold 19, 52
Avid Errors view 13, 19, 52
online support 8 synchronization errors 19, 52
training services 8
F
B
Filtering entries in the Traffic view 47
Background activities during synchronization 30 Filters check boxes 47
Basic synchronization concepts 22
Button
Activate 47
G
Refresh 33, 42, 47 Group rights 11
Submit 19, 52
Synchronize 14, 29
H
C Health indicator 42
High priority 50
CBA rules handling 22
Central Index 9, 29, 48, 50
monitoring status of services 20, 50 I
Checking health status 42 Index rebuild 30
CI Services Monitor view 13, 20, 50 Interplay MAM
status information 50 Administrator 13
Clear error flags 19, 52 Sync Central Index Service 9
Color coding 14, 16, 33, 42 Sync Service Administrator 9
Comparision statistics 18, 49 System Administrator 11
Configuration options 11 User Manager 11
Create object 30
L
D
Legal list handling 22, 30
Data schema synchronization 30 Low priority 50
Delete object 30
Deletion of invalid objects 22
Details 14, 16 M
Details pane 33, 40, 42 MAM/CI Compare view 13, 18, 49
Displaying comparision statistics 18, 49
sync queue statistics 50 MediaCentral UX 9
synchronization details 33, 40, 42 Monitor view 13, 14, 33, 40
synchronization statistics 48 Auto refresh 14
DM_SYNC table 9, 19, 22, 30, 50, 52 checking health status 42
color coding 14, 33
54
Index
S U
Schema synchronization 33, 40 Update object 30
Sort order 22
Starting Sync Service Administrator 13 V
Statistics view 13, 18, 48
synchronization statistics 18, 48 View
Status of Central Index services 20, 50 CI Services Monitor 13, 20, 50
Sync Central Index service 9 Errors 13, 19, 52
Sync queue statistics 50 MAM/CI Compare 13, 18, 49
Sync Queue view 13, 19, 50 Monitor 13, 14, 33, 40, 42
statistics 50 Statistics 13, 18, 48
synchronization statistics 19 Sync Queue 13, 19, 50
Sync Service Administrator Traffic 13, 16, 42, 47
background activities 30
basic synchronization concepts 22 W
checking health status 42
configuration options 11 Warning 33, 40, 42
displaying synchronization details 33, 40 Water marks 42
error handling 52 Working with Sync Service Administrator 22
features 9
55
Avid Technical Support (USA) Product Information
75 Network Drive Visit the Online Support Center For company and product informa-
Burlington, MA 01803-2756 USA at www.avid.com/support tion, visit us on the web at www.av-
id.com