Database (Catalog) CIs Service Mapping

[Srinivas Cheer1]

Posted the same question on ITOM forum, pasting here for any other helping hands.

We are in the process of converting our Business Services into Calculated Application Services, but encountering with the following challenge.

• When we made DB Instance relationship to a Calculated Application Service; Server & all Databases(Catalogs) which are related to that Instance is populating under CI association table (hope this is expected as Databases are child of DB Instance).

Now the concern here is, only few Databases are related to that particular Application Service(1), the other Databases are related to some other Application Service(2) which we don't want to show in the Application Service(1).

Any thoughts how do you handle this scenario?

Example:

1. DB Instance1 is running on Server1
2. Databases A,B,C,X,Y&Z are contained by DB Instance1
3. Databases A,B&C are belongs to AppService1
4. Databases X,Y&Z are belongs to AppService2

When we made relationship for AppService1 with DB Instance1 (Appl) by using Depends On:: Used By type - Server1 & all Databases A,B,C,X,Y&Z are listing under CI Association table or on the Service Map. We don't to show X,Y& Z Databases which are related to AppService2.

Thanks.,

[SebastianKunzke]

In my understanding the use of the database instance as application service isn't correct. I am unsure, how it would look with Service mapping from ServiceNow, but for manual mapping my expectation would be the following.

App Service 1 & 2 = You create them as an application service an map the different database and create the relationship to the databases.

The databases again have a connection to the server, they are running on. This is also the OOTB suggested relationship in the CMDB.

For the database instance I would not create an application service, because I can not think of a use case, that this would be necessary. I would go with "just" the suggested relationships. A database instance has its on class under applications (Be careful: Application doesn't need to be an application service). With the suggested relationship you could build the dependency map for database instance to database.

[Srinivas Cheer1]

Thanks for your reply Sebastian, this gave me some more insight to drill down the MSFT SQL Instance relationships.

Please find below suggested relationships of MSFT SQL Instance and the pointers.

What I understand from above diagram is, if we make a relationship with Tomcat as an entry point to the Calculated Application Service with Level3 - DB Instance & the corresponding Databases (all) which are having relationship with that DB Instance will be populated under CI Associations (svc_ci_assoc).

My concern now is, all Databases are not related to that particular Application Service, very few related. This may represent incorrect service map.

As per your first diagram, once we made Application Service relationship with the Application (cmdb_ci_appl) - Association table brings in the Database & Server. But in our case relationships not establishing b/w  Application to Database & Database to Server under cmdb_rel_ci table (Might be due to custom patterns or reachability issue)

If Tomcat brings in all Databases through DB Instance also represent incorrect.

Thanks!