The application service map is either incomplete or failing to discover dependencies.

Venkatesh Janag
Tera Contributor

Tuesday

Details below:
Application Name: Venafi – Prod
URL / Entry Point: https://venafiprod.scj.com/aperture/
Hostname: zvnfipcusw101
Service Type: Calculated Application Service

Issue Observed:
Application service map is not fully populated
Dependencies and underlying infrastructure are missing or incomplete
Possible failure in discovery or mapping process

Preview file
72 KB
Preview file
72 KB
0 Helpfuls
  • 216 Views
3 REPLIES 3

Yogesh11bhatt
Kilo Guru

Tuesday

Hi @Venkatesh Janag ,

 

Looking at the details you provided, there appears to be a core architectural discrepancy that may explain the incomplete service map.

You listed an Entry Point (URL), but the Service Type is set to Calculated Application Service. In ServiceNow, these two concepts use different mapping approaches. Calculated services rely on existing CMDB relationships, whereas URL-based top-down discovery is typically associated with a Mapped Application Service.

To troubleshoot effectively, it would help to clarify which approach you're intending to use.

Scenario A: You want to map the application via the URL (Top-Down Discovery)

If your goal is to use the URL (https://venafiprod.scj.com/aperture/) to discover and trace the application infrastructure, then review whether the service should be configured as a Mapped Application Service.

In that case, validate:

  • The entry point configuration.

  • MID Server connectivity.

  • Credentials used for discovery and service mapping.

  • Service Mapping logs and pattern execution results.

  • Network/firewall access to zvnfipcusw101.

Scenario B: You want a Calculated Application Service (CMDB-Driven)

If the service is intentionally configured as a Calculated Application Service, then the URL itself is not what drives the map.

Instead, verify:

  • The service population criteria or Service Builder rules.

  • Whether zvnfipcusw101 is included in the calculation scope.

  • Whether the underlying infrastructure CIs exist in the CMDB.

  • Whether the required CMDB relationships (for example, Depends on::Used by) have been established between the application and its supporting components.

A Calculated Application Service can only visualize relationships that already exist in the CMDB. If those relationships are missing or incomplete, the resulting service map will also be incomplete.

Could you confirm whether you're trying to build the service map through URL-based discovery or through existing CMDB relationships? That will help narrow down the root cause.

Hope this helps point you in the right direction!

Please mark this answer as Helpful if it resolves your question. 🙂

 

Thanks,
Yogesh Bhatt

Venkatesh Janag
Tera Contributor

Tuesday

Hi @Yogesh11bhatt.,

Thank you for your responce.

We are using URL based discovery, but how can we know that which approach we have to follow for a particular application?

0 Helpfuls

Yogesh11bhatt
Kilo Guru

Tuesday

Hi @Venkatesh Janag ,

 

The choice between a Mapped Application Service and a Calculated Application Service should be driven by how accurately you need the application dependencies to be discovered and maintained.

Use a Mapped Application Service when:

  • You have a known entry point (URL, VIP, hostname, IP, etc.).

  • You want Service Mapping to automatically discover the application topology.

  • You need end-to-end visibility of web servers, application servers, databases, load balancers, and their dependencies.

  • The application architecture changes frequently, and you want the map to stay current through active discovery.

Examples: Venafi, ServiceNow-integrated web applications, SAP web portals, or any custom business application with a specific URL entry point.

Use a Calculated Application Service when:

  • The required CIs and relationships already exist in the CMDB.

  • You want to build a service dynamically using Service Builder, tags, Dynamic CI Groups, or existing relationship rules.

  • You do not need Service Mapping to execute top-down discovery of the topology.

  • The service acts more as a logical/business grouping than a tightly coupled technical application.

Examples: "All Production Windows Servers," "SCJ EUC Support Service," or a business service composed of manually related infrastructure CIs.

Conclusion for your Venafi Application

Since you mentioned that you are using URL-based discovery for Venafi, I would expect this to be implemented as a Mapped Application Service rather than a Calculated Application Service.

I recommend checking with your Service Mapping team or reviewing the Application Service record to determine why it was initially created as a Calculated Service. If the intent is to discover underlying dependencies directly from that URL, a Mapped Application Service would typically be the preferred architectural approach.

 

Hope this helps clarify when each approach should be used!

 

Please mark this answer as Helpful if it resolves your question. 🙂

 

Thanks,
Yogesh Bhatt