
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on
12-19-2022
05:06 PM
- edited on
02-19-2025
07:23 AM
by
Steph Morillo
When planning a journey, think about more than just the destination. This advice is especially true when your organization embarks on a journey to "Service Aware CMDB" or "Predictable AIOps."
You should also consider the approach, resources, and input you need from various application, service, and CI owners. By planning these details, you can ensure that your journey is smooth, efficient, and successful.
We will start with an assumption that your CMDB is healthy. I like ensuring my house is clean before heading out to my favorite destination! Please make sure you are using the right discovery method and how frequently you are discovering the CIs, and in complex environments, you should implement and govern the use of tags on your cloud resources.
Here is a list of the available approaches to mapping Services to your infrastructure configuration items.
- Dynamic CI Groups – used to map small application services, uses CIs that are easily grouped using created list filters or CMDB queries. A simple license server, for example. There are limitations to the number of CIs in an application service that a Dynamic CI group populates. This method does not require an ITOM Visibility license.
- Manual mapping – best fit for mainframes or small application services that do not change much and have high availability. This mapping can be done within the CSDM Menu>Manage Technical Services>Application Services module to ensure you use the in-platform relationships. If you create a manual mapping and later decide to use a more automated approach, you may have duplicate relationships if you do not first delete the manual relationships. This method does not require an ITOM Visibility license.
- Tag-based mapping – is great for cloud-native, hybrid environments. Tags identify critical applications, microservices, and cloud resources without needing credentials, elevated rights, and MID Servers or firewall openings. You should implement and govern the use of tags on your cloud resources.
- Automated Service Suggestions **New** - Create application services to CI mappings quickly based on service suggestions using machine learning. Use Service Mapping Plus, which is available through store download. Time to value. You don't need to figure out the entry points. If you have already created an Application Service using the CSDM menu or import, this process will create another Application Service of the same name or conflict.
- Top-Down mapping and Connection Suggestions – This is to get highly detailed surgical maps that use patterns and connection suggestions. This approach is the most granular of the approaches. It is recommended for mission-critical application services for on-premises and legacy applications. Top-down uses connection suggestions and still requires starting with an entry point. This approach is like taking the train or bus, you will see a lot of detail, but it will take longer to get there.
You may need to take several different approaches. You can use the guide I've included below to understand the approach and value based on the type of application services you have in your organization. Dynamic CI groups, Manual mapping, and tag-based mapping provide quick visualization and less detailed maps and may require human updates. Use the top-down pattern and connection suggestion-based mapping approach for higher effort for visualization and detailed maps, but know it takes longer to value.
Approach Considerations
(image from Now Create Service Mapping Workshop presentation)
Find out more and click on the links below:
Now Create implementation guidance
**NEW** Automated Service Suggestions
- 5,726 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
@Mary Vanatta1 Thanks for sharing this.
Can you please also share some guidance on following areas
1. API methods.
2. Non DC or cloud native application services such as the ones that existing in Teleco industry, those are not application services but we would need to create them as app services in order for OOB impact analysis to work.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi ,
Can you please share your exp. with ML Based Mapping for Server based applications ( NO URL entry point).How is this approach goes on ?
Appreciate your response .
Thanks
Jyothi

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Please check out the Service Mapping Workshop deck in Now Create. It covers the "Automated Service Suggestions" the ML based way to map services. Also the video above covers that as well. Automated Service Suggestions
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Can you please share more details about manual service mapping? like process, pre-req etc.

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Have you checked Product documentation and the Now Create content?
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello @Mary Vanatta1 ,
Yes, i have checked the documentation but no detailed information is available.
They have just mentioned 2 lines.

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
1. Manual is for stable, low change environments like mainframe. It is unstainable for critical applications. We recommend to use Dynamic CI Groups where possible. Also if the Product Service Mapping is purchased, the manual mappings will be duplicative and need to be removed.
2. In Now Create, Service Mapping Workshop deck starting with Slide 34 we over go how to create the Application Service record using the CSDM menu (Slide 70). Slide 71 covers the population method (manual, dynamic, tags etc.) Because we recommend Dynamic Method we cover those steps in Slide 72-79 with screenshots. Manual mapping is covered in Slides 80, additionally it is truly very simple to manual map. Go to the Application Service in the "CSDM Menu" in the navigational filter. Add the Application Service, and select Manual for the Population method. A choice of CIs can be selected. Just select the servers at bare miniunum. If you are using Discovery, it will add the application dependency mapping.

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Here is the product documentation: https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/service-mappin...
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thank you so much for help !
We have integrated the Rapid7 and Intune to get the CIs in CMDB, we have not used traditional port scanning discovery. Whatever CIs we have that are getting from integrations. Now, we have to create a service maps for application services. Hence, we decide to do the manual service mapping.
What you will suggest on this ?
Also, Please correct me if I am wrong, so in manual type of service mapping we have to just add the CIs as per hierachy of application? Like LB > Web Servers > Application Servers > Middlewire > Databases.
Means entry point will be LB and then all of remaining. Need to connect CIs like this ?