This chapter discusses DIVAdirector 5.4 installation and deployment, and includes the following information:
DIVAdirector consists of four main components installed on the same host and interacting with each other:
DIVAdirector Web Server (IIS)
DIVAdirector Database - PostgreSQL DB Engine running as a service
Oracle DIVAdirector TaskManager running as a service
Oracle DIVAdirector API running as a service
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.
The minimum system specifications for deploying DIVAdirector are as follows (see the Oracle DIVArchive Supported Environments Guide in the Oracle DIVArchive Core documentation library for more information):
2 GHz or higher
8 GB or higher (16 GB or higher is recommended)
(1) GbE Ethernet connection
Hardware mirrored (RAID 1) 100 GB, or higher, using SATA, SAS, or equivalent drives.
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.
Required for dial-in support if a VPN connection is not available.
Recommended redundant hot-swap power supplies.
Use the following procedure to install DIVAdirector 5.4 on a new system:
Caution:
Ensure that the computer name is set before running DIVAdirector installer. The computer name cannot be changed after DIVAdirector is installed because it invalidates the rights and permissions of the IIS user account.Confirm that the Windows Update Service and Remote Registry Service are enabled before installation. You can disable them after the installation completes. These services are required to allow a component within the installer called the Windows Desktop Experience to be installed.
Double-click the DIVAdirector installer to begin installation.
You will see an Installation Prerequisites Warning dialog box displayed.
Click OK to continue.
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.
Click Install to proceed.
The installer first checks if the Windows Desktop Experience or Windows Media Player are installed. If not, it will install the appropriate program. This will require a restart of the computer to continue the installation
The installer program will continue after checking (and possibly restarting) the computer.
If performing a fresh install, select Install DIVAdirector 5.4.1 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.2 or DIVAdirector 5.3, choose the appropriate option in the list for the type of installation being performed. The available installation types are as follows:
This selection performs a new DIVAdirector installation when no previous DIVAdirector release has been installed.
This selection upgrades DIVAdirector from release 5.2.x to DIVAdirector 5.4.
This selection upgrades DIVAdirector from release 5.3.x to DIVAdirector 5.4.
Caution:
In the next steps, do not specify a path pointing to a network mapped drive if you intend to use a network share. Only UNC (Uniform Naming Convention) 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.Specify the Database Folder Pathname (this folder must be empty), and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
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.4.
Specify the source location in the Local Archive field, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the destination location in the Local Restore field, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the location in the QC Reports Folder field, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the Transcode Service api url, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the Oracle DIVA Enterprise Connect address, port, client ID, and API key, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the DIVAdirector host name, IP address, and port, and then click Next. This page is not available if upgrading from an earlier version of DIVAdirector 5.4.
Specify the Username and Password for a local user account that will run the DIVAdirector Web application.
A complex password is necessary. If you are using either a SAN, or NAS, for proxy storage, then it is better to run IIS as a domain account.
Click Install to continue.
When the installation is complete you will be prompted to restart. Click OK to continue.
Choose Reboot Now and click Finish.
After the computer has restarted, login as Administrator and locate the Internet Information Services Manager using the Windows Start menu.
After the IIS Manager loads, click the computer name of the computer where you are installing DIVAdirector, then click Sites, and then click DIVAdirector 5.
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.
This section describes instructions for adapting the system if it is getting short on disk space.
You can migrate database files to another storage system after installation if necessary. Use the following procedure to migrate the DIVAdirector database to another location:
Stop IIS and all DIVAdirector services. Use the Windows TaskManager to verify that there are no DIVAdirector processes running.
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.6 - PostgreSQL Server 9.6.
Stop the Postgres service. Using the Windows TaskManager, verify that there are no Postgres processes running.
Modify the PostgreSQL Service registry settings as follows:
Open the Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services.
Underneath this key is a key for the Postgres service. It will have the same name as the service identified in Step 2 - navigate to this key.
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.
Save the modified setting.
Modify the DIVAdirector database location registry setting as follows:
Open the Windows Registry Editor and navigate to the appropriate registry key as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Front Porch Digital Inc.\DIVAdirector\DB
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Front Porch Digital Inc.\DIVAdirector\DB
Modify the registry value PostgresDB to the new database directory location.
Close the Windows Services Administration window (if it is still open), and then reopen it.
Restart the PostgreSQL service.
Restart the DIVAdirector Server service.
The Proxy File Storage Folder may become very large. You can place it on internal Server Storage or on an external (larger) NAS (Network Attached Storage) array. You must add new Proxy Storage Location pointing to a Shared Network Folder. See 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:
\\host_name\share_name\subfolder\...\subfolder
The Microsoft Windows Local System account is restricted from accessing network resources. Therefore, you must use a dedicated user account instead. You must grant access rights to read the Proxy folder on the NAS to the same account. You must configure the Proxy folder to allow the user account running the IIS application pool and the Oracle DIVAdirector TaskManager to write to the Proxy folder.
You must grant this account 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. You must also add the account to the IIS_IUSRS group to run the IIS application pool.
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:
DIVAdirector Proxy storage can also be on a SAN. However, some SANs do not have drivers that are fully compatible with IIS and cannot be used for this purpose. See the Oracle DIVAdirector Administrator's Guide for step by step account configuration procedures.If you are upgrading an existing DIVAdirector 4 system, it must be running one of the operating systems specified in DIVAdirector Prerequisites. Contacting Oracle support for assistance in properly upgrading DIVAdirector is highly recommended.
Use the following procedure to upgrade from DIVAdirector 5.2 (and later) to DIVAdirector 5.4:
Perform a full database backup to a known location before starting any upgrade process.
Run the installer, and click Install to continue.
The installer first checks if any prerequisites need to be installed. If one of the prerequisites is not found, it will install the appropriate application. This will require a restart of the computer to continue the installation.
After the computer has been restarted, select the Upgrade DD5.2 to DD5.4.x, or Upgrade DD5.2 to DD5.4.x Server option as the Type of Install using the drop-down list, and then click Next.
From this point forward, follow the same procedure as installing DIVAdirector onto a new system (see New System Installation).
You can set up PostgreSQL SSPI Pass-Through Authentication after DIVAdirector is upgraded if you are using the same domain user account to run all DIVAdirector services, the IIS application pool, and PostgreSQL. This configuration removes the need to have plain text user names and passwords in the connection strings, providing improved security.
Follow the instructions at https://wiki.postgresql.org/wiki/Configuring_for_single_sign-on_using_SSPI_on_Windows to enable SSPI for PostgreSQL.
After you complete the instructions, you must update the configuration files for each of the following DIVAdirector services. You must modify the configuration files in the following default locations:
C:\Program Files(x86)\DIVAdirector 5\www\Web.config
C:\Program Files (x86)\Divadirector 5\TaskManager\Oracle.DIVAdirector.TaskManager.exe.config
C:\Program Files (x86)\Divadirector 5\Api\Oracle.DIVAdirector.Api.exe.config
C:\Program Files (x86)\Divadirector 5\Tools\DDServices\DIVADirectorServices.exe.config
In each of the services the key will be the same:
<connectionStrings>
<add name="DIVAdirectorContext"
connectionString="Server=localhost;Database=DIVAdirector;User Id=postgres;Password=MANAGER;" providerName="Npgsql"
/>
</connectionStrings>
You must modify the connection string parameter as follows:
connectionString="Server=localhost;Database=DIVAdirector;Integrated Security=true;Include Realm=true;"