How do I include an .exe running process in a Service Map?

[jimmillet]

I am working on a service map, most of the app involves IIS-SQLDB and that part is mapped. The app teams are telling me there are additional components of the app running on additional Windows servers. These other Windows servers each have 1 running process (.exe) that is unique and can be used to identify as part of the map. I am struggling with how to include these other .exe processes into the map. On the running process tab for the Windows server, this process does not showing anything for "Listening on" , it does have values for "Connecting to" of ":80:1433:8090:". My first attempt was to create separate "Generic Application" entry points for each (there are 8 of these), but I was not sure what to put for a port number, which is required field. One extreme that I am thinking is to create a CI class and new pattern to identify this .exe, but then I think I would need to create new endpoint class also and new entry point.  Seems like a lot of work, and would not scale for all the apps in the enterprise. So I wanted to ask the Service Mapping community on best practice for how to handle .exe running process. Thanks in advance!

[CMDB Whisperer]

What it comes down to is probably "what is good enough" and this answer may change from one application to the next.  Is it good enough to capture the primary Web Server entry point?  Do individual processes need to be represented which enable the alternate entry points?  Are they likely to be managed independently from one another or are they likely to experience outages independently from one another?  Do they have different downstream dependencies that would be impossible to discover without doing the deep top-down discovery that requires development of a custom class or pattern?  If not, then don't be concerned about defining every running process for every unique application in the enterprise.  But if there are compelling reasons for capturing those endpoints, then yes you should create the necessary process classifiers, CI classes, and patterns to enable the additional service mapping steps to occur.