ESDA query concepts

This topic describes ESDA query concepts, ESDA data sources, and selecting only the data you need.

After you have selected the seed service template for either child or parent rules, you create an SQL query to select the service data from an external data source. The SQL query selects a set of data you use to obtain the service names for the child and parent services of a given seed service.

ESDA data sources

Before you create an ESDA query, you must configure the data source you want to use for TBSM. You can configure the data source for TBSM from the Edit Data Source tab.

Note: If you use the Query Builder to create your query, the fields you select with your query are added to the drop-down lists in the Results section of the window for the Instance Name, Display Name, and Description expression fields.

Important: select only the data you need

Whenever you create a query for an ESDA rule, it is important that you only select the tables and fields you need to identify unique service names for the services you want to discover. The Select * clause should only be used in cases where you need data from all the columns in a table. Otherwise, your queries will take more time and system resources to execute.

In the following example, the query only selects the fields you need to identify the services from the TBSMDEMO.ESDA_APPLICATION table.


select APPLICATIONID,APPLICATIONNAME,APPLICATIONTYPE from TBSMDEMO.ESDA_APPLICATION
where BUSINESSID = __BUSINESSID__

This query also uses the __fieldname__ notation. This notation lets you specify a variable field value. In this example, both the TBSM.DEMO.ESDA_APPLICATION table, and the TBSM.DEMO.ESDA_BUSINESSUNIT table contain a key field named BUSINESSID. The query only selects rows where the value of the BUSINESSID field (in TBSM.DEMO.ESDA_APPLICATION table) matches the field value (in businessunits table) for the seed service. This notation refers to the value for the seed service instance.

For the business services in the service model, this example query dynamically imports the data about the child services of a given business unit service. Each business unit service has a field called BUSINESSID which was set by the ESDA query that created the business unit services from data in the TBSM.DEMO.ESDA_BUSINESSUNIT table.

The data about the child service is in a table called TBSM.DEMO.ESDA_APPLICATION, which also has a BUSINESSID field that maps each application to a given business unit. The ESDA rule uses the data from the TBSM.DEMO.ESDA_APPLICATION table to import the corresponding applications as child services of the matching business unit service. That is, when the BUSINESSID value matches in both tables, the ESDA rule creates a child application service for the matching business unit service.