... {section}
{column:width=25%}
{livesearch:spaceKey=xVM}
h6. Contents
{children:depth=1}
h6. [Index]
{column}
{column:width=75%}
h4. What Are Policies?
A policy defines how a job should be performed and sets the automation level of the job.
Policies determine the actions that will be taken up by the Sun ^TM^ xVM Ops Center to run a task. You can assign the actions that need to be performed when installing certain patches and packages. You can predefine some actions as unacceptable or automate the task without user intervention.
Policies focus on the component level. Select a component from the inventory, possible deployment action, and then apply a deployment policy setting to the pair.
h4. Policy Settings
The different policy component settings include the following:
* *Install*: Installs the selected component.
* *Uninstall*: Uninstalls the selected component.
* *Upgrade*: Upgrades the selected component to the given version.
* *Downgrade*: Downgrades the selected component to the given version.
* *Apply Fix*: Deploys the provided fix.
* *Ignore File Conflict*: A file conflict occurs when the selected component provides a file that cannot be installed on a machine with a file provided by another component that is already installed. If both components are certified, the rules in the knowledge base of the Sun hosted tier handle the deployment without conflicts. If one or both components are not in the knowledge base, the conflict causes the job to fail.
The actions for the policy component settings include the following:
* *Ask*
Waits for user confirmation before performing a job.
* *Always*
Performs the job automatically without user intervention.
* *Never*
Does not perform an operation or job.
|