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?

[Jeff WelchBAE]

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?

[Tom104]

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).

[David77]

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!