Skip to main content

datajar.mobi Software Deployment Overview

  • Updated

Introduction

dataJAR utilises a number of different techniques and data sources for the 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 Software Deployment

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 directly 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 updates are deployed directly 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 can be deployed directly from your datajar.mobi instance (depending on size and scale), or from your own web-hosted solution. These cannot be cached with an Apple Content Caching server.

macOS Software Deployment

macOS content deployment can be broken down as follows:

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

App Store content (such as Apps and Books)

This is deployed directly 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 GarageBand and Logic)

Due to the size of this content, these are deployed directly 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 directly from your onsite dataJAR appliance for onsite devices. For offsite devices, these will come directly from the dataJAR CDN.

Non-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.

Please note: We are unable to track versions on manually added applications. Any version updates to these applications will need to be requested via a ticket to our support team.

Related Articles

Need further support?

Automate. Simplify. Succeed. If you still require assistance with us or have any further questions, please raise a ticket with our support team.

Alternatively, please see our frequently updated knowledge base articles for reference.

 

Related articles