Properties description

A property is a symbolic representation of information that is likely to change from object to object in BMC Server Automation, such as the path to an installation directory on a server. You can assign properties to most objects. Some common uses for properties are:

• Assigning values to objects so those values can be used elsewhere in BMC Server Automation. For example, a property can indicate an object's development status (such as DEV, QA, or PROD).
• Creating parameters, which are references to properties (see Parameters-description).
• Defining smart groups, which are groups of objects that are automatically populated based on criteria in the form of property settings. All folders except RBAC Manager let you create smart groups. In BMC Server Automation you can perform many actions on server and component groups, so a well designed scheme for assigning properties to servers can enhance productivity. For example, you can create a property, such as OWNER, and then assign different values for that property to different servers. If some servers have OWNER set to QA and others have OWNER set to DEV, then smart groups can automatically separate QA servers into one group and development servers into another.

BLPackages, component templates, and system packages let you assign local properties that only apply to a particular object. Local properties are primarily used to create multiple instances of an object on a single server. For example, you can use local properties to deploy a BLPackage to multiple locations on the same server.