After installing and configuring Hub, as soon as you are finished setting up your AI provider, configuration, and mappings in Zoom, your AI module in Zoom starts locating existing assets in the Zoom repository to be eligible for AI analysis. If any existing or new assets match your configured AI mapping rules, these are sent […]
From Zoom 7.3 onwards, zoom properties can be added through the Web Management Console. These are synced with other Zoom Server peers, Preview Servers, Curator Servers, and Zoom Clients. To add a property, follow these steps: In the Web Management Console, open the Server Zoom Properties page under the System node in the Admin Menu
Zoom Properties in Web Management Console Read More »
After setting up the Hub Server and configuring Amazon settings on it, we also need to configure detailed Amazon AI parameters in Zoom using the Web Management Console. We need to set Amazon as the AI Provider, provide configurations for AI engines, and then map AI rules to AI engines. Follow these steps: AI Providers
Configure Amazon AI in Zoom Read More »
Once you have configured Hub in Zoom and installed your Hub Server, you can add Amazon settings to it. Start the Hub Server where you want to run AI jobs. On this Hub Server, open the conf folder inside the Hub installation directory. Inside the conf folder, locate ai-spec.xml. ai-spec.xml will be created automatically on
Configure Amazon AI on Hub Read More »
After your VideoFX / VideoLX system is set up, you can also set up Aspera for automatic high-res file duplication based on pre-configured conditions. You will need to set up an Aspera High-speed Transfer Server and an Aspera Client / CLI as part of this setup. Components The interaction of the Aspera system with the
Setting up Aspera for file transfer Read More »
Zoom 7.5 comes with the capability to integrate with Artificial Intelligence (AI) providers to analyze files and media in Zoom, store the results from AI, make the results searchable, and display the results in an innovative UI. Data from AI engines can also be used to automatically run tasks based on certain triggers. You can
Getting started with AI Read More »
We need to enable AI in Zoom before beginning to configure it. Follow these steps to enable AI for the first time or to update the AI Settings later: Open the Web Management Console for your Zoom Server. Example: https://zoom-server:9443 Log in using your admin credentials. In the Admin Menu sidebar, click Server Control Panel under the System node. Click AI
Once you have configured Hub in Zoom and installed your Hub Server, you can add Veritone settings to it. Start the Hub Server where you want to run AI jobs. On this Hub Server, open the conf folder inside the Hub installation directory. Inside the conf folder, locate ai-spec.xml. ai-spec.xml will be created automatically on
Configure Veritone AI on Hub Read More »
After setting up the Hub Server and configuring Veritone settings on it, we also need to configure detailed Veritone AI parameters in Zoom using the Web Management Console. We need to set Veritone as the AI Provider, provide configurations for AI engines, and then map AI rules to AI engines. Follow these steps: AI Providers
Configure Veritone AI in Zoom Read More »
The Hub writes its events to a log file ejh_server.log. This file is saved in the logs folder inside your Hub installation directory. Apart from ejh_server.log, wrapper.log is another log file present in the logs directory. The wrapper.log file logs any errors that were not logged in the Hub logs, including logs generated when the
The Hub Server handles archive/restore processes for Zoom version 7.3 onwards when configured as part of a Hierarchical Archive system on Zoom. It needs to be configured on Zoom first and also installed on a server machine later. The Hub Server’s configuration can be managed through Zoom’s Web Management Console. This guide will cover: Hub
Managing Hubs in Zoom Read More »
Hierarchical Archive allows multi-level archiving to be implemented in Zoom. An asset can independently move between different tiers of the hierarchy as configured for the system. You need to set up a Hub Server for this to work. The Hub manages the jobs that move assets between tiers and provides reports for the admin users.
Getting started with Hierarchical Archive Read More »
While enabling Hierarchical Archive we need to also enable Basic Archive on Zoom, if it is not already done. Follow these steps to enable Hierarchical Archive after setting up basic archive: Open the Web Management Console for your Zoom Server. ex. http://localhost:8443 or http://<zoomserver>:8443 Log in using your admin credentials. In the Admin Menu sidebar, click Server Control Panel under the System node.
Hierarchical Archive Settings Read More »
Zoom stores Hub configuration settings to connect with a Hub Server. These configuration values should be added to Zoom before installing the Hub Server. If these Hub configuration values in Zoom are updated after installing and starting the Hub Server, then restart the Hub after you have finished updating these values. Log in to the
Hub Configuration in Zoom Read More »
Several Zoom services depend on shared storage provided by a NAS or SAN in order to process files across multiple machines or Zoom services. The permissions (read/write/delete) on files or folders on these shared storage devices need to be setup to ensure requirements listed below are met for various deployment configurations for Zoom: Terminology Term
Permissions with shared storage (NAS/SAN) Read More »
Archiving is an optional feature that is available with an appropriate license. You can check your license information in Zoom’s Web Management Console. To check the license information, log on to your Web Management Console, for example, http://MyZoomServer:8443/ Open the License Management node under the System node in the Admin Menu sidebar. Click License Information
Checking Archive license Read More »
When the Archive Module is included as a part of the Zoom license, Zoom can be set up to archive assets to a single designated archive location using its internal Basic Archive Module. This folder location must exist on the Zoom MAM server in order for the configuration to work. Enable and set up the
Basic Archive Settings Read More »
As of Zoom 7.3, it is possible to automatically receive updates from the LDAP Server regarding the changes in existing user accounts as well as the addition of new users. In order to do this, you need to specify Auto Pull Frequency in the LDAP Server Settings inside the Web Management Console. Follow these steps:
Automatic Pull-Users from LDAP Server Read More »
Context Evolphin Managed Cloud-based Zoom Servers can technically be accessed from anywhere in the world. Without strict firewall settings, a user from any IP address can run the Zoom desktop apps or Web Client and access the cloud-based Zoom or Preview Servers. To protect against malicious users, by default, Evolphin locks down the Zoom server
Using Evolphin Managed VPN with Evolphin Managed Cloud based Zoom Servers Read More »
A new feature for Auto-Retirement has been introduced from Zoom 7.3 onwards, which allows Zoom admins to set up rules to determine which assets are automatically retired. This post outlines how the feature works and then shows how to configure it on your Zoom setup. Auto-retirement offers a mechanism by which assets can be identified
Setting up Auto-Retirement Policy Read More »
