You must continue to configure DIVAdirector after the Oracle Delivery and Installation Team has completed the initial installation. You typically complete the initial configuration tasks in this chapter one time unless there are major system or network changes (for example if IP addressing changes, port numbers change, and so on).
This chapter describes initial configuration after installation and includes the following information:
The installation technician installs DIVAdirector using a default administrative login and password, both of which are admin (these are case-sensitive and all lowercase). You will be prompted to change the DIVAdirector administrative password when you log in for the first time.
DIVAdirector interacts with DIVArchive using a standards-based Web Service API. The integration with this service, Oracle DIVA Enterprise Connect (DIVAEC), is configured in two different configuration files in DIVAdirector. Both of these files should be configured automatically during the installation process. However, Oracle recommends manually verifying the configuration.
The first file is web.config located in the www folder in the installation directory (for example, C:\Program Files (x86)\DIVAdirector 5\www\web.config). The second file Oracle.DIVAdirector.TaskManager.exe.config located in the TaskManager subdirectory in the installation directory (C:\Program Files (x86)\DIVAdirector 5\TaskManager\Oracle.DIVAdirector.TaskManager.exe.config).
The following keys are duplicated in the appSettings section of both files:
DIVArchiveApiUrlThis key identifies the URL of the Oracle DIVA Enterprise Connect endpoint.
<add key="DIVArchiveApiUrl" value="https://server:9444/diva/service/rest/2.2/DIVArchiveWS_REST" />
DWSVersionThis key identifies the version of the API Service DIVAdirector will target.
<add key="DWSVersion" value="2.2" />
ClientIdThis key identifies the user name to connect to the API. This value is generated on the DIVA Enterprise Connect server.
<add key="ClientId" value="e3af4c10-e7ca-4143-970a-46bc0264a46f" />
ApiKeyThis key identifies the password to connect to the API. This value is generated on the DIVA Enterprise Connect server.
<add key="ApiKey" value="kAkWTK3ObnEOmHheJAKP" />
AppNameThis key identifies the name of the application invoking the services. This value is used when creating a client session.
<add key="AppName" value="DIVAdirector" />
ProcessIdThis key identifies the ID of the client process that is executing, or another unique ID that identifies the instance of the application that is executing. This value is used when creating a client session.
<add key="ProcessId" value="1234" />
LocationNameThis key identifies a string describing the location of the client (caller). This value is used when creating a client session.
<add key="LocationName" value="DIVAdirector Web" />
Use the following procedure to confirm that Oracle DIVA Enterprise Connect is operational:
Open a Web Browser from the DIVAdirector Server.
Navigate to http://server:7001/ws_utc/login.do.
If you are able to log in to the Try It interface, then the service is operational. Otherwise, consult the Oracle DIVA Enterprise Connect documentation to resolve any issues with the service.
Now that you have configured all of the network and system connectivity, you must configure the internal system parameters that affect how users interact with DIVAdirector and DIVArchive. To configure the DIVAdirector user interface navigate to the Admin, System menu tree on the left side of the GUI screen.
First you will configure the System Settings.
The Defaults screen enables configuration of systemwide default values. For example, the language that search metadata is collated in, the global date and time display format, and so on.
Navigate to the Defaults screen under the Admin, System menu tree on the left side of the GUI.
Enter the appropriate values that are optimal for your organization and users for each option.
As the System Administrator you can identify most of these values according to existing organizational policies and your physical location. For example, calendar display format, time display format, and so on.
The following fields are configurable in the Default Settings area of the screen:
Caution:
Recalculating your search language is an exhaustive database procedure and should be completed only during a maintenance window of at least eight hours with the guidance of Oracle Support.Defines the language used to optimize full text search. If your metadata is mainly not in a particular language, or your language is not in the list, then select the Simple option.
Defines a metadata column that is used as the primary source for sorting.
Defines the format used for all date-type fields in DIVAdirector.
The list includes three format options.
American - mm/dd/yyyy
European - dd/mm/yyyy
Custom - This option does not support any codes except dd, mm, yy, and yyyy. The order of the codes is arbitrary and can be whatever you define (can be defined in a relatively free-style format, for example yyyy.dd.mm). The allowed separator symbols are:
Space
Period
Comma
Underscore
Hyphen
Colon
Slash
Backslash
Defines whether the time is displayed in 12 hour or 24 hour format.
Defines the first day of the week in the calendar.
Defines the maximum number of characters to display in the Tooltips label. If the metadata field title exceeds this setting it will be truncated with three dots at the end.
Defines the maximum number of characters to display in Tooltips content. If the metadata field value exceeds this setting it will be truncated with three dots at the end.
Defines the transcoding workflow that handles frame extraction for shot list segments and annotations.
Define a user defined metadata field to replace the name of downloaded files. The metadata field must be of the Text type and must have a length of 100 characters or less to be selectable.
Note:
This option is only visible if enabled through the Web.Config file.The following field is configurable in DIVArchive Settings area of the screen:
Defines a user defined metadata field to replace the name of downloaded files. The metadata field must be of the Text type and must have a length of 100 characters or less to be selectable.
Note:
This option is only visible if enabled through the Web.Config file.This field is the physical path of the virtual directory that local archive files are being stored in. Generally this field is populated during installation, but you can modify it here if needed.
The following field is configurable in the Connections area of the screen:
Defines the external url of the DIVAdirector server such that password recovery links and Oracle Client Uploader installers can be used from outside the network.
DIVAdirector 5.3 and later licensing is per user, not per concurrent user. You set the maximum number of concurrent users (between 1 and 100) in this field. If no entry is made, the default number of users (100) is used. The maximum number of concurrent users is restricted by the amount of system resources available. If the system appears to slow down with a certain number of concurrent users online, you should lower the maximum number and reevaluate the performance.
The following fields are configurable in the Housekeeper File Management Settings area of the screen located under Admin, System, Service Settings, House Keeper:
Defines the number of days to keep the files that have been restored to the DIVAdirector Server host computer through all local request operations (Restore, Partial File Restore, Archive folders, and so on).
Defines the number of days to keep the DIVArchive status information on the Operation Status screen.
Defines the number of days to keep the audit trail and Drop Folder log information.
Defines the retention policy for all DIVAdirector logs.
Defines the number of days to keep backup files created by scheduled backups.
The following fields are configurable in Database Pre-Caching Settings area of the screen:
Displays the current memory use on the server.
Defines which tables, if any, are to be held in memory for easy access. This can dramatically speed up certain functional areas of the application.
Next you will configure the System Synchronization.
The System Synchronization page enables configuration of frequency and size of synchronization actions between DIVAdirector and DIVArchive. You can also observe synchronization tasks, downloadable logs for each task execution, set flags to permanently delete objects that no longer exist within the archive system, or delete proxies that have been removed on this screen.
Navigate to the Synchronization screen under the Admin, System navigation tree on the left side of the GUI.
You can adjust the frequency and size of each synchronization call under the Automatic Synchronization section on the top right of the screen.
Note:
For systems that have numerous files per object, you should lower the Objects Per Call value. The lower value slows the rate of synchronization, while avoiding any potential request timeouts.You can stop, or start, synchronization at any time by clicking Stop/Start above the Synchronization Tasks list. Stopping synchronization cancels any currently executing synchronization task.
Caution:
Synchronization processes are highly demanding and will result in some performance degradation until they are complete. You must only run manual synchronization operations during off hours, or at the request of Oracle Support.You can perform a manual synchronization at any time. Performing a manual synchronization supersedes any active automatic synchronization currently processing. Automatic synchronization will resume after all manual tasks are complete.
There are three types of Manual Synchronization as follows:
A Partial Synchronization specifies that synchronization will occur from a given date forward. Only objects that were removed from the archive system within this period will be marked as inactive.
A Full Synchronization will synchronize the entire contents of the archive system. A full synchronization initially marks all objects in a Synchronizing state. In this state they will still be searchable, but DIVArchive operations will not be allowed until they have been moved back to an Active state. Any objects that were not found during synchronization will be marked as Inactive. Inactive objects are not reflected in search results.
Similar to Full Synchronization, this option will synchronize the entire contents of the archive system. This option assumes that large portions of the current synchronized objects are invalid and will initially mark all objects as Inactive.
You can configure two housekeeping flags to cleanup synchronization artifacts as follows:
This button notifies the housekeeper to permanently delete objects marked as Inactive by the synchronization process once per day. Proxies and binary files associated with deleted objects are moved to the deleted folder in their respective proxy storage location.
This button notifies the housekeeper to permanently delete all files contained within the deleted folders on each proxy storage location.
Synchronization filters define which objects are processed during synchronization. Each synchronization filter represents a combination of an object's parameters such as object name, object category and media name, and has its own time of last synchronization. Parameters can be defined as masks using the asterisk wildcard. By default the asterisk is set for fields that are empty. Filters with an asterisk in all three fields are invalid and cannot be added to the filter list.
All synchronization filters are inclusive of each other and are maintained by their own synchronization process. Because they are inclusive, the ordering of the filters does not matter.
You must issue a New Instance manual synchronization (as previously described) if you have added filters after DIVAdirector has already been synchronized and want to remove objects that do not conform to the new filters. This manual synchronization will mark all objects that were not found within these filters as Inactive and they can be removed during housekeeping.
Next you will configure the Keyboard Shortcuts.
Caution:
You must be careful during configuration of keyboard shortcuts because they may coincide with hot keys used in internet browsers or other software, and cause unexpected results.Keyboard shortcuts save time when performing common routine procedures during daily work tasks. DIVAdirector has hot key combinations that are predefined and configured automatically during installation.The Proxy Player can be run in two different modes; Shotlist Mode and Proxy Player Mode. There are two corresponding subsections in the Admin, System, Shortcuts navigation tree - one for each mode. Each subsection defines the keyboard bindings for the player in that specific mode. You should assign keyboard shortcuts for the Proxy Player in each mode.The following hot key combinations are predefined in DIVAdirector:
Edit
Rewind x4
Rewind x8
Fast Forward x4
Fast Forward x8
Add
Frame Back
Decrease Volume
Forward
Mark In
Loop
Mute
Frame Forward
Mark Out
Play or Pause
Rewind
Stop
Switch Time Format
Increase Volume
Mark Out and Add
Use the following procedure to change the shortcut key combinations for either subsection:
Navigate to the Admin, System, Shortcuts, Shotlist Shortcuts screen, or to the Admin, System, Shortcuts, Player Shortcuts screen, as applicable.
Click the Pencil icon to edit the desired hot key combination.
Select the required combination of Control+ Shift {Key}. Where {Key} is the key to assign to the shortcut.
Click the Check mark to save the changes.
Test all of the configured hot keys, one at a time, to ensure there are no conflicts with other applications installed on the system.
You configure hot keys used to perform routine functions with the Proxy Player in Shotlist Mode on the Admin, System, Shortcuts, Shotlist screen in the navigation tree on the left side of the screen. Click the Pencil icon to edit existing shortcut combinations.
The Proxy Player is the default player mode. You configure hot keys used to perform functions with the Proxy Player in the default Play mode on the Admin, System, Shortcuts, Player screen in the navigation tree on the left side of the screen. Click the Pencil icon to edit existing shortcut combinations.
Next you will add your organization's logo.
If required, you can quickly customize the interface style with an organizational logo that appears on all GUI screens in the top right corner of the screen. Use the following procedure to add a logo:
Navigate to the Admin, System, Style screen on the navigation tree on the left side of the GUI.
Click Browse, and then navigate to the desired image file in the Browse dialog box.
Select the desired file, and then click OK.
Click Save on the top right side of the screen to apply the changes.
Refresh the browser screen to view the changes.
Next you will configure the DIVAdirector Web Server.
DIVAdirector uses Microsoft Internet Information Server (IIS) 7 as the web server engine. IIS is installed during Windows Server 2008 R2, and 2012 R2 installation.The DIVAdirector Web Server is fully configured by the installation application. There is no need to adjust the configuration unless specific web server parameters require modification. The default IP port is port 80 and will bind to the first network adapter in the system device list. Contact Oracle Support if you need assistance binding the server to a different network adapter.
First you will configure the Listening Port.
The default listening port value is 80. This is the standard internet HTTP port for web servers. This value may be any port number not being used in the system, and should be changed if port 80 is unavailable. IIS must be restarted from the command line using the issreset command to apply a change to the port number.
Note:
After changing the server to a nonstandard port number, DIVAdirector users may be required to explicitly specify the port number in the web address, for example,http://dd5server:8080.If changes are made to the listening port, test the web server configuration by opening your web browser and entering the DIVAdirector IP address and port number (if required) in the URL Address field.
Next you will configure the IIS Service Account.
DIVAdirector is a permission based system that allows a limited number of simultaneously logged in users. This number of concurrent users depends on system resources and the maximum configurable valuer is 100 concurrent users. Any user accessing the system must be validated through the log in procedure. To be authorized to access the system, the user must enter a valid login username or email address and password specific to the user account.
There are three tiers of access control in DIVAdirector which are structured as follows:
This category is the top level account for different internal departments. Organizations are comprised of groups.
This category is the second level account for different groups within an organization. Groups are comprised of user accounts.
This category is the third level account for individual system users. Users are members of groups.
First you will configure a new organization.
Organizations are comprised of a set of groups. Organizations allow restricting access to information from users outside of the organization or group who do not require access to the data. For example, a company may not want to make its data viewable to other companies, or a department within a company may not want its data to be viewable by other departments within the same company. In these two scenarios, the entire company, or the specific department, desiring restricted access can be represented by an organization in DIVAdirector.
Use the following procedure to create an organization:
Navigate to Admin, Users, Organizations in the menu on the left side of the screen.
Click the + next to the Users menu item to expand the menu tree.
Select New Organization in the Organization list.
Enter the Organization Name in the Organization Name field.
Enter the LDAP settings in the LDAP Settings field if an LDAP login is required.
If your organization uses LDAP (Lightweight Directory Access Protocol), you can configure DIVAdirector users so they log in to the system using LDAP. Your administrative account should never be configured to use LDAP login because if the LDAP server address is incorrect, or the LDAP servers become unavailable, nobody (including you) will be able to log in. You are only able to log in using DIVAdirector's user name and password log in mechanism, which enables resetting the LDAP settings if the servers become unavailable or the settings had been incorrectly specified.
You can specify a port number by suffixing the IP address with the :port option. The port is the port number for DIVAdirector to listen for LDAP connections. If no port is specified, the default LDAP Port (port 389) is used. You can also specify an optional secondary LDAP server address (and port number if required) for authentication in case the primary server fails or is unreachable.
Enter SMTP Server information in the SMTP related fields (if applicable). Enabling SMTP allows users the ability to recover lost passwords through email.
In the Permissions' Content Filters area enter any Objects, Categories and Sites - multiple entries are separated by a semicolon. Use an asterisk to denote wildcards (for example ABC* or AB*D, and so on). An exclamation point preceding any filter implies that only objects determined by that filter should be included.
The site permissions are extremely important because they allow the organization to access objects on specific sites that match the filter.
Identify the Metadata Access fields that will be accessible by the organization by selecting the check box to the right of the metadata name. If the check box is deselected the organization will not have access to that metadata field. Groups within an organization may further refine their authorized selections.
Click on the DIVArchive Settings Tab. Add any Source/Destinations, Storage Plans, or Media this organization should have access to. Groups contained within this organization will only be permitted the ability to grant access to each resource defined here.
Click Save on the top right side of the screen to save the information.
Next you will add a new group.
Groups are collections of users and part of an organization. Each group is assigned a set of permissions to grant users of the group access to specific system features and functions. Groups are customizable and are configurable to fit organizational security requirements. By default, the system is installed with two user groups - SystemAdmins and admins.
The SystemAdmins group is the most powerful group in the system, and has special privileges to access all configuration elements of the system. Users who are members of the SystemAdmins group are the only users who have complete access to all permissions, configuration parameters, queries, Work Bins, and Shot Lists for every other user in the system.
When creating a new group you assign the new group a unique name. Group names should be descriptive and unambiguous to make further system administration and maintenance simple and clear. Group names must not exceed 32 characters.
Use the following procedure to create a group and set the group's permissions:
Navigate to the Admin, Users, Groups screen. The screen will initially display with the Profile tab selected.
Select New Group from the Group list.
Enter a new group name in the Group Name field.
Select the group's organization from the Organization list.
Click Save on the top right of the screen to create the new group.
Now that you have created the group and associated it with the correct organization, you must identify the roles for the group.
All users, regardless of their group's roles, always have access to the Operation Status, Change Password, and Logout functions. Only SystemAdmins have access to the Organization screen, Shortcuts screens, Public Resources screen, and the Proxy Configuration screens.
Use the following procedure to set the group member's roles:
Navigate to the Admin, Users, Groups screen.
Click the Permissions tab to view the Permissions screen.
Configure the appropriate roles for the group using the check boxes in the Privileges area.
A selected check box indicates that the group has been granted permission to that function. A deselected check box indicates that the group has been denied permission to the function.
Click Save on the top right of the screen to save the new group and its associated permissions.
The following sections describe the different permissions available for groups.
You can enable or disable the following general group privileges:
Allows users to view and save queries they performed, or were shared by a group they have access to.
Allows users to create personal and public work bins and perform actions within them.
Allows users to create and use group defined Drop Folders.
Allows users to modify the object metadata within the Edit Metadata page. If this permission is disabled, the metadata is displayed to the user in a read-only format.
Allows users to access the Shot List screen, add objects and segments of proxies, and perform file management and editing operations. If the user does not have this permission, Edit (and the icons) will not be displayed on the Query Results and Work Bin panels, and the Shot List menu item will not be displayed.
Allows users to create their own public Shot Lists. If this permission is disabled, Make Public will not be displayed on the Shot List panel.
Allows users to view the proxy and also enables Play.
Allows users to download proxy videos to their local system.
Allows users to have the ability to add, edit, and delete annotation metadata.
Allows users to request generation of a proxy for an object. The generation uses the rules defined in the System, Proxies, Proxy Generation page.
You can enable or disable the following DIVArchive group operation privileges:
Allows users to archive new data to the DIVArchive long term storage.
Allows users to delete object instances from the DIVArchive long term storage.
Allows users to restore objects from the DIVArchive long-term storage so they are available for immediate access on the specified destination (for example an FTP destination, or a video server).
Allows users to perform Partial File Restore operations on the selected file in the Shot List.
Allows users to upload content from their local system to a staging location associated with their user name on the Local Archive Source/Destination.
Allows users to restore files and to download directly from the Operation Status page.
Allows users to partially restore files and to download directly from the Operation Status page.
Allows users to create virtual objects.
Allows users to upload files to a Proxy Drop Folder that has been configured to automatically extract metadata and proxy frames.
Note:
Continued use of proxies produced outside of DIVAdirector and DIVArchive for local proxies will continue to function, but is highly discouraged.You can enable or disable the following group administration privileges:
Enables the configured group to manage users through the Admin, Users, User page.
Enabling this will prevent the auto playback of proxies when navigating through the Shotlist page.
Enables users to access the Admin, Metadata screen to manage Asset Metadata fields by viewing, editing, adding, and deleting metadata columns.
Enables users to access the Admin, System, Style screen, and to upload a new banner logo image. The banner logo image is used for customizing the look and feel of DIVAdirector by adding an organization's logo on the top right corner of all pages.
Enables or disables viewing of the site information for objects.
Enables users to configure and create groups within an organization. The groups created will not have access to any system administration privileges unless they have been explicitly granted by a SystemAdmin. Each member of the group will also be able to see queries, Work Bins, and Shot Lists of every other user within the user's organization.
Enables users to modify and create user accounts within a group. Each member of the group will also be able to see queries, Work Bins, and Shot Lists of every other user within the group.
Allows users to create new Drop Folders, and modify existing ones.
You can enable or disable the following group system administration privileges:
Grants users access to administrative functionality for synchronization and managing system requests. Request management is performed on the Operation Status screen and enables users with this permission to manage the request priority or cancel requests in the system.
Enables users to edit the default system settings (located on the System, Defaults screen), settings under the Service Settings page, and the Public Resource page.
Enables users to access the Perform Database Backup Operations area located on the Admin, Backup menu. Backup operations include viewing the last operation, scheduling an automatic backup, and performing a manual backup or restore.
Enables or disables the audit trail. The audit trail is located on the System, Audit Trail screen.
Enables or disables session management. The session management is located on the System, Session Management screen.
Enables users to access the Storage Locations page located under Admin, System.
Enables users to access the Proxy Generation page located under Admin, System, Proxies.
Enables users to access the Proxy Migration page located under Admin, System, Proxies.
Enables users to access the Transcode Service pages located under Admin, system, Service Settings.
Group based filters are configured on the Permissions screen. Any changes made and saved in the filters are applied immediately for all currently logged in users associated with the group. The Content Filter enables users to see only data complying with a set of filters for Object Name, Object Category, and Sites.The Content Filter is a table with three fields at the bottom of the Permissions screen. All of the fields in the table are initially empty. An empty field indicates that no filtering will take place for that type of discriminator. The content filters are applied to both queries and Work Bins, but do not affect Shot Lists and the Status screen.
Each field can have multiple filters separated by semicolons. An asterisk is used as a wildcard symbol. An exclamation point at the beginning of a filter indicates that only items that match the filter should be included, while the lack of an exclamation point indicates an exclusion. The filter can also be blank or have white space indicating that no filtering is required; white spaces between filters are ignored.
Note:
Organization level filters are also applied with, but are obfuscated, from the group level configuration.Use the Permissions (Metadata) tab to configure Metadata Permissions for a given group. There are two types of permissions:
Access — grants the group the ability to see and manipulate the associated metadata field.
Publish — grants the group permission to send the selected metadata to a DIVApublish server.
Note:
Only metadata that the containing Organization has been granted access to will be visible in this list.Next you will configure DIVArchive operational parameters.
The parameter values for the following DIVArchive operations are configured on the DIVArchive Settings tab on the Admin, Users, Groups screen. Not all parameters are applicable to all operations. Valid operational parameters are as follows:
Valid parameters are Source, Media, Storage Plan, QoS, Priority, and Category.
Valid parameters are Source, Storage Plan, QoS, Priority, and Category.
Valid parameters are Destination, QoS, and Priority.
Valid parameters are QoS and Priority.
Valid parameters are Destination, QoS, Priority, File Format, and PFR Name Format.
Valid parameter is Priority.
The valid parameters for each operation are applied according to the following descriptions:
The Source parameter defines a list of DIVArchive source storage locations for DIVArchive operations. Users only see the selected sources in the list. Whichever DIVArchive source is chosen to be the default will appear as the default item in the user's list.
The Destination parameter defines a list of DIVArchive destination storage locations for DIVArchive operations. Users only see the selected destinations in the list. Whichever DIVArchive destination is chosen to be default will appear as the default item in the user's list.
The Media parameter defines a list of DIVArchive media for DIVArchive operations. Users only see the selected media in the list. Whichever DIVArchive media is chosen to be the default will appear as the default item in the user's list.
The Storage Plan parameter defines a list of DIVArchive Storage Plans for DIVArchive operations. Users only see the selected Storage Plans in the list. Whichever DIVArchive Storage Plan is chosen to be the default will appear as the default item in the user's list.
The QoS parameter defines the Quality of Service for DIVArchive operations. The available choices are Default, Cache, Direct, Cache and Direct, and Direct and Cache. If the Force Default Value check box is selected, the chosen option cannot be changed by the user before executing an operation.
The Priority parameter defines the execution priority of DIVArchive operations. This parameter has a minimum value of 0 and maximum value of 100 (100 is the highest priority). If the Force Default Value check box is selected, the chosen option cannot be changed by the user before executing an operation.
The Category parameter defines a list of object categories for DIVArchive operations. Only the selected categories will be included in the user's list. The list will initially be empty; clicking + allows new categories to be added.
The File Format parameter defines the format of the high-resolution files stored in DIVArchive for Partial File Restore operations.
The PFR Name Format parameter defines the file name format for files displayed in the Partial File Restore operation results. The first list contains the types of separators used in the name format (underline, dash, or period). The second list contains additional name construction types as follows:
none: the object name is used as the file name; additional construction is not used.
1: one digit of the segment number in the Shot List is added to the file name with the separator (for example, objectname_1.gxf).
2: two digits of the segment number in the Shot List are added to the file name with the separator (for example, objectname_01.gxf).
3: three digits of the segment number in the Shot List are added to the file name with the separator (for example, objectname_001.gxf).
4: four digits of the segment number in the Shot List are added to the file name with the separator (for example, objectname_0001.gxf).
SOM-EOM: time codes are used in the file name (for example, {objectname_start-timecode-of-segment}-{end-timecode-of-segment}.gxf).
The Use Relative TC check box determines whether relative or absolute timecodes are used in the PFR File Name construction and the Partial File Restore operation.
Next you will configure data export roles.
You choose the data export settings for the group from three lists on the Export Settings tab. The lists are as follows:
This list determines the video format in an EDL export file. Select either NTSC or PAL from the list.
This list determines the Shot List export format. Select from either Final Cut Pro or Avid ALE.
This list determines the metadata export format. Select from either CSV or XML.
Next you will add a new user.
In DIVArchive and DIVAdirector, a Source/Destination is a disk or server that DIVArchive can archive from or restore to. The difference is in the actions being performed. For example, Tape Storage-A can be defined as a source for Restore or Partial File Restore operations. However, Tape Storage-A can also be designated as a destination for Archive and Copy operations. You configure the storage locations and identify them as a source, a destination, or both in DIVArchive. DIVAdirector will use the storage locations as they are identified in DIVArchive.
All users are members of a group and inherit the roles and accesses assigned to the group. You add new users to the system using the following procedure to create a user account:
Navigate to Admin, Users, User in the navigation tree on the left side of the screen.
From the User list select new user.
The following information is mandatory and entered in the Account Information area. All other fields are optional and may be left blank if desired.
Enter the desired user name. Users can log in using either the user name or the email address. User names must be unique within the system.
Select the organizational group to which the user will belong from the list.
Enter the email address to be used for logging in to the system. This is not case sensitive.
You should leave this selection set to Not Locked when you create the user. An administrator can lock users out of the system at any time by changing the value of this parameter.
There are two types of lockouts that can occur:
A normal Locked status occurs from login failures, and can be resolved by a password reset link sent by email or by contacting an administrator.
A Locked By Administrator status means that all attempts to gain access to the system will fail. This status only occurs when an administrator selects this status for a user.
Note:
The system ignores the Lockout Status, other than Locked By Administrator, when you configure LDAP for an organization.Enter an initial password to be used for logging in to the system for the first time. Passwords must conform to the following rules and expire every ninety days:
Passwords must be between 8 and 128 characters in length.
Passwords must contain a letter, number and a symbol.
Passwords must not contain white space characters.
New Passwords must not be any previously used passwords.
Re-enter the user's password to confirm it is correct. This must match the Temporary Password field exactly.
Note:
The Temporary Password and Confirm Password fields display only asterisks for security purposes rather than clear text.Click Save on the top right side of the screen to create the new user.
Next you will configure sources and destinations.
Drop Folders are directories on a storage location where you can place (drop) files to perform preconfigured tasks. While these tasks can be performed through various areas in the Web Interface, Drop Folders bypass the need for navigating a UI and can aggregate similar work into one simple action.
DIVAdirector actively monitors each Drop Folder for new files on disk and also has a Web Interface you can use to drop files and folders. The Web Interface section is located under the Dropfolders panel in the navigation tree. A given Drop Folder's visibility in the Web Interface is configured on a per group basis. Through the interface you may view each Drop Folder task status and any associated logs. Of the four types of Drop Folders available, there are three that are configurable; DIVArchive, Metadata, and Proxy. Annotation Drop Folders have a preset configuration as described in another section.
The Dropfolder Configuration page is located under the Admin navigation tree.
To configure Drop Folders you must have the appropriate configuration permission. You can enable (or disable) this permission as follows:
Navigate to the Admin, Users, Groups page using the navigation tree on the left side of the screen.
Select admin from the Groups list.
Click the Permissions tab.
Select the Administer Dropfolders check box under the Administration area to enable permission to configure Drop Folders.
To disable permission deselect the Administer Dropfolders check box.
Click Save to save your changes.
After you have the correct permission, you configure the following Drop Folder options on the Dropfolders Configuration screen under Menu Options on the top right side of the screen:
Clicking this menu item saves the currently selected configuration.
A file selector prompt will initiate the Drop Folder configuration import process. Both legacy XML formatted Drop Folder configurations, and new configurations are supported. After you import a configuration you must identify the Watch Path option and any other necessary configuration values before saving the configuration. Options will not be imported if the current group does not have access to them. For example, you cannot import metadata fields that your group does not have permission to edit.
Clicking this menu item deletes the currently selected configuration.
Clicking this menu item exports, and then downloads, the current Drop Folder configuration in XML format.
You can configure the following Drop Folder options on the Dropfolders Configuration screen under Drop Folder Configuration Options:
Folder Settings - all of the following options are required:
The type of Drop Folder dictates which configuration options are available.
This determines the type of DIVArchive action to perform and the configurable options available. The types of actions are as follows:
This action encompasses all types of Archive actions.
This action encompasses all types of Restore actions including file based Partial file Restore and timecode based Partial File Restore.
This action enables the copying of assets to different media.
This action enables delete type actions for both single instances and full asset deletion.
This is the title that is reflected in the navigator and the name of the export file when the Drop Folder is exported.
This parameter is the full path that the Drop Folder Monitor uses to look for new files to process. You cannot modify the Watch Path after a Drop Folder is configured and saved.
This parameter identifies the full path on the DIVAdirector Server that contains the individual log files for each file processing attempt.
This parameter identifies the currently assigned groups allowed to see this Drop Folder through the user interface. Drop Folders that do not have any group assignments will still be active, but will only be available to ingest files from the file system.
This parameter is a list of available groups to assign. The list will only contain groups within the same organization as the logged in user. Only the SystemAdmin account can see all groups at once.
Selecting this check box enables the configured Drop Folder. Deselecting the check box disables the configuration
File Process Settings:
The value in this field defines the file format the Drop Folder is expecting.
Selecting this value displays the configuration options required to define the schema (see the following details).
XML formatted metadata can be ingested provided the XML format guidelines are followed (see the following details).
This format is not currently implemented.
This parameter identifies the configuration of the expected ingest files encoding. Confirm that these encoding settings are correct to properly ingest character sets outside of the ASCII standard.
Selecting the check box for this option will save a copy of the ingested file in case there were any errors detected in processing.
This parameter identifies the full path on the server where backup copies are made in case an error in processing occurs. This field is required if the Save Backup File check box is selected (the option is enabled).
CSV File Format Settings:
Importing CSV files supports using one of three delimiting characters; comma, semicolon, and tab.
An encapsulation character enables the use of a delimiting character within the metadata value. Currently the only encapsulation character supported is a quotation mark. If an encapsulation character is present within the imported metadata, it must be escaped with a backslash.
When this check box is selected it indicates that the CSV has a one line header at the top of the file that must ignored by the parser.
This parameter enables matching a CSV row to objects without supplying a category within the dropped file. You can achieve matching through a list of categories, or all categories, if the Use Only Object Name check box is selected.
Note:
When a proxy drop folder is configured with this setting, the drop folder will assign the proxy based on a matched file name convention for objects that only contain one file.DIVArchive Drop Folders allow you to execute large numbers of DIVArchive requests based on the folder configuration. The volume of requests submitted simultaneously is throttled to avoid overwhelming the archive system. You can perform four types of actions including Archive, Copy, Restore and Purge. All dropped CSV files must contain a field for Object Name. Depending on the Category Matching settings previously described, a column defined for Object Category may also be necessary.
DIVArchive Request Processing Settings:
This option sets the maximum number of active processing requests before the Drop Folder will pause any new submissions.
This option defines the number of requests to send per sleep interval.
This option determines the length of time before sending new requests or checking the status of the DIVArchive processing queue.
This option sets the priority level of requests submitted to DIVArchive. Requests with higher priority take precedence over requests with lower priority. This option can be overridden as part of the dropped CSV.
DIVArchive Request Settings (All request settings can be overridden as part of the dropped CSV):
This option identifies the originating Source of a request. You can provide specific log in credentials associated with the source. You can also set a flag for deleting archived files after the request is processed.
This option identifies the Media Name or Storage Plan for the archived asset.
This option identifies the Quality of Service for the archive request. See the Oracle DIVArchive documentation for further information.
This option identifies the root path of the Archive request such that the file list will contain relative paths to this root.
This option is the comments field of the archive request. You cannot edit comments after they are submitted and they are attached to the resulting objects metadata.
Additional CSV Field Mappings
This option is a semicolon delimited list of files to archive. Files must use a relative path from the root path if it is set or the base of the source if it is not. You can use an asterisk wildcard to indicate a recursive archive from a folder path.
DIVArchive Request Settings (All request settings can be overridden as part of the dropped CSV):
This option identifies the Media Name or Storage Plan to copy an object.
Additional CSV Field Mappings
This option identifies an instance number to perform the object copy from.
DIVArchive Request Settings (All request settings can be overridden as part of the dropped CSV):
This option identifies the restore destination of a request. You can provide specific log in credentials associated with the destination.
This option identifies the Quality of Service for the archive request. See the Oracle DIVArchive documentation for further information.
Additional Restore Options (Cannot be overridden by the CSV file)
You can indicate what actions to take on the Restore request. For example, you may want to prevent overwriting existing files on the restore location, or conversely, make sure the existing files are deleted first.
This option identifies the root path of the Restore request such that the file list will be restored to a specific folder within the destination.
Additional CSV Field Mappings
This option identifies a semicolon delimited list of files to restore. You can use an asterisk wildcard to indicate a Recursive Restore from a folder in the object file list.
This option identifies an instance number to perform the restore operation from.
This option identifies a Mark In timecode in SMPTE format for a timecode based Partial File Restore. If you also enter a List of Files value, DIVArchive will attempt to perform a timecode Partial File Restore on each file.
This option identifies a Mark Out timecode in SMPTE format for a timecode based Partial File Restore. If you enter a List Of Files value, DIVArchive will attempt to do a timecode Partial File Restore on each file.
DIVArchive Request Settings (All request settings can be overridden as part of the dropped CSV):
This option identifies sets the media name to delete instances of an object from. This field is optional.
Additional CSV Field Mappings
This option identifies a specific instance number to delete. If neither an Instance or Media is defined, the process deletes the entire object from the archive system.
Action Settings:
This option overwrites existing metadata if an object already has metadata defined in the specified field.
This option removes specified metadata from an object if an empty value is parsed from the processed file.
This option creates virtual objects if metadata is added to an object that does not currently exist in the archive.
Field Mappings (CSV Specific)
Field mappings identify the order of the columns defined in your CSV file. You can reorder defined mappings by dragging and dropping the fields into the desired positions. Every CSV import requires the predefined fields Name and Category. You can add fields by clicking the + button. This displays the Field Mappings dialog box.
The Metadata Type list will only include fields that have not already been added to the Drop Folder, and metadata types that the group has access to. You can define the DateTime Mask field for date or time metadata. However, if no mask is specified, a generic format will be used. You can edit edited or delete fields at any time by clicking either the Pencil or X icons respectively.
The Space Removal option enables trimming of white space from your provided file.
Note:
DateTime Masks use standard formatting strings. You can find a full list of possible options athttps://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110). aspx.XML Formatting:
The following example shows the required XML formatting:
<DIVADirectorMetadataXML>
<Category object_category="a_category">
<Object object_name="an_object_name1">
<Item metadata_name="metadata_field1">
<Value>Data</Value>
</Item>
<Item metadata_name="metadata_field2" dt_mask="MM/dd/yyyy">
<Value>01/01/2017</Value>
</Item>
</Object>
</Category>
</DIVADirectorMetadataXML>
Annotation Drop Folders allow the importation of commented segments for files within objects. The CSV's that are dropped with this type of folder have a predefined structure as follows.
This column is limited to 240 characters and should match the object name in DIVArchive.
This column is limited to 240 characters and should match the object category name in DIVArchive.
The filename within the object to add the segment to.
Start time of the locator in the format hh:mm:ss:ff.
End time of the locator in the format hh:mm:ss:ff. This field is not mandatory and if left empty, the locator is considered a marker (description of a single frame).
The text description of the segment, limited to 2000 characters.
Note:
Oracle recommends using the new transcode service rather than Proxy Drop Folders. Continued use of proxies produced outside of DIVAdirector and DIVArchive for local proxies will continue to function.All proxies registered in the DIVAdirector system are kept on Proxy Storage Locations. These are configured in the Admin, System, Proxies section of the web interface. By default, one proxy location is added during DIVAdirector installation. However, you can configure and manage multiple proxy storage locations.
The Proxy Storage Location is defined by the path to the folder on the file system (either a local location or network share). The default location will be the C:\Program Files\DIVAdirector\proxies folder. During a custom installation the location will be a folder selected by you.
Each location has limited usable space on the storage device, either relative or fixed. A relative limit is set as a percentage relative to the capacity of the storage device, while a fixed limit is set in megabytes.
The Proxy Storage Location control enables viewing of the following information about each proxy location:
This field displays the current state of the proxy location.
This field displays the path to the proxy location folder.
This field displays the path used by the web application to access the storage location. On most installations, this will be DIVAdirector Proxies.
This field displays the space available in the proxy location.
This field displays the type of limit (bytes or percent) used to configure the storage location.
This field displays the amount of space that can be used on the storage device.
Use the following procedures to add a Proxy Storage Location:
Map the storage location so it is visible in Windows.
If the folder is a network drive, confirm it is set to reconnect on Windows start.
In Windows File Explorer, right-click the folder, and then select Properties from the menu.
Click Edit in the middle of the Security Tab screen.
Click Add in the middle of the screen to add a user to the folder's permissions.
When the Select Users or Groups dialog box appears, enter the IIS web server account (the default is dd5-user) used during DIVAdirector installation in the Object Name field (on the bottom of the screen), and then click Check Names to verify that the entered name is valid.
When the user is verified, click OK to add the user.
Repeat Step 5, Step 6, and Step 7 for Authenticated Users. Both users are now added to the folder permissions and set correctly for the DIVAdirector Web Server.
Use the following procedure to add the proxy folder to the DIVAdirector Web SErver in IIS:
Open the IIS Manager application (inetmgr).
On the left side of the IIS Manager click the host's Computer Name under the Sites menu, and then click DIVAdirector 5.
Right-click DIVAdirector 5, and then select Add Virtual Directory from the resulting menu.
Enter the Alias (virtual path) and Physical Path of the new proxy storage location.
Click OK to complete the process.
The Storage Location configuration is located in Admin, System, Proxies screen. Add a new Storage Location with the same physical and virtual path created in IIS in the previous steps using the following procedure:
Note:
The Proxy Location Path cannot be changed after it has been added.Click the Add under the Storage Locations header.
Enter the same physical path used to setup the virtual directory in IIS in the Physical Path field.
Enter the same alias used to setup the virtual directory in IIS (usually DIVAdirector proxies) in the Virtual Path field.
Select either Bytes or Percent from the Limit Type list.
Enter a value in the Limit Value field.
Click Update to save your configuration.
After saving the configuration, the state of the storage location will be updated to one of the following values:
This status indicates that the limit value has not been reached for this storage location. Open locations can accept new files.
This status indicates that this storage location does not accept new files. A Closed location can be explicitly transitioned to the Open state only.
This status indicates that the limit value has been reached for this storage location. Overflown locations do not accept new files and cannot be transitioned to another state.
This status indicates that the storage location is not currently detected in the environment (the path is not found). An Unreachable location cannot be transitioned to another state or removed.
You must configure a new Proxy Drop Folder in the Admin, Dropfolder Configuration section after you have created the virtual directory in IIS, and configured the Storage Location. Use the following procedure to create the Proxy Drop Folder:
Select Create new Folder from the menu list at the top of the screen.
Select Proxy from the Dropfolder Type list.
You can configure the remaining fields in the panel on the left side like other folders described in Drop Folder Configuration.
To have a transcoder workflow create the Proxy Key Frames and metadata, check 'Automatically Generate' and then select a workflow from the drop-down.
If you chose to not automatically generate these, you can manually add the Proxy Key Frames to a folder labeled 'Keyframes' in a relative path to the proxy location. Then, to add the metadata, you can create a 'metadata.json' file in the same location to the proxy.
You may opt to create a Proxy Drop Folder based on file naming convention, where just the proxy is dropped into the drop folder. This configuration will only work for objects that have a single file within them. You must also configure the Automatic Generation of Proxy Key Frames and metadata in order to use this option.
Click Save in the upper right corner to save your changes.
DIVAdirector associates proxies with files in an object, instead of the object itself. It is also possible for multiple proxies to be associated with a single file. This is a new feature starting with DIVAdirector 5.4. To support this functionality, proxies dropped into a Proxy Drop Folder require a Manifest File associated with them. The Manifest File triggers the proxy creation process. The Manifest File is a .csv file that associates an object name, category, and file with a proxy file. The following fields are required:
This parameter identifies the object name containing the file that will have a proxy associated with it.
This parameter identifies the object category containing the file that will have a proxy associated with it.
This parameter identifies the object file that will have a proxy associated with it. This is the relative path of the object file in the object file hierarchy. For example, sub1/sub2/file1.mxf.
This parameter identifies the full file path of the low resolution proxy file that will be used by DIVAdirector.
This parameter identifies a boolean value specifying if existing proxies should be replaced with the current one. If this value is false, additional proxies will be created for that object file when Manifest File for that object name, category, and file are processed. If this value is true, then any proxies for that object file will be removed and replaced with the one specified in the Manifest File.
This parameter identifies a string value defining the language track to use in audio proxy files.
The addition and configuration of the new location is now complete. Test the new location by dropping a proxy file into the folder as a non-administrative user, and then open the file with the Proxy Player.
Proxy generation is configured in the Admin, System, Proxies, Proxy Generation area. This section is only available to users in groups that have the Modify Proxy Generation Settings permissions. Before configuring this section, follow the steps in Configuring the Proxy Storage Location to create a location to store proxies.
You can add Category filters to control which object categories will have proxies created for them, which files they can be associated with, and where the generated proxies will be stored. Use the following procedure to assign a category filter:
Click Add in the Category Filters section.
Check the "Enable Full Restore" checkbox to send a full restore request for each object in the selected category filter. If this checkbox is left unchecked, then a partial file restore request will be sent for the selected proxyable file(s).
Check the "Proxy All Files" checkbox to generate a proxy for each file matching the "Proxyable file extensions" filter.
Note:
There is a limit of 100 proxies per object. If this checkbox is left unchecked, then only one matching the "Proxyable file extensions" will be selected for proxy creation.Select the category name that should have proxies created for it from the list. You can select the asterisk if the filter should apply to all categories.
Select the storage location where the proxies should be stored. You can select the asterisk here if multiple storage locations have been defined and you want to use the default filling strategy.
Enter the file extensions that should have proxies created for them. This is a comma separated list of file extensions (for example, mxf, mov, mp4, and so on).
Select the transcoder workflow to use for proxy generation.
Click Update to save the filter.
Next, you must configure the DIVArchive options used to restore the source file. These restore options will also be used for manual proxy generation tasks. At the top of the section on the right, locate the DIVArchive Restore Options panel, and configure the following values:
This field identifies the Source/Destination where files will be restored.
This field identifies the folder under Restore Destination where files will be restored.
This field identifies the Quality of Service parameter issued to the DIVArchive Restore request.
This field identifies the priority parameter issued to the DIVArchive Restore request.
This field identifies any additional parameters that need to be issued to the DIVArchive Restore request.
You can configure proxy generation to run continuously or only within a specified period. You configure these settings in the second section on the right side of the screen. In the Schedule panel, a list of check boxes and time selectors are displayed next to each day of the week.
To have the proxy generation task run continuously, deselect the check box next to each day of the week. To constrain the generation task to run within a certain period, select the check box next to the desired day of the week and the appropriate start time and end time.
Click Save at the top of the page when configuration is complete. Click Start in the Task History section to start the generation task.
You can use the proxy migration process to convert legacy proxy formats (for example, WMV) to a newer format (MP4). This process is configured under Admin, System, Proxies, Proxy Migration, and is only available to users in groups that have the Modify Proxy Migration Settings permissions. Before configuring this section, follow the steps in Configuring the Proxy Storage Location to create a location to store proxies.
In the top section under Legacy Proxies, a summary is displayed showing the counts of legacy proxy formats. Beneath that is a section for configuring the object categories that will have legacy proxy formats migration. The process for configuring these categories is similar to configuring proxy generation.
You can add category filters to control which object categories will have proxies migrated for them, which files they can be associated with, and where the migrated proxies will be stored.
Use the following procedure to configure category filters:
Click Add in the Category Filters section.
Select the category name that should have proxies migrated for it from the Category Name list. You can select the asterisk if the filter should apply to all categories.
Select the storage location where the proxies should be stored from the Storage Location list.
Click Update to save the filter.
Set the queue size to update the number of concurrent migrations that will occur in the top section on the right under Additional Settings. Next, select the check box next to the Legacy Proxy Types to migrate.
To have the proxy migration task run continuously, deselect the check box next to each day of the week. To constrain the generation task to run within a certain period, select the check box next to the desired day of the week and the appropriate start time and end time.
Click Save at the top of the page when configuration is complete. Click Start in the Task History section to start the generation task.
Similar to proxy generation, you can configure proxy migration to run continuously or only within a specified period. You configure these settings in the second section on the right side of the screen. In the Schedule panel, a list of check boxes and time selectors are displayed next to each day of the week.
You configure the Transcode service through the DIVAdirector web interface. Navigate to the Transcode Service configuration section under the Admin, Service Settings, Transcode Service section. You must start the service before continuing configuration. If the service is started but the status is showing as down in the configuration section, verify that configuration settings documented in the Oracle Installation and Configuration Guide are set correctly.
Note:
FFmpeg and Vantage are supported for use with the transcode service.Use the following procedure to configure the transcoder settings:
Set the transcoder implementation's Host Address and Port.
Define any Metadata Action Descriptions. These values store the descriptions of actions in a workflow that expose metadata variables that should be associated with a job.
Add any Workflow Presets required. These values store a named mapping to a transcoder implementation's internal workflow identifier. For Vantage, the InternalId is the workflow identifier. Typically, you will add at least one preset for creating proxies. You can add additional presets for alternate workflows. For example, if a Proxy Drop Folder is configured to automatically obtain thumbnails or metadata from dropped proxy files, then you can add those presets here.
Define an Output Storage Location. This value will form the base output path for the transcoded job. The remainder of the path will be formed by the JobID returned from the transcode service. For example, if the location path is \\10.0.0.1\output, and a JobID 6449d0db-2377-4e3d-a969-be09a742a63d is returned from the transcode service, then the final output path for the transcoded file will be \\10.0.0.1\output\6449d0db-2377-4e3d-a969-be09a742a63d.
Both Windows services installed with the Transcode Service should be set to start automatically. The two services display in the Windows Service Manager using the names Oracle.Transcode.Api.Owin and Oracle.Transcode.TaskManager.
You can manually control either of the services from the Windows Services Manager or using a Windows command line. Use the following command line options to control either of the services:
This option installs the service.
This option starts the service.
This option stops the service.
This option stops and then restarts the service.
This option removes the service.
This option shows the current status of the service.
This option displays a help dialog.
For example, use the following command to start the API Service:
Oracle.Transcode.Api.Owin.exe start
Use the following command to stop and subsequently restart the Background Task Service:
Oracle.Transcode.TaskManager.exe restart
The Oracle.DIVAdirector.TaskManager Windows Service configuration file (Oracle.DIVAdirector.TaskManager.exe.config) is located in the C:\Program Files (x86)\DIVAdirector 5\TaskManager\ folder.
The configuration file has four main sections that need your attention as described below.
DIVA Enterprise Connect Endpoint Configuration
You must configure the following parameters for the DIVA Enterprise Connect endpoint:
AppNameThis parameter is the name of the application to be registered in the WS API interface. Specifically, this is the value of the appName parameter passed to the registerClient method. This is required before interfacing with the WS API.
<add key="AppName" value="DIVAdirector"/>
ProcessIdThis parameter identifies the process ID number used for registering the client application. Specifically, the value of the processID parameter passed to the registerClient method. This is required before interfacing with the API.
<add key="ProcessId" value="1234" />
LocationNameThis parameter identifies the physical location where the computer running the client is located. Specifically, the value of the locName parameter passed to the registerClient method. This is required before interfacing with the WS API.
<add key="LocationName" value="location name" />
DIVArchiveApiUrlThis parameter identifies the WS API REST endpoint.
<add key="DIVArchiveApiUrl" value=" https://DIVA-VM-105:9444/diva/service/rest/2.2/DIVArchiveWS_REST" />
ClientIdThis parameter is the client id (user name) generated by the Key Generator script during the DWS installation.
<add key="ClientId" value="e3af4c10-e7ca-4143-970a-46bc0264a46f" />
ApiKeyThis parameter is the API key (password) generated by the Key Generator script during the DWS installation.
<add key="ApiKey" value="kAkWTK3ObnEOmHheJAKP" />
DWSVersionThis parameter is the version of the API service that DIVAdirector is targeting.
<add key="DWSVersion" value="2.2"/>
Four settings require configuration in the <appSettings> section:
applicationNameThis is the name of the application to be registered in the WS API interface. Specifically, this is the value of the appName parameter passed to the registerClient method. This is required before interfacing with the WS API.
<add key="applicationName" value="app name" />
locationNameThis identifies the physical location where the computer running the client is located. Specifically, the value of the locName parameter passed to the registerClient method. This is required before interfacing with the WS API.
<add key="locationName" value="location name" />
processIDThis identifies the process ID number used for registering the client application. Specifically, the value of the processID parameter passed to the registerClient method. This is required before interfacing with the WS API.
<add key="processId" value="1234" />
DIVArchiveApiUrlThis identifies the WS API REST endpoint. You can use any available port number for the endpoint.
<add key="DIVArchiveApiUrl" value="http://10.80.106.57:9763/services/DIVArchiveWS_REST_2.1/" />
Transcoder Service Access Configuration
You must set the URL for the transcode service endpoint in the <TranscodeSettingsConfigurationSection> section.
<TranscoderClientSettings TranscoderApiUrl="http://localhost:9876/api/" />
Task and Task Interval Configuration
The following tasks are configured in the <ScheduledTasks> section and run by the Windows service. You cannot disable any of these tasks without losing functionality. However, you can tune an interval timer with the IntervalInSeconds parameter to achieve better performance.
HouseKeeperTaskThis task automates system maintenance operations needed by DIVAdirector. These maintenance operations include both file system cleanup (removing old log files, purging system directories like local archive, local proxy, and so on), and database maintenance tasks.
TranscodeOnRestoreCompleteTaskThis task polls the progress of a DIVArchive Restore request (through the DIVArchive Web Services API REST endpoint), and initiates a Transcode request upon completion. This task is also responsible for calling the Proxy Creation Service.
DIVArchiveSyncTaskThis task controls synchronizing objects with DIVArchive.
UpdateRequestsStatusTaskThis task is responsible for updating the status of a DIVArchive request.
CreateProxyOnRequestCompleteTaskThis task is responsible for creating proxies in DIVAdirector by sending requests to the transcoding service when a DIVArchive request completes.
ProxyGenerationTaskThis task is responsible for handling the automatic queuing of proxy generation tasks.
ProxiesMigrationTaskThis task is responsible for handling the automatic migration of legacy proxies to newer formats.
CreateProxyOnJobCompleteTaskThis task is responsible for creating proxies in DIVAdirector for transcode jobs not associated with a DIVArchive request.
LegacyStorageMigrationTaskThis task governs the restructuring of the proxy storage locations after an upgrade from an earlier release. Users will not be able to log in to the system while the task is in progress.
The Transcode Service can integrate with one or more Vantage servers through the Vantage web SDK. At a high level, configuration of a Vantage integration involves setting the IP address and port number of the Vantage SDK endpoint and mapping Vantage Workflow properties to Transcode Service preset values.
The most straightforward Vantage integration option is one where a single Vantage server generates all of the required artifacts (video file, thumbnail images, metadata) for a DIVAdirector proxy. To use this integration option, you can use the sample workflow installed with the Transcode Service (DefaultVideoProxy_Analysis). This option requires a Vantage Analysis license because it uses the Analyze and MediaInfo actions to extract the required metadata.
Navigate to Admin>System>Service Settings>Transcoder Service>Transcoders
Click the red plus button to create a new transcoder.
In Transcoder Settings, select Vantage for the type.
Give the transcoder a unique name.
Add additional descriptive text to the description field.
Adjust queue size if needed. This value will determine the number of simultaneous transcode jobs the transcoder can accept.
Select the Enabled? checkbox to activate this transcoder and allow it to be used in DIVAdirector workflows.
Set the IP address of the server hosting the Vantage SDK service.
Set the port used by the Vantage SDK service. On default installations, this will be port 8676.
In the Presets panel, click Add new record.
Give the preset a name. This must be unique per transcoder, but the same preset name can be used by other transcoders.
You can configure a multiple transcoder setup by defining multiple transcoders with the same preset name. See "Multiple Transcoders and Load Balancing".
Select the preset type:
Video Proxy — creates a proxy with automatic or manual workflow.
Thumbnail Only — extracts thumbnail images for EDLs (such as Shotlist page).
Metadata Only — extracts the required metadata fields for proxy generation. This is used for configuring split workflow setups. See "Configuring Vantage Split Workflow".
Thumbnail & Metadata — extracts thumbnail images and metadata for use in drop folders configurations.
Set the Internal Id to match the Vantage Workflow Id of the corresponding workflow.
If you are using a Video proxy preset in a split workflow configuration (ex. Vanatage server without an Analysis license), then select the Requires External Metadata checkbox. See "Configuring Vantage Split Workflow".
Enter any metadata action descriptions. This field is a comma-separated list of strings defining Vantage action descriptions that produce the metadata required for proxy creation. Required metadata fields are:
OutputFileFullPath — the fully qualified path of transcoded file.
Video Framerate — the frame rate of transcoded file.
Content Duration — the duration of transcoded file
Header Timecode — the timecode offset of first frame. This is only required if using a clip with a non-zero SOM.
Click Insert, and then Save.
A Vantage split workflow configuration allows a Vantage server to be used for proxy file and thumbnail generation, while another transcoder is used for extracting the required metadata. This setup is achieved by configuring presets to indicate when one preset produces metadata and when another requires externally produced metadata.
Navigate to Admin>System>Service Settings>Transcoder Service>Transcoders.
Click the red plus button to create a new transcoder.
In Transcoder Settings, select Default Command line for the type.
Give the transcoder a unique name.
Add additional descriptive text to the description field.
Adjust queue size if needed. This value will determine the number of simultaneous transcode jobs the transcoder can accept.
Select the Enabled? checkbox to activate this transcoder and allow it to be used in DIVAdirector workflows.
In the Presets panel, click Add new record.
Give the preset a name. This must be unique per transcoder, but the same preset name can be used by other transcoders.
Select Metadata Only for the preset type.
In ”exe path”, enter the fully qualified path to the executable (without parameters) to be used for extraction.
In a default setup this path is used: C:\Program Files (x86)\Oracle Corporation\TranscodeService\Plugins\ffprobe.exe
In ”exe args”, enter the arguments to pass to the executable entered above.
In a default setup, this value used is: -i "{{input_filepath}}"
Where the {{input_filepath}} string will be substituted with the fully qualified path of the input file when processing a job request.
Select the Ignore StdError Output checkbox if the exe will write output to std error that shouldn't be interpreted as an error.
Click Update, and then Save.
On the Vantage server, create or import a workflow that will create the proxy video and thumbnail (but doesn't extract required metadata).
An example is DefaultVideoProxy_No_Metadata.xml, installed by the Transcode Service in the installation directory: C:\Program Files (x86)\Oracle Corporation\TranscodeService\SampleWorkflows\TranscoderSetupFiles\Vantage
Create a new preset record and select type Video Proxy.
Map the Internal Id field to the corresponding Vantage workflow Id.
Select the Requires External Metadata checkbox.
When this option is selected and a job is submitted with this preset, the Transcode Service will search for any preset of type ”Metadata Only” in any enabled transcoder. If no such preset is available, then the job will fail. If a ”Metadata Only” is available, then the metadata extraction task will be queued first. If the metadata extraction task succeeds, then the processing of the original preset will continue.
Set ”Metadata action descriptions” for the metadata output by Vantage. Since this is a split workflow and most of the metadata is produced by an external preset, typically the only value here will be the action description that produces the fully qualified path of the output file (MD_OUTPUT_PATH for the sample workflow).
Click Update, and then Save.
With DIVAdirector 5.4.1, you can distribute transcoding tasks among multiple transcoder implementations. You configure this by setting up multiple transcoders with a shared preset name. An example scenario would be configuring load balancing for automatic proxy generation tasks across servers: Vantage1 and Vantage2.
With the following configuration, any automatic proxy generation tasks for the configured category will be distributed between Vantage 1 and Vantage 2:
Note:
The preset name does not have to be ”shared”, but it must be the same for both servers.Follow the steps in "Configuring the Vantage Stand-alone Presets" to configure the Vantage 1 server.
Create a Video Proxy preset with name ”shared” in Vantage 1.
Save Vantage 1 configuration.
Follow the steps in "Configuring the Vantage Stand-alone Presets" to configure the Vantage 2 server.
Create a Video Proxy preset with name ”shared” in Vantage 2.
Save Vantage 2 configuration.
Navigate to Admin>System>Proxies>Proxy Generation.
Create a new Category Filter with workflow name set to ”shared”.
You can directly integrate Command line transcoders, like FFmpeg, with the Transcode Service by configuring an implementation to directly invoke the command line executable.
There are several drawbacks to this approach. First, the transcoder must be able to produce all of the required proxy artifacts: video file, thumbnail images, and metadata – with a single command. Second, the artifacts will need to conform to a specific format. For example, the thumbnail images will need to be named in a format with the SOM-based SMPTE timecode appended to the file name. Because it can be difficult to produce all of these artifacts with a single command in the required format, another integration option is available.
Instead of directly invoking the command-line transcoder, you can configure the Transcode Service to call a custom script to produce the required proxy artifacts. With this option, the script can call multiple commands.
Sample Powershell scripts are installed with the Transcode Service in the directory: C:\Program Files (x86)\Oracle Corporation\TranscodeService\SampleWorkflows\TranscoderSetupFiles\Custom for default configurations. The scripts are not limited to Powershell. You can use other scripting engines like Python.
Navigate to Admin>System>Service Settings>Transcoder Service>Transcoders.
Click the red plus button to create a new transcoder.
In Transcoder Settings, select Custom Command line for the type.
Give the transcoder a unique name.
Add additional descriptive text to the description field.
Adjust queue size if needed. This value will determine the number of simultaneous transcode jobs the transcoder can accept.
Select the Enabled? checkbox to activate this transcoder and allow it to be used in DIVAdirector workflows.
In the Presets panel, click Add new record button.
Give the preset a name. This must be unique per transcoder, but the same preset name can be used by other transcoders.
Select Video Proxy for the preset type.
In ”exe path”, enter the path of the scripting engine that will be used. For default installations, this is: Powershell.exe.
In ”exe args”, enter the arguments to pass to the executable entered above. In a default setup, this is:
-ExecutionPolicy ByPass -File "C:\Program Files (x86)\Oracle Corporation\TranscodeService\SampleWorkflows\TranscoderSetupFiles\Custom\ffmpeg_proxy.ps1" "{{input_filepath}}" "{{output_basepath}}" "{{output_filename}}.mp4"
Select the Ignore StdError Output checkbox if the exe will write output to std error that shouldn't be interpreted as an error.
Click Update, and then Save.
The following parameters, enclosed in double curly braces, will be substituted at runtime.
{{input_filepath}} — Fully-qualified path of the input file to the custom script.
{{output_basepath}} — Fully-qualified base path for storing the proxy artifacts. This is a temporary subdirectory stored under the staging location. Files output by the transcoder will be stored here until they are transferred by the DIVAdirector Task Manager service to the proxy storage location.
{{output_filename}} — Filename (without extension) of the transcoded proxy file.
The custom script will need to use the interpolated values for placing the artifacts in the correct location. The following are example parameters from the default Powershell script installed with Transcode Service:
Param( [string]$input_filepath, [string]$output_basepath, [string]$output_filename )
With the following parameter values:
$output_basepath — \\Staging\4d769747-adde-456e-8350-125360241daf
$output_filename — outputfilename
$intput_filepath — \\RestoreLocation\inputfile.mxf
The custom script would need to create a proxy file named $output_filename under the $output_basepath directory.
For example: \\Staging\4d769747-adde-456e-8350-125360241daf\outputfilename.mp4
You will need to place thumbnail images in a subdirectory named Keyframes under $output_basepath. The filename format of the images should contain the SOM based SMPTE timecode appended after an underscore character.
For example, for thumbnails extracted every 10 sec from a source clip with a 01:00:00:00 SOM.
\\Staging\4d769747-adde-456e-8350-125360241daf\Keyframes\prefix_01001000.jpg ... \\Staging\4d769747-adde-456e-8350-125360241daf\Keyframes\prefix_01004000.jpg
You should store metadata in a JSON formatted string in a file named metadata.json under the $output_basepath directory.
For example: \\Staging\4d769747-adde-456e-8350-125360241daf\metadata.json.
Required keys are ”content duration” and ”video framerate”.
Now that the storage is configured for the system, you are going to configure the log files. There are three important sets of log files used in DIVAdirector:
WWW Log Files
Task Manager Log Files
API Log Files
All DIVAdirector logs aggregate on the same UDP port (7071 by default) and can be monitored by Log4Net compliant logging applications (for example, Log2Console) to provide live system monitoring. However, many of these logging applications are extremely resource intensive and should not be left running in the background.
The xml format for logging configuration will be the same for every type of log as follows:
<log4net>
<appender name="UdpAppender" type="log4net.Appender.UdpAppender">
<remoteAddress value="127.0.0.1" />
<remotePort value="7071" />
<layout type="log4net.Layout.XmlLayoutSchemaLog4j" />
</appender>
<appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="logs/logfile.log" />
<appendToFile value="true" />
<maximumFileSize value="5MB" />
<maxSizeRollBackups value="5" />
<layout type="log4net.Layout.XmlLayoutSchemaLog4j" />
</appender>
<root>
<level value="DEBUG" />
<appender-ref ref="RollingFileAppender" />
<appender-ref ref="UdpAppender" />
</root>
</log4net>
The only values that should be adjusted are the following:
maximumFileSizeThis parameter is the maximum size a log file will attain before rolling over to another log. If you find that having larger individual log files better suits your needs, then adjust this value.
maxSizeRollBackupsThis parameter is the maximum number of rolled log files that can be produced per day. Any additional logging for the day will be ignored. If you find that too many log entries are being created per day, then adjust this value.
levelThis value refers to the detail of the logs. Valid values are the following:
At this level all logs are collected including Trace level logging. Only use this option at the request of Oracle Support.
Debug logging is quite extensive and can degrade performance in a particularly busy system. Only use this option at the request of Oracle Support.
At this level only informational messages, warnings and errors are collected. Oracle recommends using this as your production system setting.
At this level only warnings and errors are collected.
At this level you will only see errors appear in the logs.
Note:
The Oracle DIVA Enterprise Connect logs, IIS logs and PostgreSQL logs may also be useful when troubleshooting potential problems. See the respective application documentation for advice on setting logging levels and location.Caution:
Changing theWeb.Config file should only be done when the site is offline. Making changes when the site is live will force the site to reset, logging out all users.The WWW logs contain information regarding any user interactions with the Web Interface and secondary interactions with various connected services, such as Oracle DIVA Enterprise Connect. The default setting for these logs is enabled, and they provide a good starting point for investigating any operational, or configuration, errors.
The configuration for these log files is located in the C:\Program Files (x86)\DIVAdirector 5\www\Web.Config file.
The Task Manager logs contain information regarding scheduled tasks, including Drop Folder operations, synchronization, request updating, and housekeeping, among others (see Task Manager and DIVAdirector API Windows Services for more information).
The configuration for these log files is located in the C:\Program Files (x86)\DIVAdirector 5\Task Manager\log4net.config file.
Note:
After changing the any parameters in the configuration file you must restart theOracle.DIVAdirector.TaskManager service. The restart triggers an automatic HouseKeeping task, and therefore Oracle recommends restarting during non-business hours (if possible).The API logs contain information regarding user log in, and any interactions with the Oracle Client Uploader.
The configuration for these log files is located in the C:\Program Files (x86)\DIVAdirector 5\API\log4net.config file.
Note:
After changing the any parameters in the configuration file you must restart theOracle.DIVAdirector.Api service.Next you will configure search parameters.
The following sections include detailed information for managing metadata. Metadata is used in system wide searches on the DIVAdirector and DIVArchive systems to locate a specific file, category of files, objects, or video clips. These roles are set for the group and apply to all members of the group.
Object metadata is a set of search terms that belong to an object. Each object has its own predefined set of metadata. Metadata is imported from DIVArchive (OBJECT_NAME, OBJECT_CATEGORY, ARCHIVE_DATE, and so on).
The Object Metadata screen is accessible from the Admin, Users, Metadata screen. The following functions are available from the Object Metadata screen:
You click Add on the top right side of the screen to add new metadata for objects in DIVAdirector.
You select the metadata type to be deleted in the list, and then click Delete on the top right side of the screen to delete an existing metadata type.
You click the Pencil icon at the beginning of the row for the metadata to be edited to edit a metadata type.
DIVAdirector supports various data types for metadata field definitions and associated presentation controls. When you select a specific data type additional parameters are presented to the user.
The following are the valid metadata types:
Any character string; restricted to 1 - 100000 characters in length. The String data type can be represented using an EditBox, TextBox, or SelectBox control (refer to DIVAdirector Presentation Controls).
Any integer numeric value. The Number data type can be represented using an EditBox or CheckBox control.
Any numeric value - including decimals. The Decimal data type can be represented using an EditBox or CheckBox control.
The Date field can be represented using an EditBox, SelectBox, or Calendar control.
The Time field can be represented using an EditBox or SelectBox control.
A fixed representation file of arbitrary internal format which is represented using a FileSelect control.
A graphical representation of metadata that originated from Oracle SAMMAsolo. The graph can represent the entire object or just a portion of the object.
A representation of thumbnails of frames that match the portion of the object represented by the SAMMA Graph.
Used for Quality Control reporting. Options include the following:
Report Type
Selected (selected or deselected)
Data file extension
Report file extension
Most metadata field data types have multiple ways of displaying data and some are restricted to using particular controls. The following are descriptions of the controls used to display the metadata fields:
A single line text entry control that allows users to edit its value.
A general multi-line text editing control.
Allows users to select a value from the supplied list of unique values.
Allows users to select an option by selecting the appropriate check box.
Allows users to browse through a graphical calendar and select the appropriate date. This format is used only for the Date data type.
A special composite control comprised of an Upload button, and link to an existing binary file. This format is used only for the Binary File data type.
This control is only used for the SAMMA Graph data type and shows a graphical representation of Oracle SAMMAsolo generated metadata.
This is only used for the SAMMA Thumbnail data type to provide thumbnail representations of frames that match the portion of the objects represented by a SAMMA Graph control.
The metadata display screen is arranged in a tabular format. The columns in the table are predefined and described as follows:
DIVAdirector defined unique identifier for the object.
DIVArchive system defined object name used as a unique identifier with the category.
DIVArchive system defined object category used with the name.
The date when the object was archived to the DIVArchive system.
A comment text field that contains comments added during the object's creation.
The original source of the file from which the object was created.
The current object status that determines whether the object exists.
The flag defining whether the object is virtual (YES or NO).
The archive system, or systems, that an object is on.
The total size on disk for an object.
The tape barcodes that contain instances of an object.
First you will add new metadata entries.
Use the following procedure to add a new metadata entry to the Metadata Manager:
Navigate to Admin, Metadata in the navigation menu on the left side of the screen.
Click Add on the top right side of the screen.
Enter the information in the resulting dialog box.
Click the Check icon on the lower left side of the screen to add the new entry, or to click the X icon on the lower left side of the screen to cancel the addition.
Repeat the previous steps for each metadata entry you must add to the system.
When a metadata type is selected from the list additional parameter fields are displayed that are specific to the type selected. Each metadata entry has the following parameters:
The Title field is the Metadata column name displayed in the user interface. The title can be any unicode text with maximum length of 32 characters.
The Type field determines the entry's data type and is defined automatically when selected from the Type list. For example, if the type of the Metadata column is DATETIME in the database, then one of the two types can be selected from the list, DATE or TIME.
The type of the presentation control used.
If you select the Binary File type, the edit field will be displayed instead of the column length. Only files with this mask can be selected to be uploaded using the Object Metadata area of the Shot List screen. Multiple masks can be set and separated by a semicolon. For example, you can enter *.txt; *.log and any spaces will be removed when saved (in this case).
This is the description of the column displayed in the Tooltip when the user hovers over the column title in the Query Results, the Work Bin tables on the Search screen, and the Asset Metadata area on the Shot List screen. The description can be any unicode text and has a maximum length of 240 characters.
One or more of the following:
Hidden
Read Only
Display in Search Results
Display in Tooltips
In addition to the above, a SAMMA Graph metadata column type requires the following parameters:
This specifies the name of the Y Axis for the SAMMA Graph.
Specifies the type of information to be displayed on the SAMMA Graph. Click + on the Field Tag button to add each tag and specify a color. Predefined tags are available in the Choose Type list or by clicking on the default type displayed under the Field Tag. For example, using the Choose Type list and selecting the type as Video results in three field tags being created automatically:
Luminance Average
Chroma U Average
Chroma V Average
Next you will configure quality control report metadata.
You add Quality Control report metadata to the system's search functions using the following procedure:
Open the Metadata Column Manager on the Admin, Metadata screen.
Click Add on the top right side of the screen.
Enter a name for the metadata in the Title field.
Select qc report from the Type list.
Select QC Report from the Format list.
Select which reports should be visible using the check boxes next to each type of report.
Enter the data file extension (usually xml) for each visible report in the Data Extension field.
Enter the report file extension (xml or pdf) in the Report File Extension field.
If an XML file for data and PDF file for viewing are both available, set the Report File Extension to pdf. In most cases, it can remain set to the default value (xml).
Enter a description in the Description field.
Select the Hidden (Hid) check box if you want the report hidden from users; otherwise, leave it deselected.
Click the Check icon on the lower left side of the screen to save the new report column, or click the red X icon to cancel the addition.
Next you will configure metadata access for the group.
Metadata filters authorize and restrict user access to various metadata fields. You configure the filters on a per group (not per user) basis on the Permissions (Metadata) tab in the Groups screen. Users can only view the metadata fields that their group has access permissions to.
The metadata filters are applied only within Queries, Edit Metadata, and Shot List screens. Each field can be made accessible, inaccessible, and available or unavailable, for publishing (refer to the Oracle DIVAdirector User's Guide for more information on publishing).
Next you will configure metadata publishing settings.
DIVAdirector can publish restored video clips to editing software. A destination configured in DIVArchive must point to the editing software location that is receiving the restored video clips and their metadata to use the publishing functions. This setting must be selected as the location for publishing in the DIVArchive Destination list on the Metadata Publish Settings tab on the Groups screen.
The FTP network protocol is used for DIVAdirector's Publish Metadata feature and must be configured in the FTP area of the screen. Publishing clips to editing software requires sending the video clip's metadata as an XML file.
Metadata fields to be included in the XML file are selectable in the Metadata area of the screen. The available fields are determined by the settings configured in the Metadata Permissions Filter.
Select the available metadata fields to include in the XML file using the check box to the right of each field. A selected check box will include the field in the XML file and a deselected check box will not be included.
Enter the FTP server's Host, Username, Password and Port number in the designated fields. The port number can be entered manually or you can use the up and down arrows to the right of the port field to raise or lower the displayed number. The default FTP port (25) will be used if the port field is left empty.
Select the destination from the DIVArchive Destination list.
Click Save on the top right side of the screen to save the settings.
Next you will configure quality control reports.
You configure automated backup operations by identifying your desired schedule, and then selecting the check box to make the scheduled task active. The schedule can be set to run on a weekly or monthly basis.
Caution:
Although you can delete scheduled tasks in the Windows Explorer, do not use this method to remove the task. If the task was accidentally deleted in the Scheduled Tasks, the Windows registry key namedHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Front Porch Digital Inc.\DIVAdirector\DB\Backup must be removed, enabling DIVAdirector to be able to configure further scheduled backups correctly. If you require assistance or are not comfortable editing the Windows registry contact Oracle Support.Use the following procedure to configure your automated backups:
Navigate to Admin, Backup, Schedule on the navigation tree on the left side of the screen.
Either enter the time to begin the backup directly in the Start Time field, or use the clock icon to the right of the Start Time field to display a selectable time menu called the Time Picker.
The Start Time field denotes the time when the backup should start and must be in 24 hour format using standard hh:mm notation where:
hh = hours (0 - 23)
mm = minutes (0 - 59)
Use the Occurrence list to select either a weekly or monthly backup frequency.
If the Occurrence is set to Weekly, you can assign the days of the week when the backup should be performed by selecting the check box to the left of each day desired.
If the Occurrence is set to Monthly, you can set a day of the month (by date) when the backup should be performed by selecting the day of the month from the Days list.
Select the destination folder for the backup snapshot files in the Directory field.
The root location is mapped to the virtual folder named DIVAdirector Database Backup Storage. Select the backup destination using the navigation provided in, or above, the Directory area on the right side of the screen.
Click Save on the top right side of the screen to apply the settings. When the changes are saved successfully, a confirmation message is displayed.
The DIVAdirector scheduled backup task that was created is now available (named At1). You can confirm correctness in the Windows Task Scheduler. Additional backup tasks will be numbered sequentially (for example, At2, At3, At4, and so on).
Your initial configuration of DIVAdirector is now complete. In the next chapter you will find daily tasks that you use to keep DIVAdirector running.
DIVAdirector supports integration with QC Reports from Venera Rapid, Venera Pulsar, Tektronix Cerify, and Interra Baton. Report files should be placed in the path under the IIS DIVAdirector 5 Root Folder:
DIVAdirector QC Report\{Report Name}\{Category}\{Object Name}\{Object Name}.xml
For example:
DIVAdirector QC Report\Venera Rapid\WMV\AUTO_20120615_031030\AUTO_20120615_031030.xml
First you will create a folder for the QC reports, then you will place all reports in the folder you create.
Use the following procedure to create a folder for the QC Reports. After reports are created you will place the reports in the appropriate folder.
Open IIS and navigate to the DIVAdirector QC Report virtual directory under the DIVAdirector 5 menu item.
Right-click the DIVAdirector QC Report folder, and then select Explore from the context menu.
Create a new folder with a specific category (for example, Venera Rapid or Venera Pulsar) for the files under the report type folder.
Create a new folder using the report name (for example, AUTO_20120615_031030).
Place the QC Report XML files in the newly created folder. Other report files (for example, PDF files) can be placed in the same location.
Next you will configure automated system backups.