Manually update an application service with changes from the CMDB

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
  • Ensure that an application service is up-to-date and reflects all the latest changes to its configuration items (CIs). Regularly update application services to reflect any changes to CIs and their relationships in the CMDB.

    Before you begin

    Role required: app_service_admin

    About this task

    There is no mechanism or an API that automatically updates application services that were created manually. Also, you may need to manually update application services discovered by Service Mapping, if they contain manually added CIs. You can only update application services which contain manually created entry points and which are not discovered by Service Mapping.

    An example of a change is deleting CIs from the CMDB or connecting two CIs one of which is part of an application service. In the first case, your application service may show a CI that no longer exists. In the second case, on the contrary, the application service omits a CI.

    An update might involve adding CIs of the following CI types, which cannot be added to an application service:
    • 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
    If necessary, you can prevent CIs of other CI types from being added to application services by modifying the Manual CI Inclusions / Exclusions [svc_manual_ci_exclusions_inclusions.list] table.

    Also, the system can connect a CI from the application service only to actual CIs that exist in the CMDB, not a visualization of other items on the map like clusters or boundaries.

    The maximum number of CI connections added to application services during this operation is controlled by the sa.service.max_ci_service_population property. By default, the value is 1,000 (one thousand connections). Increasing the number of CI connections may cause performance issues. To adjust the maximum number of added CI connections, add the sa.service.max_ci_service_population property, as described in Add a system property.

    In environments with domain separation, only CIs belonging to the same domain as the application service are added into the application service. If there is a domain hierarchy, CIs must belong to the same child domain.

    You can also update application services by using APIs.

    Procedure

    1. Navigate to All > CSDM > Manage Technical Services > Application Service.
    2. On the Application Services list view, select the application service that you want to update.
    3. Click Advanced and then click Advanced Configurations.
    4. On the Additional Info page, click the Update with changes from CMDB related link.
    5. Select a number in the Up to list to limit the number of levels of related items to be updated.
      If the specified number is higher than the number of levels of related items that already exist in the application service, then the system adds the missing CIs and their connections.
      Warning:
      Specifying a lower number than the number of levels that already exist in the application service, does not result in the removal of CIs from the application service.
    6. Click OK.

    Result

    • The system updates the application service with the changes from the CMDB and shows them on the map.
    • After the update process is complete, the application service form opens.