What table is used for Application Service

[jimmillet]

When I look in the CSDM documentation for the table name for Application Service, I see this: cmdb_ci_service_auto. Even the CI Class Manager shows this.

But in the filter navigator, under Configuration > Application Services, I see csdm_app_services_list. When I go to tables module, I don't see any table with name of csdm_app_services

In the filter navigator, under Service Mapping > Application Services, I see "sa_discovered_services_list". When I go to tables module, i don't see any table with name of sa_discovered_services. In the CSDM documentation and CI Class Manager, the table name for a mapped application service is "cmdb_ci_service_discovered"

So why do the filter navigator selections go to somewhere different than the tables that are in the documentation?

Thanks,

Jim Millet

[Community Alums]

Hi @jimmillet ,

Application services types Primarily are:

• Mapped Application Service [cmdb_ci_service_discovered]
• Calculated Application Service [cmdb_ci_service_calculated]

There are 3 more Application Service types available:

• Application Service [cmdb_ci_service_auto] where no CI Associations are created at all
• Dynamic CI Group [cmdb_ci_query_based_service] where CI Associations are automatically created based on the specified CMDB Group
• Tag Based Application Service [cmdb_ci_service_by_tags] where CI Associations are automatically created based on Tags

An application service is a set of interconnected applications and hosts which are configured to offer a service to the organization. Application services can be internal, like an organization email system or customer-facing, like an organization website. For example, creating financial reports through a web-based application requires a computer, web server, application server, databases, middleware, and network infrastructure. These applications and hosts are all configured to offer the service of financial reporting. In development environments, application services represent instances of a business application or system in different types of development environments, like development, test, or production.

ServiceNow applications refer to devices and applications that comprise an application service as configuration items (CIs). The various CIs and the relationships between them, that comprise an application service, are stored in the Configuration Management Database (CMDB).

Each application service contains an entry point as the top-level CI. An entry point is how clients access an application service. Typically, it is a URL, or a combination of the IP address and port for application services in enterprise deployments. For cloud-based deployments, an entry point can be a URL to a cloud resource like an AWS gateway.

Application service

The Common Service Data Model (CSDM) helps you streamline service types and service offerings. You can add relationships between application services and other service-related objects in the CSDM: Business Application, Technical Service Offerings, or Business Service Offerings.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Rob Saunders]

Hi Sandeep,

Very helpful in your thread but I had a follow-on question.

As you state we expect an application service to be interconnected with hosts and applications to provide services and offerings but I am considering the best solution for modelling SaaS applications.  In conjunction, with Service and Service Offerings I think we need to document an Application Service as a Configuration Item as typically we have different environments and there is a use case for Incident and Change Management. 

However, the concept of interconnected is the challenge as we have zero visibility into the SaaS environment.  I also wish to retain OOB business rules to ensure that Application Services cannot be made Operational without the entry points first being put in place.

I see two following options on this;

1) Create it as a Mapped Application Service expecting that at least one CI is put in place.  That could be a URL CI or possibly other application services which have dependencies to it such as SSO.  Again, I need to tread carefully with the URL entries since we are hoping to invest in ITOM Discovery this year.

2) Turn off the business rule and accept that SaaS applications are allowed to have zero relationships.  This can also be configured into the CMDB Health Rules.

Curious if you have any other guidance or suggestions to this.

Rob

[Vivi Brasil]

Hello @jimmillet , as Sandeep Dutta well described above, there are tables for different purposes. Just for reference, here there are some articles which helped me to understand how to use them:

• Application Services: How to use them?
• Application Services: Tips and Tricks
• Application Services: What's new in Rome

Thank you,

Viviane Brasil

[jimmillet]

Sorry, but none of these posts addressed my question. Let me try to restate it:

Why do the "Application Service" navigation links point to tables that don't exist?

When you click on Configuration > Application Services, I see csdm_app_services_list in the URL. When I go to tables module, I don't see any table with name of csdm_app_services

and

In the filter navigator, under Service Mapping > Application Services, I see "sa_discovered_services_list" in the URL. When I go to tables module, i don't see any table with name of sa_discovered_services.

In ServiceNow URL's, xxxxx_list will display all the records from the xxxxx table. But in both examples I showed, there is no table that matches the name in the URL.