Introduction

dataJAR utilises a number of different techniques and data sources for deployment of content and software to both macOS and iOS (including tvOS and iPadOS) devices for our datajar.mobi customers. This document provides an overview of the differences and sources.

iOS

iOS content deployment can be broken down into:

App Store content (such as Apps and Books)
iOS updates
Enterprise / In-House Apps

App Store Content

This is deployed direct from Apple via the MDM framework. This content can be cached to aid with delivery via the use of an Apple Content Caching server.

iOS Updates

These deployed direct from Apple via the MDM framework. This content can be cached to aid with delivery via the use of an Apple Content Caching server.

Enterprise / In-House Apps

These are deployed either direct from your datajar.mobi instance, or from your own web-hosted solution. These cannot be cached with an Apple Content Caching server.

macOS

macOS content deployment can be broken down as follows:

App Store content (such as Apps and Books)
Music Loops (such as for GarageBand and Logic)
macOS updates
Auto-Update Applications
Non-Auto-Update Applications

App Store content (such as Apps and Books)

This is deployed direct from Apple via the MDM framework. This content can be cached to aid with delivery via the use of an Apple Content Caching server.

Music Loops (such as for GarageBand and Logic)

Due to the size of this content, these are deployed direct via your local onsite dataJAR appliance, triggered by a datajar.mobi policy.

macOS updates

These are deployed via the default Apple frameworks, direct from Apple. This content can be cached to aid with delivery via the use of an Apple Content Caching server.

Auto-Update Applications

These are deployed direct from your onsite dataJAR appliance for onsite devices. For offsite devices, these will come direct from the dataJAR CDN.

Non-Auto-Update Applications