Overview
This documentation outlines the prerequisite for installing the VIDIZMO V9 application.
Applies To
- On-premises
- Microsoft Azure
- AWS
- Private Cloud Environments.
Server Requirements
This section explains the server requirements for the deployment of the VIDIZMO application.
Application Server Requirements
Requirements for setting up the VIDIZMO Application server system:
- Operating System: Windows Server 2022 Standard Edition (VM/Physical Server)
- RAM: Minimum of 8 GB RAM
- CPU: 4 Core CPU
- Storage: Minimum 128 GB SSD or NVMe Hard Drive with a recommended throughput of 500 Mbps.
- Network Throughput: A recommended minimum network throughput of 1 Gbps is necessary for optimal network performance, ensuring smooth data communication and responsiveness.
- Internet Information Services (IIS): Version 10/11 or a later version of IIS must be installed and configured on the server.
- Microsoft .NET 6.0.12 framework
- .NET Core Hosting Bundle: Version 6.0.22
Database Server Requirements
To ensure optimal performance and compatibility for a smooth database operation, adhere to the following prerequisites for the database server setup.
- Operating System: Windows Server 2022 Standard Edition (VM/Physical Server)
- RAM: Minimum of 16 GB RAM. 32 GB of RAM is recommended for optimal performance.
- CPU: 8 Core CPU
- Storage: Minimum 256 GB SSD or NVMe with a minimum throughput of 500 Mbps
- SQL Server: SQL Server 2022 Standard or Enterprise Editions.
- Network Throughput: Recommended 1 Gbps network throughput for optimal network performance.
- Microsoft .NET Framework: Version 4.8
- User Privileges: A SQL Server Local Service Admin User is required for installation.
- Network Configuration: Ensure all machines are connected to the same Local or Virtual Network for seamless communication and operation.
Encoding Server Requirements
The Encoding Server is essential for organizations that require heavy content-processing tasks. Ensure that your system meets these requirements for optimal performance and functionality—the prerequisites for setting up the VIDIZMO Encoder (Video Processing) system.
- Operating System: Windows Server 2022 Standard Edition VM/Physical Server
- Processor: Minimum 8 Core Intel or AMD processor with integrated graphics.
- RAM: Minimum 16 GB RAM
- Storage: 256 GB SSD with a minimum throughput of 200 Mbps or NVMe with a minimum throughput of 500 Mbps.
- Network Throughput: Recommended 1 Gbps network throughput for optimal network performance.
- .NET Core Hosting Bundle: Version 6.0.22
- Python: Version 3.8.4
- Network Configuration: All machines should be on the same Local or Virtual Network for efficient communication and data processing.
AI Server Requirements
The prerequisites for setting up the VIDIZMO AI Server.
- Operating System: Windows Server 2022 Standard Edition VM/Physical Server.
- Processor: Minimum 8 Core Intel or AMD processor with integrated graphics.
- Recommended NVIDIA NVENC-enabled GPU for optimal video processing performance; consider a processor with an NVIDIA NVENC-enabled GPU. This will accelerate video encoding and decoding.
- Recommended GeForce RTX series with Cuda version 11.7 or above.
- RAM: Minimum 32 GB RAM
- Storage: 256 GB SSD with a minimum throughput of 200 Mbps or NVMe with a minimum throughput of 500 Mbps.
- Network Throughput: Recommended 1 Gbps network throughput for optimal network performance.
- Microsoft .NET Framework: Version 4.8
- .NET Core Hosting Bundle: Version 6.0.22
- Python: Version 3.9.13
- Network Configuration: All machines should be on the same Local or Virtual Network for efficient communication and data processing.
Streaming Server Requirements
This section outlines the system requirements and specifications for the WOWZA Live Streaming Server, ensuring optimal performance and reliability.
- Minimum Recommended Production Hardware
- CPU: Single quad-core, 3.00 GHz or better
- RAM: 4GB
- Disk: 2 or more disks in RAID 0 (striping)
- Network:1Gbps Ethernet
- High-Load Recommended Production Hardware
- CPU: Dual quad-core or a single hex-core, 3.00 GHz or better
- RAM:16-32GB
- Disk: 2 or more disks in RAID 0 (striping)
- Network:10Gbps Ethernet
- Supported Operating Systems
- Windows
- Linux
- Mac®
- Java Installation
WOWZA Streaming Engine version 4.7.8 and later requires OpenJDK Java SE JRE 9.0.4 at a minimum but supports up to Java version 12. Earlier versions of Java aren't supported.
For detailed information about supported Java versions, refer to WOWZA documentation.
Note for Server Admin: VIDIZMO needs server systems to host the web application, content processing, and databases. The application components can be distributed across multiple server systems to achieve redundancy and ensure high availability. Both physical systems and Virtual Machines (VMs) are supported for the VIDIZMO application deployment.
Administrator Requirement: System Administrators are required to have Elevated Access Permissions on Virtual Machines (VMs) and servers to facilitate the successful deployment, configuration, and management of the VIDIZMO application. It is imperative that dedicated user accounts with elevated access permissions be granted on all VMs and servers where VIDIZMO will be installed.
Network Configuration
To achieve a successful VIDIZMO deployment, it is essential to meet specific network configurations and port requirements. VIDIZMO's vital components must establish communication amongst themselves, primarily utilizing Fully Qualified Domain Names (FQDNs). This FQDN-based approach is favored due to its dynamic adaptability, as FQDNs can seamlessly resolve to different IPs. Furthermore, it's advisable to enable firewall port exceptions to facilitate uninterrupted communication, ensuring robust and flexible deployment.
Firewall rules and exceptions (Network Ports)
Enable the following firewall port exceptions on the network and Windows firewall for web application server, content processing, and database server systems. The following network ports need to be open for VIDIZMO to operate:
# | Port Description | Default Port | Source | Destination | Direction |
1 | HTTP | 80 | Any | Application Server | Inbound |
2 | HTTPS | 443 | Any | Application Server | Inbound |
3 | Memcached | 11211 | Application and encoder servers | Memcached service | Inbound |
4 | SMTP (Notification) | 25 | Application Server | Any | Outbound |
5 | SQL Port | 1433 | Application and encoder servers | SQL Server | Inbound |
6 | License Activation | 443 | Application and encoder servers | license.enterprisetube.com | Outbound |
Web Application Firewall (WAF)
As a prerequisite for implementing a Web Application Firewall (WAF), it is essential to configure it to allow necessary traffic into VIDIZMO. This involves creating custom rules or policies to whitelist required traffic. During this configuration, it may be necessary to turn off specific rules. In particular, when making policy settings in WAFV2, ensure that the "inspect request body" policy is turned off. This is crucial for applications like VIDIZMO that involve uploading large files, as leaving this feature open might prompt restrictions on the maximum file upload size.
Additionally, as WAFs typically adhere to OWASP policies, it is advised to disable the rule "URL file extension is restricted by Policy." Failure to disable this rule may restrict uploading and downloading files in VIDIZMO. Therefore, adjusting this setting is imperative for the seamless operation of the application within the WAF framework.
Broker Service Options
Before integrating and utilizing a broker service to handle message exchange between microservices, it is essential to understand and configure the available options based on specific use cases. VIDIZMO supports multiple broker service options to handle real-time data feeds and facilitate seamless communication between microservices.
The following broker service options are available for customers, each associated with the requisite port for Broker services:
- Azure Service Bus is a cloud-based broker service provided by Microsoft, utilizing AMQP to transmit messages.
Port Description | Default Port | Source | Destination | Direction |
Azure Service Bus-AMQP | 5671-5672 | Application& encoder servers | Broker Server | Inbound |
- Apache Kafka, often referred to as a message broker service, is a distributed event streaming platform designed to handle real-time data feeds.
Kafka client-server connection | 9092 - 9094 | VIDIZMO app and Encoder servers | Kafka server | Inbound
|
Kafka zookeeper | 2181 - 2188 | VIDIZMO app and Encoder servers | Kafka server | Inbound
|
- RabbitMQ, an on-premises broker service, is an option for message handling within VIDIZMO.
Rabbit MQ client-server connection | 5672 | VIDIZMO app and Encoder servers
| Rabbit MQ server | Inbound
|
Rabbit MQ management | 15672 | VIDIZMO app and Encoder servers
| Rabbit MQ server | Inbound
|
- DAPR is not a traditional broker service but offers features for messaging and communication between microservices.
Domain Setup Prerequisites
Domain Name and IP Address Configuration
- Domain Setup for Web Application: Ensure the web application has a designated domain (FQDN) for proper functionality. Determine and configure a domain name that will serve as the access point for the media portal.
- Domain Mapping: To ensure accessibility, map domain name(s) to the IP address of the Web Application server. If multiple domains are used, provide separate entries for each.
- IP Address Mapping: Assign an IP address to the Web Application server and configure DNS accordingly for seamless domain resolution.
- Domain Name for Your Media Portal: Define a user-friendly domain name for accessing the media portal. The domain name serves as the user-accessible address for your media portal. It is essential for user interaction and content access. Configure this domain name to map to a public IP address for external accessibility or a private IP address for internal access based on intended portal configurations. For detailed instructions on configuring VIDIZMO with a custom domain, please refer to the "How to Set a Custom Domain for a Portal" section.
Licensing and Activation
- License Activation Key for VIDIZMO Application: Before initiating a fresh deployment, it is essential to obtain a new License Activation Key for the latest version of the application. This License Activation Key is vital for users to start utilizing VIDIZMO as their chosen digital content management solution.
- When performing an upgrade to a new version of VIDIZMO, it is essential to note that the new License Activation Key will require the truncation of the "ServerLicense" table within the "VidizmoDB" database. This step is essential to remove any existing licenses and must be carried out prior to adding the new license. This process ensures a seamless and successful activation of the updated version by clearing the database of previous licenses. To learn more about it, refer to the article “How to View and Update VIDIZMO License.”
Security Configuration
- SSL Certificate for Selected Domain Name: To ensure secure communications between users' browsers and the VIDIZMO application, you'll need to configure SSL certificates for the domain name(s) used by the VIDIZMO web application.
SMTP Service Credentials
- Ensure SMTP configuration within the portal to enable email notifications sent during various application steps, essential for user interactions and system events.
- Configure SMTP to allow email notifications triggered by different scenarios like registration requests, content uploads, content sharing, password resets, etc., either through a service account (recommended) or a user account from the corporate email server or a third-party SMTP service.
- SMTP is fundamentally required for registering new users in VIDIZMO, facilitating workflows, user registrations, license activations, and other critical notifications within the application.
Storage Requirements
To ensure the seamless functioning of the VIDIZMO application, appropriate storage and backup solutions need to be in place. The following storage types are currently supported with the VIDIZMO application:
Content Storage: VIDIZMO provides multiple options for content storage, including:
Local File System: Suitable for on-premises deployments.
Azure Blob Storage: Microsoft Azure-based storage solution.
AWS (Amazon Web Services): Amazon-based cloud storage solution.
Wowza Media Server: A specialized media server solution.
Local File System
Before implementing the local file system storage, it is essential to ensure that the following prerequisites are met to enable efficient and secure access to the file share using the SMB (Server Message Block) protocol.
It is essential to ensure that users who require access to the local file system have a valid user account and the necessary permissions to read and write files within the specified file share.
Ensure that the network router used within your infrastructure has SMB protocol support enabled.
VIDIZMO supports SMB 2.0 or SMB 3.0, as these versions offer improved performance, security, and feature sets.
Make sure that users have access to the Universal Naming Convention (UNC) path that corresponds to the file share on the server. The UNC path typically follows the format: \\server name\file share name.
Azure Blob Storage
Before setting up Azure Blob Storage to meet your storage requirements, it is essential to establish the following prerequisites:
Ensure you have a dedicated non-Multi-Factor Authentication (MFA) user account with "Contributor" level access on the Azure Subscription.
AWS Storage
Prerequisite for AWS storage requirement:
Ensure you have an AWS Access Key and Secret Key associated with the AWS Identity and Access Management (IAM) user or role responsible for managing the storage solution.
Define bucket-level policies to control who can access and perform actions on the S3 bucket.
Attach IAM policies to IAM users or roles for precise control over their actions within the S3 bucket. Ensure that these policies align with your storage requirements.
WOWZA Media Server
Before implementing storage requirements with WOWZA Media Server, you must establish the following prerequisites to ensure smooth and efficient handling of media content.
To utilize the WOWZA Media Server effectively, ensure you have a playback URL from your WOWZA Player that will serve as the Provider URL. This playback URL acts as the source of the content that WOWZA Media Server will distribute to viewers.
The Streaming Provider URL is essential for WOWZA to identify the source of your media content.
Determine and specify the storage path where your media assets will be stored.
Ensure that an appropriate storage option is ready and configured for each portal. You can utilize the Setup Wizard, which streamlines the provisioning of the required storage accounts.