This section will assist you in upgrading from an existing Curator 3.4 system to the Curator 3.5.1 or 3.5.2 software release.
There are no differences in procedures and requirements between Curator 3.5.1 and 3.5.2 version.
Services and applications in white below have a new version, those in blue received HotFix/Upgrade in Curator Patch and in grey have not received an upgrade in this release:
Service | Previous Version - 3.4 | Current Version - 3.5.1 |
Analytics | 1.2.1.2 | 1.2.1.2 |
Curator Server | 4.0.1.151 (Hotfix 4.0.1.177) | 4.1.1.207 |
Curator Media Agent | 1.1.1.7 (Hotfix 1.1.1.9) | 1.1.1.9 |
Device Director | 5.18.1.61 (Hotfix 5.18.1.72) | 5.18.1.72 |
Licence Manager | 1.7.1.13 | 1.7.1.13 |
Metadata Central Teragator (optional) | 2.0.4 | 2.2.1 |
Process Engine | 2.17.1.43 (Hotfix 2.17.1.30) | 2.19.1.47 Accelerated Update (3.5.1 was 2.18.1.41) |
Workflow Agent (optional) | 1.0.1.15 | 1.0.1.15 |
XChange Manager | 2.6.1.76 | 2.6.1.76 |
XCode | 4.0.1.81 | 4.1.1.21 |
XFer | 2.13.1.13 (Hotfix 2.13.1.24) | 2.14.1.46 |
Applications | Previous Version - 3.4 | Current Version - 3.5.1 |
Curator Clip Link | 3.2.1.67 | 3.4.1.104 Hot Fix (3.5.1 was 3.4.1.97) |
Curator Clip Select | 2.13.1.21 (Hotfix 2.13.1.29) | 2.13.1.29 |
Curator File Service | 1.0.1.100 (Hotfix 1.1.1.34) | 1.1.1.34 |
Curator Gateway | 1.5.1.151 (Hotfix 1.5.1.156) | 1.8.1.28 |
Curator Logger | 2.3.1.49 (Hotfix 2.3.1.55) | 2.4.1.23 |
Curator System Administrator | 1.6.1.93 | 1.6.1.93 |
Curator Connect | 1.6.1.42 (PC) 1.6.1.45 (Mac) | 1.6.1.102 (PC) or 1.6.1.106 (Mac) |
Curator For Adobe | 3.2.1.6 (PC) \ 3.2.9 (Mac) (Hotfix 3.2.1.11 (PC) \ 3.2.14 (Mac)) |
3.3.1.43 (PC) \ 3.3.52 (Mac) |
Upgrading Software
Backups
Databases
Open MySQL Workbench | |
|
|
Open Data Export panel |
Under Server, open a Data Export tab: |
|
|
Tick Objects to Export |
Tick all three options under Objects to Export:
|
|
|
Set Export Options | Under Export Options, choose Export to Self-Contained File: |
|
|
Export curatordb |
Under Tables to Export, tick curatordb only: Set the export path and filename under Export Options: Click Start Export and confirm the export is successful: |
|
|
Export device director | Under Tables to Export, tick devicedirector only: Set the export path and filename under Export Options: Click Start Export and confirm the export is successful: |
|
|
Export process engine | Under Tables to Export, tick processengine only: Set the export path and filename under Export Options: Click Start Export and confirm the export is successful: |
Solr Directory
Navigate to Solr Folder |
As part of the backup process with regards to Curator services, it is recommended to make a backup of the Solr folder structure in the event of needing to roll back. Note: This is a manual step and should only be attempted when the Curator Server Service has been stopped, making a backup copy while it is running may lead to corruption of the copied database. By default, the Solr folder to copy is found here: C:\Program Files\IPV\Curator\Server\Solr\server\ |
|
|
Back up Solr Folder | Copy and Paste the entire Solr folder into the same folder with other backups. |
Workflows
Open Process Designer | |
|
|
Select Bulk Export | Under File, select Bulk Export: |
|
|
Set Export Directory | Enter a suitable output path. Do not use the Browse button. Copy and paste a path into the box: Please note: Files are saved individually, not in a packaged zip. |
|
|
Click All and Export | |
|
|
Confirm Successful Export | Check the output folder for the saved xml files: When finished, click the X in the top right of the confirmation dialog box: |
Plugins
Browse to Curator Server Installation | |
|
|
Copy Config Folder | Copy the entire Config folder to a safe location. |
|
|
Copy Options Folder | Copy the entire Options folder to a safe location. |
|
|
Browse to Clip Link Folder | |
|
|
Copy Plugins Folder |
Copy the entire Plugins folder to a safe location. |
|
|
Browse to Clip Select Folder |
Browse to: %ROOT_TO_INETPUB%\inetpub\wwwroot\CuratorClipSelect |
|
|
Make a Copy of Plugins Folder | Copy the entire Plugins folder to a safe location. |
Content Images
Browse to Clip Link Folder | |
|
|
Open the Content Folder | |
|
|
Copy the Pinned Searches Folder | Copy the entire PinnedSearches folder to a safe location. |
Config Files
Curator Server Config | Under Curator Server's install directory, make a copy of the Config folder and Services.CuratorServer.Hosts.WindowsService.exe.Config file. |
|
|
Device Director Config | Under Device Director's install directory, make a copy of the Services.XCodeManager.Hosts.WindowsService.exe.Config file. |
|
|
Process Engine Config | Under Process Engine's install directory, make a copy of the Services.ProcessEngine.Hosts.WindowsService.exe.Config file. |
|
|
Curator Clip Link Config | Under Clip Link's install directory, make a copy of the Web.config file. |
|
|
Curator Clip Select Config | Under Clip Select's install directory, make a copy of the Web.config file |
|
|
Curator Gateway appsettings.json JSON file | Under Curator Gateways install directory, make a copy of the appsettings.json file. |
|
|
Curator Logger Config | If Curator Logger is installed, under its install directory, make a copy of the Web.config file. |
Resources
Browse to Curator Folder Share | Browse to the Curator Folder Share created by Process Engine during initial setup: |
|
|
Make a copy of the Resources Folder | Make a copy of the entire Resources folder: |
Services
Prerequisites
|
Note: Yellow-labeled prerequisites denote previously installed prerequisites from the previous release. Green-labeled prerequisites are new for this release. |
Storage considerations for Curator File Service | Please read this article to ensure the correct Curator File Server storage method is set in order to allow users to have access to all assets including High Resolution files. |
SSL Certificate | An SSL Certificate is required by default for Curator Server and should be acquired and installed before continuing. |
.NET 4.7.2 | dotNET 4.7 is required for certain Curator Services and Applications. If not already installed by default on the system, Windows 2016 Servers and earlier will not have it by default - download it and install it from Microsoft's website. |
VC Runtimes |
The Microsoft Visual C++ Runtime libraries are required. Download and run the installers using the links below and accept default settings. Visual Studio 2013 C++ Redistributable can be downloaded from Microsoft's Website. Visual Studio 2015-2019 C++ Redistributable can be downloaded from Microsoft's Website. |
QuickTime |
Only install Apple's ProRes codecs if the system needs to support ProRes material - this is an optional component that only applies to XCode machines. The ProRes codecs are included as "QuickTime Essentials" within the QuickTime installer from Apple's Website. |
Install IIS |
Click Install IIS to look at a detailed install guide if required. IIS (Internet Information Services) is a webserver which can be selected as a Server Role in the OS Server Manager. Add all dot net options to the default features and select all the Application Development options under Role Services when prompted. |
WebDeploy 3.6 |
WebDeploy is an IIS tool that enables Curator Web applications to be easily imported into the webserver. Download the 64-bit installer from Microsoft's official website. Note: You may already have WebDeploy installed as part of your previous install. |
URL Rewrite Module |
URL Rewrite is a module for IIS Download an installer from Microsoft's Website. |
Install ASP dotNET Core Runtime | Runtime version .Net Core 3.1 and .Net Core 5.0 are required support for Curator Gateway. Download the installers from Microsoft's Website. |
Java |
Java provides features to the Curator Server Service. Click here to view the recommended Java options. |
MySQL |
Some IPV Services require the MySQL relational database. Download the installer from MySQL's Official Website. |
Neo4j | The Analytics Service requires Neo4j as its database. Check the required version in Neo4j and Download the Community version zip file from Neo4j's website. |
GhostScript |
Ghostscript is a standalone installer required for creating thumbnail previews of graphic files, providing support for .ai, .eps and .psd files. Download version 9.25 from Ghostscripts github.
Sept 2022 Note: gs9561w64.exe has been downloaded and tested from Ghostscript : Downloads. Note that this test has been completed using the GNU Affero General Public License version, NOT the Artifex Commercial License which is likely required to be a paid for licence in order to download and install for commercial entitles in this respect. |
First Install Erlang. Refer to the guide below for RabbitMq, which includes both Erlang and RabbitMq. | |
RabbitMQ | Install RabbitMq. Refer to the guide here. |
Curator Server
Required Prerequisites |
- SSL Certificate - Erlang and RabbitMQ - Net Framework 4.6.2 - MySQL 5.7 & Workbench 6.3.9 Minimum - OpenJDK/ Eclipse or Amazon Corretto |
Compulsory steps |
- During the upgrade to this release, you MUST delete the Solr Core located in [installation path]\Curator\Server\Solr\server\solr\. From here, delete the curator_2_4 folder. The correct Core will be generated by starting the service.
- As it is time-consuming the upgrade step for database version 2.7 to 3.0 is now marked as manual. Warning: This script may take some time to complete. This script should be executed as follows:
|
Run Installer | |
|
|
Accept Licence Agreement | |
|
|
Set Service Account | Choose the Service Account option and enter valid credentials for a user with local administrative rights. Click Test Credentials, and after confirming your details, click Next: |
|
|
Enter MySQL Details |
Click Test Connection: If the MySQL Dump Fullpath field is not already configured as shown in the screenshots, find the MySQL installation directory and the mysqldump.exe file under the Bin folder. After confirming valid details, click Next:
|
|
|
Enter RabbitMq details | Then click Next. |
|
|
Set Install Directory | |
|
|
Set Logging Level | |
|
|
Configuration Details |
Note: Do not change the Solr core configuration. Solr is installed alongside Curator Server. Enter an SSL certificate thumbprint for setting up HTTPS connectivity. For finding a Certificate thumbprint, click here. Change the Curator Gateway host with the IIS hosts FQDN/IP. Replace: https://localhost/CuratorGateway With: |
|
|
Click Install | |
|
|
Click Finish |
Database Scripts
A collection of helper scripts are needed during this upgrade.
Refer to the below steps to verify the curatordb version number.
Open MySQL Workbench | |
|
|
Open Database Connection |
Open the database connection to the MySQL database hosting the curatordb schema: |
|
|
Highlight Curatordb |
From the Schemas tab, double-click the curatordb database: |
|
|
Select all from version | From within curatordb, scroll down to find the version table. Right-click and choose Select Rows - Limit 1000: |
|
|
Note version number | |
|
|
Select appropriate script file based on version number | From Curator Server, navigate to this location: C:\Program Files\IPV\Curator\Server\Sql\Upgrade Using the version ID noted above, select the specific script file from the *current* version number to the *upgrade* version number. Once the upgrade script has been run, the version number will be updated. When upgrading to the latest curator version, ensure the highest possible script file has been run (some upgrades have more than one helper script file to run in sequence). Note: If your database version is incorrect, your Curator service will not start. An appropriate log will be made within the Event logs of the Curator Server machine noting that an additional upgrade/additional helper script is required. |
|
|
Start Curator Server Service |
Once the helper scripts have been run and the database version is up-to-date, start the Curator Server Service. To do this, load the Services list and start IPV Curator Server: |
Curator File Service
Curator File Service is necessary for the functionality of Curator 3.5.
You should have Curator File Service already installed Version: 1.1.1.34, if not, install for the first time or update to Curator File Service 1.1.1.34, and follow Curator file Service Configuration below.
Device Director
Required Prerequisites |
Device Director requires the following prerequisites: |
|
|
Run Installer | |
|
|
Accept Licence Agreement | |
|
|
Set Service Logon Account | Specify logon details for a service account here. This can be left as Local System and changed to a user with sufficient access rights later: |
|
|
Enter and confirm MySQL details | Enter your MySQL database details: Host, Username, and Password. The default schema name of devicedirector will be created when the Device Director Service starts. Enter the relevant details where appropriate and click Test Connection, if valid:Proceed to the next step: If the connection fails, check for errors and confirm the login details with the client and/or IPV (The login details or the MySQL database were created during the Prerequisites install stage). |
|
|
Set Gateway Host and add Client Id and Secret |
Change the Curator Gateway host with the IIS host FQDN/IP. Replace: https://localhost/CuratorGateway With: https://IIS_HOST/CuratorGateway The Client Id for IPV Device Director Service and Client Secret for IPV Device Director Service should be entered here to allow Device Director to use Curator Gateway authentication. To find these, go to the Curator Gateway Clients tab and select Device Director Service from the list, then copy the Id and Secret values using the copy to clipboard icon to the right of each value. If the Secret value is not yet present, this will need to be set for this client. The client secret can be set by selecting the edit icon to the right of the Device Director Service client and saving without making any changes. This will generate the Secret where this is not yet present, which you will then be able to copy. |
|
|
Choose Installation Destination | |
|
|
Set Logging Options | |
|
|
Click Install | |
|
|
Restart Services Prompt | A prompt may appear to close MySQL, SpectreView Server and Licence Manager for updates. It is not necessary to close the application at this time, but this is advised: |
|
|
Click Finish |
Process Engine Service
Required Prerequisites |
Process Engine Service requires the following Prerequisites. |
|
|
Run Installer | |
|
|
Accept Licence Agreement | |
|
|
Set Service Logon Account | Specify logon details for a service account here. This can be left as Local System and changed to a user with sufficient access rights later: |
|
|
Enter MySQL Details | |
|
|
Set Curator Gateway Host |
Change the Curator Gateway host with the IIS hosts FQDN/IP. Replace: https://localhost/CuratorGateway With: |
|
|
Choose Installation Destination | |
|
|
Set Logging Options | |
|
|
Click Install | |
|
|
Click Finish |
Process Designer
Required Prerequisites |
Process Designer requires the following Prerequisites. |
|
|
Run the Process Designer installer and click Next | |
|
|
Accept the licence terms and click Next | |
|
|
Enter Process Engine Service Host | If the Process Designer is being installed on the same host as the Process Engine Service, localhost will connect. |
|
|
Choose the log location and click Next | |
|
|
Set logging options and click Next | |
|
|
Click Install | |
|
|
Click Finish |
XCode
Note: An uninstall/reinstall is only needed if the XCode version number does not match 3.9.1.68. Any previous version requires an upgrade to version 3.9.1.68.
Required Prerequisites |
XCode has the following required prerequisites: |
|
|
Run Installer | Run the XCodeService.msi installer. Installation proceeds as follows: |
|
|
Accept Licence Agreement | |
|
|
Click Next | |
|
|
Click Next | Leave the Service Account details blank - this can be set in the services panel after installation. Click Next: |
|
|
Click Install | |
|
|
Click Finish |
XFer
Required Prerequisites |
XFer requires the following Prerequisites.
|
|
|
Run Installer | |
|
|
Accept Licence Agreement | |
|
|
Set Logon details | |
|
|
Click Next | |
|
|
Edit logging configuration | |
|
|
Click Install | |
|
|
Click Finish |
Note: When upgrading to Xfer 2.12 you must also upgrade the Core workflows module to minimum of version 3.2. Failure to do so will result in failures while comparing Checksums. |
Websites and Applications
Curator Gateway
Stop IIS | In IIS Manager, open the top level of the server: On the right, click Stop under the actions pane: |
|
|
Remove CuratorGateway Application | Under the site where CuratorGateway is installed, right-click and expand Deploy. Click Delete Application and Content: Click OK to the following prompt: |
|
|
Import Application |
Click on the top level site to import to: Under Deploy, click Import Application... |
|
|
Find the CuratorGateway Zip | Browse and select the CuratorGateway zip provided: Click Next when done: |
|
|
Click Next | |
|
|
Click Next | |
|
|
Click Finish | |
|
|
Restart IIS | Return to the IIS top level. Under Manage Server, click Start: |
Websites
Delete Application and Content | Right-click on the application. Under Deploy, click the Delete Application and Content option: Click OK to the following prompt: If prompted for recycling content, click OK. |
|
|
Import Application |
Remove and Import the following applications:
Import the following application:
Use WebDeploy to import the new version. For a reminder on how to import applications in IIS, click here. |
Curator System Administrator -TLS1 removal
Panel content
Modify the Curator Service Administrator web.config (if needed) |
Additional web.config modification is needed in systems running Curator 3.4 or newer with CSA version 1.6 where the TSL1 has been removed as is possible from Curator 3.4 onwards. This will be automatically set from CSA 2.0 (scheduled for Curator 3.6) The CSA 1.6 web.config needs to be modified where TSL1 is not available. You will need to add the following two lines to the CSA web.config file: <add key="AppContext.SetSwitch:Switch.System.Net.DontEnableSchUseStrongCrypto" value="false" /> <add key="AppContext.SetSwitch:Switch.System.Net.DontEnableSystemDefaultTlsVersions" value="false" /> |
Curator System Administrator - Schema Updates
For Curator Connect Open Curator System Administrator navigating to the configuration tab
|
Navigate to the Configuration tab. |
|
|
Select the specific version and then click Default |
|
|
|
Click Add New Version |
Click Choose File. |
|
|
Click Open |
|
|
|
Click Save |
|
|
|
For Curator For Adobe, select specific version and then click Default | |
|
|
Click Add New Version |
Click Choose File. |
|
|
Click Open | |
|
|
Click Save |
Curator for Adobe
Required Prerequisites | On installation of version 3.3.1, you must deploy or update Curator for Adobe to version 3.1 to users' machines to take advantage of the now default method of authentication via opening a browser page (Authentication Code). If an upgrade of Curator for Adobe is not possible at this time then client authentication grant types should be manually changed from Authentication Code to Implicit for the application. To do this, go to Curator Gateway>Authentication>Clients and update all Curator for Adobe clients, with the exception of Curator for Adobe Importer/Exporter. Please check to ensure this has been changed on upgrade, updating these manually if necessary. |
|
|
Run Installer |
Note: If upgrading from any previous release of this product on a PC, please uninstall the previous release and check that the following folder locations are empty before attempting to install this version: |
|
|
Accept Licence Agreement | |
|
|
Click Install | |
|
|
Click Finish |
Note: If you're attempting to use Adobe 2021 and experiencing login issues, you may need to move the Access-Control-Allow-Origin HTTP Response header from the IIS Default Website to your virtual proxy directory. If the virtual proxy directory does not exist or is hosted in AWS, remove the HTTP Response header and re-attempt login. |
|
|
Open Specific Adobe Product | Configure Gateway host through the cog wheel (as demonstrated in the below Curator Connect configuration steps). This applies to Adobe Premiere Pro, Photoshop, Illustrator, and others. |
Curator Connect
Required Prerequisites | On installation of version 3.3.1, you must deploy or update Curator Connect to version 1.6 to users' machines to take advantage of the now default method of authentication via opening a browser page (Authentication Code). If an upgrade of Curator Connect is not possible at this time then the client authentication grant type should be manually changed from Authentication Code to Implicit for the application. To do this, go to Curator Gateway>Authentication>Clients and update Curator Connect. Please check to ensure this has been changed on upgrade, updating this manually if necessary. |
|
|
Run Installer | Uninstall the previous release and then install the latest version: |
|
|
Click Install | |
|
|
Click Install | |
|
|
Click Finish | |
|
|
Run Curator Connect |
Curator Connect will open and display an error message as the Curator Gateway URL will be the default and needs configuring: |
|
|
Set the GATEWAYHOST generic text as the specific Gateway Hostname | |
|
|
Check Ingest Panel to confirm the connection has been successful |
Note: Additional configuration steps are needed before files can be Ingested through Curator Connect. |
Configuration Overview
Start Services
Setting Service Account | Ensure that all Curator Services are set to run as the previously configured values prior to upgrade. |
|
|
Start Curator Server |
If you haven't already, start the Curator Server. |
|
|
Start Device Director Service | If you haven't already, start the Device Director Service. |
|
|
Start XCode Service | If you haven't already, start your XCode Services. |
|
|
Start Xfer Service | If you haven't already, start the Xfer Service. |
Process Engine Setup
Start Process Engine Service | In the services panel, start the IPV Process Engine Service if it has not already been started. | |
|
||
Start Process Engine Agent Service | In the services panel, start the IPV Process Engine Agent service if it has not already been started. | |
|
||
Browse to Process Engine Monitor Modules Webpage |
Browse to: http://localhost/ProcessEngineMonitor/Modules Click Choose file. |
|
|
||
Select the Workflow Module file |
Browse to the Process Engine install directory and select the corresponding version package ( x.y.z.a and in the image below replaced by the version of Workflows-Core provided with your installation of the Process Engine e.g. 3.3.0.7) %INSTALL_PATH%\Program Files\IPV\Process Engine Service\BundledModules\Workflows-Core-x.y.z.a.zip Click Open. |
|
|
||
Open new Workflow Module |
|
|
|
||
Click Install | Click Install, and a System Setup workflow will start: | |
|
||
From the Modules screen, click "Choose File" |
Choose the appropriate Adobe workflow zip file, then click Open: |
|
|
||
Click Install | ||
|
||
Confirm Successful System Setup |
A System Setup workflow will start: |
|
|
||
Confirm Updated Module Version Numbers | ||
|
||
Confirm GLOBAL MediaStore settings | Browse to the MediaStores tab, select the GLOBAL MediaStore and check the key FileTypesImage to make sure that the values include ai, psd and mogrt. If not, manually add these values. |
|
|
||
Set optional MediaStores as needed |
This is necessary where the site requires non-default settings.
Configure image Essence generation for Clip SelectThis is only needed in Curator 3.5. In future Curator versions, the support for Clip Select and image essence will be withdrawn in favor of Clip Link with extended features.
Navigate to Process Engine Monitor in a browser, select the MediaStores tab and scroll down to "Proxy MediaStores", select PROXY-IMAGE. Click Edit and in the new screen change the value for StoreEssenceBlob toTrue: Click Save Changes and confirm:
|
Device Director Setup
As of XCode release version 4.1, for efficiency reasons, where your material contains ProRes 4444 and the alpha channel needs to be decoded into proxies, you will need to manually set a Control Switches value of renderalpha in the Device Director proxy generation profile used (e.g., HLS-FMP4-D1).
Configure the XCode profile for alpha proxy generation |
Update the Control Switches value to include renderalpha in the Device Director profile used (this will be HLS-FMP4-D1 by default). If another value is already presend add renderalpha following a comma. |
|
|
Configure XCode profile to disable edit lists |
For the 4.1 XCode release, in order for HLS proxies to show the correct number of frames on output, you will need to manually enable the Control Switches value of disableqtelst in the Device Director profile used. Please refer to the screenshot above, setting disableqtelst where render alpha is shown. Where both or additional properties are required use comma separated entries e.g: renderalpha,disableqtelst . |
Curator Gateway Setup
Folder Permissions
Give the IIS_IUSRS user Write permissions to the CuratorGateway folders.
Apply folder permissions |
Execute the steps on this page for the two folders listed below. The examples are on CuratorGateway but must also be applied to ProgramData\IPV:
|
|
|
Open IIS Default Root Folder | Browse to the inetpub\wwwroot folder - this can be accessed quickly through IIS Manager by right-clicking and selecting Explore on the Default Web Site. |
|
|
Open CuratorGateway Properties | Right-click the CuratorGateway folder and open its Properties window: |
|
|
Click Edit on the Security tab | Open the Security tab and click Edit: |
|
|
Give IIS_IUSRS Write Permission | Select the IIS_IUSRS account, and allow the Write permission:Click Apply and OK when finished. |
|
|
Open ProgramData Folder |
Under the root Windows install directory, find the ProgramData folder: This folder is a hidden item. To show this folder, ensure hidden items are visible (these can be made visible from the View tab): |
|
|
Open Curator Gateway Properties | Browse down to the IPV folder under ProgramData. Right-click on Curator Gateway and open its Properties: |
|
|
Edit Permissions | Under the Security tab, click Edit: |
|
|
Add IIS_IUSRS |
Click Add: Click Locations. If prompted to log in, provide valid credentials or credentials to the system, and select the host machine:In the object names field, enter IIS_IUSRS and click Check Names:When finished, click OK. |
|
|
Give IIS_IUSRS Write Permissions | Select the IIS_IUSRS account and allow Write permissions:Click Apply and OK when finished. |
IIS and Registry Config
Make changes in IIS and add new DWORDs in Registry Editor.
Open Default Web Site in IIS Manager | In IIS Manager, click on the Default Web Site: |
|
|
Check and configure the HTTP Response Headers setup | At the Default Web Site level, in the center panel, double-click the HTTP Response Headers button: |
|
|
Click Add | In the top right, click Add: |
|
|
Ensure that Access-Control-Allow-Headers is set up |
In Name, enter: Access-Control-Allow-Headers In Value, enter: Range,Cache-Control |
|
|
Check and ensure that Access-Control-Allow-Origin is not set up | If this is set up, remove it by selecting the row with “Allow-Control-Allow-Origin *” and selecting Remove from the right-hand menu. Select Yes to confirm. |
|
|
Ensure the Proxies virtual folder is set up |
In Name, enter:
Alternatively, "*" can be used for all hosts but poses security risks: |
|
|
Open Gateway Home in IIS Manager | In IIS Manager, click on the CuratorGateway application: |
|
|
Open Configuration Editor | Under the Management section, click Configuration Editor: The following dialog will appear: |
|
|
Open serverRuntime Section | From the Section dropdown, expand the system.webServer folder and select serverRuntime: |
|
|
Set maxRequestEntityAllowed Value |
Change the maxRequestEntityAllowed value (if not already set) to: 4294967295 |
|
|
Set uploadReadAheadSize Value |
Change the uploadReadAheadSize value from: 49152 To: 2147483647 |
|
|
Click Apply | From the Actions section, click Apply: |
|
|
Open request Filtering Section | Change the Section again to requestFiltering (found under system.webServer\security): |
|
|
Set maxAllowedContentLength Value |
Expand requestLimits and change the maxAllowedContentLength value from: 30000 To: 4294967295 |
|
|
Click Apply | Click Apply again: |
|
|
Open Registry | Next, Open Registry on the server which is hosting the Curator websites. |
|
|
Navigation | Navigate to : Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters |
|
|
Make Changes | Change DWORD 'MaxFieldLength' to 65534 (Decimal) |
|
|
Make Changes | Change DWORD 'MaxRequestBytes' to 16777216 (Decimal) |
|
|
Close Registry | Close the registry browser, no further changes are required. |
Database Connection
Enter MySQL database connection details here.
Browse to Curator Gateway | Browse to the following, replacing localhost with the IIS host FQDN/IP address: https://localhost/curatorgateway/ |
|
|
Configure Database Connection | Enter details to connect to the MySQL database here: NOTE: When configuring 'Name' please use/update using the following format: e.g. CustomerName - Prod and CustomerName - Dev on their two systems. |
Web Apps config
Curator Service Administrator Config
Modify the Curator Service Administrator web.config (if needed) |
Additional web.config modification is needed in systems running Curator 3.4 or newer with CSA version 1.6 where the TSL1 has been removed as is possible from Curator 3.4 onwards. This will be automatically set from CSA 2.0 (scheduled for Curator 3.6) The CSA 1.6 web.config needs to be modified where TSL1 is not available. You will need to add the following two lines to the CSA web.config file: <add key="AppContext.SetSwitch:Switch.System.Net.DontEnableSchUseStrongCrypto" value="false" /> <add key="AppContext.SetSwitch:Switch.System.Net.DontEnableSystemDefaultTlsVersions" value="false" /> |
Curator Clip Link Config
Open web.config in text editor | On the IIS server, open IIS manager and browse to the Curator Clip Link directory by right-clicking and selecting the Explore option: Open the web.config file in a text editor. |
|
|
Replace "Thumbnail VTT Location" key value |
Search for the ThumbnailVttLocation key and replace the value with the fully qualified domain name for the webserver and the virtual directory configured during the ingest functionality deployment. Replace: <add key="ThumbnailVttLocation" value="https://WEBSERVER/Proxies/WebProxy/{proxy-path}/{name}/{name}_thumbnail.vtt" /> With: <add key="ThumbnailVttLocation" value="https://IIS_HOST/Proxies/WebProxy/{proxy-path}/{name}/{name}_thumbnail.vtt" /> |
|
|
Set the Curator Logger endpoint |
Search for: <OpenInLogger url="https://localhost/CuratorLogger/Log?assetId={id}" enabled="true" /> Setting (enabled="false") will hide the option in the Clip Link menu. If Logging is required, replace localhost with the webserver hosting the logger application and set enabled="true": <OpenInLogger url="https://IIS_HOST/CuratorLogger/Log?assetId={id}" enabled="true" /> |
|
|
Recover Old Config | The next few steps regard recovering old configuration from the previously backed up Curator Clip Link config file from 3.0. |
|
|
Replace Metadata View names |
Find the following keys and replace the value with the required metadata views: <add key="SearchFilterViewName" value="SearchLevelView" /> |
|
|
Replace Pinned Searches |
Find the PinnedSearches tag and add all the missing lines below the cleartag: <pinnedSearches> <searches> <clear /> <add imageFileName="Example.svg" tooltip="Example Search" searchParameters="?assetFilter=159&s=ingestdate&d=descending" /> |
|
|
Replace Add To Collections |
Find the AddToCollection tag and change the values as required, adding missing metadata names within the Path Metadata tag if necessary. <AddToCollection> <MetadataView name="Collections" /> <BaseLocation name="Library" / <PathMetadata> <Metadata name="CollectionType" /> <Metadata name="CollectionDestination" /> <Metadata name="Priority" /> </PathMetadata> </AddToCollection> |
|
|
Replace asset pop-up metadata tabs in order to configure different views |
If you are upgrading a site where non-default tabs or views are configured, please note that as of Clip Link 3.3, the xml tags have changed from <View name=... /> to <Tab name=... /> (see the current form below). NOTE: Do not copy over old lines of configuration file. If you wish to configure additional or different metadata views in tabs, find the <AssetInfo> tag in web.config and configure this providing your view of choice, the name of the tab and whether to display metadata from the asset or its parent in this tab. With parent="true" for clipmarks this will be media metadata and nothing will display for popped up media, audio or images. <AssetInfo> <Tabs> <Tab name="ViewName1" display="Displayed Name of Tab1" parent="false"/> <Tab name="ViewName2" display="Displayed Name of Tab2" parent="false"/> </Tabs> </AssetInfo> |
|
|
Finish | Save the file. |
|
|
Recover Pinned Searches Images |
Replace any missing images in: %INSTALL_PATH%\inetpub\wwwroot\CuratorClipLink\Content\Images\PinnedSearches\ |
|
|
Recover Custom Plugins |
Replace any missing custom plugins in the plugins top-level folder: %INSTALL_PATH%\inetpub\wwwroot\CuratorClipLink\Plugins\ |
Curator Logger Config
Open web.config in text editor |
On the IIS server, open IIS manager and browse to the Curator Logger directory by right-clicking and selecting the Explore option: Open the web.config file in a text editor. |
|
|
Replace "Video Server Address" key value |
Set the value for the VideoServerAddress key with the fully qualified domain name for the IIS host. Replace: <add key="VideoServerAddress" value="https://WEBSERVER" /> With: <add key="VideoServerAddress" value="https://IIS_HOST" /> |
|
|
Replace "Thumbnail Vtt Location" key value |
Search for the ThumbnailVttLocation key and replace the value with the fully qualified domain name for the webserver and the virtual directory configured during the ingest functionality deployment. Replace: <add key="ThumbnailVttLocation" value="https://WEBSERVER/Proxies/WebProxy/{proxy-path}/{name}/{name}_thumbnail.vtt" /> With: <add key="ThumbnailVttLocation" value="https://IIS_HOST/Proxies/WebProxy/{proxy-path}/{name}/{name}_thumbnail.vtt" /> |
|
|
Finish | Save the file. |
Clean up of unnecessary elements
Removing Apache and Perl
|
Note: When upgrading from 3.2 to 3.3, Apache and Perl should already be uninstalled. Should they need to be removed, reference the provided steps. |
Uninstall Apache |
Open a Command Prompt window and execute the following two lines separately: cd C:\Apache24\bin .\httpd.exe -k uninstall
|
|
|
Remove Apache files |
After Apache has been uninstalled, close the open Command Prompt window. It is now safe to delete the Apache24 folder. |
|
|
Open Programs and Features |
Open Control Panel and go to Programs and Features:
|
|
|
Uninstall ActivePerl |
Right-click on ActivePerl and click Uninstall. To the prompt, click Yes.
|