---
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


---

# Configure Agent Client Collector for use with Service Mapping

# Configure
Agent Client Collector for use with Service Mapping {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 3, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure Agent Client Collector to discover and map application
services without having to configure credentials for the MID Server.

## Before you begin

Confirm that you have installed both Agent Client Collector for Visibility Content version 3.5.0 and the Kubernetes Visibility Agent (KVA) from the ServiceNow® Store.

Ensure that Agent Client Collector has been configured. For more information, see [Application patterns for the Agent Client Collector](https://servicenow-prod.fluidtopics.net/ga~C7dH8i6LRLDLN3_CjrQ "Application patterns gather details on the applications that run on the Agent Client Collector (ACC) host. Application patterns are supported only for servers, and are triggered after the Agent Client Collector host Discovery is complete.").  
Verify that agents have the necessary privileges to execute the required application pattern commands for successful completion of top-down discovery. For more information, see [Privileged SSH commands for probe-based discovery](https://servicenow-prod.fluidtopics.net/9zRLtV44HUO12jMk5mJ1Rw "These tables display the SSH commands run by Discovery probes during horizontal discovery. These SSH commands require elevated privileges to run.") and [Non-privileged SSH commands during probe-based discovery](https://servicenow-prod.fluidtopics.net/2r4DfPWh_GyitJ0xhfbELg "These tables display the SSH commands run by Discovery probes on target devices during horizontal discovery. These SSH commands don’t require elevated privileges to run.").  
Important:  
This configuration requires a MID Server that is up and running to work correctly. Service Mapping selects the MID Server to which the target agent connects, in order to run commands through the agent.

Role required: service_mapping_admin

## About this task

Agent Client Collector enables the discovery and mapping of application services without requiring you to set up credentials for the MID Server. You can deploy both top-down and machine learning-based Service Mapping and benefit from a simplified approach to mapping application services.

## Procedure

1. Enter <kbd class="ph userinput">sys_properties.list</kbd> in the navigation filter.
2. In the System Properties \[sys_properties\] table, search for the sa.topdown.mapping_with_acc_mode property.
3. Set the property to configure Agent Client Collector for Service Mapping and define the MID Server selection mode for top-down discovery.
   1. Confirm that the Type field value is set to integer.
   2. Determine how top-down discovery should run by setting the Value field value.  
      Possible values are:
      * <kbd class="ph userinput">0</kbd> (the default) - Top-down discovery runs using the MID Server exclusively.
      * <kbd class="ph userinput">1</kbd> - Top-down discovery initially attempts to run using Agent Client Collector. If no agent is available, then it defaults to using the MID Server.
      * <kbd class="ph userinput">2</kbd> - Top-down discovery runs using Agent Client Collector exclusively. If unsuccessful, the process terminates.
      {#configure-acc-for-service-mapping__ul_ww4_gfm_vbc}
   {#configure-acc-for-service-mapping__substeps_eg1_v2m_vbc}