<h2>Can we use the same entry point URL for 2 different service maps as entry point?</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Summary</h3><section><style type="text/css"><!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } </style> <div class="ns-kb-css-body-editor-container"> <ul style="list-style-position: inside;"><li>Based on the Service Mapping design, an Entry Point is expected to uniquely identify the starting point of a business service or application map. If the same Entry Point URL is configured for multiple Service Mapping patterns/applications, Service Mapping may not be able to unambiguously determine which application service should own the discovered topology.</li><li>As a result, using the same Entry Point URL for two different application services is not a supported configuration for top-down Service Mapping and can lead to validation errors, duplicate identification concerns, or map creation failures, which is consistent with the behaviour you observed.</li><li>To map multiple applications successfully, each application service should have a distinct Entry Point (for example, a unique URL, hostname, IP address, port combination, or other application-specific starting point) that enables Service Mapping to clearly distinguish one service from another during discovery.</li></ul> <span id="ns-kb-css-end-div-identifier" style="display: none; pointer-events: none;"></span></div></section></div></article></div>