Convert business services to application services
-
- UpdatedJan 30, 2025
- 6 minutes to read
- Yokohama
- Now Platform Capabilities
Unify the way you manage services in the organization by converting manually created records in the Service [cmdb_ci_service] table into application services. Conversion lets you streamline the different types of services in your organization, leverage ITOM Visibility capabilities, and align with the Common Service Data Model (CSDM). The conversion is irreversible: You can't transform application services back into business services.
- Viewing service maps and change history of services.
- Easily seeing the service context by providing a flat list of all CIs in the application service.
- Monitoring service health. If Event Management is deployed, you can monitor service performance and identify health issues for application services.
- In Change Management, the list of impacted services on a change request form is more accurate because the list includes only application services.
- Applying Customer Service Management tools to open and manage cases at the service level.
Discovery doesn't run on converted application services, because converted services are manual. However, if after the conversion you add Discoverable by Service Mapping entry points to the application service, then Service Mapping starts discovering such this application service.
Choosing between application services of the manually created and dynamic type
You can convert business services into application services of the manually created type or of the dynamic type. You can edit manually created application services by adding or removing CIs at any time. The system does not update manually created services automatically. If there are changes to CIs making up a manually created application service, the service does not automatically reflect it.
Dynamic services are updated automatically to reflect any change to CI relationships stored in the CMDB CI Relationship [cmdb_rel_ci] table. When you add a relationship to a CI that is contained in a dynamic service, then that service automatically updates to reflect the addition of the relationship and the associated new CI. In a similar manner, a dynamic service automatically updates upon the removal of a relationship and its associated CI from a CI within the service.
To learn more about different types of application services, see application services.
Conversion process
- The service record is moved from the Service [cmdb_ci_service] table into the Mapped Application Service [cmdb_ci_service_discovered] table by changing the record class.
- The service instance is set with all the original business service attributes such as name, owner, and operational status.
- The system adds related items from the business service to the converted service instance, up to the specified level.
- The system queries the CMDB for the latest CI changes.
- Event Management, if activated, applies CI impact rules to CIs that are associated with alerts and that are part of the service instance. Event Management deploys CI impact rules for alert monitoring.
- You can edit a converted application service of the manually created type by navigating to Converted Business Service. For more information about
editing application services, see Create an application service.Note: You can't edit a dynamic application service by adding or removing CIs from it. The system automatically modifies an application service of the dynamic type when you modify relevant relationships for CIs that are part of that application service.
. Then select a converted application service. The service population method for a converted application service, is set to
Non-compliant CIs
- cmdb_ci_file_system
- cmdb_ci_network_adapter
- cmdb_ci_storage_device
- cmdb_ci_disk_partition
- cmdb_ci_memory_module
- cmdb_ci_ip_address
- cmdb_ci_storage_pool_member
- dscy_net_base
- cmdb_ci_storage_export
- cmdb_ci_endpoint
- cmdb_ci_translation_rule
- cmdb_ci_qualifier
- cmdb_ci_application_cluster
- cmdb_ci_config_file
Domain separation
In environments with domain separation, only CIs belonging to the same domain as the service instance are added to the service instance. If there is a domain hierarchy, CIs must belong to the same child domain as the service instance.
Convert business services to application services in bulk
Convert a subset of business services to application services, in bulk and automatically rather than one at a time. Individually select the business services for the conversion, and then convert them into application services.
Before you begin
About this task
Use bulk conversion to convert legacy business services to application services. For the bulk conversion, individually select the business services from the Services list view, typically up to 100 business services in a single conversion. You can create multiple bulk conversion records, each with a different set of business services. However, do not include a business service in more than one bulk conversion.
Procedure
What to do next
- Check the status of a conversion: On the Bulk Convert Services form, scroll to the Bulk Convert Services Entries section to see the status (such as Ready or Completed) of a conversion.
- Track the progress of a conversion as it runs: In the navigation filter, enter cmdb_convert_bulk_services.list and press the Enter key to see the list of conversions, and their progress.
- (Optional) On a change request form, view affected dynamic services. For
example, after you add an affected CI that is associated with a dynamic
service:
- Navigate to .
- Select a new change request to add affected CIs to.
- On the Change Request form, scroll to the Related Links section.
- Click the Affected CIs tab and then click Add to add an affected CI to the change request.
- Open the form context menu and select Refresh Impacted Services.
- Click the Impacted Services/CIs tab to see any dynamic services that are associated with the affected CI and that are impacted by the change request.
Convert an individual business service to an application service
Manually convert a specific business service to an application service.
Before you begin
- Make sure that all CIs and CI relations are relevant for the future application service. If necessary, change the CI relations in the CMDB.
- Make sure that the original business service doesn't contain more than 5000 CI relations. Application services that contain more than 5000 CI relations cause mapping and monitoring performance issues.
- Decide how many levels of CI relations you are going to use during conversion.
Procedure
Result
What to do next
Open the map for the newly converted service instances.
- 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 the service is too large, perform the following actions:
- Review the converted service instance to identify CI relations irrelevant or redundant for this service. Remove such CI relations in the CMDB.
- Decide how many levels of related CIs you must include into this service instance. If necessary, change the number of levels used in conversion to reduce the service size.
On this page
Related Content
- Application services
Understand application services, learn about different application service types and how multiple ServiceNow business units and products use them.