3.2
Table Of Contents
- Title Page
- Contents
- Using This Guide
- Getting Started with the Interplay | Administrator
- Database Settings
- Creating an Interplay Database
- Interplay Databases, Folders, and Files
- Creating and Restoring Database Backups
- Types of Interplay Administrator Backups
- Recommendations for Backup Configuration
- Setting the Number of Database Backups to Keep
- Scheduling Automatic Database Backups
- Starting a Backup Manually
- Using an Archiving Tool for Backup
- Restoring an Earlier Version of a Database
- Performing a Partial Restore of an Interplay Production Database
- Creating a Metadata-Only Backup for Customer Support
- Performing a Consistency Check
- Viewing Database Information
- Locking and Unlocking Databases
- Managing Databases: Deactivating, Activating, and Migrating
- Moving a Database to Another Server (Non-Clustered Systems)
- Moving a Database and Users to Another Server (Non-Clustered Systems)
- Moving a Database to Another Server (Clustered Systems)
- Moving a Database and Users to Another Server (Clustered Systems)
- Moving a Database Under Low Disk Space Conditions
- Renaming a Database
- Running Database Maintenance Tools
- Identifying the Root Folder of the Interplay Server Database
- Server Settings
- User Management
- Understanding the Central Configuration Server
- Adding Users to a Central Configuration Server
- Setting User Authentication Providers and Importing Users
- Managing Users, User Groups, and User Rights
- Understanding Default User Groups, Users, and Roles
- Adding User Groups
- Adding Users Manually
- Viewing and Setting Attributes
- Understanding Standard Roles and Default Rights
- Viewing and Changing Roles
- Viewing and Setting Authentication Providers for Individual Users
- Deleting Users and User Groups
- Removing Users from User Groups
- Managing Database Roles
- Guidelines for User Management
- Site Settings
- Defining Property Layouts
- Setting the Resolutions Available for Display
- Creating Custom Properties
- Configuring Remote Workgroups
- Configuring Categories
- Setting Server Hostnames and the Workgroup Name
- Interplay Media Services View
- Interplay Transfer Status View
- Interplay Transfer Settings View
- Workgroup Transfer Presets View
- Specifying Remote Servers for Asset Tracking
- Specifying Archive Settings
- Setting the Ownership for New Database Folders
- Enabling Interplay Synced Projects
- Setting Options for Deletion
- Viewing and Setting the Metadata Override Status
- Production Engine Bus Connector
- Application Settings
- Application Database Settings View
- Setting Options in the Editing Settings Tab
- Setting Audio Mixing Defaults for Access, Assist, and MediaCentral | UX
- Sending a Source to Playback in Interplay Assist
- Setting the Shotlist Start Timecode for Interplay Access and Interplay Assist
- Setting an Automatic Timeout for Interplay Assist and Avid Instinct
- Configuring the Frame Locators Display
- Configuring the Restrictions Display
- Media Composer | Cloud Settings
- Setting Instinct/Assist User Options
- Pro Tools Plug-Ins Settings
- Application Database Settings View
- Interplay Services
- Troubleshooting
- Reuniting a Split Database
- Installed Components and Services
- Interplay Engine Configuration Files
- Valid and Invalid Characters in Interplay
- System Metadata Properties
- Server Error Codes
- Consistency Check Codes
- Index
Managing Licenses
99
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 MediaCentral 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.
n
To run MediaCentral and other applications concurrently with a single license, the client
workstation must be connected to the same LAN as the MediaCentral server. The client
workstation must have a correct DNS entry and the ICS server must be configured to resolve the
client workstation’s hostname.
The Interplay Engine uses “smart licensing” to manage Base and Advance licenses to allow
optimum usage of free licenses. It assigns an Advance license to a Base client if a Base license is
not available. It switches the assignment if an Advance client needs a license and a Base license
becomes available. For example:
1. Client 1 requires a Base license, and is assigned the last free Base license. Client workstation
2 requires a Base license, but only an Advance license is available. Workstation 2 is assigned
an Advance license.
2. Client workstation 1 logs out from the application, and a Base license is freed.
3. Client workstation 3 requires an Advance license, but only a Base license is available.
Workstation 2’s license is switched to a Base license and workstation 3 is assigned an
Advance license.
The following figure illustrates this example.
Client 1
Base
Client 2
Base
Client 3
Advance
KEY-G
Base
KEY-J
Advance
Client 1
Base
Client 2
Base
Client 3
Advance
KEY-G
Base
KEY-J
Advance
Client 1
Base
Client 2
Base
Client 3
Advance
KEY-G
Base
KEY-J
Advance
qq qwe
Clients 1 and 2 logged in Client 1 logs out, Base license free Client 3 logs in