Local properties for a component template

When editing a component template, you can assign properties directly to the component template.

These are called local properties, and they only apply to the component template; they are not available globally like properties created in the Property Dictionary.

Assigning local properties to a component template allows you to discover multiple instances of the same component on the same server. To accomplish this you must create sets of local properties defined to the values you need. For example, suppose you wanted two instances of an Apache server component on the same machine. Using multiple instances of local property sets, you can define different locations for the components encapsulating the Apache server. When you run a Component Discovery Job, it examines the different sets of local properties and create a component for each set.

Another purpose of local properties is for use as variables in Compliance rules, as described in Defining-a-basic-condition. Such variables can be either transient (temporarily stored only for the duration of rule execution) or persistent (stored persistently in the database). For any local property that you want to use as a transient variable, include the VAR_ prefix (in uppercase) at the beginning of the property name.

Note

The list of properties on the Local Properties tab might be quite long. Therefore, by default, all transient variables are hidden when you access the Local Properties tab. You can to show or hide the transient variables using the Show Transient Properties check box below the list of properties.

The Local Properties tab lets you perform the following procedures:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*