1.3 Ondemand Content Server Architecture

Ondemand content is replicated in similar fashion as other ZENworks content using both Primary and Satellite Servers or via a Shared Content Repository. The process for content requests originates with an agent on the workstation and each request moves upstream through content server channels until the request for content is fulfilled. This sequence is explained below:

  1. A request for content is made by an agent installed on the workstation to its content server. Typically a satellite assigned a Content Server role. Satellite Server serving bundle, policy, system update and patch (new feed) content can have both SSL and non-SSL. Only for Antimalware content, content satellite SSL should be enabled.

    If the content is available on that content server, it is served to the workstation.

  2. If the content is not available, the satellite server checks its Content Replication Method to discover its upstream content server (a primary server) and forwards the request to that server.

    If the content is available on that Primary Server and only throttling is enabled, it is throttled to the workstation through the satellite content server.

  3. If the content is not available on the primary server, it checks its Ondemand Content Master list to discover its upstream OCM, and then sends the content request to that server.

    If the content is available on the OCM, it is throttled to the workstation through the primary server.

  4. If the content is not available upstream, the OCM downloads the content from the CDN and throttles it to the workstation through the primary server.