Do you guys always register cmdb_ci_appl

[JesperGuldfeldt]

Hello Everyone, 😊

I encountered a discussion in the forums and am curious about whether it's deemed necessary for an application to always be registered in your guys view.

In our organization, we lack Discovery, and due to our size, this would involve registering numerous "small" system applications, which is a time-consuming process. Currently, we only have these Configuration Items (CIs) and a relationship to:

- Service related to Server.

Additionally, is it appropriate to register a cloud application in this context (cmdb_ci_appl), even if we lack a server to associate it with?

I hope my question is clear - I am certainly not an expert in ServiceNow.

The thread I found:

cmdb_ci_appl = Application CIs created in CMDB that represent something in your environment that you care about. Could be a running process classified by Discovery, or a piece of software that you want to represent or relate via a CMDB CI relationship to a server. Lots of types of applications can be created in this class (web services, for example are subclassed here)... any type of Application that represent a running apps/process/thing that is important to you to track in your CMDB

[Kieran Anson]

Hi,

My personal take would be that trying to manually maintain cmdb_ci_appl without a toolset in place would be somewhat disastrous and a waste of effort. The business maturity will lack any governance or process to maintain the data in this table to produce a return on investment.

However, starting the journey by populating cmdb_ci_business_app would be advantageous. It wouldn't inform you of your deployments, but would aid in painting an architectural image of what applications are in use.

[JesperGuldfeldt]

Hi Kieran,

Thank you for your response. To ensure I understand correctly, could you clarify what a toolset refers to?

Is it an integration with another system that can be utilized to populate cmdb_ci_appl?

- For instance, SCCM or Snow (a licensing program capable of detecting software on servers).

[Kieran Anson]

Yes correct, some sort of discovery tool/application

[Prahlad Kumar]

Hi @JesperGuldfeldt ,

Application and Application Service are two different things. An Application is running on compute and can be discovered. An Application Service is the logic representation of a installation (a system or Business Application) and contains Application CIs and other infrastructure CIs. 

When discovery will run it will not even discover this Application unless same name process is found as running process and still that process will go to corresponding CI class not in APPLICATION CI Class.

If not using Service Mapping then I would recommend creating Application Services per environment manually and create CI relationships to contain the lower level CIs within the Application Service.

Thanks 

Prahlad kumar