Map a single application service using classic Service Mapping

  • Release version: Yokohama
  • Updated January 30, 2025
  • 5 minutes to read

    • In addition to mapping application services in bulk, you can map individual, single application services by defining attributes for each application service. Use this mapping method if you already know or are planning to find out application service details. You must have Service Mapping enabled to map or review application services.

    Before you begin

    Role required: service_mapping_admin

    About this task

    You can map single application services in addition to bulk mapping, which is effective at mapping multiple application services, but is not precise. You may need to individually map application services omitted during bulk mapping.

    The most important attribute you must know and configure to discover an application service is an entry point.

    An entry point is a point where clients access a service instance. Usually, it is either a URL or a combination of the IP address and port. Service Mapping starts the mapping process from this point. For example, to map your electronic mailing service instance, define an IP address or host name of the email server as an entry point.

    Entry points vary depending on the nature of the service instance. Service Mapping comes with a wide range of preconfigured entry point types that cover many commonly used applications.

    In addition to entry points that Service Mapping can discover, you may add entry points that Service Mapping cannot discover. You may want to add such an entry point as an indication that your service instance contains a device or application.

    Also, you must define an owner for your service instance. The service instance owner is a user who is familiar with the infrastructure and applications making up the service. This user is the service instance SME who provides information necessary for a successful creation of a service instance. After a service is mapped, this user reviews the results, and either approves it or suggests changes.

    After Service Mapping discovers configuration items (CIs) belonging to your service instance for the first time, it then rediscovers CIs to find changes and updates. Create or modify discovery schedules to control how often Service Mapping rediscovers services or CIs.

    All service instances, both manually created and discovered by Service Mapping, are stored in the Mapped Service Instance [cmdb_ci_service_discovered] table.

    You can also create a single application service manually using the flow based on Common Service Data Model. The Common Service Data Model (CSDM) helps you streamline service types and service offerings. You can add relationships between application services and other service-related objects in the CSDM: Business Application, Technical Service Offerings, or Business Service Offerings. For more information, see Create application services .

    Procedure

    1. Navigate to All > Service Mapping > Home.
      The Home page displays only information on service instances that Service Mapping can discover or already discovered. The Home page does not display information on service instances that are created manually or using the API.
    2. Click Additional options under the Map tile.
    3. Click Define A Single Service Map.
    4. Define the basic service instance attributes:
      Field Description
      Name Enter a unique application service name which is not in use by any other type of application service. Use self-explanatory names such asmailing service or printing service.
      Owner Select an owner who is responsible for this service instance in the organization.

      If the owner name does not appear in the list, create a user for this person and assign the sm_app_owner role to this user. Alternatively, choose a user with the service_mapping_admin role.
    5. If you do not know the entry points, request them from the service instance owner, as described in Request information about entry points for application services.
    6. To add an entry point that Service Mapping can discover, perform these steps.
      1. Click Discoverable by Service Mapping.
        The page offers tiles for applications most commonly used for entry points.
      2. Click the tile matching the application to which the entry point belongs.

        For example, Web Application if you create an service instance with a web interface. If the tiles do not contain the necessary application, click See More Types to choose from a list of all preconfigured entry point types.

        Important:
        Do not use central IT components like Microsoft MQ or Microsoft Active Directory as entry points. Using such entry points creates large services, which cause performance issues during mapping and monitoring.
      3. Optional: If the required entry point type does not appear in the list, you may need to create it as described in Create entry point types for Service Mapping.
      4. Configure attributes for the entry point as described in Entry point attributes.
        Entry point attributes depend on the type you select.
      5. Click Add.
        The entry point is added under Entry Points.
      6. To add more entry points, click Add Entry Point and repeat step 6.
    7. Optional: To add a static entry point that Service Mapping cannot discover, perform these steps.
      1. Click Manually created.
      2. Define the CI to serve as the entry point.
        Field Description
        CI Type Select the CI type (CI class) for the CI you are adding. Every CI belongs to a CI type which contains a set of attributes configured for this kind of CI, for example, cmdb_ci_appl for applications.
        CI Name Select the CI from the list of CIs of the selected CI type.
        Note:
        To eliminate the possibility of delayed results when searching for a specific CI, make your search as specific as possible. A search with *<name> might take a long time and return a large data set.
        The CI type list includes only allowed CI types. For example, you cannot add an application cluster.
      3. Click Submit.
    8. To save attributes you have defined up until this moment and carry on configuring attributes for this service instance, click Save or Update.
      Service Mapping saves the new service instance in the Mapped Application Service [cmdb_ci_service_discovered] table. It also starts the discovery process in the background.
    9. To save definitions, discover this service instance, and navigate to the map for this service instance, click View Map.
      Service Mapping starts the discovery process. The map for this service instance page opens and displays the mapping in progress. The service instance status changes to In Progress.

    What to do next

    • If Service Mapping discovers the service instance with errors, fix errors in individual application services using discovery messages.
    • Make sure that the service instances aren't too large:
      • Service Mapping doesn't offer to view CI list instead of a map for a service instance.
      • There is no discovery message indicating that the service instance is too large: The map does not display the entire service, because it is too large. The number of CI connections exceeded the allowed maximum.
      If some application services are too large, resolve the service size issue:
      • If you use customized discovery patterns and mapping results in very large service instances, modify the patterns so that they don't map irrelevant CIs.
      • Split the service into smaller services.
    • Send application services discovered without errors to their respective owners for approval. For more information, see Send application service maps for review.