Complex Job Processes

You create a single job to be run on one or multiple hosts. Each agent that receives the job runs it individually, optimizing on the software configuration of the host.

To fulfill a job, an agent uses rules and components from the knowledge base. The agent runs the dependency resolver, which takes into account installed inventory, selected policy, and selected profile.

The dependency resolver is a set of algorithms that describes the best possible solution for an agent to complete a job. The best possible solution includes:

• The most cost-effective package to deploy, matching component rules in the knowledge base to the existing configuration of the host

• The most cost-effective way to fulfill dependency requirements, ensuring that the managed host will operate correctly after the job

When you create a job, the agent of each selected managed host picks up the job and runs the following processes. Each agent performs these actions only for the components of its distribution-architecture; irrelevant components are ignored. Therefore, you can safely create a multiple distribution job and send it to a mixed group of hosts.

The job process of each agent, for each task, is as follows:

• Reads the knowledge base to find rule and component updates

• Sends the software component inventory of the host to the dependency manager

• Runs probes to test that host resources can fulfill the job, if you selected probes

• Runs dependency resolver

• Builds a tasklist (if a simulation job, job ends after this step)

• Saves an inventory of each host to be changed

• Gets confirmation for tasks, either from a policy or interactively

• Runs local pre-actions, if you selected any

• Installs local Configuration files, if you selected any

• Customizes local Configuration files with macros, if any are called upon

• Installs requested knowledge base components

• Runs local post-actions, if you selected any

• Runs post-fix actions, if applicable (see Post-Fix Actions)

• Sends job status (success/failure) and new inventory to the DM

Post-Fix Actions

A post-fix action is a binary that performs an action on hosts when a specific package has been installed. Sun Update Connection – Enterprise runs post-fixes without user intervention. Post-fixes ensure machine functionality after changes.

Example 11–1 Using Post-Fix Actions

You create a job that upgrades the kernel. Before the job ends, a post-fix action is triggered, which updates the boot-loader file for the new kernel version.

Agent Queuing

While an agent is running a job, it cannot perform other Sun Update Connection – Enterprise actions:

• It cannot upload its files to the File Browser window.

• It cannot upload its parameters to the Host Settings window.

• It cannot upload an updated inventory to the console. The inventory of the managed host will be updated on the console after the job is done.

  You may assign more jobs to this host, and the jobs will be queued.