Application Service Dependencies to other Services with Service Mapping

[Marshall Parker]

When you are utilizing Service Mapping to build out an Application Service, what is the recommendation on where to build dependencies to other Application Services?

Scenario is: You have mapped a Business Application -> Application Service with service mapping providing a view of infrastructure that makes up this Application Service.

This Application Service [web based store-front] relies on another Application Service [ETL middleware] to push data on a daily basis to a 3rd App Service [Reporting software].

I can represent this logical connection with CI Relationships showing a Depends On/Used by between the various Services - but the CI Relationship won't show any connection in the Event Dashboard.

Do we keep the Svc-to-Svc relationships in CI Relationships?  Do we add manual entry points on the map pointing to the other Service [i.e. a manual EP on the web map pointing to the ETL Service]?

[DuaneNMore · Accepted solution]

If the dependent Service has been mapped, ETL middleware in this case, has been already mapped and has an entry point then it can/should be included by one of 2 methods For sake of discussion, lets say the entry point to the ETL is a TCP Connection 10.1.1.1:4000.

First, during the top-down discovery of the web-based store-front it encounters the entrypoint for the ETL middleware (10.1.1.1:4000), it will automatically include the Service in the map, and not remap the ETL Service.

Second, you could add a manual connection. You right click the CI which will be the source of the connection,  select "Manually add a connection", select Entrypoint type "TCP Connection" then put in 10.1.1.1 for the host and 4000 for the port. Service Mapping will recognize this as an existing entrypoint and include the service in the map.