3 System Installation

This chapter discusses the DIVAdirector 5.2 installation and deployment.

Planning System Deployment

DIVAdirector consists of three main components which are 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.

It is highly recommended to install DIVAdirector on a host separate from the DIVArchive system to improve the performance of both systems. However, they may be installed together on the same computer for 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) Gigabit 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 size of the drives 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 but 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.2 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 since 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 displayed.

  4. Click OK to continue.

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

    • Click the Yes button to uninstall the previous release or the No button to leave the previous release in place.

  6. Click the Install button 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 computer restart 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.2.0.x as Type of Install (this is the default selection) and click the Next button. The list describes the various Type of Install list options. 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.2.0.x

    Use this selection for new DIVAdirector installation where no previous release has been installed.

    Upgrade DD4 to DD5.2.0.x

    Use this selection to upgrade DIVAdirector from release 4.0 or 4.1 to DIVAdirector 5.2.

    Upgrade older DD5 to DD5.2.0.x

    Use this selection to upgrade DIVAdirector from release 5 to DIVAdirector 5.2.

    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 must be 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 it is highly recommended to have a dedicated drive, local storage (RAID, and so on), or NAS as proxy storage.

  10. Click the Next button.

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

  12. Specify the Database Backup Folder for database backup and restore and click the Next button. This page is not available if upgrading from an earlier release of DIVAdirector 5.2.

  13. Specify the Binary Metadata Folder for user upload of binary files and click the Next button. This page is not available if upgrading from an earlier release of DIVAdirector 5.2.

  14. Specify the source location for Local Archive and then click Next.

  15. Specify the destination location for Local Restore and then click Next.

  16. Specify the location for the Local Metadata Drop Folder and then click Next.

  17. Specify the location for the SAMMA Metadata Folder and then click Next.

  18. Specify the location for the QC Reports Folder and then click Next.

  19. Specify the DIVArchive Manager Connection Settings including the DIVArchive Manager Port, DIVArchive Manager IP Address, DIVAdirector Server TCP Port and DIVAdirector Server Proxy Drop Folder Location, 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. Choose 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 proxy storages configured as network shares. The user must belong to the Administrators group and must be 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 will eventually prompt you for QuickTime Player Options. Click YES when prompted.

  23. The QuickTime player will start automatically - close the 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.

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

Once the IIS Manager loads, click the name of the computer where you are installing DIVAdirector, then Sites, and then 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.

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]-[release] - PostgreSQL Server [release]. 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 with 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 can become very large and can be placed on Internal Server Storage or on an External (larger) Network Attached Storage (NAS) Array by adding a new Proxy Storage Location pointing to a Shared Network Folder. Refer to the Oracle DIVAdirector Administrator's Guide for directions on adding a new Proxy Storage Location. The Network Path must be specified using 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 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. 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 by reconfiguring the DIVAdirector Binary Storage Virtual Directory 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 using the 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.2

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.2:

  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 the Install button 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 computer restart to continue the installation.

  4. Installation will continue after the computer has restarted. Select Upgrade DD4 to DD5 Server as the Type of Install using the list and click Next.

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