Service Mapping - Executables as Entry Points

[Tom104]

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?

[Joby]

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.

[Tom104]

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?

[Mary Vanatta1]

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.

[Tom104]

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