Software policy templates

Software policy templates are a defined set of software polices that are handled as individual policies and can be installed, modified, or detached as discrete policies. The template itself is just the container and is not actually installed on the server.

The value of the software policy templates is that the software policies can be managed independently even after they are installed. For example, policies that were installed from a template can be detached, modified, and updated as individual policies, whereas policies that were installed as embedded sub-policies of another software policy cannot.

A software template can be associated with either a single operating system family or multiple operating system families. When you add software resources to a software template, the software resources must belong to the same operating system family as the software template. For example, if you define the operating system for a software template as HP-UX, you can only add software resources applicable to versions of HP-UX to the software policy.

About installing software using a software policy template

You can install software by using a software template.You use the same procedure to create a software template as you use to create a software policy, however, you specify that the policy is to be a software template. See Remediate and install software.

The difference is that when you attach, install, or remediate a server against a template, the template itself is not attached or installed, just the policies it contains. For example:

  • When you attach a software policy template, the template itself is not attached, just the policies it contains.
  • When you remediate a server against a software policy template, the software policies specified in the software template are installed individually; the template itself is not installed.

Note that software templates are different than software policies with embedded sub-policies which are handled as one flattened policy after installation and are not recognized as discrete policies. See Embedded software subpolicies.