Service Mapping - Entry Point

[gernst]

Our CMDB uses an agentless discovery. I'm having limited success with my service mapping even when using IP address of entry point (web server usually). We have 20-30 domains in our environment, and the DNS doesn't always resolve, so I usually use the webserver's internal IP (e.g. https:\\xx.xx.xx.xx\folder\). Should the URL always go to the config folder (where config file lives)? Does it matter if the application is built with (e.g. - C#, C, or clickonce) or should I focus more on the hardware entry point (e.g. - IIS, apache)? Please describe the entry point (URL) in more detail.

[SK Chand Basha]

Hi @gernst 

You can try with the TCP entry point which is combination of the IP address and port 

In the running process tab you can find where the application listen along with the port number of the Application servers

Eg. http://172.90.6.x:8043

[Sohail Khilji]

Hi @gernst ,

so, entry point for service mapping should ideally be the URL that external clients or users access to interact with the application. This is usually the URL of the front-end web server.

usually https://xx.xx.xx.xx/folder/ may not always be necessary.

instead focus on the base URL that users would interact with, such as https://xxxxxxxxxx:port or a specific application URL

Eg: 192.168.1.1:8080

I hope this helps....