Service model: example 2

This topic describes an example service hierarchy, the dependencies for the example service hierarchy, and the service hierarchy displayed in the View Service tab of the Service Editor/Viewer.

Figure 1 shows another way you could create a service hierarchy for a similar service. In this example, the status of the services depends on both ObjectServer events and data from a DNS SQL data source.

Figure 1. Example service hierarchy
Example service hierarchy

Table 1 describes the dependencies for the example service model in Figure 1.

Table 1. Service model dependencies
Template Service instances Aggregation rules Incoming status rules
WebApp customer8 Status of WebFarm, DBFarm, and NetGroup services None
WebFarm webfarm1 Status of Webserver services None
WebServer webserver4

webserver5

webserver6

 None Netcool/OMNIbus events for web servers 4, 5, and 6
DBFarm dbfarm1 Status of Database services None.
Database database3

database4

 None Netcool/OMNIbus events for databases 3 and 4
NetGroup netgroup1 Status of DNSServer services

Status of AuthServer services

 None.
DNSService dnserver2 None Data from a database that contains DNS availability information for dnsserver2
AuthServer authServer2 None Netcool/OMNIbus events for authserver2

In Figure 1, the provider has created service templates for:

  • WebApp (with a service called customerB) that depends on the status of services tagged with the WebFarm, DBFarm and NetGroup templates as defined in the WebApp template's aggregation rules.
  • WebFarm (with a service called webfarm1) that depends on the status of services tagged with the WebServer service template as defined in the WebFarm template's aggregation rules.
  • WebServer (with services webserver4, webserver5, and webserver6) that gets its status from Netcool/OMNIbus events as defined in the template's incoming status rules.
  • DBFarm (with a service called dbfarm1) that depends on the status of services tagged with the Database service template as defined in the DBFarm template's aggregation rules.
  • Database (with services database3 and database4) that gets its status from Netcool/OMNIbus events as defined in the template's incoming status rules.
  • NetGroup (with a service called netgroup1) that depends on the status of services tagged with the Authserver and DNSserver service template as defined in the NetGroup template's aggregation rules.
  • Authserver (with a service called authserver2) that gets its status from Netcool/OMNIbus events as defined in the template's incoming status rules.
  • DNSserver (with one instance called dnsserver2) that gets its status from an SQL query into a database with information about DNS events.