Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Create entry point types for Service Mapping

Log in to subscribe to topics and get notified when content changes.

Create entry point types for Service Mapping

An entry point is how clients access an application service. If necessary, you can create a new entry point type in addition to preconfigured entry point types in Service Mapping.

Before you begin

If your ServiceNow instance uses domain separation and you have access to the global domain, select the domain to which the application service belongs from the domain picker (Domain picker). The selected domain must be a domain without any child domains.

Role required: sm_admin or admin

About this task

Service Mapping starts the discovery and mapping process for every application service from the entry point you define for it. In addition to this, Service Mapping patterns use entry points to discover CI outbound connections.

Service Mapping includes a wide range of preconfigured entry point types that cover most commonly used applications. If your organization uses a less known or proprietary application that does not have a corresponding entry point type in Service Mapping, you must create it.

Entry points are modeled in the ServiceNow CMDB as CIs of endpoint type. Entry points are stored as records in the Endpoint [cmdb_ci_endpoint] tables.

Like any other CI type, an entry point contains several important definitions that apply to all CIs belonging to it:
  • CI attributes are added as fields to the CMDB tables.
  • Identifiers help Service Mapping and Discovery to differentiate between new and existing CIs. For example, if there is an Active Directory Forest endpoint CI type defined in the CMDB, and Service Mapping discovers an Active Directory Forest CI, it processes it using identifiers and recognizes it as an updated version of the Active Directory Forest CI that exists in the system, not a new Active Directory Forest CI. Unlike with regular CI types, identifiers for new endpoint CI types are created automatically.
  • CI type hierarchy. CMDB stores CI class in the form of a hierarchy where some CI classes are parents to other CI classes, who automatically derive their parent's attributes in addition to attributes you configure specifically for child CI classes. CI class hierarchy is used widely for configuring CI behavior, relationships, and display. Create standard entry points as child CIs for the endpoint CI type, which creates an extension for the cmdb_ci_endpoint table. For entry points of inclusion type create child CIs for the inclusion endpoint CI type extending the cmdb_ci_endpoint_inclusion table. In an inclusion, a server hosts applications that are treated as independent objects.


  1. Navigate to Configuration > CI Class Manager.
  2. To create a standard entry point, right-click Endpoint from the Class Hierarchy pane and select Add Child Class.
  3. To create an entry point of the inclusion type, right-click Inclusion Endpoint from the Class Hierarchy pane and select Extend.
  4. Create an entry point type using the following parameters.
    See Create a table.
    Table 1. New table form
    Field Description
    Label Entry point type name. For example, HTTP entry point.
    Name The table name. For example, cmdb_ci_endpoint_http.
    Extends table The table name of the parent CI type is automatically filled by the system:
    • cmdb_ci_endpoint - for entry points
    • cmdb_ci_endpoint_inclusion - for entry points of the inclusion type
  5. Add entry point attributes on the Columns tab at the bottom of the page.
    By default the new entry point derives attributes from its parent CI, but you can modify the attributes as necessary.
  6. Click Submit.