Manually Add an Entry Point to a Service Model Component
Sometimes the service map modeled by ASM may not be as complete as you expected. For example, you know there is another running software behind a load balancer, or your organization's policy stopped ASM to discover and model some CIs.
As a service modeler, if you fully understand your topology and know all the details about the topology, to achieve a full modeling topology diagram, you may extend the service map by manually adding an entry point to any component of a service model (business application or running software), so that the new entry point can trigger further ASM discovery to find the next hop from the service model component.
Caution Perform this action only when you fully understand your topology.
To add an entry point manually to a service model component,
- From the Service Modeling dashboard page, click the service model (business application or running software) of your interest.
- On the service map, hover your mouse over or click the component to which you want to add an entry point.
- In the context menu, click
and then select Add Entry Point 
. -
In the Add Entry Point pane that appears, provide values for the following settings:
Field (* required) Description IP* Provide the IP address in IPv4 format.
For details about IPv4 format, see New/Edit Range Dialog Boxin the Universal CMDB Data Flow Management Guide.
Port* Provide the port number Context Provide a context string. The context string is optional and is used to identify the unique module. For example, if the entry point refers to an application in Web Server as http://1.1.1.1:8080/test, the context string should be "/test". -
Click OK.
After the new entry point is added successfully, it will automatically trigger new instances of the Host Discovery by Shell jobs in this service activity to discover the target RunningSoftware CIs.
