® Interplay | Engine and Interplay | Archive Engine Administration Guide Version 3.
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 document is protected under copyright law.
Copyright 1996 Daniel Dardailler. Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). © DevelopMentor This product may include the JCifs library, for which the following notice applies: JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party Software directory on the installation CD. Avid Interplay contains components licensed from LavanTech.
Contents Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Viewing Help and Documentation on the Interplay Production Portal. . . . . . . . . . . . . . . 13 Interplay Documentation . . . . . . . . .
Performing a Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Viewing Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Database Information Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Locking and Unlocking Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting User Authentication Providers and Importing Users . . . . . . . . . . . . . . . . . . . . . 114 Setting Avid ISIS Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Setting Windows Domain Authentication and Importing Users . . . . . . . . . . . . . . . 118 Setting LDAP Authentication and Importing Users. . . . . . . . . . . . . . . . . . . . . . . . . 120 Managing Users, User Groups, and User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interplay Media Services View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Interplay Transfer Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Interplay Transfer Settings View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Workgroup Transfer Presets View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7 Interplay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Chapter 8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Troubleshooting Login Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Troubleshooting Client Connection Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Optimizing Interplay Performance. . .
Avid Workgroup Server Browser Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Avid Workgroup Preview Server Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Avid Workgroup TCP/COM Bridge Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Avid Workgroup VSS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Avid Workgroup Engine Monitor Service . . . . . . . . . . . . . . . . . . . . . . . .
Symbols and Conventions Using This Guide Congratulations on your purchase of Interplay® | Production, a powerful system for managing media in a shared storage environment. This guide describes how to use Interplay | Administrator, an Interplay client application that provides tools to configure the Interplay | Engine and to manage the database on the server.
If You Need Help Symbol or Convention Meaning or Action > 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. This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
Viewing Help and Documentation on the Interplay Production Portal Viewing Help and Documentation on the Interplay Production Portal You can quickly access the Interplay Production Help, links to the PDF versions of the Interplay Production guides, and other useful links by viewing the Interplay Production User Information Center on the Interplay Production Portal. The Interplay Production Portal is a Web site that runs on the Interplay Production Engine.
Interplay Documentation Interplay Documentation The following documents describe how to use Interplay Production: • Interplay | Production Best Practices — provides an overview of the major Interplay components, shows sample configuration diagrams, and describes several of the key features, such as setting up a user database and using the Interplay Archive Engine.
Avid Training Services Avid Training Services Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment. For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.
1 Getting Started with the Interplay | Administrator The Interplay Administrator provides database administrators and maintenance engineers with the tools required to configure the Interplay Engine and to manage the database on the server.
Understanding the Interplay Engine and Interplay Workgroups An Interplay database consists of two parts: • A metadata database, which holds information about the assets, or metadata. • Source files for the assets, for example, graphics files and Avid media files. The source files for file assets can be stored on the Interplay Engine or on an Avid shared-storage system. The source files for Avid assets are always stored on shared storage.
Understanding the Interplay Engine and Interplay Workgroups Media files for Avid assets are always stored on an Avid shared-storage system. Source files for file assets can be stored on the Interplay Engine or on an Avid shared-storage workspace. The location that holds file assets is called the file repository. When you first install Interplay Engine software, the installation program requires you to set one root folder for the database on a local drive.
Understanding the Interplay Engine and Interplay Workgroups Interplay Archive Engine A facility might also include an Interplay Archive Engine. An Interplay Archive Engine is configured similarly to an Interplay Engine. An Archive Engine is integrated with a third-party archive system. An Interplay Archive database is always named AvidAM. An Interplay database is always named AvidWG.
Understanding the Interplay Engine and Interplay Workgroups n In this guide, references to the Interplay Engine also refer to the Archive Engine, unless otherwise noted. Central Configuration Server If a production facility includes more than one Interplay workgroup, you can specify one Interplay Engine as the Central Configuration Server (CCS). The CCS is an Interplay Engine module that stores information that is common to all other Interplay Engines.
Using the Interplay Administrator Using the Interplay Administrator The Interplay Administrator is a client application that you use to manage either the Interplay Engine or the Interplay Archive Engine. The Interplay Administrator is installed at the same time that you install Interplay Access. You can install the Interplay Administrator as a client on any computer in your network and then use it to manage any Interplay Engine or Interplay Archive Engine that is available on the network.
Starting the Interplay Administrator The first time you open the Interplay Administrator, the Server text box is empty. If you have already logged into a server, the text box shows the last server you logged in to. 2. Select the server you want to work with by doing one of the following: t Accept the server that is displayed. t Type the name of the server that you want to log in to. You can also use an IP address. t Click the arrow for the Server list and select the server name from the list.
Using the Interplay | Administrator Window 3. Type a user name and password for an account with administration rights. On the first start after installing the Interplay Engine, only the user Administrator exists. Type “Administrator” in the dialog box. The password is empty by default. Change the password of the Administrator as soon as possible (see “Viewing and Setting Attributes” on page 132). n The Interplay Administrator account is different from the Server Execution User account.
Using the Interplay | Administrator Window Each group contains views for managing components of the Interplay Engine.
Opening an Interplay | Administrator View Opening an Interplay | Administrator View To open an Interplay Administrator view: t In the Interplay Administrator window, click an icon. The view you select replaces the Interplay Administrator window. Each view includes a path that shows the relative location of that view. The following illustration shows part of the Create Database view.
Exiting the Interplay Administrator t Select Documentation Website on Server. The Interplay Production User Information Center page opens. You can open the Help, PDF versions of the Interplay user guides, and other useful links. See “Viewing Help and Documentation on the Interplay Production Portal” on page 13 Exiting the Interplay Administrator When you are finished using the Interplay Administrator, you should log out or close the application.
2 Database Settings The Database settings allow you to create, configure, and manage the Interpla y database.
Creating an Interplay Database n To identify the actual folder, open a Command Prompt window and type net share. If the Interplay Engine server does not have adequate local storage for your Interplay database (for example, if your facility stores a large number of file assets in the Interplay database), you can configure the Interplay Engine to store only the metadata database on the Interplay Engine.
Interplay Databases, Folders, and Files To create an Interplay database: 1. In the Database section of the Interplay Administrator window, click the Create Database icon. The Create Database view opens. 2. In the New Database Information area, leave the default “AvidWG” in the Database Name text box. For an archive database, leave the default “AvidAM.” These are the only two supported database names. 3. Type a description for the database in the Description text box, such as “Main Production Server.” 4.
Interplay Databases, Folders, and Files Database File Structure The database file structure is based on the administrative share that was set during the Interplay Engine installation. By default, this administrative share is named WG_Database$ and is associated with the folder D:\Workgroup_Databases (S:\Workgroup_Databases for cluster systems). The “$” indicates a hidden share. To identify the actual folder, open a Command Prompt window and type net share.
Interplay Databases, Folders, and Files Database Directories and Files Directory or File Directory or File Description _Database The main database directory, which contains database files and the database journal. These files contain the database structure and all metadata. All files within this folder contain binary information and cannot be viewed or edited with a text editor.
Creating and Restoring Database Backups Creating and Restoring Database Backups There are two basic approaches to backing up an Interplay database: • Using a combination of backups scheduled through the Interplay Administrator (automatic backups) and manual backups of other parts of the database. This approach should be used as part of a regular backup strategy. • Using a professional backup tool to do a complete backup to offline media.
Creating and Restoring Database Backups Types of Interplay Administrator Backups The Interplay Administrator lets you run create two different kinds of metadata backups: a Complete metadata backup and a Fast metadata backup. You can schedule backups to run automatically or you can run a backup manually. The following table describes the different types of backups.
Creating and Restoring Database Backups Recommendations for Backup Configuration Automatic backups, as scheduled through the Interplay Administrator, do not back up the entire database, so they are only one component of a complete backup strategy. The following table lists the different types of backups needed to completely back up the Interplay database. For an Interplay archive, substitute AvidAM for AvidWG. Type of Backup Folders or Files Backed Up Fast Metadata Only backup AvidWG\_Database Complete
Creating and Restoring Database Backups It is extremely important to use the automatic backup process available through the Interplay Administrator instead of just a tape backup for backing up the _Database and _PropertyStore folders. Tape backups can be: • Inconsistent: A tape backup of the _Database folder while the server is running can lead to inconsistent backup files because the server might not have applied all the transactions to the database yet.
Creating and Restoring Database Backups Non-cluster systems: The default path is - D:\Workgroup_Databases\AvidWG\_Backup If you are working with a split database, by default the _Backup folder is located with the file repository on the shared-storage workspace, for example: - \\SharedStorageServer\WorkspaceName\AvidWG\_Backup Storing backups on shared storage is an acceptable configuration, either as part of a split database or as a custom location. n Prior to Interplay Engine v1.2.
Creating and Restoring Database Backups c • After a Complete backup, copy the backup folder to offline media to prevent data loss. You can do this as a separate step or as part of a backup of the complete database to offline media (see the next bullet). Use a backup tool (such as Robocopy or 7-Zip) that can handle long path names and does not use excessive bandwidth, to avoid slowing down activity on the Interplay Engine. (See “Using an Archiving Tool for Backup” on page 44).
Creating and Restoring Database Backups Sun Mon Tue Wed Thu Fri Sat Sun 1 2 3 4 5 6 7 8 C F F F F F F C In the same example, the Interplay Engine does not check the number of backups again until it performs a Complete backup on Sunday the 15th. On that day, it deletes the 7 oldest backups, leaving 8. The following illustration shows the 7 oldest backups deleted.
Creating and Restoring Database Backups The Backup History section displays incremental and differential backups up to the last successful complete backup. Administrators can use this as a troubleshooting tool to see if the last backup was successful and if not, which backups have failed. It also can be used to view which incremental and differential backups are required for the most recent full restore. This display does not necessarily match the backups stored in the _Backup folder.
Creating and Restoring Database Backups To schedule database backups: 1. In the Database section of the Interplay Administrator window, click the Schedule Backups icon. The Schedule Backups view opens.
Creating and Restoring Database Backups 2. In the list on the left side of the view, select the database for which you want to view or specify automatic backup settings. The current settings are displayed.
Creating and Restoring Database Backups 3. (Option) In the Backup Information area, change your preferences if necessary. “Backup only if modified” is selected by default to save space and avoid duplicate identical copies. The default number of versions to keep is 10. The Interplay Engine always keeps the last Complete backup and later Fast backups. For more information, see “Recommendations for Backup Configuration” on page 34. 4. (Option) In the Backup Location preference, change the path if desired. a.
Creating and Restoring Database Backups 10. (Option) Change the Backup time by selecting one of the following: t Select Once at and change the hour and minutes (within 10 minute intervals) on which it occurs using the up and down arrows. t Select Every and set the backup to occur at regular intervals starting at midnight. Use the down arrow to select the interval. t Select Custom and specify custom backup times. Use the up and down arrows to select the time, and then click Add.
Creating and Restoring Database Backups The backup is created in the location you specified. If you navigate to the location, and the backup is still being created, the folder name includes the words “backup in progress.” Using an Archiving Tool for Backup In some circumstances, such as performing a system upgrade, you might want to use an archive tool to create a backup copy of the complete database folder (AvidWG or AvidAM) and the user database folder (_InternalData).
Creating and Restoring Database Backups Interplay Engine (Split Database) Folder Name Default Location AvidWG (_Database folder only) D:\Workgroup_Databases\AvidWG AvidWG (all other database folders) \\SharedStorageServer\WorkspaceName\AvidWG _InternalData (user database if engine is a Central Configuration Server) D:\Workgroup_Databases\_InternalData To make a backup copy of the database on a cluster system: 1. Open the Interplay Administration tool. 2.
Creating and Restoring Database Backups Interplay Engine or Interplay Archive Engine Folder Name Default Location _InternalData (user database if engine is a Central Configuration Server) S:\Workgroup_Databases\_InternalData Interplay Engine (Split Database) n Folder Name Default Location AvidWG (_Database folder only) S:\Workgroup_Databases\AvidWG AvidWG (all other database folders) \\SharedStorageServer\WorkspaceName\AvidWG _InternalData (user database if engine is a Central Configuration Ser
Creating and Restoring Database Backups You cannot restore parts of a backup, for example, a specific sequence or folder. You can restore only a Complete backup or a Fast backup. How the Restore Tool Works with Streamed Properties Files Beginning with Interplay Engine v1.2.4, the Interplay backup mechanism consolidates the streamed properties files (all files in the _PropertyStore folder) into large “archive” files. These files are written into the _PropertyStore folder of the corresponding backup folder.
Creating and Restoring Database Backups Restoring a Complete Backup or a Fast Backup To restore a database, you need to restore a Complete backup, a Fast backup, or both, depending on the type of backups available. (see “Types of Interplay Administrator Backups” on page 33 for a description of each type of backup). • A Complete backup contains a _Database folder and a _PropertyStore folder. A Complete backup is needed if the complete database needs to be restored, for example, if a hard disk crashes.
Creating and Restoring Database Backups Distinguishing Between Types of Backups To distinguish between a Fast Metadata Only backup and the other types of backups, open the backup folder and check if a _PropertyStore folder exists. A Fast Metadata Only backup does not contain a _PropertyStore folder.
Creating and Restoring Database Backups Fast Incremental backup type Example of a Complete Restore Process Imagine that you have a backup schedule of a Complete backup on Saturday and a Fast Differential backup every other day of the week. If there is a failure on Friday in which the _Database folder, the _PropertyStore folder, and other Interplay folders are lost or corrupted, you need to perform the following steps: 1.
Creating and Restoring Database Backups Using the InterplayRestore Tool on the Interplay Engine Server To restore a backup, you need to run the InterplayRestore tool in a Command Prompt window. There are two ways to run the tool: n • Without parameters, in which case the tool prompts you for the necessary entries (interactive mode). • With parameters, in which case the tool runs without prompting, depending on the number of parameters included.
Creating and Restoring Database Backups 7. At the next prompt, select the correct backup from the numbered list of available backups. Complete backups are labeled “full” and Fast backups are labeled “increment” “difference,” or “metadataonly.” After you select the backup, press Enter. The restore process begins. For an example of the process, see “Database Restore Session Example” on page 54. At the end of the process, a message informs you that you need to restore the _Master directory manually. 8.
Creating and Restoring Database Backups t For a split database, navigate to the folder that holds InterplayRestore, type the following, and press Enter: InterplayRestore /m /assets /backupdir For example: InterplayRestore /m d:\Workgroup_Databases\AvidWG /assets \\isis\workspace1\AvidWG /backupdir \\isis\workspace1\AvidWG\_Backup InterplayRestore prompts you to choose from a numbered list of available backups and then re
Creating and Restoring Database Backups Database Restore Session Example The following is an example of an interactive session, which begins with the command for starting the InterplayRestore tool. C:\>”C:\Program Files\Avid\Avid Interplay Engine\Server\InterplayRestore” ******************************************************************** InterplayRestore - Restore Interplay databases from backup A non interactive mode is also available. Run "InterplayRestore.
Creating and Restoring Database Backups Assume you choose 1. The tool locks the project so that no one can access the database and then copies the files: Beginning restore from \\isis\workspace1\avidwg\_Backup\AvidWG_2010-06-10_03-05\ This is a Full backup Restoring split database. Metadata restored to d:\Workgroup_Databases\avidwg\. PropertyStore Assets restored to \\isis\workspace1\avidwg Locked project AvidWG Copying files into d:\Workgroup_Databases\avidwg\_Database Copying file AvidWG.dor ...
Creating and Restoring Database Backups For example, the following illustration shows the contents of the 0-1999 subfolder in the active _PropertyStore folder on the Interplay Engine: The following illustration shows the corresponding files as they appear in the archive file \AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertyStore\streamed_prop1.bar: The .bar file is a file that you can only open by using the BackupArchive tool.
Creating and Restoring Database Backups To list all streamed properties files in an archive file: 1. On the Interplay Engine, click Programs and select Accessories > Command Prompt. 2. At the command line, navigate to the folder that contains the BackupArchive tool. For example, type the following and press Enter: cd C:\Program Files\Avid\Avid Interplay Engine\Server 3. Type the following and press Enter: backuparchive /L Do not use the file extension when typing the name of the archive file.
Creating and Restoring Database Backups Restoring Archived Log Files In Interplay version 1.6 and later, the Interplay Engine compresses and archives log files older than 7 days. The log compression process runs during project backup. (This process runs at most once per day, even if multiple backups are scheduled on the same day.) Archive files (with the extensions .bar and .bin) are stored in the same directory as the log files for 30 days and then are automatically deleted.
Creating and Restoring Database Backups [4] 07 February 2013 16:00:00 incremental Choose an entry ( 1 - 4 ): 3 Backup restore chain 0. Test_2013-02-04_16-00 full 1. Test_2013-02-05_16-00 incremental 2. Test_2013-02-06_16-00 incremental 3. Test_2013-02-07_16-00 incremental The InterplayRestore tool gives you an option of selecting a partial restore. If you type “y,” you are asked to select which file in the restore chain from which to start the restore.
Creating and Restoring Database Backups Displaying a Restore Chain You have the option of displaying the restore chain for a selected backup without performing the restore. To display the restore chain, use the /printchain option in a interactive or non-interactive command line, as shown in the following examples: Non-interactive mode: InterplayRestore /metadata F:\Workgroup_Databases\Test /backupdir F:\Workgroup_Databases\Test\_Backup /printchain Interactive mode: InterplayRestore /printchain In either
Creating and Restoring Database Backups Choose a backup to restore from: [1] 04 February 2013 16:39:00 full [2] 04 February 2013 16:42:00 incremental [3] 04 February 2013 16:44:00 incremental [4] 24 February 2013 01:00:00 full Choose an entry ( 1 - 4 ): 3 Backup restore chain 0. Test_2013-02-04_16-39 full 1. Test_2013-02-04_16-42 incremental 2.
Creating and Restoring Database Backups F:\Workgroup_Databases\Test\_PropertyStore\2013-35\1436_StreamedProperty_A AFBinary1073743260-0.prp Verifying that we have all streamed property BAR files... Copying Copying ... Restore Project files into F:\Workgroup_Databases\Test\_Database file Test.jdf operation successful Test is still locked for your restore of _Master. The database is still locked because you need to restore the _Master directory manually, or through your existing tape backup mechanism.
Performing a Consistency Check 4. In the Start Backup dialog box, select Metadata only and click OK. The backup file is created in specified backup location, for example: AvidWG\_Backup\AvidWG_2013-02-12_01-00 To distinguish between a metadata-only backup and the other types of backups, open the backup folder and check if a _PropertyStore folder exists. A metadata-only backup does not contain a _PropertyStore folder. 5.
Viewing Database Information Viewing Database Information Use the Database Information view to display information about an Interplay database. This information includes various statistics and the connected users. To view the information about a database: 1. In the Database section of the Interplay Administrator window, click the Database Information icon. The Database Information view opens. This might take a minute or two, depending on how long the engine has been running.
Viewing Database Information - Root folder for database (Meta Data): See “Creating an Interplay Database” on page 27. - Root folder for data (Assets): See “Creating an Interplay Database” on page 27. 2. Click one of the following tabs: - Database Statistics - Deletion Statistics - Command Statistics - Object Statistics - Connected User Information For information about these tabs, see “Database Information Tabs” on page 65.
Viewing Database Information Statistics in this tab refer to assets that were sent to the Orphan Clips folder as a result of a scheduled deletion. Statistics are shown for the following parameters: • - Processed Assets: The number of assets in the Orphan Clips folder that the Interplay Engine processed during the deletion. This process includes examining whether the assets should be deleted or moved to another folder. This number is usually higher than other similar statistics.
Viewing Database Information Statistics are shown for the following parameters: • Period: The ten most recent measurement periods are listed in the Period column. Periods are a maximum of one minute and are created only if there are search commands executed. You cannot check statistics for earlier periods. • Duration: The length of the measurement period, from the finish of the first search until the finish of the last search in this period.
Locking and Unlocking Databases Locking and Unlocking Databases Use the Lock/Unlock Databases view to prevent users from connecting to the database. You might need to lock the database if you are upgrading the database or using a archive tool to create a backup of the database. By default, the database is unlocked. To lock a database: 1. In the Database section of the Interplay Administrator window, click the Lock/Unlock Database icon. The Lock/Unlock database view opens. 2.
Managing Databases: Deactivating, Activating, and Migrating To unlock a database: 1. Select the database in the Locked Databases list. 2. Click Unlock Database. The database is displayed in Unlocked Databases. Managing Databases: Deactivating, Activating, and Migrating Use the Managing Databases view to remove a database from the list of active databases (deactivate) or to restore it to the list (activate).
Managing Databases: Deactivating, Activating, and Migrating 2. Select the database name in the Databases list. 3. Click Deactivate. The database name is removed from the Databases list. Activating a Deactivated Database If a specific database is not listed in the Databases view, it means that it is unknown to the Interplay Engine and users cannot connect to it. If the database exists but is not listed, it is probably deactivated. You activate a database by navigating to the database .pro file (AvidWG.
Managing Databases: Deactivating, Activating, and Migrating 2. Do one of the following: t In the “Database (.pro) file to activate” text box, type the full UNC path to the .pro file. For example: \\IEServer\WG_Database$\AvidWG\AvidWG.pro t Click the Browse button, log in if prompted, navigate to the .pro file using a network, select the file, and click Open. The following illustration shows the path to AvidWG.pro, using the Microsoft Windows smb network and the administrative share WG_Database$.
Managing Databases: Deactivating, Activating, and Migrating The .pro file is displayed in the Activate Database dialog box.
Managing Databases: Deactivating, Activating, and Migrating 3. Make sure the option “Load Database on Activation” is selected. Deselect this option only if directed by Avid support. 4. Click Activate. The database is activated and loaded. The database name is displayed in the Databases list and users can connect to the database. If the option “Load Database on Activation” is selected, the database is automatically unlocked.
Managing Databases: Deactivating, Activating, and Migrating To migrate a database to a new CCS: 1. In the Database section of the Interplay Administrator window, click the Manage Databases icon. The Manage Databases view opens. 2. In the Manage Databases view, click the name of the database that needs migration. The State reads “Database Requires Migration.” A warning explains the consequences of a database migration. 3. Click Migrate Database. After the migration, the State reads “OK.
Moving a Database to Another Server (Non-Clustered Systems) Moving a Database to Another Server (Non-Clustered Systems) Under special circumstances, you might need to move a database to a different server. The following procedure refers to Interplay Engine servers that are not configured as failover clusters. For clustered systems, see “Moving a Database to Another Server (Clustered Systems)” on page 79.
Moving a Database to Another Server (Non-Clustered Systems) 6. Pack the database folder into a zip file or use Robocopy from the Microsoft Windows Resource Kit for path names longer than 256 characters. To save time and storage, you do not need to copy all the backups in the D:\Workgroup_Databases\AvidWG\_Backup folder. One complete backup and the most recent Fast backup are sufficient. If you are moving a split database, create two zip files, one for D:\Workgroup_Databases\AvidWG and the other for \\serve
Moving a Database and Users to Another Server (Non-Clustered Systems) Moving a Database and Users to Another Server (Non-Clustered Systems) Under special circumstances, you might need to move a database and users to a different server. The following procedure refers to Interplay Engine servers that are not configured as failover clusters. For cluster systems, see “Moving a Database and Users to Another Server (Clustered Systems)” on page 81.
Moving a Database and Users to Another Server (Non-Clustered Systems) 7. Pack the database folder into a zip file or use Robocopy from the Microsoft Windows Resource Kit for path names longer than 256 characters. To save time and storage, you do not need to copy all the backups in the D:\Workgroup_Databases\AvidWG\_Backup folder. One complete backup and the most recent Fast backup are sufficient. If you are moving a split database, create two zip files, one for D:\Workgroup_Databases\AvidWG and the other f
Moving a Database to Another Server (Clustered Systems) If necessary, remove the old database from Interplay Access by right-clicking the database name and then clicking Remove Databases. 20. (Option) On the source server, rename the original database folder to avoid unwanted future access. Moving a Database to Another Server (Clustered Systems) Under special circumstances, you might need to move a database to a different server.
Moving a Database to Another Server (Clustered Systems) 4. Make sure the database is unloaded by using the Cluster Administrator on one of the cluster nodes: c a. Select Programs > Administrative Tools > Cluster Administrator. b. Open the Avid Workgroup Server resource group. c. In the list of resources, select Avid Workgroup Engine Monitor and change the state to “Offline.
Moving a Database and Users to Another Server (Clustered Systems) If you are copying a split database, copy and unzip both zipped files to the correct locations. Then edit the FolderLocations.xml file to show the correct paths. See “Splitting a Database for Existing Interplay Installations” on page 243. 11. Activate the database by using the Manage Databases view (see “Activating a Deactivated Database” on page 70). 12.
Moving a Database and Users to Another Server (Clustered Systems) To move a database and users to another server (clustered systems): 1. Install the Interplay Engine on a new server (the target server). Make sure the configuration is the same on both systems. For example, if you are moving an AvidWG database, create an AvidWG database on the new server.
Moving a Database and Users to Another Server (Clustered Systems) If you are moving a split database, create two zip files, one for S:\Workgroup_Databases\AvidWG and the other for \\server_name\\workspace_name\\AvidWG. 8. Locate the user folder _InternalData on the source server. The default path is S:\Workgroup_Databases\_InternalData. 9. Copy the zipped file and the _InternalData folder to a network server, removable media, laptop, or directly to the target server. 10.
Moving a Database Under Low Disk Space Conditions Moving a Database Under Low Disk Space Conditions If disk space on the server is critically low, the Interplay Engine refuses client connections and displays an error message.
Running Database Maintenance Tools c Before beginning this procedure, be sure to make a backup of the database. See “Creating and Restoring Database Backups” on page 32 for information on running a backup. Temporarily change the Backup time field to “Once at” and enter or select from the list the time in the future closest to the current time. To rename a database: 1. In the Database section of the Interplay Administrator window, click the Manage Databases icon. The Manage Databases view opens. 2.
Running Database Maintenance Tools Link inconsistencies are not visible. They are obsolete or invalid entries in internal database tables. A high number might cause slowdowns for certain operations. • Cleanup Invalid Dependencies: Use this tool to detect and remove dependency inconsistencies. Dependency inconsistencies are not visible. They are obsolete or invalid entries in internal database tables. A high number might cause slowdowns for certain operations.
Running Database Maintenance Tools When to run these tools: You can run any of these tools as part of a troubleshooting procedure, as recommended by an Avid representative. You can also run them for maintenance during regular maintenance windows. However, they are not designed to be run on a daily basis, because they require Exclusive Access to the database (see below). One approach to using the tools for maintenance is to run them in the first convenient maintenance window.
Running Database Maintenance Tools To run a database maintenance tool: 1. In the Database section of the Interplay Administrator window, click the Maintenance icon. The Maintenance view opens. 2. In the left column of the view, select the database on which you want to run the tool. 3. Double-click the icon for the tool you want to use. 4. Select options for the tool as described in the following table: Tool Options Verify Link Consistency • Fix broken links.
Running Database Maintenance Tools Tool Options Validate User Tree (Interplay Engine v2.6 or later) • Fix Invalid Users. Select this option to repair certain inconsistencies in the user structure. If you do not select this option, the tool reports problems but does not take action to fix them. Validate AssignedRoles Table • Verbose Output. Select this option to display user names. • Remove Invalid Entries. Select this option to remove invalid entries from the AssignedRoles table.
Running Database Maintenance Tools 5. Click Run. A dialog box asks if you want to set Exclusive Access to the database. 6. Click Yes. The tool runs with the options you selected. While the tool is running, information about the progress and found issues is displayed. When the tool is finished the following options are displayed: - Open Log in editor: Opens the displayed information in Notepad or another default text editor.
3 Server Settings The Server settings enable you to configure and change server settings and shutdown and restart the server. The following topics describe how to use these settings: • Changing the Database and Data Locations • Viewing Server Information • Locking and Unlocking the Server • Restarting the Server • Managing Licenses • Configuring Third-Party Storage Changing the Database and Data Locations The Server Settings view lets you change the default locations for a new database.
Viewing Server Information To change the root folders for a new database: 1. In the Server section of the Interplay Administrator window, click the Server Settings icon. The Server Settings view opens. 2. For the root folder of the database (metadata), keep the folder that was set during the installation of the server (the default is \\IEServer\WG_Database$\). 3.
Viewing Server Information • The number of databases on the server The Connected User Information area displays information about the following: - Which database users are connected to - Which user is connected to which database - Which machine the user is connected from - What time a user has been connected since - The license class used The license class is different from the license type. The license class is an internal key that is used by the Interplay Engine.
Locking and Unlocking the Server Locking and Unlocking the Server The Lock Server view allows the administrator to lock the Interplay Engine server for a specific period of time. Locking the server is useful when carrying out tasks such as: n • Server maintenance or upgrading the server software. • Maintaining or rebooting the Avid shared-storage server. Whenever a database or data location is unavailable, you should lock the database or the server.
Locking and Unlocking the Server The Lock Server view provides two different means of locking the Interplay Engine server: Lock Server and Exclusive Access. • If Lock Server is activated, the Interplay Engine server is locked and all the clients that are connected to it are disconnected. • If Exclusive Access is activated, the server process continues to run and the database can be used.
Locking and Unlocking the Server To lock the server and prevent any user access: 1. In the Server section of the Interplay Administrator window, click the Lock Server icon. The Lock Server view opens. 2. In the Lock Server section, select one of the following for the locking duration: - Indefinitely: An indefinite shutdown. This is a good choice when shutting down the server to carry out any vital maintenance, for example replacing hard drives, or making the first backup of a new database.
Locking and Unlocking the Server - Lock until: Allows you to stipulate when to restart the server (longer time frame). Specify the time period by clicking the Up and Down arrows. 3. In the “Lock comment” text box, type a comment as to why you are locking the server. This comment is displayed when an Interplay Administrator tries to log into the Interplay Engine. 4. Click Lock Server. The Lock Server view changes to display lock information.
Restarting the Server You can return to the Interplay Administrator window by clicking the Menu button, log out of the Interplay Administrator tool and then log in again, and perform other database tasks. To manually unlock the server after activating Exclusive Access, do one of the following: t t Log in to the Interplay Administrator from the host where you acquired Exclusive Access or on the Engine host itself, click the Lock Server icon, then click Release Exclusive Access.
Managing Licenses Managing Licenses Interplay needs valid licenses in order to function. Licenses are delivered to the customer in a license file, which the administrator imports through the Licenses view.
Managing Licenses Installing Permanent Licenses If you are installing the Interplay Engine on a new system, temporary licenses are activated automatically so that you can administer and install the system. There is no time limit for these licenses. If you are performing an upgrade, the currently installed licenses are used. A set of permanent licenses is provided by Avid in the form of a file (with the extension .nxn) on a USB flash drive or another delivery mechanism.
Managing Licenses Displaying the Licenses View To view information about your licenses: t In the Server section of the Interplay Administrator window, click the Licenses icon. The Licenses view opens. The Licenses view has four sections: - The License Types section displays information about the following: - Your current license types (see “License Types and Usage” on page 102). - Number of license types available. - Number of license types used.
Managing Licenses - - n Days Remaining: The number of days until expiration of a time-limited license. Interplay licenses are usually not time limited, so in most cases the value for a license type is “0.” Only one value for the days remaining is stored for each license type. The Server Information section displays information about the following: - Customer ID. The customer name or ID number. - Hardware ID, which matches the physical application key (dongle).
Managing Licenses Customers can also buy two types of server licenses: n • Interplay Archive Engine • Interplay Streaming Server There is no license required for the Interplay Engine. Current License Types The following table describes the license types used for Interplay Production v2.7.0.2 and later, how they are displayed in the Interplay Administrator Licenses view, and which applications they license.
Managing Licenses How Licenses Are Shared A client workstation, through its IP address, can use a single license to run more than one Avid client application concurrently. For example, a user can run both Media Composer and Interplay Access while using a single Interplay Central license (Base or Advance). The Interplay Engine manages access through the hostname of the workstation. The license is not released from the client workstation until all applications that require a license are closed.
Managing Licenses License Types Previously Used for Interplay Production Applications Prior to Interplay version 2.7, customers purchased licenses for individual products. The following table lists how these legacy licenses relate to current license types, how they are displayed in the Interplay Administrator Licenses view, and which applications they license.
Managing Licenses Legacy license types Current license types Current license types and legacy license types 106
Managing Licenses If a facility is using a mix of legacy licenses and current licenses, the Interplay Engine first looks for an appropriate legacy license. If none are available, it looks for an appropriate current license. For example: 1. An Assist client logs on. The Interplay Engine looks for an Assist license (KEY-XL) 2. If it does not find one available, it looks for a Base license (KEY-J). 3.
Configuring Third-Party Storage 3. Locate the registry key for the original dongle, found here: HKEY_LOCAL_MACHINE\SOFTWARE\Avid Technology\Workgroup\Avid Workgroup Server\FeatureKeys\Permanent 4. Delete the Permanent folder. 5. Close the Registry Editor window. 6. Reload the new registration file as described in “Installing Permanent Licenses” on page 100.
4 User Management An administrator controls access to Interplay through user accounts and user roles.
Understanding the Central Configuration Server Depending on the number of Interplay Engines that are installed, several CCS configurations are possible: c • One Interplay Engine: Configure this server as the CCS. • Several Interplay Engines: Usually you configure only one Interplay Engine as the CCS. The use of more than one CCS in a company might be useful if there are several independent domains, departments, or sites where there is no need to share users or other settings in Interplay.
Understanding the Central Configuration Server The following procedure is based on these assumptions: c • Server A is the CCS. • You want to keep the CCS settings and user information that exist on server A, but move them to server B. • You do not want to keep the original CCS information that exists server B. Server B should be created by a clean installation and should serve as its own CCS.
Understanding the Central Configuration Server Viewing and Changing the CCS for a Server c Before beginning the following procedure, be sure to make a backup of the database. See “Creating and Restoring Database Backups” on page 32 for information on running a backup. You can use the Start Backup Now feature to start a backup immediately. The following procedure is based on these assumptions: • Server A is the CCS. • You want server B to be the CCS for server A.
Understanding the Central Configuration Server 6. Do one of the following: t To keep the original CCS, click Cancel. t To change to a new CCS, click Change CCS. 7. If you have not moved the original CCS server (see “Moving the CCS to Another Server” on page 110), you need to migrate the database to the new CCS and all of your CCS-related data (such as users and local administration) are lost. Unmigrated databases should not be used; databases should always be migrated to a CCS.
Adding Users to a Central Configuration Server Adding Users to a Central Configuration Server There are several ways to add users to a Central Configuration Server: • Automatically adding Avid Unity (shared-storage) users. These users are added to the CCS the first time they log in. They log in using their Avid Unity username and password. For more information, see “Setting Avid ISIS Authentication” on page 116. • Importing users from a Windows domain or LDAP directory.
Setting User Authentication Providers and Importing Users n All special characters are allowed in user names except for \ (backslash), / (forward slash), | (vertical bar), and quotes (" and '). When LDAP and Windows Domain users are imported, these characters are replaced with “_”. If two users have different user names that are mapped to the same converted name (for example, dann/o and dann\o become dann_o), only one converted user name is imported.
Setting User Authentication Providers and Importing Users The users are added to the Imported Users folder in the User Management page, under the respective subfolder for LDAP, Microsoft, or Avid Unity. Users are also added to the Everyone folder. The following illustration shows these subfolders with the LDAP folder selected.
Setting User Authentication Providers and Importing Users This method of authorization is implicit. In other words, there is no active import of users at the time the Avid ISIS Authentication is enabled. Instead, the first time that an Avid ISIS user logs in to Interplay, the user is added to the UNITY user group subfolder. By default, this user group has Read rights. If your workgroup includes multiple ISIS systems, you need to specify each additional ISIS server name.
Setting User Authentication Providers and Importing Users Setting Windows Domain Authentication and Importing Users If you activate Windows Domain authentication, a user is able to log in to an Interplay database with a Windows domain user name and password. Any time a user tries to access an Interplay database, the CCS (Central Configuration Server) can use the Windows login information to authenticate the user and in turn to check which databases the user can access.
Setting User Authentication Providers and Importing Users To enable Windows domain authentication: 1. In the User Management section of the Interplay Administrator window, click the User Authentication Providers icon. The User Authentication Providers view opens. 2. Select the Windows Domain Authentication option. 3. Click Import Windows Domain Users. The Import User Groups dialog box opens. 4. Do one of the following: t Select the user groups you want to import into the Interplay system.
Setting User Authentication Providers and Importing Users Setting LDAP Authentication and Importing Users If you select the LDAP Authentication option, a user can log in to Interplay databases with an LDAP user name and password. Interplay supports LDAP Version 2 and LDAP Version 3. To properly configure LDAP authentication, you must know the schema of the LDAP database.
Setting User Authentication Providers and Importing Users If an Active Directory is made up of multiple OUs (organizational units) in multiple domains, you can select a specific OU for user authentication. See “Authentication from an Active Directory that Includes Multiple Domains” on page 125. To import LDAP users and enable LDAP authentication: 1. In the User Management section of the Interplay Administrator window, click the User Authentication Providers icon.
Setting User Authentication Providers and Importing Users LDAP Server Configuration Settings The following table describes the LDAP server settings that are needed for authentication and import. Setting Description LDAP Server IP address of the LDAP server. LDAP Port Port for the LDAP service. For Standard LDAP, accept the default port 389. For Active Directory Global Catalog LDAP, specify port 3268.
Setting User Authentication Providers and Importing Users Setting Description User Name Attribute Attribute that stores the user name to use for LDAP-authenticated logins. The content of this attribute becomes the imported user name in Interplay and defines the user name for LDAP-authenticated login attempts. This attribute might vary according to the LDAP schema, and there might be multiple attributes storing different varieties of the user name.
Setting User Authentication Providers and Importing Users The following illustration shows an example of settings for an Active Directory LDAP implementation. The following illustration shows an example of settings for an OpenLDAP implementation.
Setting User Authentication Providers and Importing Users Authentication from an Active Directory that Includes Multiple Domains An organization might have an Active Directory that includes several domains.
Setting User Authentication Providers and Importing Users LDAP Authentication from a Single OU A domain might have more than one OU. The following illustration shows three user OUs for test1.test.avid.com. In the LDAP Authentication Settings, you would specify the specific OU as the Search Root DN, and then specify a User DN Suffix to authenticate users in that OU. In this example, the Search Root DN is set for the OU test\userou1 in the domain test1.test.avid.com.
Setting User Authentication Providers and Importing Users Combined LDAP Authentication and Windows Domain Authentication If you want to import and authenticate users from two domains, you can combine LDAP authentication as described in the previous sections (either for a single domain or for a single OU) with Windows Domain authentication for a second domain. For information on Windows Domain authentication, see “Setting Windows Domain Authentication and Importing Users” on page 118.
Managing Users, User Groups, and User Rights Managing Users, User Groups, and User Rights The User Management view lets you create, modify, manage and delete users and user groups. It also lets you define user roles and authentication protocols. If you are working in an environment that includes more than one Interplay Engine, you should manage users through a CCS (see “Understanding the Central Configuration Server” on page 109).
Managing Users, User Groups, and User Rights The following illustration shows the User Management view with the Administrators group selected. In this example, there are three custom user groups: Assistants, Editors, and Graphic Artists.
Managing Users, User Groups, and User Rights Understanding Default User Groups, Users, and Roles The User Management view displays all user groups and users. The user groups created during the server installation are as follows: • Administrators, with the user Administrator: Users with administrator rights. When you first log in after the first installation, if you have not yet imported Windows Domain or LDAP server users, the only user displayed is the user “Administrator” with administrator rights.
Managing Users, User Groups, and User Rights also have a group of assistants that should have Read/Write privileges. In this case you can set up two user groups that have different sets of privileges: one named Editors, and one named Assistants. To create a user group: 1. In the User Management section of the Interplay Administrator window, click the User Management icon. The User Management view opens. 2. In the Users pane, select the group into which you want to add a the new user group.
Managing Users, User Groups, and User Rights 4. Add attributes for the new user: name, description (inherited from the user group by default), password, password confirmation, and email. All special characters are allowed in user and group names except “\”, “/”, “|” and quotes (" and '). For more information, see “Viewing and Setting Attributes” on page 132. 5. (Option) Select a role for the new user. Roles are inherited from the group in which you create the user.
Managing Users, User Groups, and User Rights To set the internal password: 1. In the Users list, select a user. 2. Type the password and the confirmation in the text box. 3. Click Apply. The user can change his or her password anytime in the login dialog box. c If you select the Internal Authentication option and do not set a password, anyone can log in with that user name and no password.
Managing Users, User Groups, and User Rights Viewing and Changing Roles By default, all users in a group inherit the role assigned to the group. You cannot assign rights to specific users in the User Management view. If you want to change a user’s rights, you can move the user to a different group. For more information about setting up roles correctly, see “Managing Database Roles” on page 138.
Managing Users, User Groups, and User Rights To navigate to the Users tree from the Part of Group(s) pane: 1. Select the user group in the Part of Group(s) pane. 2. For any user group other than the Users group, right-click and select one of the following: t Select “Go To” to switch the focus of the Users tree to the group you selected. t Select “Go to user in this group” to switch the focus of the Users tree to the selected user in the selected user group.
Managing Users, User Groups, and User Rights To change the role for a user, do one of the following: t Right-click the user and select Cut, select the group, right-click the group and select Paste. This action moves the user from one group to another. You can also drag the user from one group to another. t Right-click the user and select Copy, select the group, right-click the group and select Paste. This action removes the user from one group and adds it to another.
Managing Users, User Groups, and User Rights To change or add an authentication provider: 1. In the Users list of the User Management view, select the user. 2. In the Authentication Providers pane of the User Management view, select the appropriate options. 3. Click Apply to make the change, or Revert to discard your changes. Deleting Users and User Groups You can delete any user except Administrator and you can delete any user group except Administrators, Migrated Users, and Everyone.
Managing Database Roles Removing Users from User Groups You can remove any user except Administrator from any user group except the Everyone group. Removing a user does not delete the user from other groups. To remove a user from a user group: 1. Select the user in the group from which you want it removed. 2. Do one of the following: t Press the Delete key. t Click the Remove User button.
Managing Database Roles 2. Select the General Role Assignment option. General Role Assignment option 3. In the Database pane, select the database or a folder for which you want to view roles.
Managing Database Roles If the database icon has a red X, you are not connected. Click the database icon to connect. The database icon shows a green check mark when you are connected. The following table describes three different states of the database icon. Icon Meaning (Green circle with check mark) Database you are connected to. (Red box with X) Database you are not connected to. (Red box with X and yellow arrow) Database needs migration. See “Migrating a Database” on page 73. 4.
Managing Database Roles Setting or Changing a General Role Assignment Use the Manage Database Roles view to set or change rights to a particular folder. Note the following: • To delete items, the user must have deletion rights for the folder, even if the user is the owner of the item to be deleted. • To move items, the user must have write rights on the object, the folder the object is being moved out of, and the target folder.
Managing Database Roles for Orphan Clips. Administrators have full access to all folders. For more information about the Unchecked-in Avid Assets folder and the Orphan Clips folder, see the Interplay Access User’s Guide. To set or change a role for users of the database or a folder: 1. In the User Management section of the Interplay Administrator window, click the Manage Database Roles icon. The Manage Database Roles view opens. 2. Select the General Role Assignment option. 3.
Managing Database Roles 6. Click Set Role. The role appears in the lower panel. To change a role: t Select the entry in the lower pane, right-click, and select Set Role > role name. To remove a role for users of the database or a folder: 1. Select the database or a folder in the Database column. 2. Select an entry in the list in the lower pane. 3. Do one of the following: t Click the Remove Role button. t Right-click and select Remove Role.
Managing Database Roles Blocking Access by a Group or User When you are trying to block access by a whole group, it is not sufficient to change the user rights for the user group to NoAccess; individual users who have rights assigned to them specifically or through memberships in other user groups could still log in. To block members of an entire group: 1. In the Manage Database Roles view, in the Database pane, select the project from which you want to block users. 2.
Managing Database Roles 3. Click the Apply button for the option “Mark as Special Access Folder: Grant path access and allow to view path.” This option allows users to log in to the database and navigate to the specified location. The tree structure above the folder will be visible, but not the contents of the other folders in the structure. The first option makes the contents of the tree structure accessible as well (not recommended).
Managing Database Roles The following illustration shows that the user jeditor has special access to the folder /Outside Productions/Graphics. To view what specific role jeditor has, select the folder in the Database pane. Special Access Folder User who can access Special Access Folders To remove a role assigned for Special Access folders: 1. Click the Special Access Folders option. 2. Select the appropriate folder. 3. Select the user in the list in the lower pane. 4.
Guidelines for User Management Guidelines for User Management This topic provides information and suggestions that can help you manage users and access. For more information about managing user roles, with specific examples, see “Setting Up a Folder Structure and a User Database” in Interplay Best Practices.
Guidelines for User Management 3. If there are no inherited permissions, the server checks the global user rights. In this case, the server determines what role the user has from the CCS settings. 4. In case of a conflict where the evaluation sees a user with multiple roles, for example: - the user has the read role through one group - the user has the read/write role through another group then the highest ranking role wins. In this case, the user gets the read/write role.
5 Site Settings Site settings include configuration options for various Interplay components.
Defining Property Layouts These properties are sometimes referred to as system metadata. However, it is only part of the metadata included in an Interplay database. For a description of available properties, see “System Metadata Properties” on page 294. For Interplay Access, administrators select which properties are displayed by default in the Content tab and Object Inspector Property tabs. Users can then add other available properties to these tabs.
Defining Property Layouts To set the properties displayed in Interplay Access: 1. In the Site Settings section of the Interplay Administrator window, click the Property Layout icon. The Property Layout view opens. 2. Select the database for which you want to set properties. 3. Click the System Properties tab. 4.
Setting the Resolutions Available for Display This option determines which set of properties is displayed in the client applications. 5. Select and deselect properties as follows: n t (Option) To make a property available for users to add into displays on their own, and to use in an Extended Search in Interplay Access, select the property in the Available column. To make a property unavailable, deselect it.
Setting the Resolutions Available for Display In some circumstances you might want to make additional resolutions available for display. For example, if you are using Interplay Access to view the status of assets on remote workgroups, and the database for the local workgroup does not include resolutions used on the remote workgroup, you can select those resolutions for display in the local version of Interplay Access. By default, the option “Enable used resolutions automatically” is selected.
Creating Custom Properties Resolution in local database: grayed-out check box, name in bold face Resolution not in local database: grayed-out check box, name not n bold face 5. To remove a resolution, deselect its check box in the Available column. If you want to remove a default resolution, deselect “Enable used resolutions automatically” and then deselect the resolution’s checkbox. Keep in mind that any new resolutions added to the database will not be automatically selected as available for display.
Creating Custom Properties By default, the user needs to type the value for a custom property. Administrators can import an XML file that creates a list of values from which the user can select a value.
Creating Custom Properties When the Available column is selected, the custom property is available for users to add into the application displays, and to use in an Extended search. If the user performs an All Custom search, only the available custom properties are used in the search. n Deselect the property in the Available column to turn off custom properties that you do not want displayed in the properties lists. You cannot delete custom properties for this release but you can turn off their display.
Creating Custom Properties 8. Click Apply to save the added custom property and new layout. 9. (Option) If you want to prevent a user or group from supplying a value for a custom property, change the role in the User Management view (see “Setting Access Control for Custom Properties” on page 158). The next time a user starts Interplay Access and logs in, the new custom property is displayed.
Creating Custom Properties To select a value, click an item in the list, then click Apply. In this example, a user associated the value Team A to the folder. Users can add a custom property as a column in Interplay Assist, Avid Instinct, and the Interplay Window. Setting Access Control for Custom Properties You can control which users can supply a value for a custom property. This setting applies to both typing a value and selecting one from a list. By default, users are allowed to supply a value.
Creating Custom Properties Users pane Additional Roles pane Edit button 2. In the Users pane, select a group or user. 3. In the Additional Roles pane, select an option for “Can modify properties in Access”: - Inherited: Allows the selected user or group to inherit the role of the parent group - Yes: Allows users to type a value or to select from a menu. - No: Prevents users from typing or selecting from a menu. Users can see the property and its text box, but cannot supply a value for it.
Creating Custom Properties Working with Lists for Custom Properties You can create a custom property that includes a list of values from which users can choose (see “Creating Custom Properties” on page 154). These lists are sometimes referred to as dictionaries or taxonomies.
Creating Custom Properties The following example shows an XML file that creates a two-level hierarchy, with “League 1 Team A” as the default value.
Creating Custom Properties n A custom property with a list of values is blank until you select a value. After you select a value, you cannot return the field to a blank state. If appropriate for your custom property, you can include a value in the list called “No Value” or something similar. To clear a value and completely remove a list, see “Removing a List for a Custom Property” on page 162. To create an XML file of values for a custom property: 1.
Creating Custom Properties To remove a list of values for a custom property: 1. Use a text editor or XML editor to create a file that matches the following format. Use quotation marks as shown: 2. Save the file. 3. In the Custom Meta Data tab, select the custom property and import the file, as described in “Adding a Custom Property” on page 155.
Configuring Remote Workgroups Configuring Remote Workgroups A large site can include more than one workgroup. When a workflow requires searching across remote workgroups or performing workgroup-to-workgroup transfers through Interplay Access, you must set up the local workgroup so that a user can access a remote workgroup. You set up this access in the Configure Remote Workgroups view. You can add an Interplay Archive Engine as a remote workgroup.
Configuring Remote Workgroups 4. Select a database from the Available Databases list. 5. In the New server pane, add information about the remote workgroup you want to access. a. b. Select the Host Type: - Interplay Server/Remote Search—to add access to a remote Interplay workgroup - TransferManager—to add access to a Workgroup 4 TransferManager - MediaManager—to add access to a Workgroup 4 workgroup or Nearchive™ system - Interplay Server / 3d Party Search—to add access for a third-party plug-in.
Configuring Categories c. Click Add. The Server name and other information about the remote workgroup appears in the list of accessible remote servers. To remove a remote workgroup from the accessible list: 1. Click the name of the remote workgroup in the list. 2. Click Remove. Configuring Categories Categories provide a grouping mechanism for the data that is stored in the database. Categories are displayed in Interplay Access, Interplay Assist, and Avid Instinct.
Configuring Categories 2. Select a database from the Available Databases list. 3. In the New Categories text box, type one name for a category, or type a comma-separated list (commas and spaces are automatically removed). 4. Click Add, and then click Apply. After refreshing Interplay Access, the categories you specified are visible in the Categories pane. When performing a search, you can use a Category name to locate items that belong to that category.
Configuring Categories Removing Categories Removing a category only removes it from the Configured Categories list in the Interplay Administrator. Objects in the database that have this category keep it, even if it is not listed anymore. If an item was assigned to a category but you removed that category in the Interplay Administrator, users are informed that the category is not valid anymore in the Interplay Access Categories tab. To remove a category: 1.
Setting Server Hostnames and the Workgroup Name Setting Server Hostnames and the Workgroup Name The Server Hostname Settings view lets you set the information described in the following table. Group Setting Description Interplay Media Services Settings Interplay Media Services Engine Enter the name of the Interplay Media Services Engine so that you can run the Interplay Media Services view (see “Interplay Media Services View” on page 174) or use any Interplay Media Services.
Setting Server Hostnames and the Workgroup Name Group Setting Description Media Indexer AMA Shared-Storage Location Enter the name of the shared-storage location in which Media Indexer looks for AMA .spaff files. Enter the name as a full UNC path. This must be the same location that you identified for the .spaaf files in the Media Indexer web interface. For more information, see “Using AMA Material in Interplay” in the Interplay Best Practices Guide.
Setting Server Hostnames and the Workgroup Name Group Setting Description Server MI Connection URL Click the Add button to add one or more Media Indexer servers. The following applications use this setting to locate the Media Indexer servers: • Avid editing applications • Media Services Transcode provider • STP Encode • Interplay Transfer engine • Interplay Access • Avid Instinct n Interplay Access uses the Workgroup Name option.
Setting Server Hostnames and the Workgroup Name 2. Supply the information described in the above table. 3. Where appropriate, click Apply Changes. Configuring the Interplay Streaming Server After you install the Interplay Streaming Server software, you need to enter the name of the computer on which you installed the software. For installation information, see Interplay Software Installation and Configuration. c After installation, exclude the folder C:\Program Files (x86)\Avid\Avid Interplay Streaming
Setting Server Hostnames and the Workgroup Name You can add one or more additional Interplay Streaming Servers to a workgroup. See Interplay Software Installation and Configuration. n In Interplay v2.4, the Interplay Streaming Server was re-engineered to directly play MPEG-4/H.263 and H.264 video media and MPEG1 layer 2 audio media. There is no longer any need to use the Publishing service or Workflow Engine to create QuickTime reference movies for streaming play.
Interplay Media Services View To rename an Interplay Streaming Server: 1. In the Stream Server Settings area, click the Rename button. The Rename Stream Server and Share dialog box opens. 2. Type the computer name of the system that is now running the Interplay Streaming Server. You do not have to type \\ before the name of the server. 3. Click OK. The computer name is displayed in the Server Hostname Settings view. To delete an Interplay Streaming Server: 1.
Interplay Transfer Status View Before you can use the Interplay Media Services view, the Interplay Media Services Engine for the workgroup must be configured in the Server Hostname Settings view. For details, see “Setting Server Hostnames and the Workgroup Name” on page 169. Also, the Interplay Media Services Engine must be running. If the Interplay Media Services connection to the Interplay Media Services Engine fails, the login panel is displayed to let you manually attempt to login again.
Specifying Remote Servers for Asset Tracking n Users with Administration rights can change the configuration to another destination in the Send to Workgroup dialog box in Interplay Access. For procedures that explain the Workgroup Transfer Presets view, see the Interplay Transfer Setup and User's Guide. Specifying Remote Servers for Asset Tracking If your facility includes more than one workgroup, you can use Interplay Access to display information for assets that are shared by different workgroups.
Specifying Remote Servers for Asset Tracking 2. If you want to track assets in a non-archive server, in the Online server name text box, type the computer name of the Interplay Engine server and click Add. The server name is added to the list of configured hosts. 3. If you want to track assets on an archive server, in the Archive Server name text box, type the computer name of the Interplay Archive Engine. 4. Click Apply Changes.
Specifying Archive Settings Specifying Archive Settings The Asset Tracking/Archive Settings view lets you select options for how the Interplay Engine operates with the Interplay Archive Engine and the Archive Provider. The view displays different settings, depending on where you are logged in. If you are logged into an Interplay Archive Engine, the settings include: • Allow duplicate media files ) - • This option lets you choose whether the Archive Provider archives duplicate versions of the media.
Specifying Archive Settings To change whether archive operations create duplicate media: 1. Open the Interplay Administrator and log into the system running the Archive Engine. 2. In the Site Settings section of the Interplay Administrator window, click the Asset Tracking/Archive Settings icon. The Asset Tracking/Archive Settings view opens. 3. Select the Archive database AvidAM from the database list. The system displays the Asset Tracking/Archive Settings window for the Interplay Archive Engine. 4.
Specifying Archive Settings Adding AAF Metadata to an Archive The Asset Tracking/Archive Settings view on the Interplay Archive Engine includes an option labeled “Allow Metadata Archive.” If you select Yes, AAF metadata for Avid assets is sent to the tape archive along with the media. This option requires special implementation by the tape archive vendor. If you select No, only media is sent to tape (the default). This option is supported for the SGL FlashNet™ solution.
Setting the Ownership for New Database Folders t c Use best effort restore - if you select this option, a restore process restores as many files as it can without returning errors. This option requires special implementation by supported third-party vendors to ignore any missing files that are no longer in the archive storage. If you do not select this option, then the restore process fails when there are any missing files (the default).
Setting the Ownership for New Database Folders To prevent this situation, you can set an option so that a new folder is owned by the same owner as the parent folder. If this option is set, in the previous example, Editor 2 inherits read/write permissions on the new folder but does not have delete permission and thus cannot delete the sequence or master clips. n An administrator can change the owner and permissions for a folder after it is created.
Enabling Interplay Synced Projects Enabling Interplay Synced Projects Interplay Synced Projects provide you with a way to link your bins and projects in Media Composer or NewsCutter with the folder structure for assets stored in your Interplay database. Before you can use synced projects, you need to enable the Synced Projects setting in Interplay. Folders for Interplay Synced Projects are indicated by a synced project icon.
Setting Options for Deletion 2. Select Enable, and then click Apply. The application enables synced projects for the selected workgroup.
Setting Options for Deletion This distinction between links and database assets is important in understanding how the deletion process works and the how it is affected by a deletion schedule. The following topics describe the deletion process: • “Three Parts of the Deletion Process” on page 185 • “Changes in Interplay v2.
Setting Options for Deletion 2. Links for assets that are not reserved or referenced by other assets are deleted from the database. V1 media 3. After the last link for an asset is deleted, database assets are deleted unless they reference online media. The following illustration shows the completed deletion. V1 media The last part of the process is the part that takes the longest time and places the heaviest load on the Interplay Engine.
Setting Options for Deletion You can think of deletion prior to v2.4 as synchronous, because all three parts of the process occur at approximately the same time, during the interactive part of the deletion (that is, while the Delete dialog box is open). Deletion in v2.4 and later is asynchronous, because deletion of the database assets takes place after the interactive part of the deletion. c It is important to remember that in Interplay v2.4 and later the deletion process is always asynchronous.
Setting Options for Deletion Previously the Orphan Clips folder contained links for assets deleted or removed from Interplay folders that still referenced media files on shared storage (“classic” orphan clips). Now, in addition to these links, the Orphan Clips folder also contains links for assets whose database assets are scheduled for deletion, whether or not the assets have online media.
Setting Options for Deletion These folders are useful in two ways: • It is easier to browse and search a large Orphan Clips folder for assets with online media and assets that cannot be deleted. • The scheduled deletion process ignores both of these folders, resulting in improved performance. You can manually delete assets from the Orphan Clips folder at any time.
Setting Options for Deletion • When a scheduled deletion permanently deletes metadata from the Orphan Clips folder: [Tue Mar 08 13:45:00 2011] Scheduled deletion: deleting metadata from Orphan Clips: [Tue Mar 08 13:45:00 2011] 'Administrator' 'Film BKG.mov' handle 1368 user [Tue Mar 08 13:45:00 2011] 1361 user 'Administrator' • 'computer BLUE internet NN BG.
Setting Options for Deletion To schedule the deletion of database assets: 1. In the Site Settings section of the Interplay Administrator window, click the Delete Behavior icon. The Scheduled Deletion Options section is at the bottom of the view. 2. In the Scheduled Deletion Options section, select “Enable custom schedule.
Setting Options for Deletion Select this option if you want to delay the scheduled deletion by a specified number of days. You can specify 1 to 30 days. This option gives you the opportunity to review the contents of the Orphan Clips folder before the scheduled deletion. To help determine which links will be deleted, you can check the asset deletion date in the Date Deleted column (see “New Properties for Deletion” on page 190).
Setting Options for Deletion - The first time span specifies deletions to take place from midnight until 4:00 am every day of the week. - The second time span specifies deletions from 4:01 am until 8 am every Saturday and Sunday. - The third time span specifies deletions from 8:30 pm until 11:59 pm every Monday, Wednesday, and Saturday. 5. When you are satisfied with your settings, click Apply. Note the following: • By default, all days are selected.
Setting Options for Deletion To set an option that allows deleting only OMF media or only MXF media: 1. In the Site Settings section of the Interplay Administrator window, click the Delete Behavior icon. 2. In the OMF media handling section, select “Allow user choice for deleting OMF/MXF media.” 3. Click Apply.
Setting Options for Deletion Activating the Option to Delete Referenced Assets Starting with Interplay Access v2.3, you cannot delete referenced assets (including rendered effects) without deleting the sequence that references them (see “Restricted Deletion of Referenced Assets” in the Interplay Access User’s Guide). This feature was introduced to prevent deletion of referenced assets that were still in use, and because most customers prefer keeping consistency between a sequence and its referenced assets.
Setting Options for Deletion To activate the option to delete referenced assets on a Macintosh system, do one of the following: t On an Interplay Access client system, check if the following file exists: $HOME/Library/Preferences/Workgroup/configuration.xml If the file exists, open the file in a text editor and insert the following line between the tags and <\bindings>: PAGE 197Setting Options for Deletion For a cluster engine, you need to execute this tool directly on the online node. You should run this tool during off hours because it deletes as quickly as possible and therefore puts extra load on the Interplay Engine, ISIS shared storage system, and Media Indexer. The syntax of the tool is described in the following in-line help: *********************************************************************** delete_kept_media - Deletes assets in Kept Media folder.
Viewing and Setting the Metadata Override Status To run the Delete Kept Media tool: 1. On the Interplay Engine system (or for a cluster system, on the online node), open a Windows Command Prompt. 2. Navigate to the location of the tool. For example, type cd C:\Program Files\Avid\Avid Interplay Engine\Server 3.
Production Engine Bus Connector Folders with metadata override disabled are listed in the Locations window. Red icon = metadata override is disabled Blue icon = metadata override is enabled Gray icons = inherited setting 2. (Option) Select a folder in the folder tree to limit the folders displayed in the Locations window to subfolders. To enable metadata override: t Select a folder in the folder tree or one or more folders in the Locations window and click Enable Override.
6 Application Settings In the Application settings, you can configure application-specific permissions and options, as described in the following topics: • Application Database Settings View • Media Composer | Cloud Settings • Setting Instinct/Assist User Options • Pro Tools Plug-Ins Settings Application Database Settings View The Application Database Settings view lets you specify on a database or folder level the settings that are relevant when using an Interplay application.
Application Database Settings View Setting Options in the Editing Settings Tab The Editing Settings tab in the Application Database Settings view includes settings that apply to several different applications. Some settings apply to Interplay Instinct and Interplay Assist, some apply to Interplay Instinct only, and one setting (“Check in bins when closing”) applies only to Avid editing systems such as Media Composer®.
Application Database Settings View If the database icon has a red X, you are not connected. Click the database icon to connect. The database icon shows a green check mark when you are connected. For more information, see “Viewing General Role Assignments” on page 138. 4. Do one of the following: t Select an option from a drop-down list or by clicking an option button. t Type a setting in the text box. If a setting is grayed out, click the Edit button to enable editing. Edit button 5. Click Apply.
Application Database Settings View These settings are described in “Application Database Settings: Editing Settings Tab” on page 203. For more information about using these settings, see the Avid Instinct User’s Guide. Application Database Settings: Editing Settings Tab You can set options for the Editing Settings tab in the Application Database Settings view as described in the following table. The Applications column lists which applications are affected by each option.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Natural Sound trackAvid Instinct Interplay Central 2 If two channels are selected for NAT, Avid Instinct specifies which track of the source clip Interplay Central is mapped to NAT track 2. The default is A4. Sound on Tape track Specifies which track of the source clip Avid Instinct 1 is mapped to SOT track 1. The default Interplay Central is A2.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Audio – general settings Media Creation workspace Description Applications Sets the workspace location used for Avid Instinct media clips created by users, such as Interplay Assist voice-over recordings and clips created Interplay Central during send-to-playback operations.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Dynamic Relink Description Applications Enables or disables the Dynamic Avid Instinct Relink feature (for MultiRez editing). Interplay Assist If Dynamic Relink is “true,” all relink settings in the Send to Playback option are enabled; if Dynamic Relink is “false,” these settings are disabled, with the exception Audio Mixdown Mode. The default for Dynamic Relink is “not set.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Target resolution, secondary Sets a resolution to use for a second playback device. Avid Instinct Secondary target field Leave the field blank to send a sequence to playback on the primary device. Enter a value to send the sequence to the secondary playback device. Avid Instinct n Story fields are set in Avid Instinct.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Mixdown Mode Sets the mixdown mode used for send-to-playback operations: Avid Instinct Interplay Assist • Mono — Maps to a center pan, which creates a mono mixdown of all audio tracks and outputs the resulting track to two channels when sent to playback. This results in two identical channels of audio, each containing the original audio tracks.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Target Resolution Sets an audio resolution for output to a Avid Instinct playback device. Currently, the only Interplay Assist option is PCM. Sample Rate and Bit Depth: sets the resolution of the source audio for audio mixdowns. n If dynamic relink is enabled, you must set the audio target resolution to PCM and select a Sample Rate and Bit Depth.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Auto Reservation Duration [h] Allows you to set a default duration (in Avid Instinct hours) for auto reservations. If you do Interplay Assist not want auto reservation on a folder, set the duration to zero. The default duration is 24 hours.
Application Database Settings View Setting Audio Mixing Defaults for Access and Assist The Audio Mixing Defaults in the Application Defaults tab apply to Interplay Access and Interplay Assist. • For Interplay Access, the settings apply to the Audio Mixer controls, which let you enable and mute tracks and adjust volume. Adjustments that you make with these controls apply only when you play Avid assets and file assets in Interplay Access. For more information, see the Interplay Access User’s Guide.
Application Database Settings View To set audio mixing defaults for Interplay Access and Interplay Assist: 1. In the Application Settings section of the Interplay Administrator window, click the Application Database Settings icon. 2. Click the Application Defaults tab. 3. Select the Enable Audio Mixing Defaults option so that a green check mark is displayed. 4. For each track that you want to enable, click the corresponding button, so that the button has a green icon. 5.
Application Database Settings View 6. Click Apply. Sending a Source to Playback in Interplay Assist The target settings for Send to Playback depend on the folder in which a loaded shotlist exists. The following sections describe how Interplay Assist uses target settings when sending a source to playback. Settings in the Interplay Administrator You set the target audio and video resolution for a folder in the Interplay Administrator.
Application Database Settings View If a shotlist is not open, the send to playback operation uses the target resolution that is set at the database root. If this resolution is not what you want to use for the source, you need to create or open a shotlist in a folder that has the desired settings.
Application Database Settings View 3. Click the Application Defaults tab. 4. Select the database (AvidWG). 5. For the Shotlist Start Timecode option, enter the timecode in the format HH:MM:SS. You cannot enter a default starting frame. 6. For Interplay Assist, specify the Default NTSC Shotlist Format as Drop Frame or Non-Drop Frame. 7. Click Apply.
Application Database Settings View Configuring the Frame Locators Display The Frame Locators tab in the Object Inspector displays information about locators associated with an Avid asset. Administrators and users can configure which attributes (as columns) are displayed in the Frame Locators tab. Administrators can select a default set of columns in the Interplay Administrator, and users can change the default settings in Interplay Access.
Application Database Settings View 3. Click the View Settings tab. 4. In the Frame Locators View section, select “Use local column configuration.” 5. Select the columns you want to display, or deselect the columns you do not want to display, then click OK. 6. Refresh Interplay Access (select View > Refresh or perform an action). Configuring the Restrictions Display The Restrictions tab in the Object Inspector displays information about restrictions associated with an Avid asset.
Media Composer | Cloud Settings To configure the default display in the Interplay Administrator: 1. Open the Interplay Administrator and log in to the database for which you want to set the default display. 2. In the Application Settings section, click Application Database Settings. 3. Click the Application Defaults tab. 4. In the Access Restrictions View section, select the columns that you want to display in the Restrictions tab. The Start Time, End Time, and Comment columns are always displayed. 5.
Setting Instinct/Assist User Options Setting Instinct/Assist User Options In the Instinct/Assist User Settings view, you can set permissions for various editing functions on the group or user level (working resolutions for video and audio are not available for groups). These settings apply to all folders in the database, so in some cases the settings apply to users on Avid editing systems (NewsCutter, Media Composer) who are checking Avid assets into the Interplay database.
Setting Instinct/Assist User Options To change the Instinct/Assist User settings: 1. In the Application Settings section of the Interplay Administrator window, click the Instinct/Assist User Settings icon. 2. In the Users tree on the left, select a group of users or an individual user. The settings for the selected user or user group area are displayed in the pane on the right. 3. Do one of the following: t Select an option from the drop-down list or by clicking an option button.
Setting Instinct/Assist User Options Edit button 4. Select among the following options for each setting: Option Description Inherited The user inherits this setting from the group it is a part of. Yes Grants the user this setting. No Denies the user this setting. If you select Inherited, and then click Apply, the option changes to the inherited setting and the options are grayed out. 5. Click Apply. A notification box tells you whether or not the changes have been successfully applied.
Setting Instinct/Assist User Options Instinct/Assist User Settings The following table describes options for the Instinct/Assist User Settings. The table includes columns that specify which applications the setting applies to. Setting Avid editing Media Instinct Assist Access applications Central Can send to playback x x Can modify column properties x x Description If yes, allows the selected user or group to send material to a playback device.
Setting Instinct/Assist User Options Setting Can use higher resolutions Avid editing Media Instinct Assist Access applications Central x x Description If yes, allows the selected user or group to work with a higher quality than the working resolution for video and audio clips if the working resolution is not available. If this option is set to No and the only available resolution is higher than the working resolution, the user sees Media Offline in the Video monitor.
Setting Instinct/Assist User Options Setting Can create locators Avid editing Media Instinct Assist Access applications Central x x x x Description If yes, allows the selected user or group to create locators. If no, a user of an Avid editing application can still create locators for an asset, but can check in only the asset, not the locator metadata (an error message is displayed).
Setting Instinct/Assist User Options Setting Avid editing Media Instinct Assist Access applications Central Can create restrictions x x Description If yes, allows the selected user or group to mark a section of a clip with a restriction locator. In most cases, if you want a user to create restrictions, select “yes” for both “Can create restrictions” and “Can modify restrictions.” Adding text is considered modifying a restriction. Administrators and owners have this right set by default.
Pro Tools Plug-Ins Settings Pro Tools Plug-Ins Settings You can use Interplay Pro Tools Plug-ins to pass audio files back and forth between Avid video editing systems and Pro Tools audio editing and mixing systems. As of Interplay v3.0, Pro Tools Interplay Integration Plug-Ins for Interplay are no longer available on the Interplay Client Installer. For more information about using Pro Tools with Interplay, go to the Knowledge Base page titled “Avid Interplay Requirements With Pro Tools.
7 Interplay Services The Interplay Services settings include the Workgroup Properties and Service Configuration views, which are identical to parts of the Avid Service Framework. For example, the following illustration shows the Service Configuration view examining the Interplay Media Indexer settings for a computer in the Interplay workgroup. You can use the Service Configuration view to configure services such as the Interplay Media Indexers for all the clients in your workgroup from one computer.
n Avid Workgroup Properties and Avid Service Configuration are also available from the Interplay Access View menu.
8 Troubleshooting The following topics provide information for troubleshooting problems with the Interplay Engine server: • Troubleshooting Login Problems • Troubleshooting Client Connection Problems • Optimizing Interplay Performance • Troubleshooting Firewalls and Interplay • Troubleshooting the Server Execution User Account • Shutting Down or Locking the Server Process Also see “Creating a Metadata-Only Backup for Customer Support” on page 62.
Troubleshooting Client Connection Problems 6. Unlock the server. Troubleshooting Client Connection Problems This topic provides suggestions for settings to check if a client system is not connecting properly. Network Configuration • Check the TCP/IP connection by typing ping in the Command Prompt on the client. Server Settings • Check if there is a user account for the user. See “Managing Users, User Groups, and User Rights” on page 128. • Check if the password is expired.
Troubleshooting Firewalls and Interplay • Check the speed of the LAN between the Interplay Engine and the shared storage server. Make sure that the Interplay Engine and the Avid shared-storage server are connected appropriately; for example, the Interplay Engine needs to read the files to create thumbnails. If the connection is slow, performance can drop. • Check the speed of file operations of the Interplay Engine on the shared storage server.
Troubleshooting the Server Execution User Account Troubleshooting the Server Execution User Account The Server Execution User is a Windows operating system user account that is used only to run the Interplay Engine processes. You specify the user name and password for the Server Execution User when you install the Interplay Engine on the server. The following topics provide more information about the Server Execution User account and information about how to recreate the account.
Troubleshooting the Server Execution User Account • You have the option of allowing the Interplay Engine installer to create the account. Select a name before the installation and specify the name and a password during the installation. The installer will create a local user in the Administrators group with the appropriate permissions. • You can also create a local Administrator account manually and specify that account during the installation.
Troubleshooting the Server Execution User Account Determining the Server Execution User Name If necessary, you can check the user name of the Server Execution User account. To determine the Server Execution User name: 1. Right-click My Computer and select Manage. 2. Expand the Services and Applications branch, then click Services. 3. Right-click Avid Workgroup TCP COM Bridge and select Properties. 4. Click the Log On tab. The Log On tab contains the name of the Server Execution User.
Troubleshooting the Server Execution User Account Re-creating the Server Execution User If you need to re-create the Server Execution User, use the NXNServerUser.exe tool. To re-create the Server Execution User account: 1. Run the tool NxNServerUser.exe on the Interplay Engine server. The tool is located in the following directory on the Interplay Server: Installers\AssetMgr\Tools\NxNServerUser 2. Select Custom User. 3. Type the name, such as MYDOMAIN\IPEngine, and the password of the account.
Shutting Down or Locking the Server Process The Avid Interplay Engine processes have all necessary access rights. Shutting Down or Locking the Server Process You might need to shut down or lock the Avid Interplay Engine Server process in certain circumstances, such as low disk space conditions (see “Moving a Database Under Low Disk Space Conditions” on page 84). For more information about the process, see “Avid Interplay Engine Server” on page 270.
9 Configuring Interplay for a Split Database An Interplay database includes a metadata database and a file repository (for file assets). If you do not have adequate local storage for your Interplay database, you can configure (or “split”) the Interplay database so that the metadata database remains on the Interplay Engine server and the file repository resides on an Avid shared storage workspace.
Understanding a Split Database If the Interplay Engine server does not have adequate local storage for your Interplay database, you can configure the Interplay Engine to store only the metadata database on the Interplay Engine. All other database files and folders can be stored on an Avid shared-storage workspace. This configuration is called a split database.
Supported Configurations You can configure your system to store the file repository on shared storage. However, for performance and reliability reasons, Avid requires that the metadata database be stored on the server running the Interplay Engine. If the metadata database is stored on an external file server, network problems or unavailability of the shared storage server causes the Interplay Engine to lock the databases because it cannot write changes persistently.
Preparing for a Split Database Supported Configurations for the Interplay Engine (Continued) Metadata Location File Repository Location Supported Comments Dedicated file server Interplay Engine server No Not supported. Metadata database must be on Interplay Engine server. Preparing for a Split Database To split the database, you need to prepare the Avid ISIS workspace. To prepare for a split database: 1.
Splitting a Database for New Interplay Installations 3. Edit the workgroup.xml file to include the path for the shared storage workspace (see “Configuring the workgroup.xml File” on page 247). 4. Open the Interplay Administrator. 5. In the Server section of the Interplay Administrator window, click Server Settings. The Server Settings view opens. This view shows the settings for two root folders: one for the metadata database and one for the data (file assets).
Splitting a Database for New Interplay Installations 10. Accept the Database Name, type a description, and click Create. The new database is created. - You should find the database folder on the Interplay Engine, for example D:\Workgroup_Databases\AvidWG\_Database. - You should find the file repository on the Avid shared-storage workspace, for example \\AAC-ISIS\File_Assets\AvidWG. The AvidWG folder should contain _Master and other database folders and files. 11.
Splitting a Database for Existing Interplay Installations Splitting a Database for Existing Interplay Installations In some situations, you might need to split the database after you have created it. The following procedure assumes that you want to relocate the file repository of database AvidWG from the Interplay Engine server to an Avid ISIS workspace. n During the installation of the Interplay Engine, a shared folder for the database is created on the Interplay Engine server.
Splitting a Database for Existing Interplay Installations 4. Lock the database to make sure that no user can access it: a. In the Database section of the Interplay Administrator window, click Lock/Unlock Databases. b. Select the database in the Unlocked Databases list. c. Click Lock Database. The database name appears in the Locked Databases list. 5. Deactivate the database: a. In the Database section of the Interplay Administrator window, click Manage Databases. b.
Splitting a Database for Existing Interplay Installations 10. Navigate to the folder \\SharedStorageServer\WorkspaceName\AvidWG and open the FolderLocations.xml file. 11. Make sure the file includes the correct path for the _Database directory. It should include the line \\IEServer\WG_Database$\AvidWG\_Database For IEServer, substitute the network name for the Interplay Engine server. This path points to the metadata database on the Interplay Engine. If the FolderLocations.
Splitting a Database for Existing Interplay Installations Add the file location information as follows: \\IEServer\WG_Database$\AvidWG\_Database For IEServer, substitute the network name for the Interplay Engine server. Be sure to use a UNC path. The Interplay Engine effectively maps it to a local path if possible. c Make sure to type this information accurately. Errors in the file can prevent you from activating the database.
Splitting a Database for Existing Interplay Installations By default, the _Backup folder is now located on the shared storage workspace. To avoid filling up the workspace with backups, select Custom and specify the UNC path for a different external file server. Make sure the Server Execution User has read/write access to this external file server. 15.
Splitting a Database for Existing Interplay Installations If you move the file repository to a different location, this location must be published in this file as well. For example: PAGE 249Reuniting a Split Database Database root folder Reuniting a Split Database An Interplay configuration might include a split database (see “Understanding a Split Database” on page 237). This topic provides information about reuniting a split database.
Reuniting a Split Database The following illustration shows all database files located in the same AvidWG folder on the Interplay Engine server.
Reuniting a Split Database c In a correctly split database, the AvidWG folder on the Interplay Engine should contain only the _Database folder. If the AvidWG folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine. Rename this folder _Database_UNUSED or something similar before copying the other content to the Interplay Engine.
Reuniting a Split Database Follow one of these procedures to reunite a split database: • If the _InternalData folder is already located on the Interplay Engine, see “Reuniting a Split Database (AvidWG Only)” on page 253. • If the _InternalData folder is located on a shared storage workspace, or split between the Interplay Engine and shared storage, see “Reuniting a Split Database (AvidWG and _InternalData)” on page 255.
Reuniting a Split Database Reuniting a Split Database (AvidWG Only) To reunite a split database (AvidWG only): 1. If you are working on a cluster system, make sure that cluster services that provide the local S drive are running. 2. Lock the database to make sure that no user can access it: a. In the Database section of the Interplay Administrator window, click Lock/Unlock Database. b. Select the database in the Unlocked Databases list. c. Click Lock Database.
Reuniting a Split Database Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.xml c In a correctly split database, the AvidWG folder on the Interplay Engine should contain only the _Database folder.
Reuniting a Split Database c. Make sure “Load Database on Activation” is selected, and click Activate. If the database is activated, its name is displayed in the Databases list. The database is automatically unlocked. 9. Check the backup location in the Schedule Backups view of the Interplay Administrator. If the _Backup folder was located on shared storage, it is now located on the Interplay Engine. If necessary, change the location to the Interplay Engine or to another external file server. 10.
Reuniting a Split Database The database name no longer appears in the Databases list. 4. In the Server Settings view of the Interplay Administrator, edith the path for the “Root folder for data” to match the path for the “Root folder for database.” This location is used if you create a new database. 5. Shut down the Interplay Engine services: - On a cluster system, bring the Avid Workgroup Engine Monitor resource (not the resource group) offline.
Reuniting a Split Database The following table lists the files and folders that you need to copy. These files and folders are illustrated in “Reuniting a Split Database” on page 249. Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.
Reuniting a Split Database Copy from \\SharedStorageServer\WorkspaceName\_InternalData to \\IEServer\WG_Database$\_InternalData _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.xml c If the _InternalData folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine.
Reuniting a Split Database 13. Start the Interplay Engine services: - On a cluster system, bring the Avid Workgroup Engine Monitor resource (not the resource group) online. - On a non-cluster system, start the services Avid Workgroup TCP COM Bridge and the service Avid Workgroup Server Browser. 14. Activate the database: a. In the Interplay Administrator, click Manage Databases. b. In the “Database (.pro) file to activate” text box, type the full UNC path to the .
Reuniting a Split Database d. After reconnecting to the database with Interplay Access, check if the file is still in the database. 17. If the test is successful, delete or rename the folder \\SharedStorageServer\WorkspaceName\AvidWG.
A Installed Components and Services The following topics provide information about components and services that are installed as part of the Interplay Administrator: • Avid Interplay Engine Directory: Folders and Files • Required TCP/IP Ports • Avid Interplay Engine Servers and Services Avid Interplay Engine Directory: Folders and Files The following components are installed in the Avid Interplay Engine directory. By default, this directory is created during installation as C:\Program Files\Avid\Avid
Avid Interplay Engine Directory: Folders and Files Apache Folder The Apache web server handles every incoming request and forwards them to the database server. The Apache folder includes important logs from the Apache process. File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Apache\logs\error.log The central Apache web server log file that contains important messages from the Apache process, especially warnings and errors. Apache\logs\access.
Avid Interplay Engine Directory: Folders and Files The items in such a log entry are: • The IP address of the machine where the request was coming from; • The date and time when the request was received; • The request method (GET or POST), the request URI and any request parameters; • The HTTP status codes returned to the client. The returned status codes are the standard HTTP codes as described in RFC 2616 available under http://www.ietf.org/rfc/rfc2616.txt.
Avid Interplay Engine Directory: Folders and Files Data Folder The Data folder contains server-relevant configuration and data files, including the following Apache modules and configuration files used by the Avid Interplay Preview Server and Avid Interplay HTTP Server. File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Data\Apache\conf\httpd.conf The configuration file for the Apache web server. Data\Apache\conf\workgroup.
Avid Interplay Engine Directory: Folders and Files File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Logs\Machines\[COMPUTER NAME]\NxNServer.log The central Avid Interplay Engine Server log file containing information messages, warning and error messages generated by the Avid Interplay Engine Server. Logs\Machines\[COMPUTERNAME]\ NxNTCPCOMBridge.log The log file for the Avid Interplay TCP/COM Bridge. Is not created until the first message occurs. Logs\Machines\[COMPUTERNAME]\ NxNBack
Avid Interplay Engine Directory: Folders and Files AvDeletes.log The AvDeletes.log file includes the following information about media delete operations: • Date and time of the delete operation • Login of the user who performed the delete operation • Computer name of the machine on which the delete operation was performed • Name and path of the master clip deleted • Name and path of the media files deleted, with deletion time in milliseconds (ms) The following example shows these items.
Avid Interplay Engine Directory: Folders and Files AvMetaDataDelete.log The AvMetaDataDelete.
Avid Interplay Engine Directory: Folders and Files AvMoveEx.log The AvMoveEx.
Required TCP/IP Ports Server Folder The Server folder contains the Avid Interplay Engine Server installation. File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Server\Machines\[COMPUTER NAME]\MachineConfig.ini This file is generated by the Avid Interplay Engine Server. It contains information about the versions of the dll's loaded by the server. Server\Config\Config.
Avid Interplay Engine Servers and Services Two servers are installed on the Interplay Engine: • The Avid Interplay Engine Server is the central process where all assets and asset meta-information are managed. See “Avid Interplay Engine Server” on page 270. • The Avid Workgroup HTTP Server is a module for the Apache server that allows clients to connect to the Avid Interplay Engine Server using a HTTP protocol.
Avid Interplay Engine Servers and Services Processes The process running is usually listed as NxNServer.exe or NXNSer~3.exe. This process is automatically launched at startup (machine boot) from the Avid Workgroup Server Browser Service. If, however, it is not running at any time and clients try to access it, it is automatically launched. The Interplay Engine always runs under the user specified in the DCOMConfig Settings.
Avid Interplay Engine Servers and Services n The Avid Interplay HTTP Server uses the Apache modules NxNworkgroupFileTransferService.nsm and NxNworkgroupInternetBridge.nsm. Windows Services See “Avid Workgroup Preview Server Service” on page 272. Requirements See “Avid Workgroup Preview Server Service” on page 272.
Avid Interplay Engine Servers and Services On both the Preview Server and on the local machine, cache directories keep the generated previews. • On the Preview Server: in the directory you specified during installation, by default \\IEServer\\WG_Database$\PreviewServer\Cache. • On the local machine: C:\Documents and Settings\User\Local Settings\Application Data\Avid\Workgroup\Cache\Preview. The server is implemented as a module for Apache.
Avid Interplay Engine Servers and Services c Change the impersonation settings for the Avid Interplay Preview Server with the NXNServerUser.exe tool only. See “Troubleshooting the Server Execution User Account” on page 232. Configuring the Preview Service The Preview Service is responsible for the generation of thumbnails and preview images on the server, as well as delivering them to the Interplay application. All settings can be edited in the workgroup.xml file in the section.
Avid Interplay Engine Servers and Services best performance, this path should reside on a disk that has enough free space available to hold a reasonable working set of cached images. While the default is inside of the database directory of the Avid Interplay Engine, it is a good idea to place it on a different disk. • IconRoot: Path to a directory where a set of icons is stored, usually pointing into the Avid Interplay Engine installation directory.
Avid Interplay Engine Servers and Services Processes The process running is usually NXNTCP~1.exe from NXNTCPCOMBridge.exe. Windows Services The service “Avid Workgroup TCP COM Bridge” is automatically started at system startup and should be running all the time. Requirements • The Avid Workgroup Server Browser must run on the same machine as the Avid Interplay Engine Server. • The Avid Workgroup TCP/COM bridge needs to run under the same user account as the Avid Interplay Engine Server.
Avid Interplay Engine Servers and Services Windows Services The Avid Workgroup VSS service is automatically started at system startup and should be running all the time. This service always runs under the local system account. The Avid Workgroup VSS service requires that the Windows Volume Shadow Copy service is also running. The Windows Volume Shadow Copy service is installed by default and started automatically.
Avid Interplay Engine Servers and Services Example 2: COM Failure Avid Workgroup Engine Monitor Event ID 42: Failed to connect Workgroup Engine with DCOM 'Error 800706bb happened 8 times within the last 14981 msec' Avid Workgroup Engine Monitor Event ID 31: Thorough check failed: Result code: 0x800706be Avid Workgroup Engine Monitor Event ID 33: Monitoring thread terminated Processes The process running is usually listed as IEMonitorService.exe or IEMONI~1.EXE.
B Interplay Engine Configuration Files The following topics provide information for configuration that you might need to do only under certain circumstances, such as troubleshooting: • Configuring the Server Event Manager • Configuring Client Access • Setting the Filetransfer Server If you are moving the file repository to a shared-storage workspace, you need to edit the workgroup.xml file. See “Configuring the workgroup.xml File” on page 247.
Configuring the Server Event Manager The configuration file is an XML file that has the following format: Value of Parameter ... Value of Parameter ... Value of Parameter ...
Configuring the Server Event Manager The blocks are used to specify the behavior of an action. It is also possible to identify a parameter by its “Name” attribute. Parameters are identified by their “Name” attributes. Whenever the server performs an action, it searches the parameters from the inside out, which means it searches the parameter block inside the block first and then inside the block. This allows you to specify a parameter for all events.
Configuring the Server Event Manager SendMail The SendMail action is configured with the following XML block: SERVERMACHINE administrator@mydomain.com, info@mydomain.com ServerExecutionUser@mydomain.com 123.123.123.
Configuring the Server Event Manager Supported Events in Config.xml The following sections describe the events that are currently supported in Interplay and that can be configured in Config.xml as events to which the Interplay Engine should react.
Configuring the Server Event Manager The LogEvent is configured in the Config.xml with the following XML block: To send an e-mail when a “LogEvent” event is triggered, use the “SendMail” action. See also “LogWatch.xml” on page 286. ClusterResourceFailure Event The “ClusterResourceFailure” event is triggered only in a failover cluster setup. It is sent whenever a problem inside the cluster is detected.
Configuring the Server Event Manager Server Event Configuration Example The following is an example of the configuration of a server to send e-mails whenever the backup fails, or the free space on a server disk reaches one of the limits set, in this case 30, 100, or 500 MB: 30 100 500
Configuring the Server Event Manager 123.123.123.123 Here is an example of an e-mail sent by the Event Manager: 11/23/1999 12:09:14 [WGServer] INFO: This is a message sent by the Event Manager. LogWatch.xml Log event notifications are configured in LogWatch.xml, located in the Avid Interplay Engine installation directory: C:\Program Files\Avid\Avid Interplay Engine\Data\Server\Config. Edit this file to assign actions for different log events.
Configuring the Server Event Manager ID Severity -100 [WARN] (warnings like “loading took more than 3 sec”) 0 [ERROR] (normal errors, like “file couldn't be imported because it exists already”) 100 [FATAL] (Recoverable critical Errors, like “couldn't save database - disk full”) 200 Critical (non-recoverable errors, such as crashes) Sending E-mail Notifications from LogWatch.xml To send e-mail notification on any error with a specific severity level: t Add a mapping entry to LogWatch.
Configuring Client Access The message ID is the last number in brackets before the actual message string in the log file. The message ID of the entry below is 0x00004678. Note that the log file displays hexadecimal ids. You need to convert the numbers to decimal format before adding to the message mapping. [Thu Sep 16 17:27:43 2004] [FATAL] [.\NxNDbServer.
Configuring Client Access The “name” attribute specifies the name of the database. This name must be the same as the name of the database configured in the Active Database List through the Interplay Administrator. If a database is not in the Active Database List, it cannot be made visible by specifying its name in token either. You can also use the “*” as a wildcard character representing all databases in the Active Database List.
Configuring Client Access Example 2: PAGE 291Configuring Client Access Example 4: PAGE 292Setting the Filetransfer Server Setting the Filetransfer Server Additional configuration might be required when the Interplay Server is running inside of a network configured using NAT. In this case, the IP returned by the Interplay Engine is the internal address and not the external address needed by the client. The following change in the workgroup.xml configuration file tells the client to connect to the file transfer server via its name instead of address.
C Valid and Invalid Characters in Interplay The following table lists the valid and invalid characters (also known as special characters) for Interplay. Allowed Avid asset names Not Allowed Characters: / \ | File asset names and All characters allowed Characters: * ? : / \ " < > | Interplay database for files in Windows Names ending with a dot folder names Names used as DOS devices (LPT1, com1, .., .,, for example) Property names (metadata field names) Characters: / \ | Video ID metadata field Spaces
D System Metadata Properties Metadata is textual data you can use to identify and describe the creation, contents, and disposition of the clip or shotlist you are logging. Interplay comes with an extensive list of system metadata. The administrator determines some of the metadata properties that can be viewed in Interplay Access as headings in the Content View and Object Inspector, and also used in Interplay searches. Some metadata properties are always available and cannot be disabled.
Search Values and Hints on Searching in Interplay Heading Description All Custom All custom properties defined in the Property Layout of the Interplay Administrator. Access Rights The access level or user role assigned to a particular folder or asset. The column displays an icon that represents the type of access. AFD Value for Active Format Description (AFD) in an ancillary data track. Media Composer v6.1 and later allows the creation of AFD values, which are supported in Interplay v2.7 and later.
Search Values and Hints on Searching in Interplay Heading Description Auxiliary Ink Auxiliary ink format settings allow you to display an additional type of ink number. This lets you track additional types of film information for different film gauges. Used for 24p projects, 25p projects, and matchback projects only. Auxiliary Ink is the starting frame for the clip.
Search Values and Hints on Searching in Interplay Heading Description Comments Displays any comments added as metadata to the media file when it was originally ingested or captured. You can edit this field in Interplay Access. Created by Displays the name of the user who created the shotlist. Creation Date When the asset was created. The format of the date and time depends on the local language and regional options of the operating system and the Java software. Type text.
Search Values and Hints on Searching in Interplay Heading Description DPX Frame-counting field for Digital Picture Exchange, a SMPTE standard describing frames scanned from film. The format is the following: a descriptor of up to 32 alphanumeric characters, followed by a hyphen (-), followed by a six-digit frame count, for example, DPXChildDocu-023657. DRM Digital Rights Management property.
Search Values and Hints on Searching in Interplay Heading Description In Use (Search only) If Is in use, asset is referenced by a sequence also in the database. Select Is in use or Is not in use. IN-OUT The length of the marked segment of a clip, if any. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Initial Checkin Date Date that the asset was first checked in.
Search Values and Hints on Searching in Interplay Heading Description KNMarkIN Key number for the IN point, if you set one for the clip. Used for 24p projects, 25p projects, and matchback projects only. KNMarkOUT Key number for the OUT point, if you set Select an operator and then type numbers one for the clip. Used for 24p projects, only in the four colon-separated entry 25p projects, and matchback projects fields displayed. only. KNStart Starting key number for the clip.
Heading Description Search Values and Hints on Searching in Interplay Master Start Starting key number of the final master sequence. Used for 24p projects, 25p projects, and matchback projects only. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Media File Format Clip media format. MXF or OMF. Media Size Media file size. Specify KB, MB, GB and type a number. Note that this specification cannot be saved in a Saved Search.
Search Values and Hints on Searching in Interplay Heading Description Path Path to assets in the Interplay database. Meant to be used in conjuction with other search conditions to narrow the area where the results are coming from: for example, combine a search for all masterclips that have been updated in the last 10 minutes and that are in path "/Projects/MyName/MyBin2.” Select is or is not, then click the Select button and choose a path from the tree.
Search Values and Hints on Searching in Interplay Heading Description Reserved (Search only) Indicated item is reserved Select a user and then select a time frame. for specified timeframe by specified user. S3D Alignment Displays whether or not the media has already been aligned by a third-party application. Presently, this is just an indicator for the editor. There are no software functions associated with this field.
Search Values and Hints on Searching in Interplay Heading Description S3D Contributors (master clip only) Lists the S3D Channels (master clips) that Criterion for Extended Search in Access feed into the stereoscopic clip. S3D Eye Ordering Only available if the media is in a frame Criterion for Extended Search in Access compatible format with the S3D Channel set to either Over/Under or Side by Side. Specifies which half of the image the eye is displayed.
Search Values and Hints on Searching in Interplay Heading Description S3D Group name A common name used to identify all Criterion for Extended Search in Access master clips originating from the same stereoscopic footage. The group name is used by the application to create a single stereoscopic clip that references these master clips. Therefore, this name must be exactly the same for all clips that need to be grouped into a stereoscopic clip.
Search Values and Hints on Searching in Interplay Heading Description S3D InversionR Only available if the media is in a frame Criterion for Extended Search in Access compatible format with the S3D Channel set to either Over/Under or Side by Side. Displays how the part of the image that provides the right eye should be inverted before being used. None: Leaves the image as is. Horizontal: Inverts the right eye image horizontally. Vertical: Inverts the right eye image vertically.
Search Values and Hints on Searching in Interplay Heading Description Start Timecode of the clip’s head frame. Streamable Masterclips (Search only) Finds master clips that were are published, are not published. For published for streaming (Interplay V2.3 Interplay v2.4 and later, add criteria and earlier). Can also be used to search “Media Status is online” for clips with directly playable proxy media. Take Take number of the scene. Type a number. Tape Source tape name (from the bin).
Search Values and Hints on Searching in Interplay Heading Description Tracking Displays colored icons that indicate the status of shared assets across workgroups. For more information, see “Viewing the Status Assets Across Workgroups (Asset Tracking).” Tracks All tracks used by the asset (from the bin) Select Video, Audio, or Both. Transfer Frame-counting field for sources that have been prepped for transfer.
E Server Error Codes The following table lists the error codes and the textual expressions that the Interplay Engine can return. 0x52e Logon failure: unknown user name or bad password. 0x525 The specified user does not exist. 0x8000ffff Failed to open the database (catastrophic failure). Contact your administrator. May require Avid support. 8007000e out of memory 80070005 Failed to open project: Access denied. The project is deactivated.
89990031 invalid name 89990032 invalid handle 89990033 invalid destination 89990034 invalid property 89990035 invalid parameter 89990036 invalid filename 89990037 invalid object 89990038 invalid hostname 89990039 invalid macro string or tool installation file 89990040 object not found 89990041 parent not found 89990042 the template for the object could not be found 89990043 iterator is invalid for this iteration-capable command 89990050 property not found 89990051 property not s
89990072 root object has no parent 89990073 invalid operation for root object 89990080 cannot open file 89990081 cannot write to file 89990082 cannot read from file 89990083 the file does not exist 89990084 file system operation failed 89990085 access to file denied 89990086 sharing violation 89990087 corrupt file 89990090 cannot set mount point 89990091 object not mounted into file system 89990092 cannot create directory 89990093 cannot move directory or file 89990094 cannot co
89990111 workspace already initialized 89990120 already connected to a server 89990121 not connected to a server 89990122 cannot connect to server 89990123 cannot disconnect from server 89990124 The database share on the server is not accessible. Please contact your administrator.
89990162 the dongle is not available on the server 89990163 the registration key is invalid 89990164 the server and client versions are not compatible 89990165 the server could not be instantiated (is the server installed on this machine?) 89990166 the server is locked by the Administrator 89990167 the server is low on virtual memory 89990168 the server is low on disk space 89990169 the server is out of disk space 89990170 the specified search expression is invalid 89990171 the database i
89990201 object not found 89990202 object already exists 89990220 CopyFile command failed 89990221 file already exists 89990222 file does not exist 89990224 cookie file does not exist 89990225 can not create cookie file 89990226 can not read cookie file 89990227 cookie file is corrupt 89990228 found cookie does not match wanted cookie 89990230 object must support INxNPersistDatabase 89990231 object must support INxNPersistDatabaseObj 89990232 object must support INxNVersionControlPr
89990261 version control is disabled for this object 89990262 Connect to version control server failed 89990280 Copying file from server location to local destination failed 89990290 archive is corrupted 89990291 file is not of correct type 89990292 Disabling version creation for abstract assets is not supported 89990300 the user 'UserManagement' is not allowed 89990301 user rights do not allow this operation 89990302 user/user group exists already 89990303 command exists already 8999030
89990321 The operation cannot be performed on a system defined role 89990322 The operation cannot be performed on a system defined action 89990323 The action is not assigned to the role 89990324 The system id's for roles or actions are out - impossible to create new system actions or roles 89990326 The operation is not permitted on the user administrator 89990327 The initialization of the authorization subsystem failed - read message for more information 89990340 The initialization of the user
89990369 could not connect to the LDAP server 8999036a The operation failed because the object is protected by a reservation 8999036b CCS Connection failed 8999036c CCS is corrupt (for example, GUID missing) 8999036d The authorization config file is missing 8999036e The CCS does not have the same version as the server of the database 89990370 An LDAP search enum failed 89990371 Structural changes are not allowed on that object 89990372 No Children can be added to this folder or moved out of
89990615 use proxy 89990620 bad request 89990621 unauthorized 89990622 payment required 89990623 forbidden 89990624 not found 89990625 method not allowed 89990626 not acceptable 89990627 proxy authentication required 89990628 request timeout 89990629 conflict 8999062a gone 8999062b length required 8999062c precondition failed 8999062d request entity too large 8999062e request URI too long 8999062f unsupported media type 89990630 internal server error 89990631 not impleme
89990704 failed to apply database journal transaction 89990705 failed to apply database journal operation 89990706 error opening database journal 89990707 error reading from database journal 89990708 error writing to database journal 89990709 database journal file error 89990800 SQL error 89990801 SQL error, more info available 89990802 invalid SQL configuration 89990900 the sender of the message does not exist 89990901 the recipient of the message does not exist 89990902 The sender m
89990a07 An image could not be loaded or saved because the license for the LZW algorithm is not available. 89990a08 The image could not be read or stored because the file or image has an invalid format.
89990b0e A search request sent to the LDAP server could not dereference an alias because of missing access rights, LDAP error: LDAP_ALIAS_DEREF_PROBLEM(0x24) 89990b0f An incorrect authentication method was used when sending a request to the LDAP server, LDAP v: LDAP_INAPPROPRIATE_AUTH(0x30) 89990b10 The credentials sent to the LDAP server are invalid, LDAP error: LDAP_INVALID_CREDENTIALS(0x31) 89990b11 The request sent to the LDAP server was not completed because of missing access rights, LDAP error:
89990b1f The LDAP operation needs to be performed by multiple LDAP servers, where this operation is not permitted, LDAP error: LDAP_AFFECTS_MULTIPLE_DSAS(0x47) 89990b20 The LDAP server cannot perform the operation because of a virtual list view error, LDAP error: LDAP_VIRTUAL_LIST_VIEW_ERROR(0x4C) 89990b21 The LDAP server encountered an unknown error, LDAP error: LDAP_OTHER(0x50) 89990b22 The LDAP server could not be contacted, LDAP error: LDAP_SERVER_DOWN(0x51) 89990b23 The LDAP client detected an
89990b31 A loop was detected in an LDAP alias or referral, LDAP error: LDAP_CLIENT_LOOP(0x60) 89990b32 An LDAP operation failed because a referral required too many referral hops, LDAP error: LDAP_REFERRAL_LIMIT_EXCEEDED(0x61) 89990b50 The operation failed because the user authentication provider is not enabled 89990b51 The authentication failed because empty passwords are not allowed 89990b52 The CCS was unable to retrieve the users from a user authentication provider 89990b53 The specified user
F Consistency Check Codes The following tables explain the codes reported when you run a Consistency Check: c • Consistency Check Critical Errors • Consistency Check Errors • Consistency Check Warnings The Consistency Check is for support purposes. You should perform this check only if requested by Avid Technical Support.
Consistency Check Errors Code Meaning 7142 repository data corruption 7143 repository data corruption 7144 repository data corruption 11064 user management failed to initialize Consistency Check Errors n If any of the following errors are reported, some problems were found related to the particular object. It is still possible to use your database, but you should contact Avid using the protocol outlined in the “If You Need Help” topic in the front of this manual to resolve the problem.
Consistency Check Errors Code Meaning 7111 unknown property handle 7112 streamed property flag is not set 7113 unknown streamed property name 7114 invalid streamed property 7153 internal object state is invalid 7171 link is invalid 7172 link is invalid 7173 link is invalid 7174 link is invalid 7175 link is invalid 7176 link is invalid 11058 master user is not valid 11059 master user is not valid 11060 master user does not exist 11061 master user is not valid 11062 master us
Consistency Check Warnings Consistency Check Warnings If any of the following warnings are reported, some problems were found, but no action is urgently needed. Code Meaning 7062 file size mismatch 7072 invalid dependency source 7073 invalid dependency source 7074 invalid dependency target 7075 invalid dependency target 7076 incorrect dependency type 7091 pending change problem fixed 23022 invalid entry in the authorization role table.
Index Symbols _Backup directory described 29 _Buckets directory described 29 _Database directory backing up and restoring 32, 33 described 29 _Master directory described 29 _PropertyStore directory backing up and restoring 32, 33 described 29 Numerics 7-Zip for Interplay backups 44 A AAF metadata adding to tape archive 180 Access control for custom properties 158 Accumulated inherited role described 133 Activating database 70 Administrator role described 133 Administrators group 130 Apache web server act
Index Avid online support 12 training services 15 Avid assets described 17 Avid Instinct Application Database options 203 setting Application Database options 200, 201 setting user options 219 user options 222 Avid Interplay client-server application 20 optimizing performance 230 Avid Interplay Administrator See Interplay Administrator Avid Interplay Assist Application Database options 203 setting Application Database options 200, 201 setting user options 219 user options 222 Avid Interplay Engine director
Index ClusterResourceFailure event 283 Complete backup described 32, 33 Config.
Index Everyone group 130 Exclusive Access for maintenance tools 85 setting and releasing 94 Exiting Interplay Administrator 26 Exporting license 107 Extended search custom properties 163 F Failed to Delete folder 184 Fast backup described 33 File assets described 17 source files for 237 File repository described 237 Filetransfer server 292 Firewalls troubleshooting 231 Folderlocations.
Index optimizing performance 230 ports used 269 servers and services 269 Interplay Media Services Engine registering 169 Interplay Media Services view 174 Interplay Portal viewing 13 Interplay Transfer configuring for remote workgroups 164 Interplay Transfer Settings view 175 Interplay Transfer Status view 175 Interplay Window automatic reservation 210 Interplay workgroup described 16 multiple workgroups 18 InterplayRestore tool described 46 example 54 J Journal files described 29 K Kept Media folder 184
Index N No Access role described 133 NxNServerLock.exe locking server process 236 moving database with 84 NxNServerShutdown.exe moving database with 84 shutting down server process 236 NxNServerUnlock.exe moving database with 84 NXNServerUser.exe recreating Server Execution User 235 O Object Inspector configuring Frame Locators 216 configuring Restrictions 217 OMF files option for deleting 193 Online support 12 Orphan Clips folder changes for v2.
Index Root folders setting 91 S Schedule Backups view 38 Scheduled deletion 190 Searches custom properties 163 Searching remote workgroups 164 Send mail action 281 Server error codes 309 information about 92 locking 94 restarting 98 shutting down 94 unlocking 94 Server Event configuration example 285 Server Event Manager configuring 279 Server Execution User creating 232 described 20 recreating 235 troubleshooting 232 Server folder 269 Server Hostname Settings view 169 Server Information view 92 Server Se
Index User groups adding 130 default 130 deleting 137 removing users from 138 roles 133 setting attributes for 132 setting passwords for 132 User management guidelines 147 User Management view 128 Users adding from Avid Unity 116 adding manually 131 adding to a CCS 114 default 130 deleting 137 disconnecting all 98 importing 114 importing from LDAP 120 importing from Windows domain 118 list of connected 92 management guidelines 147 managing 128 removing from group 138 roles 133 setting attributes for 132 se
Avid Technical Support (USA) Product Information 75 Network Drive Burlington, MA 01803-2756 USA Visit the Online Support Center at www.avid.com/support For company and product information, visit us on the web at www.avid.
