Korbyt Implementation Architectures

What are our three Korbyt architectures and protocols used to operate them?

 

Cloud Implementation

Korbyt Cloud Architecture

 

Important things to know about this configuration!

1. All players that are scheduled with URLs but must be able to access that url (https and http requests) from the players location on the network. This rule also applies to players scheduled with OnTarget content.

Hybrid Implementation

Korbyt Hybrid Architecture

 

Important things to know about this configuration!

1. KDA’s will attempt to make its FIRST connection  to the cloud servers for provisioning to obtain the local server name. It will then switch all communication to the on prem server. The on prem server can be manually configured on KDA configuration pages to prevent having to make this connection.

2. All KDAs are pre configured with external NTP servers to sync time. If this is not allowed all players will need to be pointed to an internal NTP server to prevent time drift.

3. All players that are scheduled with URLs but be able to access that url (https and http requests) from the players location on the network. This rule also applies to players scheduled with OnTarget content.

4. The on prem server must retain communication to the cloud. If changes to a player are made on your tenant while the connection the from the on prem server to the cloud has been severed the changes will not reflect on the player.

On Premise Implementation

Korbyt On-premise Architecture

 

Important things to know about this configuration!

1. We encourage you to ONLY update the player software when you are also scheduled to update the server software.

 

About Kevin Clark

Client Technical Support - Team Lead at RMG Networks. Been working at RMG Networks for over tens years and in technical roles for over 25 years.