Signiant Support

12.0 Avid Integration User's Guide Print


CHAPTER 1 Avid Integration
CHAPTER 2 Avid Architecture
CHAPTER 3 Avid Configuration
System Requirements
Agent Configuration
Installing Signiant Agents
Add/Edit Transfer Manager
Updating Transfer Manager Hosts
Restarting Transfer Managers
Transfer Managers List
Status
CHAPTER 4 Avid Transfers
Initiating an Avid Transfer
Monitoring Avid Transfers
Cancelling Avid Transfers
Avid Integration Maintenance
CHAPTER 5 Avid Components
CHAPTER 6 Avid Workflows
CHAPTER 7 Avid XML File
CHAPTER 8 Avid Transfer Manager Setup
Avid Transfer Manager Configuration
CHAPTER 9 Avid Troubleshooting
Avid Menu Missing Signiant Items
Avid Jobs not Created on Signiant Manager
Access Denied Errors in Job Log
Manager Restart Warning During Transfer
Media Directory Not Created During Transfer
Sequence Appears Off-Line After Successful Transfer

Avid Integration

The Signiant Avid integration allows users to employ Signiant media transfer technology with the Avid product to provide a managed, secure, accelerated transport mechanism among Avid workgroups. A Signiant Avid integration is made up of a central Signiant Manager and distributed Signiant agents. The Manager host should be a dedicated system, since it manages the agents and transfers. Each Avid Transfer Manager host involved in Signiant-accelerated Avid transfers has the Signiant agent software installed on it.

When a sequence or clip is ready for transfer, Avid users can choose Send to Workgroup from the Avid editor and specify the Avid workgroup to which to transfer the file(s). The agent that will transfer the files contacts the Signiant Manager through Simple Object Access Protocol (SOAP) calls. The Manager initiates the Signiant job, which transfers the media to the specified Avid Transfer Manager. Once the transfer is complete, users at the target Avid workgroup can view, open, and work on the transferred files. Note that the data only flows between the source and target Avid Transfer Manager systems – the data does not flow through, nor is it ever seen by the Signiant Manager.

Avid Architecture

The following diagram provides an overview of the software architecture and workflow implemented in the Signiant Avid Integration application.

Avid Configuration

The procedures required to install the Signiant product and Avid Integration application are a combination of automated and manual processes. The installation of the basic Signiant product is fully-automated via the Signiant Manager and Agent installer programs. However, some of the installation and configuration of the Avid Integration application require manual procedures.

A full installation and configuration of the Signiant Avid Integration application involves the following tasks:

  • Installing and configuring a Signiant Manager using the Signiant installer.
  • Installing and configuring multiple Signiant Agents using the Signiant installer
  • Configuring Avid Transfer Manager objects in the Signiant Manager Web Interface using the Signiant Avid Integration application.
  • Pushing configurations out to the target Avid Transfer Manager hosts.

System Requirements

You must be running Avid Interplay Transfer Engine version 1.2 or higher (for Avid Interplay environments) or Avid Transfer Manager version 2.9.7 or higher (for Avid Workgroup 4 environments). In Interplay-only environments, older versions of Interplay (1.1.2 or higher) can be a source, but not a target, for transfers. Interplay Transfer Engine version 1.2 on both sides of a transfer will ensure that the transfers can occur bi-directionally. Both Avid Unity MediaNetwork storage servers and Avid ISIS storage servers are supported by the Signiant Avid Integration application. The Avid software must be installed and functional on all relevant Avid hosts.

Agent Configuration

You must install the Signiant Agent software on all Avid Transfer Manager hosts involved in the Signiant-accelerated Avid transfers, and configure each of those agents. Signiant agent configuration involves the following tasks:

  • Installing Signiant Agents on Avid Transfer Managers
  • Defining Avid Transfer Manager Host Objects
  • Updating Avid Transfer Manager Hosts
  • Manually Restarting Avid Transfer Managers

Installing Signiant Agents

Install the Signiant agent software on each Avid Transfer Manager that will be part of a Signiant transfer. This includes workgroup and standalone Transfer Managers.

Add/Edit Transfer Manager

You define Avid Transfer Manager host objects in the Signiant Manager Web Interface. Transfer Manager objects are an extension of a Signiant agent, where the host is given a free-form name and has associated configuration parameters related to Avid Transfer Manager functionality. To define a Transfer Manager host object, follow these steps:

  1. From the Manager, click Administration > Integrations > Avid.
  2. Click Add Transfer Manager.
  3. Type a name for the Avid Transfer Manager in the Transfer Manager field. Names must be unique among Transfer Manager hosts. Names must be unique among Workstation hosts.
  4. Select a Signiant agent from the Uses Signiant Agent drop-down list.
  5. Click Add.
  6. In the Menu Item Name field, type a name for the menu item which you want the configuration to appear as in the Avid editing interface.
  7. Select an Avid Job Template Library from the dropdown menu.
  8. Select the Workflow Start Component from the dropdown menu.
  9. In the Prompts and SOAP tab, select items from the dropdown menus or accept the defaults.
    Prompt Description
    Target TransferManager The Avid TransferManager to which data will be transferred.
    Target UNC Path (workgroup) or Target Root Directory (standalone) The drive or UNC path where the "Avid MediaFiles" and/or "OMFI MediaFiles" directories are located.

    Use WAN Accelerator

     

    You must have a WAN Accelerator license in order to use this feature. Selecting "Yes" means that when the job runs, it will use UDP as the underlying transport, and will attempt to use all available bandwidth up to the user-specified bandwidth maximum. This configuration can result in a faster transfer rate than if it is not selected. The Use WAN Accelerator option should be used on high latency high bandwidth networks where throughput is a top priority.

    When running a job with "Use WAN Accelerator" set to "Yes", with a low bandwidth ceiling or low throughput, the transfer will be switched automatically to TCP. (The cutoff value is 57200 bits/second.)

    Note that bandwidth throttles may also be employed by other network devices and policies (e.g., QoS), therefore, a bandwidth throttle (or target maximum) defined here may not be achievable. If you are having difficulty achieving a particular bandwidth target ensure that other policies are not impacting your ability to reach the desired throughput.

    WAN Accelerator Aggressiveness

     

    Indicates how sensitive the WAN accelerator will be to other network traffic when it is running. Choose from one of the following:

    High: The agent will always attempt to send data at the Bandwidth Ceiling rate with no regard to other network traffic.

    Medium: The agent will always attempt to send data at the Bandwidth Ceiling rate, however, if packet loss is detected, the agent will gradually lower its transfer rate.

    Low: The agent will always attempt to send data at the Bandwidth Ceiling rate, however, if packet loss is detected, the agent will drop its transfer rate right away, and slowly attempt to increase it.

    Bandwidth Ceiling 

     

    (Applies only to WAN acceleration)

    The maximum rate at which the source will send the data on the network. Typically this is the maximum speed of the network (i.e., 100Mbps, 10Mbps, and so on). Zero means unlimited.

    (Note that testing has shown that specifying a ceiling is generally faster - as long as it is set correctly. This is because if the ceiling is set, the transfer immediately starts at that rate, rather than ramping up.)

    Click the calculator icon to calculate the amount of bandwidth as a percentage. Slide the bar to the percentage you want and click OK. The correct value appears in the Bandwidth Ceiling field.

    Bandwidth Throttles

     

    Click Add a new throttle. (You can specify up to four throttles.)

    Time-of-Day bandwidth throttles applicable to both WAN-accelerated and non-accelerated transfers. Note that you must use 24-hour time format to specify start and end times (i.e., enter 2:00 pm as 14:00). You can type directly in the field. Alternately, click the clock icon to specify 12- or 24-hour clock, choose the time and click OK. The time is converted to 24-hour clock time.

    You can also specify the rate unit in which the bandwidth is displayed (bytes/second or bits/second). You can also click the calculator icon to calculate the amount of bandwidth as a percentage. Slide the bar to the percentage you want and click OK. The correct value appears in the Maximum Bandwidth field.

    Note that bandwidth throttles may also be employed by other network devices and policies (e.g., QoS), therefore, a bandwidth throttle (or target maximum) defined here may not be achievable. If you are having difficulty achieving a particular bandwidth target, ensure that other policies are not impacting your ability to reach the desired throughput.

    Email To The email address of the person to receive the logging report. Separate multiple addresses with a comma.

    Email Condition

     

    Specifies when a job report is emailed to users specified in the Email Job Report To prompt. Choose from the following:

    • Always - Users receive a job report after every job run.
    • On Error - Users receive a job report after a job run that reports an error exit code.
    • Never - Users never receive job reports.
    Log Detail Level The type of logging information for this job. Choose from Error, Warn (warning), Info (Information) or Debug. Debug provides the greatest level of detail while Error provides the least.
    SOAP
    Controlling Signiant Manager The Signiant Manager used to create and run the SOAP job. The Manager name appears here by default.
    Create Jobs as User The Signiant Manager userid used to create and run the job. The Avid SOAP user is the default user.
    Password

    Type a password for the "Create Jobs as User" user name.

    Note: Do not change the password if you are using the (default) Avid SOAP user. The password is encrypted, and is unrecoverable through Signiant.

    Confirm Password Verify the password for the "Create Jobs as User" user name.
    Job Name Prefix The text to prepend to the Avid transfer job names.
  10. Click OK
  11. Click Save.
  12. Repeat for the number of Transfer Managers you want to define.

Changes do not take effect until you click Update in the Transfer Manager Listing screen. See the section Updating Avid Transfer Manager Hosts. After the update, you must restart the Avid Transfer Manager service on all affected Avid Transfer Managers.

Updating Transfer Manager Hosts

Once you have defined at least one Transfer Manager object and its targets, you may update it. Updating the Transfer Manager hosts accomplishes the following:

  • Installs/updates any required binaries and DLLs on the Transfer Manager hosts (source and targets).
  • Builds the Avid Dynamically Extensible Transfer (DET) configuration files and pushes them out to the appropriate Transfer Manager hosts. The DET configuration files instruct the Transfer Manager on settings for Avid-to-Avid transfers. See DET Vendor XML Files for the structure of these configuration files.

Restarting Transfer Managers

In order to make the appropriate "Send to Workgroup" items available in the Avid editor interface, it may be necessary to manually restart the source Avid Transfer Managers after performing a Transfer Manager update. The restart is required under the following conditions:

  • A new target configuration has been configured for a given source-target Transfer Manager pair.
  • A target configuration has been modified or renamed for a given source-target Transfer Manager pair.
  • A target configuration has been deleted for a given source-target Transfer Manager pair.

Transfer Managers List

The list presented under Administration > Integrations > Avid shows the Avid Transfer Managers that have been defined on the Signiant Manager. The Configuration Status column indicates if the target system currently needs updates of software and/or configurations. Requires Update appears in the status column when there is a new or updated configuration that affects the given Transfer Manager. Other values that may appear in the Configuration Status column are Up To Date, Update Running, and Failed Update. This screen also allows users to do the following:

  • add, edit, and delete Avid Transfer Managers from the system.
  • update Avid Transfer Managers that require updating, or update all Transfer Managers.

Status

When Avid Transfer Managers are "updated" via the Signiant Manager, a Signiant job is launched which performs all of the update work. The status and logs of the job used in the update process can be viewed by examining the "Avid_TM_Update" job. You can examine this job by doing the following:

  1. Click on Jobs > Groups.
  2. Click on AvidTMUpdates.
  3. Click on View Jobs in Group.

There will be a single job in this group called "Avid_TM_Update". This job is run every time the Avid Transfer Manager update process is performed.

Avid Transfers

After installing and configuring the Signiant Avid Integration application, you can run and monitor Avid transfers.

Initiating an Avid Transfer

Once you have configured an Avid TransferManager, its associated menu items and issued an Update in the Signiant Manager Web Interface, a menu item is available in the Avid editor for each configured workflow.

  1. Highlight the item in the source bin.
  2. Right-click the item and select Send To Workgroup.
  3. Select the workflow to launch.

    There may be multiple items available under Send To Workgroup. Those that use Signiant workflows are identified by the (Signiant) suffix, for example,  Avid-1 (Signiant).

Monitoring Avid Transfers

Avid transfers may be monitored by examining the jobs in the AvidTransfers job group. You can examine these jobs by doing the following:

  1.  Click on Jobs > Groups
  2. Click on AvidTransfers
  3. Click on View Jobs in Group

There will be job in this group for every new Signiant-enabled Avid transfer. You can also monitor Avid transfer jobs using the Avid editor's Transfer Status utility. Any job that fails will show a status of Cancelled (rather than Failed) in the Avid Transfer Status window. This is an inherent behavior of the Avid interface. Cancelled therefore means Not successful, for whatever reason.

Cancelling Avid Transfers

To cancel an Avid transfer, follow these steps:

  1. From the Manager, select Job>Groups.
  2. In the display area, click the name of the job group (AvidTransfers).
  3. In the toolbar, click View Jobs in Group.
  4. In the display area, click the name of the job you wish to cancel.
  5. In the toolbar, click Cancel.

The Avid Editor Transfer / Status Window facility, highlight the transfer, right-click on the item, and select Cancel.

Avid Integration Maintenance

This section describes the following Avid Integration application maintenance activities:

User Accounts

A special Signiant account is created during the Signiant Manager installation: avid_soap. This user account is intended to be used only for creating Avid jobs via SOAP. Since it has a strong, randomly-generated password, there should be no need for an administrator to ever change it. However, if an administrator does change the avid_soap password for the user under the Manager Web Interface Administration>Users menu, then the following must also be done:

  1. Set the same password in all of the TransferManager configurations that use that same userid (in the SOAP tab for each Avid Transfer Manager menu item).
  2. Push these configurations out by clicking the Update button in the Transfer Managers screen. 

    Setting the password for a user under the Administration>Users>Groups menu and on the TransferManager forms are separate actions (that is, they are not automatically synchronized). If you change a password, you must do so in both places.

Access Permissions

Access permissions are maintained for all menu items.

Agent Remote Access Permissions

All agents require an access permission for the default user. For Avid transfers, the default user must have the ability to read (source end) and write (target end) the Avid media files.

  • In a standalone configuration, the default user can be NT Authority\System. If the NT Authority\System account does not have sufficient privileges, set a default user on those systems that does have sufficient privileges.
  • For Workgroups, configure a local or domain user who has access to the target workgroup workspace (fileshare). The System account cannot be used for workgroups since it does not have access to any network resources (e.g. file shares).

Job Maintenance

Avid transfer jobs run only once, so a new job is defined and run for every transfer. These jobs should be cleaned up (deleted) periodically. For more information on Manager maintenance and job cleanup.

Log Maintenance

Avid Transfer jobs use Log Filename delivery mode. For every Avid transfer, a file is generated under:

<install_dir>\log\delivery_logs

These should be deleted periodically. For information on creating log maintenance jobs.

Avid Components

The Signiant Avid Integration application provides the means to launch workflows from an Avid editor for a selected set of media files. The reference workflows included with the Signiant Avid Integration application enable the transfer of content from one Avid system to another, using the Avid TransferManager Dynamically Extensible Transfers (DET) API.

The following graphic illustrates the sample Avid Workflow components:

There are three distinct parts to the Signiant Avid workflows: launch, execution, and reporting.

  • The AvidEditorStart component (renamed AvidtoAvidReference in this example) specifies the parameters relating to scheduling the workflow, such as when and how the job should run.
  • The AvidtoAvidTransfer component transfers an optimized list of media files from one system to another and then uses Avid APIs to ingest the media into the target system.
  • The JobReport component provides summary information on the completion status of the workflow.

Workflows are built in the canvas of a Job Template Library, using the components in the toolbox.

  • AvidEditorStart

    The AvidEditorStart component is used as the launch point of Avid workflows initiated from the Signiant-Avid plugin on Avid TransferManager systems.

  • AvidtoAvidTransfer

    This is the type of file transfer used in the reference Avid TM to Avid TM transfer, where the source, and more importantly the target, storage are on Avid-managed storage systems (note that this includes standalone systems where a standalone TM is monitoring the storage). The key differentiators between this file transfer and a generic Signiant file transfer is that there is a custom filename mapping command that determines whether files really need to be transferred based or whether they already exist at the target; this type of functionality is normally native to the agent, but since a temporary directory is being used for the transfer none of the source files exist in that temporary directory so the comparison must be made against the "final" Avid directories instead.

    This file transfer component performs the following major functions:

    • Validates that the target Avid directories exist.
    • Creates a temporary directory within the Avid-managed filesystem to which the media files will be transferred.
    • Transfers the files to the temporary directory.
    • For each media file that has been transferred to the temp directory, determine its extension and move it to the appropriate "final" Avid media directory.
    • Refresh the Avid PMR databases so that the file locators are set correctly via calls to the Avid PMR API.
    • Import the master metadata file via the Avid TM-Auto API. For the Signiant workflow version, the master metadata file has been determined by the DET DLL and passed to the job as a variable.
  • AvidIngestMedia

    This remote command is responsible for ingesting the sequence metadata into the target TransferManager via the Signiant SigAvidTMA utility. It performs the following major functions:

    • For each media file that has been transferred to the temp directory, determine its extension and move it to the appropriate Avid media directory.
    • Refresh the Avid PMR databases so that the file locators are set correctly via calls to the Avid PMR API.
    • Import the master metadata file via the Avid TM-Auto API. For the Signiant workflow version, the master metadata file has been determined by the DET DLL and passed to the job as a variable.
  • AvidResolveExistingMedia

    This remote command is responsible for producing an optimized list of files to send, based on examining the files to send and the files already at the target end. It performs the following major functions:

    • Validates that the target Avid directories exist.
    • Creates a temporary directory on the target TM to which the media files will be transferred.
    • Compares the full list of files to be sent with those already at the target and creates an output with the optimized file list.
  • JobReport

    Specifies that a job report be sent to specified users. These are sent depending on specified exception handling conditions. For example, if the job fails, the report may go to different recipients than if the entire job succeeds.

Avid workflow components use some properties that are specific to Avid and others that are common to other Signiant components. The four Avid components AvidEditorStart, AvidIngestMedia, AvidResolveExistingMedia and AvidtoAvidTransfer use the properties described in the following table:

Component Property Description
AvidEditorStart Source Agent The agent of the source Avid TransferManager. This value is set by the Signiant-Avid DET DLL.
  Media File List The list of files to transfer (essence + metadata). This value is set by the Signiant-Avid DET DLL.
  Metadata File The master metadata file to ingest on the target TransferManager. This value is set by the Signiant-Avid DET DLL.
AvidToAvidTransfer Source Agent The agent of the source Avid TransferManager. This value is set by the Signiant-Avid DET DLL
  Media File List The list of files to transfer (essence + metadata). This value is set by the Signiant-Avid DET DLL.
  Metadata File The master metadata file to ingest on the target TransferManager. This value is set by the Signiant-Avid DET DLL.
  Target Agent The agent (target TransferManager) to which the media is being sent.
  Target Directory The base directory where the media is to be delivered. For workgroup mode, this must be the UNC path containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders. For standalone mode, this is normally a local drive (but could also be a UNC path) containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders.
  Use WAN Accelerator Enable/disable WAN accelerated transfers
  Enable/disable WAN accelerated transfers UDP transfer aggressiveness
  Bandwidth Ceiling Bandwidth ceiling
  Bandwidth Throttle by Time of Day Bandwidth throttle by time of day
AvidResolveExistingMedia Target Agent The agent (target TransferManager) to which the media is being sent.
  Target Directory The base directory where the media is to be delivered. For workgroup mode, this must be the UNC path containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders. For standalone mode, this is normally a local drive (but could also be a UNC path) containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders.
  Media File List The list of files to transfer (essence + metadata). This value is set by the Signiant-Avid DET DLL.
AvidIngestMedia Target Agent The agent (target TransferManager) to which the media is being sent.
  Target Directory The base directory where the media is to be delivered. For workgroup mode, this must be the UNC path containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders. For standalone mode, this is normally a local drive (but could also be a UNC path) containing the "Avid MediaFiles" and/or "OMFI MediaFiles" folders.
  Metadata File The master metadata file to ingest on the target TransferManager. This value is set by the Signiant-Avid DET DLL.

Avid Workflows

The Avid_Workflows template library contains three workflows:

  • AvidToAvidReference
  • AvidToAvidComponentized
  • AvidTMUpdate

The first two workflows (AvidToAvidReference and AvidToAvidComponentized) accomplish the same thing. They are provided as two separate workflows to illustrate different ways of using workflow components to accomplish a given task. The third workflow (AvidTMUpdate) is the internal-use only workflow that is employed by the Avid Transfer Manager Update process (i.e. it is launched when the user clicks on the Avid "Update"button.

The following graphic illustrates the Avid workflows:

Avid XML File

The DET vendor XML files on the source Transfer Manager for each target Transfer Manager contain the parameters used to create and control the Signiant-accelerated transfer jobs. You can edit the vendor XML files using a text editor.

The following table describes the Dynamically Extensible Transfer (DET) vendor XML files used to create and control the Signiant-accelerated transfer jobs.

Tag Description Default Value
ServerName The hostname of the Signiant Manager on which the transfer job will be created. (none)
UserName The Signiant Manager userid used to create and run the job. Admin
Password The password for the above userid (encrypted). (none)

DisplayNamePrefix

 

The name to display for this transfer target in the Avid editor's "Send To Workgroup…" menu.

(none)

 

JobLibrary The Signiant job library containing the transfer template. Avid_Integration
JobTemplate The name of the Signiant transfer template to use for the job. Avid_Transfer
Job Group The job group under which to create the transfer job. AvidTransfers
JobNamePrefix The prefix to use for the job name. A large sequential number will be suffixed to the job name. Avidxfer
TimeZone The timezone to use for log messages. GMT
SourceHost The source host of the transfer (must match the local hostname). (none)
TargetHosts The target host for the transfer (must match the hostname of the target Transfer Manager). (none)
TargetMode The mode of the target Transfer Manager: Standalone or Workgroup. (none)
TargetDirectory The media drive on the target system to use for the transfer. This may be a UNC path (e.g., \\hostname\share) or a root drive (e.g., Y:\). It is important that this be a drive that contains the Avid media directories. (none)
TargetWorkspace For workgroup transfers, this is the name of the workspace to check the media into on the target Transfer Manager. (none)
WanAcceleratorAggressiveness How sensitive the WAN accelerator will be to other network traffic when it is running. medium
BandwidthCeiling The bandwidth ceiling, in Kbps. 0 means unlimited. 0
BandwidthThrottles Time-of-Day throttles None
EmailCondition The condition under which an email notification/report is sent. Valid conditions are "Always", "On Transfer", "On Error", "Never".

On Error

 

EmailContact The email address(es) to which to send the notification/report. (none)
JobLogDetailLevelVar The log level to use for the job (0=Errors, 1= Warnings, 2 = Info, 3 = Debug). The larger the number, the more logging information is generated. 2

The DET vendor XML files normally exist under the directory: C:\Program Files\Avid\Avid Interplay Transfer Engine\DET\Vendors

The following is a sample vendor XML file:

 <DETVendorParams version="1.0">
	<Vendor>Signiant</Vendor>
	<DLLPath></DLLPath>
	<PushDLLVersion>1.0</PushDLLVersion>
	<PullDLLVersion></PullDLLVersion>
	<RemoveDLLVersion></RemoveDLLVersion>
	<IterateDLLVersion></IterateDLLVersion>
	<PushDLLName>SigAvidDET</PushDLLName>
	<PullDLLName></PullDLLName>
	<RemoveDLLName></RemoveDLLName>
	<IterateDLLName></IterateDLLName>
	<ServerName>imac1-win.ott.signiant.com</ServerName>
	<UserName>avid_soap</UserName>
	<Password>********</Password>
	<MaxPushSessions>4</MaxPushSessions>
	<MaxPullSessions>4</MaxPullSessions>
	<BlockMoveSize>4096</BlockMoveSize>
	<DisplayNamePrefix>IMAC1 (Signiant)</DisplayNamePrefix>
	<PrivateData>
		<JobLibrary>Avid_Workflows</JobLibrary>
		<JobTemplate>AvidtoAvidReference</JobTemplate>
		<JobGroup>AvidTransfers</JobGroup>
		<JobNamePrefix>AVIDxfer_imac1_standalone_IMAC1</JobNamePrefix>
		<TimeZone>GMT</TimeZone>
		<AvidtoAvidReference.SourceAgent>imac1-win.ott.signiant.com</AvidtoAvidReference.SourceAgent>
		<AvidtoAvidReference.BandwidthCeiling>0</AvidtoAvidReference.BandwidthCeiling>
		<AvidtoAvidReference.BandwidthThrottles>00:00;00:00;NNNNNNN;0;</AvidtoAvidReference.BandwidthThrottles>
		<AvidtoAvidReference.EmailCondition>Always</AvidtoAvidReference.EmailCondition>
		<AvidtoAvidReference.EmailTo></AvidtoAvidReference.EmailTo>
		<AvidtoAvidReference.JobScheduleGroup._sp_log_severity>2</AvidtoAvidReference.JobScheduleGroup._sp_log_severity>
		<AvidtoAvidReference.TargetTransferManager>imac1-win.ott.signiant.com</AvidtoAvidReference.TargetTransferManager>
		<AvidtoAvidReference.TargetUNCPathWorkgroupOrTargetRootDirectoryStandalone>C:\</AvidtoAvidReference.TargetUNCPathWorkgroupOrTargetRootDirectoryStandalone>
		<AvidtoAvidReference.UseWANAccelerator>yes</AvidtoAvidReference.UseWANAccelerator>
		<AvidtoAvidReference.WANAcceleratorAggressiveness>medium</AvidtoAvidReference.WANAcceleratorAggressiveness>
	</PrivateData>
</DETVendorParams>
             

Avid Transfer Manager Setup

While complete and in-depth information on how to set up Avid Transfer Managers is beyond the scope of this guide, this appendix provides general steps on how to complete these tasks. For detailed information on Avid Transfer Managers, see the appropriate Avid product documentation.

Before you install the Signiant Avid Integration application, ensure that the Avid Transfer Managers are set up.

Avid Transfer Manager Configuration

Ensure that the following configurations are enabled.

Interplay Workgroup

  • Interplay Enabled: (check)

  • Interplay Engine Hostname: (The hostname of the Avid Media Manager.)
  • Accept incoming transfers without Interplay login: (check)
  • No-login workspace for incoming transfers: (A valid workspace name.)
  • Workgroup transfers enabled: (check)
  • Incoming workgroup transfers enabled: (check)
  • Max simultaneous workgroup transfers: (1-10)

Workgroup 4 Workgroup (i.e., MediaManager)

  • Asset Manager Enable: (check)
  • Asset Manager Hostname: (The hostname of the Avid Media Manager.)
  • Accept incoming transfers without MediaManager login: (check)
  • No-login workspace for incoming transfers: (A valid workspace name.)
  • Workgroup transfers enabled: (check)
  • Incoming workgroup transfers enabled: (check)
  • Max simultaneous workgroup transfers: (1-10)

Standalone Transfer Manager/Transfer Engine

  • Accept incoming transfer after timeout: (check)
  • Timeout: 1
  • OMF/AAF: (The default media mode for the Transfer Manager/Transfer Engine.)
  • Directory for incoming transfers: (Root directory where incoming media is to be stored.)

All environments

  • Max DET push transfers: (1-10)

    Note: Set this to more than 1 only if the source system has very fast disk storage; otherwise multiple concurrent transfers are counter-productive due to disk-thrashing (that is, sequential Signiant transfers are faster if the disk is not very fast).

  • Max simultaneous transfers: (range: 2-10)

Avid Troubleshooting

This section presents some common Avid integration issues and suggestions for solving them.

Avid Menu Missing Signiant Items

Symptom

No Signiant menu items appear under Send to Workgroup in the Avid editor.

Possible Causes

  1. Transfer Manager configurations have not been defined and pushed-out (that is, updated) from the Signiant Manager.

    Remedy: Create the appropriate Transfer Manager configurations. Click Update in the Signiant Manager User Interface.

  2. The source Avid Transfer Manager has not been restarted. A Transfer Manager restart is required when new Target Transfer Managers (menu items) are configured for a given source Transfer Manager.

    Remedy: Restart the given source Avid Transfer Manager.

    Once a given target Transfer Manager has been defined and pushed out to a particular source Transfer Manager, updates to that configuration can be pushed-out without requiring a Transfer Manager restart. Transfer Manager restarts are required only when new targets are defined, or when existing targets are deleted.

  3. Avid editor is not connected to its Transfer Manager.

    Remedy: Connect to the Transfer Manager.  Before you do this, ensure that the Avid Transfer Manager client has been installed and configured.

Avid Jobs not Created on Signiant Manager

Symptom

No Avid transfer jobs being created on the Signiant Manager.

Possible Causes

  1. The values Controlling Signiant Manager, Create Jobs as User, or Password have not been set properly under Transfer Managers in the Signiant Manager User Interface.

    Remedy: Set the proper values and update the appropriate Transfer Managers.

  2. User may have been deactivated in the Signiant Manager because of too many failed logins.

    Remedy: Activate the user in the Signiant Manager.

    If no jobs are being created, look for applicable error or warning messages in the Avid Transfer Manager console window.

Access Denied Errors in Job Log

Symptom

Access denied or directory inaccessible errors occurring in the job log when attempting to read the media files on the source Transfer Manager or write the files on the target Transfer Manager.

Possible Causes

  1. The default user on the source or target agent does not have sufficient privileges to read (source) or write (target) the files. The user NT Authority\System may not have sufficient privileges, especially where the media drives are accessed via CIFS.

    Remedy: Configure the Signiant default user on the affected system to be one that has sufficient privileges. A privileged local account or a domain account may be required.

Manager Restart Warning During Transfer

Symptom

Warning occurs during transfer: Media directories were created successfully but Transfer Manager must be restarted in order for subsequent transfers to be successful.

Possible Causes

  1. The required media directories had not been created before running the first transfer and have now been created, but the Transfer Manager will not monitor them until it is restarted.

    Remedy: Restart target Transfer Manager and re-run the transfer.

Media Directory Not Created During Transfer

Symptom

Error occurs during transfer: Failed creating media directory: <directory_name> - Please manually create this directory and restart the Transfer Manager before performing any transfers.

Possible Causes

  1. The required media directories do not exist and could not be created by the job.

    Remedy: Create the required media directories manually, restart the target Transfer Manager, and re-run the transfer.

Sequence Appears Off-Line After Successful Transfer

Symptom

Media transfers successfully but sequence appears offline in MediaManager interface (Workgroup 4).

Possible Causes

  1. The media was transferred to new folders that the Transfer Manager is not monitoring.

    Remedy: Stop and restart the Transfer Manager.

Symptom

Media transfers successfully but sequence appears offline in Interplay interface.

Possible Causes

  1. The media was transferred to folders that Interplay is not currently indexing.

    Remedy: Using the Avid Interplay Service Configuration Utility, select the Avid Interplay Media Indexer for the appropriate Interplay system and then select Configure Storage. Make sure that all appropriate media folders are listed under Media Table.