Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Managing properties

Properties store settings and values that describe characteristics of your releases. Properties are important to the execution of requests.

Properties are assigned to components and are mapped to the components in the various environments that you create. Properties are also associated with servers and server levels. Components, servers, and server levels inherit property values from the property dictionary, which is also called a global map.

You can specify different values for a property in the context of each environment in which a component is installed (for example, a classpath). This specification ensures that the same value is mapped to each request working with those components in those environments. You could also define properties for servers and server aspects by specifying different values. The steps for a request can refer to properties.

To create a property

  1. Click the Properties tab, and then click Create Property.
  2. In the Name field, type the name of the property, and in the Default Value field, the value of the property.
     You can have a property with a numeric list:
    • If you want any of the list to be blank, type a comma with nothing else (indicating blank).
    • Otherwise, the numeric list is comma-separated.
  3. In the Components field, select the check boxes for the components.
  4. (Only for a property that follows a server or server level) Expand Server assignment and select the check boxes for your required servers from the Servers field.
  5. (Only for a property that follows a server or server level) If your release requires server levels, select the check boxes of the required server levels in the Server Levels field.
  6. Click Create.

To compare the property with the environment

After you have created a property, you can compare the environment with the property as follows:

  1. Click the Property Maps link on the right, or select Reports > Maps.
  2. Click Properties Map by.
  3. Select the required Application, Environment, and Components from the right, and click Compare to view the associations.
     You can select one application but multiple environments and components. A table displays the associations.

Note

The table appears only if associations exist among your selections. If the application, environments, and components that you select have no associations, the system tells you to make appropriate selections.

The components have properties associated with them, and the environment has values associated with it. If the environments do not have values, you must fix them.

Where to go from here

Properties are also associated with components and servers and are used in automation steps. You must map a property to use the property value in automation steps. After you have performed property mapping, the server is assigned those values or arguments.

You can also create properties to implement a release plan in advance. BMC Release Process Management provides the local properties feature.

 

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