Additional tab
This topic describes the Additional tab. This topic also describes Reserved Additional Properties.
The settings in the Additional tab are optional. With the default SLA Penalty property, you can set an hourly SLA penalty for templates that have SLA settings configured. The SLA penalty calculations let you set a cost estimate for each hour of downtime caused by an outage. For more information about adding hourly SLA penalties for templates, see Setting SLA penalty calculations.
In this tab, you can also add custom properties. For example, you can create an additional attribute that obtains its value from a field in a database row.
Reserved additional properties
- Click the New Parameter button on the toolbar.
- Enter the parameter name and the default value.
| Reserved property name | Sample value | Property description |
|---|---|---|
| ViewDefName | AppManagerView | This view definition is used for any template/instance where this value is defined. |
| MapName | maps/Europe.ivl | This map is used for an template/instance where this value is defined. |
| WebtopViewName | NewView | This Webtop view name is used in the Service Details portlet and the AEL when launching from an instance that is assigned to the template where this value is defined. |
| UseESDAIdentifiersOnly | True or False |
When the property is set to true, all existing event identifiers are deleted from the memory model during each invalidation run. For new identifiers, the service accepts only identifiers that are sent from External Service Dependency Adapter (ESDA) policies or the Service Component Repository (SCR). This means what user will no longer be able to use identifiers set from the TBSM UI, as it will be erased at every invalidation. When the property is set to false, all event identifiers are preserved for use by the service. To delete an event identifier, you must do so manually. The property is set to false by default. Note: When enabling this property, it is good practice to
invalidate the service tree from the top level node once
after saving the template. This is to ensure that the
template and identifier changes get propagated correctly
throughout the service tree for the services which have the
template applied on.
|