What is global updating?
A process that automates replication to your distributed repositories and keeps managed systems current
How is global updating initiated?
Checking in contents into the Master Repository initiates a global update
What is the typical duration of a single global updating process?
An hour
What is the best practice regarding use of global updating?
Schedule a regular pull task (master repository update) at a time when traffic is minimal (because network traffic is increased during the update)
What are the steps of the global updating process?
1 Contents are checked in to the Master Repository.
2 The server performs an incremental replication to all distributed repositories.
3 The server issues a SuperAgent wake-up call to all SuperAgent in the environment.
4 The SuperAgent broadcasts a global update message to all agents within the SuperAgent subnet.
5 Upon receipt of the broadcast, the agent is supplied with a minimum catalog version needed for updating.
6 The agent searches the distributed repositories for a site that has this minimum catalog version.
7 Once a suitable repository is found, the agent runs the update task.
If an agent doesn’t receive the broadcast emitted from the Superagent during the global updating process, how does it get the minimum catalog version?
It’s supplied at the next agent-server communication
What are the requirements that have to be met to implement global updating?
How does one enable global updating?
From the ‘Global Updating’ server setting
What are the disadvantages of global updating?
2 - Increased traffic/burden on network - because global updating involves distributing content to the entirety of the network in a short period of time, it results in a significant load on the network. It’s better to deploy updates to systems in smaller groups to spare bandwidth
What are the notable differences between a product deployment project and a product deployment client task?
What is the difference between a continuous product deployment and a fixed product deployment
A fixed product deployment means that specific systems are selected, either from the system tree or from a query
A continuous product deployment means that the affected systems are chosen either by selecting a group or groups within the system tree, or specifying a tag that systems must possess in order to qualify