Remap tag-based application services to reflect tag changes

Recreate tag-based services if the way your organization uses tags have changed or after modifying tag definitions for tag-based service families.

Avant de commencer

If necessary, modify the tag definitions for the relevant tag-based service family.

Role required: service_mapping_admin

Pourquoi et quand exécuter cette tâche

Remap existing tag-based services after you have manually modified tag definitions. If your organization uses new tag keys or tag values, you may also want to remap existing services. In both cases, Service Mapping does not automatically update existing services to reflect tag changes.

Procédure

1. Navigate to Service Mapping > Administration > Tag-based Service Families.
2. Select the tag-based service family for which tag definitions have changed.
3. Under Related Links, click Manually update candidates to generate new service candidates using the modified tag definitions.
4. In the Service candidate window, review the suggested service candidates and select the ones that you want to map.
   If there are no service candidates, ensure that you selected the tag values that exist in the Key Value [cmdb_key_value] table.
5. Click Map selected.
   Service Mapping creates application services based on the candidates you selected.
6. Under Mapped services, review the newly created services to ensure that the result is as you expected.
   If Service Mapping offers to view the CI list instead of a map for an application service, this service is too large. Fine-tune it as described in modify the tag categories.

Résultats

You have mapped the application service based on the latest tag definitions.

Figure 1. Remapped tab-based application service

Que faire ensuite

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 the service is too large, perform the following actions:

• Modify tag definitions used for mapping to make sure Service Mapping includes only relevant CIs in the service instance.
• If necessary, Tag-based discovery configuration to change which CIs Service Mapping includes in tag-based service instances.