question Service Mapping - Executables as Entry Points in ITOM forum

Service Mapping - Executables as Entry Points

Tom104 — Tue, 17 May 2022 09:59:40 GMT

Hi All,

How do you actually define your entry points? I've a number of applications running in the organisation that are only consumed by the end user via an EXE file. There's no web-based entry point for these applications.

For the life of me, I can't understand why an EXE isn't a default entry point type in Service Mapping.

Can anyone actually shed any light on this?

Re: Service Mapping - Executables as Entry Points

Joby — Tue, 17 May 2022 18:19:05 GMT

Exe's are usually run(installed) on the user's desk top. But in the back end, it might be connecting to a Webservice or Windows Service(URL or TCP etc). I would start from that point, rather than mapping the individual user desktops in the service map.

Re: Service Mapping - Executables as Entry Points

Tom104 — Thu, 09 Jun 2022 12:18:26 GMT

Hi Joby,

While this is definitely helpful, it's not unfortunately what we need.

The team here want visibility of all executable files pertaining to this particular application on every server/computer within the organisation, and want every executable as it's own endpoint, showing not only where it's installed, but also the database connections etc.

This is software developed on Prem in the 80s/90s, with a lack of any abundant knowledge about it.

Any ideas of how I'd go about doing this?

Re: Service Mapping - Executables as Entry Points

Mary Vanatta1 — Fri, 10 Jun 2022 01:18:16 GMT

Service Mapping has several approaches.

Dynamic CI mapping - Best fit for small application services that are easily grouped using conditional filters or CMDB Queries.

You possibly could create a CMDB Group from a CMDB Query using Query Builder that would find a particular "running process" on a server.

I think you are talking about Top Down Mapping?

Entry points are URL, TCP, DB Connection Strings

Connection Suggestions which can be used with Top Down would also use processes or exe based on the policy you have set.

Check out the Service Mapping Approaches in these videos:

Top Down Approach
Machine Learning (Connection Suggestions

Tag Based Mapping

Dynamic CI Groups (found in Now Create Workshop decks for CMDB, CSDM and Service Mapping)
and a CMDB deep dive covers this as well.

Re: Service Mapping - Executables as Entry Points

Tom104 — Fri, 10 Jun 2022 10:52:14 GMT

Hi Mary,

Yes, I'm attempting to do this via Top-Down Discovery, however the management team want the EXE files to be input as endpoints. We've a bespoke application, which runs on numerous client machines, and they want a full topology map containing each client machine it's installed on as well as all Server Connections and Outbound connections.

The key is that the EXE MUST be utilised as the endpoint, as, using a DB as an endpoint doesn't provide sufficient information/connection details as to the clients the EXE is installed on.

The problem I have, is getting the EXE as an Endpoint. This is not standard out of the box, so I need to identify how to do this. I've seen the links you've provided before, and none of these actually give you any explanation as to how to start this process. The ServiceNow resource is extremely vague and gives limited answers.

I just need a definitive step-by-step, but can't locate anything for this.

Thanks,

Tom

Re: Service Mapping - Executables as Entry Points

vidyarani — Wed, 23 Nov 2022 09:15:16 GMT

Hey Tom,

Did you get any information for your need on building Service Map for exe based entry points?

Thanks,

Vidya

Re: Service Mapping - Executables as Entry Points

Manuel Stimac — Thu, 01 Dec 2022 09:20:21 GMT

Hi @Tom104,

I also faced a similar question once. I was only able to bring it to paper so this is a bit of a theoretical answer to your question.

You could create an endpoint & pattern by yourself.

The endpoints usually extend from the table cmdb_ci_endpoint.

The definition could be path, filename & machine installed on. Challenge would be to get into all the clients.

Also searching the .exe for more information is quite hard as it is compiled already. In the best case you would have some configuration file to parse, like which DB your application connects to to build the map.

This is all high level of course. But to get you started, I strongly recommend the Service Mapping Implementation On Demand course. There are quite good labs how to build new patterns and connection from scratch. Especially the last chapter is really hands on with a real world example!

Some completely other approach would be the other way around. Like @Mary Vanatta1 described with the query builder. But this would leave the point of your map behind.

Let me know if this helps and how you go further. Very nice topic by the way 😎

If this answer helps you please mark it as Helpful/Solution.
Thanks & Regards - Manuel

Re: Service Mapping - Executables as Entry Points

Mary Vanatta1 — Thu, 01 Dec 2022 15:21:42 GMT

I recommend you to check out the latest improvement found in the ServiceNow store called Service Mapping Plus.
We had a release on Nov 3rd. Our product manager has made a post here: https://www.servicenow.com/community/itom-blog/automated-service-suggestions-machine-learning-is-supercharging/ba-p/2372224

Re: Service Mapping - Executables as Entry Points

Jeff WelchBAE — Tue, 15 Aug 2023 18:56:50 GMT

I have a similar situation where we have application accessed via RDP - which I think I can create a TCP endpoint with the host on port 3389. However, we also have executables that are launched via a network mapping. How do we handle these?

Re: Service Mapping - Executables as Entry Points

Prabu Velayutha — Tue, 15 Aug 2023 21:13:44 GMT

@Tom104 Mapping Client machines is not a use case for Service Mapping. Service mapping is topological representation of Infrastructure (Load Balancers, Web, App Servers, DBs) and applications hosted(IIS, Tomcat, MQ, MSQL ETC) which makes up a Business Service.

Client Machines are actually consumer of the Application/Business Service adding them to the map is not recommend.

Re: Service Mapping - Executables as Entry Points

Elvis — Fri, 01 Dec 2023 19:48:45 GMT

hi Tom,

Did you figure out the way forward? I am in the similar situation where as I need to give ".exe" as an entry point for a custom app developed on prem

Re: Service Mapping - Executables as Entry Points

Tom104 — Mon, 04 Dec 2023 15:16:23 GMT

Hi Jeff,

I've marked off the correct solution. What this inevitably came down to was user education, Service Mapping is only meant to demonstrate the infrastructure that makes up the application Service. An executable is not considered an Endpoint.

What I have done, and would do, in your scenario, is to use the TCP Endpoint, specify 3389 as the port number, and explicitly state in the "Comments" box [Remote Desktop Connection on port 3389 to "Hostname".]

It's not the ideal scenario, but what this is really meant to show us is the supporting infrastructure, i.e. SQL Databases, Tomcat Servers that support the application.

You may also need to redefine your understanding of an application vs software (as I did).

Re: Service Mapping - Executables as Entry Points

Jeff WelchBAE — Mon, 04 Dec 2023 15:29:04 GMT

To be exact, I was not referring to mapping a user machine but we have cases where a user launches an .exe on their machine which then in turn connects to the application service. We also have some apps where users are mapped to a host server and then click on the .exe on the server. We also have user machines with a Citrix app that connects to the app service.

Re: Service Mapping - Executables as Entry Points

Tom104 — Mon, 04 Dec 2023 15:35:50 GMT

Hi Elvis,

I've marked off the correct solution. What this inevitably came down to was user education, Service Mapping is only meant to demonstrate the infrastructure that makes up the application Service. An executable is not considered an Endpoint.

If yours has some underpinning database, or IIS Server, etc, those should be your entry point options.

Re: Service Mapping - Executables as Entry Points

Prabu Velayutha — Tue, 05 Dec 2023 18:30:24 GMT

@Jeff WelchBAE

Option 1: If your organization uses a less known or proprietary application that does not have a corresponding entry point type in Service Mapping, you must create it. Refer the product documentation below.

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/service-mapping/task/t_CreateEntryPoint.html

Option 2: Which I have followed in rare case of unknow entry points

In these scenario I hope the application service should be an entry point, if you have the IP address of the application server and port on with the app service running then create a TCP entry point and you have set the respective down stream connections to the DBs etc....

If my response helps to solve your issue. Kindly mark it as helpful & correct.

Re: Service Mapping - Executables as Entry Points

Jeff WelchBAE — Tue, 05 Dec 2023 18:39:23 GMT

To be clear, I was not attempting to map anything on a client machine.

Re: Service Mapping - Executables as Entry Points

Jeff WelchBAE — Tue, 05 Dec 2023 18:40:26 GMT

I have been using host/port in lieu of an application specific entry point especially for smaller applications.

Re: Service Mapping - Executables as Entry Points

David77 — Wed, 27 Mar 2024 13:43:58 GMT

Tom, what did you end up doing to resolve this?
We have a few applications where the SME is saying an .EXE is the entry point to the application, and our goal is to run Service Mapping as it's a critical application. Thanks!