Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Application Service (cmdb_ci_service_discovered vs. cmdb_ci_service)

J Shone
Tera Expert

Looking at the white paper I am a little confused on Application Service.

 

Application Service is defined as "Logical representation of a deployed application stack"

It maps to cmdb_ci_service_discovered and the white paper does not mention cmdb_ci_service (classification=application).

That said the PDI examples of Application Service are using cmdb_ci_service.  And the service classification is available on cmdb_ci_service for Application Service.

What are ServiceNow saying or what is your real-world experience?

If you haven't enabled Discovery do you use cmdb_ci_service (classification=application)?  

Once you enable discovery do you convert to use cmdb_ci_service_discovered?  

Or are both tables meant to be used in parallel?

 

 

1 ACCEPTED SOLUTION

Giles Lewis
Giga Guru

Great question!

cmdb_ci_service_discovered is a legacy table that was created several years ago as part of the Service Mapping product. When CSDM was introduced they decided to repurpose the existing table. You are supposed to ignore the fact that "discovered" is part of the name, and feel free to manually populate the Application Service table. (I am not sure what happens later if you decide to install Service Mapping; but I assume they have figured this out and there are no worries.)

Note that in the class model cmdb_ci_service_discovered inherits from cmdb_ci_service. If you add a record to Application Service [cmdb_ci_service_discovered] then it is automatically added to Business Service [cmdb_ci_service]. You can also convert a Business Service to an Application Service.

View solution in original post

20 REPLIES 20

additional detail, we're on Quebec

 

we found that this PRB fix is still not fixed in our Quebec instance: