Oracle® DIVAdirector

Installation Guide

Release 5.3

E69778-04

September 2016

Oracle DIVAdirector Installation Guide, Release 5.3

E69778-04

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Lou Bonaventura

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- Preparing for Installation

2 Oracle DIVAdirector Software

- DIVAdirector Prerequisites

- DIVAdirector 5.3 New Features and Enhancements

3 System Installation

- Planning System Deployment

- Minimum System Configuration

- New System Installation

- Optional Manual Adjustments

- Relocating DIVAdirector Database Files

- Using Network Attached Storage (NAS) for the Proxy File Storage Folder

- Using Network Attached Storage (NAS) for Binary Storage

- Upgrading DIVAdirector 4 to DIVAdirector 5.3

4 DIVA Transcode Service

- Introduction

- Web Configuration File

- Windows Services

- Database Settings

- Transcoder Settings

- Presets

- Locations

- API Endpoints

- Example #1

- Example #2

- Example #3

5 ShuttlePro V2 or ShuttleXpress Control Pad Installation and Configuration

Glossary

Preface

This document provides a basic understanding of system functionality and detailed instructions for installing Oracle DIVAdirector 5.3.

Audience

This document guides System Administrators through initial Oracle DIVAdirector system installation and configuration.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the DIVAdirector documentation set:

- Oracle DIVAdirector Release Notes

- Oracle DIVAdirector Security Guide

- Oracle DIVAdirector Administrator's Guide

- Oracle DIVAdirector User's Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

Oracle DIVAdirector is a Graphical User Interface (GUI) for Oracle DIVArchive 7.1 and later systems. Users locate and work with videos remotely, from any computer on your network, through the web-based interface. Administrators monitor and maintain the system and user accounts with minimal effort from anywhere you have access to your network.

You access DIVAdirector through a web browser using the HTTPS protocol. Some of the advantages of a web-based interface include:

- No GUI software installation required.

- A browser-based GUI can be accessed from anywhere on the network.

- No client application configuration is necessary.

- No client updates are required.

Using DIVAdirector you can:

- Search for video clips by file name, date, category, and format.

- Define metadata fields that support search.

- Use Boolean operators and greater than-less than criteria. For example you can search for video clips of farm animals in the United States, but not in Nebraska or Kansas.

- Review located clips using the built-in media player.

- Extract selected frames, add them to a list of related clips, forward them to editing applications, or arrange them for distribution.

Note:
DIVAdirector 5.3 and later is licensed per user, not per concurrent user. You identify the maximum concurrent users (between one and one hundred) on the Admin, System, Defaults screen.

Preparing for Installation

Before the Oracle Delivery and Installation Team arrives at your site you must complete installation and configuration of your system hardware. You must assign IP addresses and storage locations, open ports in the firewall, complete network cabling, and so on. When the team arrives they will review the configuration specifications before starting the installation to ensure all necessary components are in place and accessible.

Installed hardware must meet or exceed the list of recommended minimum hardware specifications provided to you. The server host hardware must have Microsoft Server 2008 R2 or Windows 2012 R2 installed.

You configure the server host computer for operation within your network and restrict access to the server with a unique, secure password. Install Microsoft Internet Information Server (IIS) 7 on the server host computer and confirm operation and network connectivity.

Any third party applications must be licensed and installed (for example Telestream). You must have all DIVArchive configuration parameters set up including IP addresses and port configurations for storage devices, video servers, Avid Interplay (if in use), Oracle SAMMAsolo (if in use), Microsoft Cluster Manager (if in use), and so on. The team needs to reference this information during DIVAdirector installation.

You must have at least one fully operational client computer available for testing during and after installation. Client computers must have Microsoft Windows 7 Professional or Ultimate (either 32-bit or 64-bit) with Service Pack 1, or Mac OSX 10.6 (Snow Leopard) or later operating system installed and one of the following supported web browsers:

- Internet Explorer 7, 8, or 9

Note:
Must be run in native mode, not in compatibility mode.

- Chrome 18.0

Note:
Playback of WMV and MOV clips are no longer supported in Google Chrome due to the End of Life (EOL) for NPAPI in the browser. Files in MP4 format will continue to play using Google Chrome.

- Firefox 12.0

- Safari 5.1.5

Note:
Drag and drop from the main right window to the left navigation pane is not supported. Drag and drop from and to the left navigation pane is supported

2 Oracle DIVAdirector Software

This chapter discusses the software in general and identifies prerequisites for installation.

DIVAdirector Prerequisites

DIVAdirector Server requires either the Microsoft Server 2008 R2, or Microsoft Server 2012 R2 operating system.

The server can connect to Oracle DIVArchive 7.1 or later. You will install DIVAdirector Server, PostgreSQL database, DIVAdirector, including the following components:

- DIVAdirector Web Server 5.3

- DIVAdirector Server 5.3

- DDMedia 5.3

- PostgreSQL 9.4.4

The client computers must have either Microsoft Windows 7 Professional or Ultimate (either 32-bit or 64-bit) with Service Pack 1 (SP1), or Mac OSX 10.6 (Snow Leopard) or later. If the target computer runs Windows 7 but does not have SP1 installed, update the computer's operating system to the SP1 level through the Windows Update utility before installing DIVAdirector.

DIVAdirector 5.3 supports the following browsers in Windows 7:

- Internet Explorer 7, 8, or 9

- Chrome 18.0

- Firefox 12.0

- Safari 5.1.5

- Drag-and-drop from the right main windows to the left navigation pane is not supported. Drag-and-drop from and to the left navigation pane is supported.

DIVAdirector 5.3 supports the following browsers in Mac OSX:

- Chrome 18.0

- Firefox 12.0

- Safari 5.1.5

Insure that the computer name is set before running DIVAdirector installer. This is important because the computer name cannot be changed once DIVAdirector is installed because it invalidates the rights and permissions of the IIS user account.

Insure that the computer's drives and network connections are correctly configured. Storage locations must have appropriate access rights, and network devices must have login credentials configured to connect automatically.

Ensure the computer's Administrator account has a secure password.

If Teamviewer is being installed only use version 6 or later and use the following procedure to confirm the required settings:

1. In Teamviewer, click the Extras menu item, then navigate to Options, and then Advanced.

2. Click the Show advanced options button.

3. Scroll down to the Advanced Network Options section of the screen and select the check box for Don't use incoming ports 80 and 443 (recommended for web servers only). This option may, or may not, be present depending on your version of Teamviewer.

4. Click OK and exit the Options area.

If you are performing an upgrade, you can upgrade to DIVAdirector 5.3 directly from DIVAdirector 4.1 or DIVAdirector 5.x. The upgrade is not compatible with DIVAdirector releases before to 4.1 or (specifically) release 4.2. Verify that older releases of DIVAdirector are upgraded to 4.1 or 5.x before using the installer to upgrade to release 5.3.

DIVAdirector 5.3 New Features and Enhancements

DIVAdirector 5.3 includes the following new and enhanced features:

- Separate licensing is no longer required. You set the maximum number of concurrent users on the Defaults page.

- Log licensing has been removed.

- Local Archive functionality has been enhanced.

- Basic Search functionality has been enhanced.

- A new DIVAdirector Transcode Service has been added.

See the Oracle DIVAdirector Administrator's Guide for detailed information on these enhancements.

3 System Installation

This chapter discusses DIVAdirector 5.3 installation and deployment.

Planning System Deployment

DIVAdirector consists of three main components installed on the same host and interact with each other:

- DIVAdirector Web Server (IIS)

- DIVAdirector Database

- PostgreSQL DB Engine running as a service

- DIVAdirector Server

- Running as a service or desktop application

Oracle highly recommends installing DIVAdirector on a host different from the DIVArchive system to improve the performance of both systems. They may be installed together on the same computer if it is a standalone system.

Minimum System Configuration

The minimum system specifications for deploying DIVAdirector are as follows:

Quad Core Processor

2 GHz or higher

Memory

4 GB or higher

Network

(1) Gb Ethernet connection

System Drive

Hardware mirrored (RAID 1) 100 GB or higher using SATA, SAS, or equivalent drives.

Proxy and Database Storage

Hardware RAID 5 (four drives - three plus one redundant) using SATA, SAS, or equivalent drives. The drive capacity depends on the size of the system.

Modem

Required for dial-in support if a VPN connection is not available.

DVD-ROM Drive

8x or higher DVD-ROM. A CD drive can also be used, however DVD is recommended.

Power

Recommended redundant hot-swap power supplies.

New System Installation

DIVAdirector Server is initially configured to have a single Proxy Drop Folder that is placed (by default) in the C:\Program Files (x86)\DIVAdirector\pdf folder. This Proxy Drop Folder is automatically configured to have the <ORPHAN> settings pointing to the C:\Program Files\DIVAdirector\proxies folder.

Use the following procedure to install DIVAdirector 5.3 on a new system:

1. Verify that the computer name is set before running the installer.

- This is important because the computer name cannot be changed after DIVAdirector is installed because it invalidates the rights and permissions of the IIS user account.

2. Confirm that the Windows Update Service and Remote Registry Service are enabled before installation; they can be disabled after the installation completes. These services are required to allow a component within the installer called the Windows Desktop Experience to be installed.

3. Double-click the DIVAdirector installer to begin installation.

- You will see an Installation Prerequisites Warning dialog box displayed.

4. Click OK to continue.

5. A notification dialog box is displayed if a previous version of DIVAdirector 5 is installed.

- Click Yes to uninstall the previous version, or click No to leave the previous version in place.

6. Click Install to proceed.

- The installer first checks if the Windows Desktop Experience or Windows Media Player is installed. If not, it will install the appropriate program. This will require a restart of the computer to continue the installation.

7. The installer program will continue after checking (and possibly restarting) the computer.

8. If performing a fresh install, select Install DIVAdirector 5.3.0.x as Type of Install (this is the default selection) and click Next. The drop-down list contains the various installation type options available. If upgrading from DIVAdirector 5.0 or DIVAdirector 4.1, choose the appropriate option in the list for the type of installation being performed.

Install DIVAdirector 5.3.0.x

This selection performs a new DIVAdirector installation when no previous version has been installed.

Upgrade DD4 to DD5.3.0.x

This selection upgrades DIVAdirector from version 4.0 or 4.1 to DIVAdirector 5.3.

Upgrade older DD5 to DD5.3.0.x

This selection upgrades DIVAdirector from version 5.x to DIVAdirector 5.3.

WARNING:

In the next step, do not specify a path pointing to a network mapped drive if you intend to use a network share. Only UNC paths can be specified for the proxies folder. The reason is that drive mapping is performed for the interactive user session only; this drive mapping does not exist in the DIVAdirector Web Server service session. Although this dialog accepts a network proxy path, the corresponding changes must be performed to the DIVAdirector Web Server service user account manually.

9. Specify the Proxies Folder Pathname. This page is not available if you are upgrading from DIVAdirector 5.0.
If the Proxy Folder is configured as a network share, the user must belong to the Administrators group and granted read and write access rights to the NAS-based proxy storage.

If the system is expected to operate with a very large set of proxies, Oracle highly recommends having a dedicated drive, local storage (RAID, and so on), or NAS as proxy storage.

10. Click Next.

11. Specify the Database Folder Pathname (this folder must be empty) and click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.3.

12. Specify the Database Backup Folder for database backup and restore, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.3.

13. Specify the Binary Metadata Folder for user uploads of binary files and click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.3.

14. Specify the source location in the Local Archive field and click Next.

15. Specify the destination location in the Local Restore field and click Next.

16. Specify the location in the Local Metadata Drop Folder field and click Next.

17. Specify the location in the SAMMA Metadata Folder field and click Next.

18. Specify the location in the QC Reports Folder field and click Next.

19. Specify the DIVArchive Manager Connection Settings in the DIVArchive Manager Port field, IP Address field, Server TCP Port field, and DIVAdirector Server Proxy Drop Folder Location field, and then click Next.

20. Specify the Username and Password for a local user account under which the DIVAdirector Web application will be run. A complex password is necessary. Click the Install button to continue.

21. Select either the Local System or This user (DOMAIN\User) user account to use for the DIVAdirector Server service.

Local System

DIVAdirector will be limited to use only Local Proxy Storages due to Local System account native Windows limitations.

This user (DOMAIN/User)

The user account provided in the form DOMAIN\User will have access to proxy storages configured as network shares. The user must belong to the Administrators group and granted read and write access rights to NAS-based Proxy Storage. If no domain or the '.' domain is specified, the Local System is implied as the account domain.

22. The installer will continue to run and eventually will prompt for QuickTime Player Options. Click YES when prompted.

23. The QuickTime player will start automatically - close the QuickTime player window to continue installation.

24. When the installation is complete you will be prompted to restart. Click OK to continue.

25. Choose Reboot Now and click Finish.

26. After the computer has restarted, login as Administrator and locate the Internet Information Services (IIS) Manager using the Windows Start Menu.

27. Once the IIS Manager loads, click the computer name of the computer where you are installing DIVAdirector, then click Sites, and then click DIVAdirector 5.

28. Verify that the DIVAdirector 5 website is running by confirming that the Start button on the right side of the screen is disabled (grayed out), indicating that the site is operational.

Optional Manual Adjustments

This section provides instructions for adapting the system if it is getting short on disk space.

Relocating DIVAdirector Database Files

Database files may be migrated to another storage system after installation if necessary. Use the following procedure to migrate the DIVAdirector database to another location:

1. Stop the DIVAdirector Server service. Using the Windows Task Manager verify that there are no DIVAdirector processes running.

2. Locate the PostgreSQL service in the Windows Services Administration window. The PostgreSQL service name has the format postgres-[platform]-[version] - PostgreSQL Server [version]. For example postgres-x64-9.2 - PostgreSQL Server 9.2.

3. Stop the Postgres service. Using the Windows Task Manager, verify that there are no running Postgres processes.

4. Modify the PostgreSQL Service registry settings as follows:

1. Open the Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services.

2. Underneath this key is a key for the Postgres service. It will have the same name as the service located in step 2 - navigate to this key.

3. Double-click the ImagePath value and find the -D path setting. Change the path to the new location. If the path contains spaces, enclose the path entry within quotations.

4. Save the modified setting.

5. Modify the DIVAdirector database location registry setting as follows:

1. Open the Windows Registry Editor and navigate to the appropriate registry key as follows:

32-bit Systems

HKEY_LOCAL_MACHINE\SOFTWARE\Front Porch Digital Inc.\DIVAdirector\DB

64-bit Systems

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Front Porch Digital Inc.\DIVAdirector\DB

2. Modify the registry value PostgresDB to the new database directory location.

6. If the Windows Services Administration window is still open, close and then reopen it.

7. Restart the PostgreSQL service.

8. Restart the DIVAdirector Server service.

Using Network Attached Storage (NAS) for the Proxy File Storage Folder

The Proxy File Storage Folder may become very large and can be placed on Internal Server Storage or on an External (larger) Network Attached Storage (NAS) Array. A new Proxy Storage Location pointing to a Shared Network Folder must be added. Refer to the Oracle DIVAdirector Administrator's Guide for directions on adding a new Proxy Storage Location. The Network Path must be specified in the following UNC format:

\\hostname\sharename\subfolder\...\subfolder

The Microsoft Windows Local System account is restricted from accessing network resources; therefore a dedicated user account must be used instead. The same account must be granted access rights to read the Proxy folder on the NAS. The Proxy folder must be configured to allow the user account running DIVAdirector Server to write to the Proxy folder.

To simplify these account settings, the same account may be used for running the DIVAdirector Web Server service and the interactive session with the DIVAdirector Server. This account must be granted read and write permissions for accessing the Proxy folder on the NAS and the user account running the DIVAdirector Web Server service must be a member of the Administrators group because typically this service must have access to the Program Files folder.

It is important to understand that using a path with a mapped drive letter (for example K:\Proxies) is not supported because this path will be used by the DIVAdirector Web Server for opening proxy files upon user requests. The Web Server that runs as a service is not aware of mapped network drives because these are associated with an interactive user session.

Note:
See the Oracle DIVAdirector Administrator's Guide for step-by-step account configuration procedures.

Using Network Attached Storage (NAS) for Binary Storage

Binary storage may become very large, so it can also be placed on a NAS array if necessary. The DIVAdirector Binary Storage Virtual Directory must be reconfigured to point to a shared network folder. See the Oracle DIVAdirector Administrator's Guide for directions on configuring the DIVAdirector Binary Storage Virtual Directory.

The network path must be specified in UNC format, for example:

\\hostname\sharename\subfolder\...\subfolder

The DIVAdirector Web Server user account used to run this service must be granted permissions to read and write the Binary Storage folder on the NAS. The user account running the DIVAdirector Web Server service must be a member of the Administrators group because typically this service must access the Program Files folder.

Note:
See the Oracle DIVAdirector Administrator's Guide for step-by-step Account Configuration Procedures.

Upgrading DIVAdirector 4 to DIVAdirector 5.3

If you are upgrading an existing DIVAdirector 4 system, it must be running one of the operating systems specified in "DIVAdirector Prerequisites."

Use the following procedure to upgrade from DIVAdirector 4 to DIVAdirector 5.3:

1. Perform a full database backup to a known location before starting any upgrade process. This can be done through the DIVAdirector 4 Web interface to produce a .LHB file. Alternatively, manually stop the DIVAdirector CMS Database Server service and then copy the entire contents of the database folder to an external drive or folder.

2. Run the installer and click Install to continue.

3. The installer first checks if the Windows Desktop Experience or the Windows Media Player is installed. If one of these is not found, it will install the appropriate application. This will require a restart of the computer to continue the installation.

4. After the computer has been restarted, select the Upgrade DD4 to DD5 Server option as the Type of Install using the drop-down list and click Next.

5. From this point forward, follow the same procedure as installing DIVAdirector onto a new system (see "New System Installation").

4 DIVA Transcode Service

This chapter discusses the new DIVA Transcode Service introduced with DIVAdirector 5.3.

Introduction

Oracle DIVAdirector 5.3 introduces a new transcode service to the system. The service contains two main components. The first component is a RESTful API for submitting and viewing requests, and viewing currently configured transcoder information (name, version, and so on). The second component is a time-based background process that executes periodically to update the progress and state of all actively transcoding requests.

The Root Path must point to a location that the currently configured transcoder implementation service can read. However, the new transcode service does not need read access to the location. To clarify the distinction between the new transcode service and the transcoder implementation, the transcode service provides a common interface for multiple transcoder implementations (for example Vantage, FlipFactory, and so on). The transcoder implementation (for example the Vantage service) requires read access to the Root Path.

The transcode service API is in a self-hosted Open Web Interface for .Net (OWIN) application and contained in a Windows service - removing any dependency on IIS. The request information is held in a SQL Server Express LocalDB database that is installed with the service installer, and accessed by the data layer through a common interface.

To use the transcoder service, users select transcodeSvc as the source or destination when submitting requests. To configure the new transcode service correctly, the Source Name must match the DIVAdirector TranscodeSourceDestName configuration value, and the Connect Options entry does not include any of the tr flags (for example tr_restore_format, tr_names, and so on).

Web Configuration File

The new transcoder service requires several changes to the DIVAdirector Web configuration. The web configuration file is located in the installation's www folder. For example C:\Program Files (x86)\DIVAdirector 5\www\Web.config.

The setting updates are as follows:

DIVArchive Web Services (WS) Endpoint

You can configure the WS Endpoint to any available port.

<add key="DIVArchiveAPIUrl" value="http://10.80.106.57:9763/services/DIVArchiveWS_REST_2.1/" />

appname

This identifies the name of the application to be registered in the DIVArchive WS API interface. Specifically, the value of the appName parameter passed to the registerClient method. This is required before interfacing with the DIVArchive WS API. For example:

<add key="appName" value="DIVAdirector" />

TranscodeSourceDestName

This identifies the name of the preconfigured source or destination that defines the DIVArchive restore location to be used by DIVAdirector for creating proxies with the transcoding service.

<add key="TranscodeSourceDestName" value="transcodeSvc"/>

Windows Services

The DIVAdirector Windows service installed along with the web application handles background tasks performed outside of the context of a web request (for example proxy creation, metadata extraction, drop folder monitoring, and so on). The Windows Management Console displays the legacy service as DIVAdirector Server Service.

Background task functionality is being migrated away from the legacy service to a new service. The new Oracle.DIVAdirector.TaskManager service currently handles only a subset of the functionality and therefore both services will be installed by the DIVAdirector installer until the legacy service has been fully migrated.

The Oracle.DIVAdirector.TaskManager 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 attention as describe below.

1. DIVArchive Web Services API REST Endpoint Configuration
Four settings require configuration in the <appSettings> section:

applicationName

This 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" />

locationName

This 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" />

processID

This 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" />

DIVArchiveApiUrl

This 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/" />

2. Transcoder Service Access Configuration
Three settings require configuration in the <TranscodeSettingsConfigurationSection> section:

TranscoderClientSettings

The TranscoderApiUrl is the url of the transcode service base API endpoint. An optional integer LocationId can be added to TranscoderClientSettings to override the default location.

<TranscoderClientSettings TranscoderApiUrl="http://localhost:9876/api/">

PresetName

The PresetName is the name of a preset configuration in the transcoder service. A preset is a name associated with a preset ID (for example a Vantage workflow ID).

PresetName="Default Video Proxy"

ProxyableFileExtensions

ProxyableFileExtensions is the list of file extensions for which the service will try to create a proxy.

ProxyableFileExtensions="mxf,lxf,avi,mpg,mpeg,mov,mp4">

The following list of parameters is being passed to the preset workflow defined by PresetName. You can add more parameters to this list as needed without any code changes.

<Parameters>
<Parameter Key="GenerateKeyFrames" Value="True" />
<Parameter Key="KeyframeCaptureInterval" Value="00:00:01:00@29.97" />
</Parameters>

3. 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.

TranscodeOnRestoreCompleteTask

This task polls the progress of a DIVArchive Restore request (through the DIVArchive Web Services (WS) API REST endpoint), and initiates a Transcode request upon completion. This task is also responsible for calling the Proxy Creation Service.

<ScheduledTask Name="TranscodeOnRestoreCompleteTask" Type="Oracle.DIVAdirector.TaskManager.Tasks.TranscodeOnRestoreCompleteTask, Oracle.DIVAdirector.TaskManager" IntervalInSeconds="10" Enabled="true" />

UpdateRequestsStatusTask

This task monitors and updates the state and progress of all active DIVArchive requests.

<ScheduledTask Name="UpdateRequestsStatusTask" Type="Oracle.DIVAdirector.TaskManager.Tasks.UpdateRequestsStatusTask, Oracle.DIVAdirector.TaskManager" IntervalInSeconds="10" Enabled="true" />

4. Postgres Database Communication Configuration
This connection string should use the same server and credentials as the connection string defined in the DIVAdirector web application's web.config file.

<connectionStrings>
<add name="DIVADirectorContext" connectionString="Server=localhost;Database=DIVAdirector;User Id=postgres;Password=Manager;" providerName="Npgsql" />
</connectionStrings>

Database Settings

WARNING:

Oracle highly recommends not performing these modifications without having an Oracle Support Technician present.

There are several configuration settings stored in the LocalDB that can only be modified by directly modifying database rows.

Transcoder Settings

The following transcoder settings can be modified directly in the database:

- TranscoderSettings.Transcoder stores the name of the current transcoder implementation. Vantage is the only transcoder supported in this release.

- VantageSettings.Host stores the name of the computer running the Vantage SDK Service.

- VantageSettings.Port stores the port number used by the Vantage SDK Service.

- VantageSettings.MetadataActionDescriptions stores the descriptions of actions in the Vantage workflow that expose metadata variables that should be associated with a job.

Presets

The Presets table stores a named mapping to a transcoder implementation's internal workflow identifier. For Vantage, the InternalId is the workflow identifier.

The CheckStatusOnStartup parameter is a Boolean flag indicating a required preset that must be checked during service startup. A warning will be logged if CheckStatusOnStartup is set to true and the preset is not found. The service will attempt to activate the preset if CheckStatusOnStartup is to true and the preset is found but not active. The transcode log files will have entries for this check and attempted activation.

Locations

The Locations table stores a set of predefined output storage locations. The transcode service will only accept jobs with a valid storage location. If no location is specified in the transcode request, the service will attempt to find a location using IsDefault (if set to true) and use that location. Log files will indicate that no location was specified, and the default value used.

The Path column stores the path associated with the location. This value will form the base output path for the transcoded job. The remainder of the path will be formed by the Job ID returned from the transcode service. For example if the location path is \\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev and a Job ID 6449d0db-2377-4e3d-a969-be09a742a63d is returned from the transcode service, then the final output path for the transcoded file will be \\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev\6449d0db-2377-4e3d-a969-be09a742a63d.

API Endpoints

There are two REST main endpoints that are configured by modifying the database entries:

- /api/transcoder is used for viewing currently configured transcoder information.

- /api/jobs/[jobId] is used for viewing job progress and submitting new jobs.

Example #1

To create a new transcode job the request is as follows:

HTTP POST to /api/jobs
{
"inputFilePath": " \\rootPath\InputFileMXF",
"output":{
"presetName": "Default Video Proxy",
"parameters": [
{
"name": "GenerateKeyFrames",
"value": "True"
},
{
"name": "KeyframeWidth",
"value": "128"
}, ….
]
}
}

The response to the request is as follows:

201 Created
Headers:
…. Location: http://localhost:9876/api/jobs/794660fe-2c37-491c-b7a9-7fe27f2c6346....
Body:
{
"jobId": "794660fe-2c37-491c-b7a9-7fe27f2c6346",
"internalId": "57d0a08b-fa5f-4ff7-8177-c1d2d4adf92a",
"inputFilePath": "\\rootPath\InputFileMXF",
"outputFilePath": null,
"status": 8,
"createdDate": "2015-08-13T10:26:06.5553211-06:00",
"createdBy": null,
"updatedDate": "2015-08-13T10:26:06.5553211-06:00",
"updatedBy": null,
"progress": 0,
"metadata": null,
"output": {
"id": 11,
"presetName": "Default Video Proxy",
"location": {
"id": 1,
"name": "Default Location",
"path": "\\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev",
"isDefault": true
},
"parameters": [
{
"id": 40,
"name": "GenerateKeyFrames",
"type": null,
"value": "True"
},
{
"id": 43,
"name": "KeyframeWidth",
"type": null,
"value": "128"
},
{
"id": 45,
"name": "OutputFileName",
"type": null,
"value": "AA004001"
}
]
}
}

Example #2

To get all jobs summaries the request is as follows:

HTTP GET TO /api/jobs

The response to the request is as follows:

[
{
"jobId": "2ebbd1e9-b404-4909-944e-8d48c0a4b370",
"internalId": "57d0a08b-fa5f-4ff7-8177-c1d2d4adf92a",
"inputFilePath": "C:\Users\Administrator\Desktop\watch\AA004001.MXF",
"outputFilePath": "\\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev\2ebbd1e9-b404-4909-944e-8d48c0a4b370\AA004001.mp4",
"status": 6,
"createdDate": "2015-08-13T10:26:06.557",
"createdBy": null,
"updatedDate": "2015-08-13T10:26:26.067",
"updatedBy": "TaskManager",
"progress": 100
},
{
"jobId": "25970df1-7f60-4f65-8ee9-49b83b908364",
"internalId": "44c54311-da47-443f-b7e2-21c56c247e0e",
"inputFilePath": "C:\Users\Administrator\Desktop\watch\AA004001.MXF",
"outputFilePath": "\\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev\25970df1-7f60-4f65-8ee9-49b83b908364\AA004001.mp4",
"status": 6,
"createdDate": "2015-08-13T10:19:26.28",
"createdBy": null,
"updatedDate": "2015-08-13T10:19:50.687",
"updatedBy": "TaskManager",
"progress": 100
}]

Example #3

To get job details the request is as follows:

HTTP GET to /api/jobs/794660fe-2c37-491c-b7a9-7fe27f2c6346

The response to the request is as follows:

{
"jobId": "794660fe-2c37-491c-b7a9-7fe27f2c6346",
"internalId": "57d0a08b-fa5f-4ff7-8177-c1d2d4adf92a",
"inputFilePath": "C:\Users\Administrator\Desktop\watch\AA004001.MXF",
"outputFilePath": "\\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev\2ebbd1e9-b404-4909-944e-8d48c0a4b370\AA004001.mp4",
"status": 6,
"createdDate": "2015-08-13T10:26:06.557",
"createdBy": null,
"updatedDate": "2015-08-13T10:26:26.067",
"updatedBy": "TaskManager",
"progress": 100,
"metadata": "[{\"Key\":\"Container Format\",\"Value\":\"Material Exchange Format (OP-1a)\"},{\"Key\":\"Content Duration\",\"Value\":\"00:00:08:04@25\"},{\"Key\":\"Video Framerate\",\"Value\":\"25\"},{\"Key\":\"Header Timecode\",\"Value\":\"01:06:18:15@25\"},{\"Key\":\"OutputFileFullPath\",\"Value\":\"\\\\10.80.106.91\\c$\\Users\\Administrator\\Desktop\\output\\Dev\\2ebbd1e9-b404-4909-944e-8d48c0a4b370\\AA004001.mp4\"}]",
"output": {
"id": 11,
"location": {
"id": 1,
"name": "Default Location",
"path": "\\10.80.106.91\c$\Users\Administrator\Desktop\output\Dev",
"isDefault": true
},
"presetName": "Default Video Proxy",
"parameters": [
{
"id": 40,
"name": "GenerateKeyFrames",
"type": null,
"value": "True"
},
{
"id": 43,
"name": "KeyframeWidth",
"type": null,
"value": "128"
},
{
"id": 45,
"name": "OutputFileName",
"type": null,
"value": "AA004001"
}
]
}
}

5 ShuttlePro V2 or ShuttleXpress Control Pad Installation and Configuration

To set up and configure ShuttlePro V2 or ShuttleXpress Control Pads, run the installer supplied with the software by the manufacturer and navigate through the installation using the default selections. When complete, copy the Shuttle configuration file as follows:

For Mac OSX:

Copy C:\Program Files (x86)\DIVAdirector 5\Support\etc\Pref file - Mac\com.contourdesign.shuttle.prefs to ~/Library/Preferences/.

For Microsoft Windows 7:

Copy C:\Program Files (x86)\DIVAdirector 5\Support\etc\Pref file - Windows\CDIshuttle.pref to C:\Program Data\Contour Design.

Note:
Windows requires privileges to show hidden files in the Folder Settings to see the Application Data or Program Data paths.

Once the setup is complete, you must set focus to the player (click once in the player area) before the Shuttle Control can be used.

Glossary

Data Store

A data repository of a set of integrated objects.

Lightweight Directory Access Protocol (LDAP)

The Lightweight Directory Access Protocol (LDAP) is an application protocol for accessing and maintaining Distributed Directory Information Services over an Internet Protocol (IP) Network.

Open Web Interface for .Net (OWIN)

OWIN defines a standard interface between .NET web servers and web applications. The goal of the OWIN interface is to decouple server and application, encourage the development of simple modules for .NET web development, and, by being an open standard, stimulate the open source ecosystem of .NET web development tools.

Proxy

In DIVAdirector, proxy refers to a lower resolution version of the asset that is archived in Oracle DIVArchive.

Root (SuperAdmin)

The DIVAdirector SuperAdmin is a special user account used for System Administration. In DIVAdirector this account is named admin and is identified with an authorization flag in the user's profile, allowing administrative functions to be performed.

Uniform Naming Convention (UNC)

The Uniform Naming Convention specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows Systems has the generic form \\ComputerName\SharedFolder\Resource.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.