---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# Map a single application service using classic Service Mapping
# Map a single application service using classic
Service Mapping {#ariaid-title1}
* 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
* [Verify that Service Mapping is set up properly](https://servicenow-prod.fluidtopics.net/9lEex6WJ4vU_VRL6xY04Tg "Before you start mapping application services, verify that you configured MID Servers to discover application services and provided all the necessary host and application credentials.").
* If the service instance relies on PaaS supported by Microsoft Azure or Amazon Web Services, [discover datacenters](https://servicenow-prod.fluidtopics.net/mvUB4lhtHGGrh93mggIcpw#select-cloud-provider-datacenter "Cloud Discovery displays the list of available datacenters when you validate the service account. Specify which datacenters you want to discover through the schedule.") and then create [horizontal discovery schedules](https://servicenow-prod.fluidtopics.net/mvUB4lhtHGGrh93mggIcpw#create-cloud-schedule "The final phase in the Discovery Manager wizard creates the schedule that triggers discovery of the cloud resources.") on the cloud service account.
{#t_DefineNewBusinessService__ul_ob2_hnb_ls}
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.{#t_DefineNewBusinessService__conref_EPExample_ph}
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.{#t_DefineNewBusinessService__AfterInitDiscoveryScheduleShort}
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](https://www.servicenow.com/docs/access?context=create-it-services&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
.
## Procedure
1. Navigate to AllService MappingHome.
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:
{#t_DefineNewBusinessService__table_wvm_h2p_ls__entry__2}
| 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. |
[ ]
{#t_DefineNewBusinessService__table_wvm_h2p_ls}
5. If you do not know the entry points, request them from the service instance owner, as described in [Request entry point information for service mapping](https://servicenow-prod.fluidtopics.net/iSK646~o0jDaVoFoo7LD7A "The most important attribute you must know and configure to discover an service instance is an entry point. If you do not know the entry points for the service instance, request this information from the service instance owner.").
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](https://servicenow-prod.fluidtopics.net/I8a_fpSTDrjMoM5zjF3YIw "An entry point is a point where clients access a service instance. Service Mapping starts the mapping process for every application service from the entry point you define for it. 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.").
4. Configure attributes for the entry point as described in [Entry point attributes](https://servicenow-prod.fluidtopics.net/Nfjn4iROeQ3tjjtVtxSrbQ "Service Mapping comes with a wide range of preconfigured entry point types that cover many commonly used applications. Check attribute definitions to correctly add entry points to your application services.").
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](https://servicenow-prod.fluidtopics.net/8sD~6Bc3quESSBMeonfe4g#t_DefineNewBusinessService__step_defineentrypoint).
{#t_DefineNewBusinessService__substeps_ing_swb_ls} {#t_DefineNewBusinessService__step_defineentrypoint}
{#t_DefineNewBusinessService__step_defineentrypoint}
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.
{#t_DefineNewBusinessService__table_ks2_1kr_31b__entry__2}
| 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 \*\ might take a long time and return a large data set. |
[ ]
{#t_DefineNewBusinessService__table_ks2_1kr_31b} The CI type list includes only allowed CI types. For example, you cannot add an application cluster.
3. Click Submit.
{#t_DefineNewBusinessService__substeps_rgl_hbp_mcb}
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](https://servicenow-prod.fluidtopics.net/Kw88zdxkkI61hdgabLIlCw "Service Mapping does not offer semi-automated resolution options for errors that require advanced resolution. Fix such errors using symptoms and 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.
{#t_DefineNewBusinessService__ul_htr_hr5_34b}
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](https://servicenow-prod.fluidtopics.net/8_AlRz5snn~YqOp5~kuhTw "You can remove a branch of a service and place it into another application service, either new or existing. Transfer map segments to split large services or when you want to organize services differently from the initial mapping result.").
{#t_DefineNewBusinessService__ul_dq4_rd2_f4b}
* Send application services discovered without errors to their respective owners for approval. For more information, see [Send application service maps for review](https://servicenow-prod.fluidtopics.net/aStpPAiHMPw9hVULLwz~sA "After you map an application service, send it to the application service owner for review to make sure that the map is accurate.").
{#t_DefineNewBusinessService__ul_jnx_jwd_j1b}
* **[Request entry point information for service mapping](https://servicenow-prod.fluidtopics.net/iSK646~o0jDaVoFoo7LD7A)**
The most important attribute you must know and configure to discover an service instance is an entry point. If you do not know the entry points for the service instance, request this information from the service instance owner.
* **[Provide entry points for mapping an application service](https://servicenow-prod.fluidtopics.net/9IQ3nSWElsdoVlxdcdPlEg)**
As an application service owner you may receive a request for information about entry points in an email notification. Provide information about entry points to enable administrators to start discovery of an application service.
* **[Manage CI connections for a single service using suggestions](https://servicenow-prod.fluidtopics.net/u~Zf40ssZOZ1CiZacOJOVQ)**
If discovery based on Predictive Intelligence is enabled, newly mapped application services include only configuration items (CIs) and CI connections added using discovery patterns. Use the suggestions for CI connections, generated by Service Mapping, to complete the application service.
* **[Add CIs to a specific application service using connection rules](https://servicenow-prod.fluidtopics.net/vmfqwwskxZhbyrjUiIDLyg)**
Create rules for automatically adding traffic-based connections and the CIs they lead to in discovered service instances. Add CIs to specific application services using connection rules.
* **[Enable traffic-based discovery for an application service](https://servicenow-prod.fluidtopics.net/7aKT0~d8tUdI~Sa3cmy9zw)**
Make Service Mapping use traffic-based connections to discover CIs making up an application service.
* **[Mapping application services containing Citrix XenApp and Presentation Server](https://servicenow-prod.fluidtopics.net/h27wMMajJ9FPfCw6hcGoeQ#mapping-services-citrix)**
Service Mapping can discover application services containing Citrix XenApp, Presentation Server, and Citrix Usage Collector.
* **[Application services with Microsoft Exchange Server](https://servicenow-prod.fluidtopics.net/6geBl31PkjCpUsRJNExPYg#mapping-service-exchange)**
Service Mapping can discover service instances containing a Microsoft Exchange Server and the Exchange Server components.
* **[Tibco BusinessWorks and EMS discovery](https://servicenow-prod.fluidtopics.net/fb3yjm0dXzaqJgCeLyxn~w#mapping-services-tibco)**
Discovery can find Tibco ActiveMatrix BusinessWorks and Enterprise Message Service (EMS). Service Mapping can discover application services containing Tibco BusinessWorks, Enterprise Message Service (EMS), and their components.
* **[Application services with Oracle GlassFish Servers](https://servicenow-prod.fluidtopics.net/UK41gJe7ufXxlmd7W9xUyA#mapping-services-glassfish)**
Service Mapping can discover application services containing Oracle GlassFish Servers.
* **[Mapping application services containing Oracle Tuxedo platform](https://servicenow-prod.fluidtopics.net/Xcq4fYLw3QESTyqHIaru3g#mapping-services-tuxedo)**
Service Mapping can discover application services containing Oracle Tuxedo platform and its components.
**Related concepts**
* [Review and approval of application service maps](https://servicenow-prod.fluidtopics.net/BjGtOsTta_Wo~8ykmxZngQ "After the Service Mapping administrator maps IT services and fixes errors in them, the administrator and the owner collaborate to review and approve the service maps. The review and approval process is available only for discovered and manually created service instances.")
* [Application service completion](https://servicenow-prod.fluidtopics.net/oTiVA8bO~~ejaFfgU_iy9w "After an application service is reviewed and approved, you can define attributes that enhance its discovery, reflect its importance, and control access to it.")
* [Application service analysis and maintenance using classic Service Mapping](https://servicenow-prod.fluidtopics.net/kktVI~k2uB35tKBH_EqH8Q "Service Mapping creates maps to help you see the architecture and organization of application services. These maps are useful for planning change or migration, as well as analyzing the continuity and availability of services.")
**Related tasks**
* [Map multiple application services suggested by classic Service Mapping](https://servicenow-prod.fluidtopics.net/qFTEgnBYmx4N~e7Wi0hmtA "You can map multiple application services identified and suggested by Service Mapping in a single operation. This method suits your organization if you do not have much information about application services.")
* [Map application services using tags with classic Service Mapping](https://servicenow-prod.fluidtopics.net/LP1_hSxqw0iYBN~sMLLWGQ "Use tags that help categorize and organize configuration items (CIs) in your organization to map application services. Tag-based mapping doesn't require configuring credentials or providing users with elevated rights.")
* [Map multiple application services from a CSV file using classic Service Mapping](https://servicenow-prod.fluidtopics.net/0ElnFoss5kGCl7N1cGU5oA "This method suits you if your organization has performed cross-organization mapping and analysis and collected some information about planned service instances. If so, you can organize the collected information in a specific order and save it as a CSV file. Service Mapping extracts information from this file and creates potential service instances referred to as service candidates.")
* [Fix application service errors in bulk](https://servicenow-prod.fluidtopics.net/AQZZC7bwEONc9WvfM9~Maw "Service Mapping classifies errors by their root cause, for example, missing credentials or task timeout. For a fast and efficient process, fix errors belonging to the same category in bulk.")
* [Fix errors in individual application service maps](https://servicenow-prod.fluidtopics.net/mCyIAds3bqivvs99ielgpg "You can address discovery issues in each application service map individually.")
* [Fine-tune application services to implement owner requests](https://servicenow-prod.fluidtopics.net/iBl4ZwvZMr6J_fUdsUa1Nw "As an administrator, you tweak and fine-tune maps based on comments from the application service owner.")
*[\>]: and then