ESDA rules and service structure

This topic describes ESDA rules and service structure. This topic also describes seed services.

You configure ESDA rules for the service templates in your service model. The ESDA rules consist of queries and naming expressions that discover and configure the child and parent services defined by the aggregation rules in the seed service template. For each of these service templates, the ESDA rule creates multiple services that share the common rules defined in the service templates. You can configure ESDA rules that discover services for each of the service templates in this service model. The seed template can be at any level, depending on your configuration.

Using the template structure shown in Figure 1, you configure the ESDA rules in the seed service template: BUSINESSUNIT. Figure 1 shows the service template structure where the BUSINESSUNIT is the seed service template, CUSTOMER is the parent service template, and APPLICATION is the child service template. Figure 1 is an example of a possible configuration.

Figure 1. Example service template structure
Example service template structure

Before you configure your ESDA rules, you should analyze your source data and create a service structure by defining the relationships between TBSM service templates. You should sketch these relationships on paper before you start your ESDA rule configuration.

Creating a seed service

After you create the service template structure, you need to create a seed service as a starting point for your ESDA rules. The rule cannot discover any new services until you create a seed service and assign it to template with an ESDA rule.

When a service has ESDA rules configured in its assigned service template, TBSM automatically executes the necessary query and logic to discover any new services related to the seed service. TBSM then combines the dynamically discovered services with any existing child or parent services of the seed service. As the data changes in the external data source, TBSM adjusts the service model to reflect the changes by adding and removing services and relationships in the service model.