Administration

EZ Updater

After the EZ Updater is set up, a lot more features are available for use by the EZ Admin. In the initial setup as shown here, one EZ Admin was registered for the EZ Updater, EZ Updater settings were saved, EZ Client bits were configured and then uploaded on EZ for use by the clients. […]

EZ Updater Read More »

Installing and setting up EZ

The EZ setup has at least one EZ Updater machine and one or more EZ Clients. We start with the EZ Updater installation first. After that, we configure the EZ Updater, so the EZ Client builds are available to client machines. Once the client machines have installed EZ Client (and Zoom Client), the EZ system

Installing and setting up EZ Read More »

Prerequisites for EZ

Here are the requirements for EZ Updater and EZ Client machines: EZ Updater At least one EZ Updater machine is required for one geographical location. It should run Linux or Windows OS. It is suggested to have more than 100GB of storage as multiple Zoom builds will be downloaded and stored here. If the storage on

Prerequisites for EZ Read More »

EZ Updater FAQs

EZ Client Q: My EZ Updater is displaying builds on the EZ web portal, but the EZ client is saying no available builds.A: Check if the builds are approved on your EZ Updater. Log into the EZ Web portal as an EZ Admin to check this. Q: I am working on Zoom. Would my work be

EZ Updater FAQs Read More »

Web Client Branding & Configuration

Zoom 7.0 introduced Evolphin Web Client application that can be branded for customer portals. This application lets users perform basic asset operations like searching, browsing, and metadata lookup. But, in addition, it is also a collaboration tool, that can be used for sharing collections of assets among a group of users and also exchange comments and

Web Client Branding & Configuration Read More »

Move Curator to Preview server

1. Take back ups of the server.xml files on both the zoom and preview server. 2. Check the curator services configuration before migration. 3. Check the zoom server module before migration 4. Check Asset browser before migration 5. Stop all services on both the services. 6. Check for any stale processes related to evolphin ( ps –ef|grep

Move Curator to Preview server Read More »

Setting up Vantage Integration

Overview Zoom VideoFX Zoom High-Res Video Management Release supports a proxy-based High-Res asset management wherein read-only stock/footage files (of typically large size) can reside outside the Zoom repository, and still be accessible to all Zoom users for their regular operations like linking or searching. Please review storage management with Zoom VideoFX from this link. Configuration

Setting up Vantage Integration Read More »

java.lang.OutOfMemoryError in the Curator Log

As your Zoom server grows the search engine will need more memory to index and deliver searches. If you encounter out of memory exceptions you will need to increase the Java heap size in zoom/conf/solr-server.conf. Please modify the values in the fields wrapper.java.additional.8=-Xms and wrapper.java.additional.9=-Xmx  accordingly. Below are some metrics to guide you.   wrapper.java.additional.8=-Xms wrapper.java.additional.9=-Xmx Default Configuration 512 MB 2

java.lang.OutOfMemoryError in the Curator Log Read More »

Storage Management with Zoom

Evolphin Zoom supports two different asset storage models: Indexed/External Asset Model Direct Ingest/Managed Asset Model Indexed/External Asset Model This requires Zoom VideoFX or VideoLX license with the base Zoom Server. It is used to index raw camera footage, large-format videos, read-only files that need to be represented in the Zoom Database via a proxy or a placeholder

Storage Management with Zoom Read More »

Changing config manually with HADR

The global settings or configuration for a Zoom server deployment with High-Availability and Disaster Recovery (HADR) enabled can be changed easily through the Server Control Panel or other options on the Zoom Web Management Portal (Webmin). Global configuration may include various aspects such as Repository settings, Metadata specification, Workflow settings etc. However, at present, the

Changing config manually with HADR Read More »

How to debug auto-checkout issues?

The best way to debug auto-checkout issues is to collect more details. You can do this by enabling process-level logging. Please follow the steps given below to do this: In your Zoom server deployment, navigate to the conf/ folder and open the wrapper.conf file. Search for the phrase “wrapper.java.additional.” and locate the last uncommented (not

How to debug auto-checkout issues? Read More »