Setting the service model structure
This topic describes how to set the service model structure using an example.
You cannot configure ESDA rules until you have defined the structure of your service model. You define your TBSM service model structure by defining the relationships between the service templates in your service model. Figure 1 shows an example service template structure. The status of a service assigned to a parent service template depends on the status of services assigned to child service templates. You define these relationships by configuring aggregation rules in your service templates.
Example service model structure
This example shows how to define the relationships
between the service templates for the CUSTOMER, BUSINESSUNIT, APPLICATION,
and HOST service templates, as described in Table 1.
| Parent Service Template | Child Service Template | Condition |
|---|---|---|
| CUSTOMER | BUSINESSUNIT | The status of CUSTOMER services changes based
on the status of BUSINESSUNIT services. |
| BUSINESSUNIT | APPLICATION | The status of BUSINESSUNIT services changes
based on the status of APPLICATION services |
| APPLICATION | HOST | The status of APPLICATION services changes
based on the status of HOST services |
Each of these service templates describes a type of TBSM service that shares common rules and attributes. For each of these service templates, you create many services that share common rules and attributes. Each service is uniquely defined by the Service Name attribute. The ESDA rules let you select and filter the data TBSM needs to create the individual services assigned to each service template.