| \n\nRole title \\[name\\]\n\n | \n\nDescription\n\n | \n\nContains roles\n\n |
|---|---|---|
| \n\n\\[app\\_service\\_admin\\]\n\n | \n\nCreates and modifies service instances, creates service groups, views, and edits service instance maps.\n\n | \n\n\\[itil\\]\n\n |
| \n\n\\[app\\_service\\_user\\]\n\n | \n\nViews maps for operational service instances and retrieves service content using the getContent - GET REST API. The itil role that serves as the basic helpdesk technician role contains the app\\_service\\_user role.\n\n | \n\n\\[cmdb\\_read\\]\n\n |
| \n\n\\[itom\\_admin\\]\n\n | \n\nConfigure IT Operations Management applications using the ITOM Guided Setup. **Note:** The ITOM Guided Setup does not cover Service Mapping.\n\n | \n\n\\[sn\\_bm\\_client.benchmark\\_data\\_viewer\\]\\[sm\\_itom\\_license.reader\\]\n\n |
| \n\n\\[sam\\_core\\_admin\\]\n\n | \n\nAn internal role.\n\n | \n\n\\[sam\\_core\\_user\\]\n\n |
| \n\n\\[sam\\_core\\_user\\]\n\n | \n\nAn internal role.\n\n | \n\n\\[itil\\]\n\n |
| \n\n\\[service\\_mapping\\_admin\\]\n\n | \n\nSets up the Service Mapping application. Maps, fixes, and maintains service instances. Also performs advanced configuration and customization of the product. Assign this role to application administrators.\n\n | \n\n- \\[app\\_service\\_admin\\]\n- \\[app\\_service\\_owner\\]\n- \\[discovery\\_admin\\]\n- \\[itil\\_admin\\]\n- \\[itom\\_admin\\]\n- \\[sam\\_core\\_admin\\]\n- \\[personalize\\_dictionary\\]\n- \\[pd\\_admin\\]\n- \\[pd\\_user\\]\n- \\[service\\_mapping\\_user\\]\n\n |
| \n\n\\[sm\\_app\\_owner\\]\n\n | \n\nProvides information necessary for successful mapping of a service instance. Once a service is mapped, this user reviews the results and either approves it or suggests changes. Assign the sm\\_app\\_owner role to users who own service instances and are familiar with the infrastructure and applications that make up the services.\n\n | \n\n\\[service\\_mapping\\_user\\]\n\n |
| \n\n\\[sm\\_itom\\_license.reader\\]\n\n | \n\nViews subscription information and statistics for IT Operations Management applications.\n\n | \n\n\\[cmdb\\_read\\]\n\n |
| \n\n\\[service\\_mapping\\_user\\]\n\n | \n\nViews maps for operational service instances to plan change or migration, as well as analyze the continuity and availability of services. Assign this role to application users.\n\n | \n\n- \\[sam\\_core\\_user.service\\_mapping\\_user\\]\n- \\[itil.service\\_mapping\\_user\\]\n\n |
| \n\n\\[sn\\_svc\\_err.admin\\]\n\n | \n\nFixes discovery errors in bulk using the error framework feature in Service Mapping and Discovery.\n\n | \n\n\\[itil\\]\n\n |
| \n\n\\[pd\\_admin\\]\n\n | \n\nCreates new and modifies existing patterns, which Service Mapping and Discovery use for performing horizontal and top-down discovery.\n\n | \n\n\\[pd\\_user\\]\n\n |
| \n\nScheduled job\n\n | \n\nDescription\n\n |
|---|---|
| \n\nDeferred Discovery Cleanup \\[sysauto\\_script\\_ba4bee737f0022008f1c3b19befa9108\\]\n\n | \n\nRuns every minute. Detects and cancels discovery schedules on TCP connections that are not in the active state anymore \\(5 minutes of no activity\\).\n\n |
| \n\nUpdate Query Based Services \\[sysauto\\_script\\_08745913f31131002e6bae4716612bf1\\]\n\n | \n\nRuns every 10 minutes. Updates views for all defined technical services.\n\n |
| \n\nUpdate App Service Status \\[sysauto\\_script\\_5641702ac32102003e76741e81d3ae9e\\]\n\n | \n\nRuns every minute. Updates the discovery status attribute for application services. The discovery status is calculated as the overall status over all endpoints that an service instance contains.\n\n |
| \n\nFlow Discovery Scheduler \\[sysauto\\_script\\_74c676f0dbb0220060ff742eaf9619f2\\]\n\n | \n\nRuns every 10 minutes. Triggers the network flow discovery and writes the data into the \\[sa\\_flow\\_connector\\] table. This scheduled job is disabled by default. Enable this scheduled job to discover CIs using Netflow as described in [Data collection and discovery using Netflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/data-collection-netflow-mapping.md).\n\n |
| \n\nGenerate entry point candidates from netflow and netstat data \\[sysauto\\_script\\_b0b95067c3d0030039a3553a81d3aeb5\\]\n\n | \n\nRuns daily. Scans the TCP Connection \\[cmdb\\_tcp\\] table and uses this data to generate entry points and store them in the Candidate Entry Points \\[sa\\_cand\\_entry\\_point\\] table. This scheduled job supports generating entry points necessary for [mapping multiple application services \\(in bulk\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/map-business-services-in-bulk.md). This scheduled job is enabled by default.\n\n |
| \n\nSave thread dumps \\[sysauto\\_script\\_a49cd030c302020039a3553a81d3aefb\\]\n\n | \n\nNot active by default. When enabled, collects thread dumps and stores the data in the \\[sys\\_thread\\_dump\\] table.\n\n |
| \n\nSlow steps stats persist \\[sysauto\\_script\\_dc0de690c302020039a3553a81d3aee0\\]\n\n | \n\nRuns every minute. Collects data on slow execution of pattern steps and writes this data into the \\[sys\\_step\\_pattern\\] table.\n\n |
| \n\nCalculate number of servers \\[sys\\_trigger\\_db438f407f510200f128134f8dfa91c6\\]\n\n | \n\nRuns every Sunday. Updates the licensing metric with the overall number of discovered servers on instance. This information is used for billing. On domain separated instances, the number is updated for each domain.\n\n |
| \n\nRun DNS Lookup For All Entry Points and Manual Connection Endpoints \\[f178ab457fb213001952baf8befa91d3\\]\n\n | \n\nRuns the DNS lookup probe on all entry points and manual connection endpoints and updates information on their IP addresses in the CMDB. This scheduled job is disabled by default.\n\n |
| \n\n\\[sm dedup tracker for specific discovery sources\\]\n\n | \n\nIn some cases, Service Mapping and third-party discovery or monitoring tools identify the same configuration item \\(CI\\) differently. It results in the CMDB application table containing two records for the same CI. This scheduled job scans the CMDB application tables that contain information about CIs identified as generic applications. If the scheduled job identifies duplicate records based on the CI type and the discovery source, it creates a deduplication task.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_5211e7e1c320220039a3553a81d3aee6\\]\n\n | \n\nCleans the \\[sa\\_flow\\_connection\\] table from records not updated for the last seven days.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_956d498b938503006a7031f6357ffbec\\]\n\n | \n\nCleans the \\[sa\\_performance\\_statistics\\] table from records containing statistics of overall event processing time and created earlier than 30 days ago.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_ce1a978193001200e0e931f6357ffb59\\]\n\n | \n\nCleans the \\[sa\\_performance\\_statistics\\] table from records created earlier than 2 days ago.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_b24d9c30c302020039a3553a81d3ae53\\]\n\n | \n\nCleans the \\[sys\\_thread\\_dump\\] table from records created earlier than 7 days ago.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_cf129ebe7f223200995cbaf8befa916f\\]\n\n | \n\nCleans the \\[sa\\_ml\\_feature\\_data\\] table from records not updated in the last 7 days, and have a special state \\(empty label field\\).\n\n |
| \n\n\\[sys\\_auto\\_flush\\_d2516be1c320220039a3553a81d3ae21\\]\n\n | \n\nCleans the \\[sa\\_flow\\_service\\] table from records not updated in the last 7 days.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_db416be1c320220039a3553a81d3ae1f\\]\n\n | \n\nCleans the \\[sa\\_flow\\_server\\_comm\\] table from records not updated in the last 7 days.\n\n |
| \n\n\\[sys\\_auto\\_flush\\_41d9b007b71310105984eb25de11a96e\\]\n\n | \n\nCleans the Connection Suggestion \\[sa\\_ml\\_connection\\_suggestion\\] table from the old records that match the following conditions: - They weren't updated in the last 7 days.\n- The suggestion record has an active discovered TCP connection \\(the TCP connection record is not absent\\).\n- The record doesn't have a user decision “Add” or “Remove” associated with it.\n\n |
| \n\n \n\n | \n\n \n\n |
| \n\nTable\n\n | \n\nDescription\n\n |
|---|---|
| \n\nPre Service Mapping Task Scripts \\[sa\\_pre\\_task\\_script\\]\n\n | \n\nContains scripts that Service Mapping runs on the instance and collect information that helps identify the relevant pattern for a CI.\n\n |
| \n\nTraffic Based Connection Qualifiers \\[cmdb\\_ci\\_qualifier\\_traffic\\_based\\_connection\\]\n\n | \n\nLegacy content. Not used in the current version.\n\n |
| \n\nDynamic CI Group \\[cmdb\\_ci\\_query\\_based\\_service\\]\n\n | \n\nContains technical services.\n\n |
| \n\nComponents \\[sa\\_bs\\_components\\]\n\n | \n\nContains information on components that are part of the service instance. Customers enter this information manually in the Questionnaire tab of the service instance form.\n\n |
| \n\nCandidate Entry Points \\[sa\\_cand\\_entry\\_point\\]\n\n | \n\nContains information on potential entry points that Service Mapping retrieved from load balancers or traffic-based connections.\n\n |
| \n\nDashboard View \\[sa\\_dashboard\\_view\\]\n\n | \n\nContains configuration that defines which services to display in the Service tree.\n\n |
| \n\nService Discovery Messages \\[sa\\_discovery\\_message\\]\n\n | \n\nContains discovery messages and errors that Service Mapping generates during the discovery process.\n\n |
| \n\nITOM Error task \\[sa\\_error\\_handler\\_task\\]\n\n | \n\nContains information that Service Mapping and Discovery use for error-handling functionality.\n\n |
| \n\nError EP AS Manual EP \\[sa\\_errors\\_as\\_manual\\_ep\\]\n\n | \n\nContains data on errors that customers skip during the following procedure: [Skip errors to continue discovering an application service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/skip-errors-continue-discovery-individual-services.md).\n\n |
| \n\nManual connections \\[sa\\_manual\\_connections\\]\n\n | \n\nContains information on endpoints that customers use while adding manual connections.\n\n |
| \n\nML Feature Data \\[sa\\_ml\\_feature\\_data\\]\n\n | \n\nInternal table.\n\n |
| \n\nML Model \\[sa\\_ml\\_model\\]\n\n | \n\nInternal table\n\n |
| \n\nML Traffic Validation \\[sa\\_ml\\_traffic\\_validation\\]\n\n | \n\nInternal table\n\n |
| \n\nPerformance Statistics \\[sa\\_performance\\_statistics\\]\n\n | \n\nInternal table for storing performance data on impact calculation in Event Management.\n\n |
| \n\nService Maps \\[sa\\_service\\_counters\\]\n\n | \n\nStores data about number of CIs and discovery errors per each discovered service.\n\n |
| \n\nSimulation entry points \\[sa\\_simulation\\_entry\\_points\\]\n\n | \n\nInternal table.\n\n |
| \n\nService Process Tasks \\[service\\_process\\_task\\]\n\n | \n\nStores data requests and review requests for application services.\n\n |
| \n\nSlow Steps \\[sys\\_step\\_pattern\\]\n\n | \n\nStores information about slow execution of pattern steps. This data is used for monitoring and troubleshooting.\n\n |
| \n\nThread dump \\[sys\\_thread\\_dump\\]\n\n | \n\nInternal table for storing performance data used for troubleshooting in Event Management.\n\n |
| \n\nAutomation Error Category \\[automation\\_error\\_category\\]\n\n | \n\nStores all supported categories for errors.\n\n |
| \n\nAutomation Error Categories Statistics \\[automation\\_error\\_category\\_stats\\]\n\n | \n\nStores the latest error statistics on all error categories.\n\n |
| \n\nAutomation Error Code \\[automation\\_error\\_code\\]\n\n | \n\nStores all supported error codes for discovery errors.\n\n |
| \n\nAutomation Error Code Statistics \\[automation\\_error\\_code\\_stats\\]\n\n | \n\nStores the latest error statistics on all error codes.\n\n |
| \n\nAutomation Error Discovery Categories Statistics \\[automation\\_error\\_discovery\\_category\\_stats\\]\n\n | \n\nDeprecated.\n\n |
| \n\nAutomation Error Discovery Code Statistics\\[automation\\_error\\_discovery\\_code\\_stats\\]\n\n | \n\nDeprecated.\n\n |
| \n\nAutomation Error Discovery Message \\[automation\\_error\\_discovery\\_msg\\]\n\n | \n\nStores the latest error messages.\n\n |
| \n\nAutomation error instance category statistics \\[automation\\_error\\_instance\\_category\\_stats\\]\n\n | \n\nStores the latest error statistics on all categories per instance \\(discovery status\\).\n\n |
| \n\nAutomation Error Categories Statistics\\[automation\\_error\\_instance\\_code\\_stats\\]\n\n | \n\nStores the latest error statistics on all error codes per instance \\(discovery status\\).\n\n |
| \n\nAutomation error instance message \\[automation\\_error\\_instance\\_msg\\]\n\n | \n\nStores all latest errors associated with the instance \\(discovery status\\).\n\n |
| \n\nAutomation error instance message\\[automation\\_error\\_stats\\_update\\_time\\]\n\n | \n\nStores the last statistics update time for every application.\n\n |
| \n\nAutomation Error Suggestion \\[automation\\_error\\_suggestion\\]\n\n | \n\nContains all the configured suggestions that presented in the UI per different error codes.\n\n |
| \n\nAutomation Source Application \\[automation\\_source\\_application\\]\n\n | \n\nContains the source applications that are using the Discovery and Service Mapping error framework.\n\n |
| \n\nMapping between suggestion and error code \\[suggestion\\_error\\_code\\_m2m\\]\n\n | \n\nContains information on mapping between error code and suggestion.\n\n |
| \n\nITOM Error task \\[sa\\_error\\_handler\\_task\\]\n\n | \n\nContains the tasks configured per different groups of errors.\n\n |
| \n\nApplicative Credentials\\[sa\\_applicative\\_credentials\\]\n\n | \n\nContains credentials used when running application-specific commands on servers.\n\n |
| \n\nService Mapping CI attributes \\[sa\\_ci\\_attr\\]\n\n | \n\nContains CI attributes relevant only for discovery process.\n\n |
| \n\nRelated CI Types \\[sa\\_ci\\_to\\_pattern\\]\n\n | \n\nAssigns CI types to patterns \\(relevant only for the horizontal discovery performed by Discovery\\).\n\n |
| \n\nPattern Debugger Session\\[sa\\_debug\\_session\\]\n\n | \n\nThis internal table is used for the Pattern Designer components.\n\n |
| \n\nPattern Debugger Session Status for UI\\[sa\\_debug\\_session\\_status\\]\n\n | \n\nThis internal table is used for the Pattern Designer components.\n\n |
| \n\nSa Deferred Service Discovery\\[sa\\_deferred\\_service\\_discovery\\]\n\n | \n\nThis internal table is used for Service Mapping components.\n\n |
| \n\nService Discovery Log\\[sa\\_discovery\\_log\\]\n\n | \n\nContains discovery logs collected by Service Mapping.\n\n |
| \n\nService Discovery Messages\\[sa\\_discovery\\_message\\]\n\n | \n\nContains messages created by Service Mapping during service discovery.\n\n |
| \n\nSa Endpoint Status\\[sa\\_endpoint\\_status\\]\n\n | \n\nContains discovery status for endpoints in Service Mapping.\n\n |
| \n\nFind Host Scripts\\[sa\\_find\\_host\\_scripts\\]\n\n | \n\nContains the names of script includes that find hosts based on the endpoint glide records.\n\n |
| \n\nnfdump file\\[sa\\_flcon\\_file\\_nfdump\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nnfdump install\\[sa\\_flcon\\_local\\_nfdump\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nAWS VPC flow logs\\[sa\\_flcon\\_vpc\\_flow\\_log\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nSA Flow Connection\\[sa\\_flow\\_connection\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nFlow Connector\\[sa\\_flow\\_connector\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nFlow Server Communication\\[sa\\_flow\\_server\\_comm\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nFlow Services IP/Port and Statistics\\[sa\\_flow\\_service\\]\n\n | \n\nThis internal table contains information used for Netflow-based discovery.\n\n |
| \n\nHost Class to Capability\\[sa\\_host\\_class\\_to\\_capability\\]\n\n | \n\nMaps server type to capabilities required by Service Mapping.\n\n |
| \n\nInfra Path To Elements\\[sa\\_infra\\_path\\_assoc\\]\n\n | \n\nContains data on components which are part of a network path.\n\n |
| \n\nMapping External Discovery Commands\\[sa\\_mapping\\_ext\\_commands\\]\n\n | \n\nContains data on customized commands created by user.\n\n |
| \n\nNetwork Paths\\[sa\\_network\\_paths\\]\n\n | \n\nContains data on network paths discovered by Service Mapping.\n\n |
| \n\nHorizontal Discovered Paged Payloads\\[sa\\_paged\\_payload\\]\n\n | \n\nService Mapping uses data in this table for splitting payload sent from the MID Server if the discovery results in a very large payload.\n\n |
| \n\nDiscovery Patterns\\[sa\\_pattern\\]\n\n | \n\nContains preconfigured and customized patterns that Service Mapping uses for discovery.\n\n |
| \n\nService Mapping Draft Pattern\\[sa\\_pattern\\_draft\\]\n\n | \n\nContains non-activated discovery patterns.\n\n |
| \n\nService Mapping Relation attributes\\[sa\\_rel\\_attr\\]\n\n | \n\nContains relation attributes used during service discovery process.\n\n |
| \n\nRel to Infra Path\\[sa\\_rel\\_to\\_infra\\_path\\]\n\n | \n\nMaps relations to network or storage paths.\n\n |
| \n\nService Mapping Server Usage\\[sa\\_server\\_usage\\]\n\n | \n\nContains count of servers used by Service Mapping.\n\n |
| \n\nFile System To Storage Path\\[sa\\_storage\\_paths\\]\n\n | \n\nContains data on storage paths discovered by Service Mapping.\n\n |
| \n\nStorage Path Connectivity Map\\[sa\\_storage\\_path\\_connectivity\\_map\\]\n\n | \n\nMaps file system to storage volume.\n\n |
| \n\nTraffic Based Discovery Rules\\[sa\\_traffic\\_based\\_rules\\]\n\n | \n\nContains data on configuration of traffic-based discovery.\n\n |
| \n\nUploaded File\\[sa\\_uploaded\\_file\\]\n\n | \n\nContains data on files uploaded to the MID Server and used by Service Mapping.\n\n |
| \n\nConfiguration Item \\[cmdb\\_ci\\]\n\n | \n\nStores data on all configuration items \\(CIs\\) in the CMDB.\n\n |
| \n\nApplication\\[cmdb\\_ci\\_appl\\]\n\n | \n\nStores data on all configuration items \\(CIs\\) of application type in the CMDB.\n\n |
| \n\nIP Service \\[cmdb\\_ip\\_service\\]\n\n | \n\nStores data for credentialless discovery support for the original table.\n\n |
| \n\nApplication Category \\[discovery\\_category\\_appl\\]\n\n | \n\nStores data on application categories used by Pattern Designer for managing pattern libraries.\n\n |
| \n\nDevice Classification Category \\[discovery\\_category\\_device\\_class\\]\n\n | \n\nStores information on relationship between a device classifier and protocol used during horizontal discovery performed by Discovery.\n\n |
| \n\nDevice Info Category \\[discovery\\_category\\_device\\_info\\]\n\n | \n\nStores information on device category used during horizontal discovery performed by Discovery.\n\n |
| \n\nProtocol Category \\[discovery\\_category\\_protocol\\]\n\n | \n\nStores information on protocol category used during horizontal discovery performed by Discovery.\n\n |
| \n\nHTTP Classification \\[discovery\\_classy\\_http\\]\n\n | \n\nStores the HTTP classification definition.\n\n |
| \n\nHTTP Classification Match \\[discovery\\_classy\\_http\\_match\\]\n\n | \n\nStores the HTTP classification conditions and the information about the pattern to launch if classification condition is matched.\n\n |
| \n\nDiscovery Pattern Launcher \\[discovery\\_pattern\\_launcher\\]\n\n | \n\nStores information about the pattern launcher mechanism.\n\n |
| \n\nCloud Execution Pattern \\[discovery\\_ptrn\\_cld\\_lchr\\]\n\n | \n\nStores information about the pattern launcher mechanism for discovering cloud applications.\n\n |
| \n\nServerless Execution Pattern \\[discovery\\_ptrn\\_hostless\\_lchr\\]\n\n | \n\nStores information about the pattern launcher mechanism for serverless discovery.\n\n |
| \n\nDiscovery Pattern Parameters \\[discovery\\_ptrn\\_lnch\\_param\\]\n\n | \n\nStores parameters for serverless/cloud application execution.\n\n |
| \n\nPattern Input Parameters \\[discovery\\_ptrn\\_lnch\\_param\\_def\\]\n\n | \n\nStores the key parameters collected by patterns.\n\n |
| \n\nApplicative Credentials \\[sa\\_applicative\\_credentials\\]\n\n | \n\nStores the applicative credentials.\n\n |
| \n\nRelated CI Types \\[sa\\_ci\\_to\\_pattern\\]\n\n | \n\nStores related CIs within patterns.\n\n |
| \n\nCustom operation \\[sa\\_custom\\_operation\\]\n\n | \n\nStores information on discovery pattern operations defined by users.\n\n |
| \n\nCustom operation parameters \\[sa\\_custom\\_operation\\_param\\]\n\n | \n\nStores custom operation parameters for discovery patterns.\n\n |
| \n\nCustom parsing strategy \\[sa\\_custom\\_parsing\\_strategy\\]\n\n | \n\nStores information on pattern parsing strategies that are defined by users.\n\n |
| \n\nDebug session \\[sa\\_debug\\_session\\]\n\n | \n\nStores information collected from debug sessions.\n\n |
| \n\nPattern Debugger Session Status for UI \\[sa\\_debug\\_session\\_status\\]\n\n | \n\nStores information on status of the debug session for the UI purposes.\n\n |
| \n\nSa Deferred Service Discovery \\[sa\\_deferred\\_service\\_discovery\\]\n\n | \n\nContains information used for starting the top-down debug session when the relevant host is still not discovered.\n\n |
| \n\nDiscovery log \\[sa\\_discovery\\_log\\]\n\n | \n\nThe log of several discoveries.\n\n |
| \n\nFind Host Scripts \\[sa\\_find\\_host\\_scripts\\]\n\n | \n\nContains scripts for finding hosts in the CMDB based on the entry point information.\n\n |
| \n\nHost Class to Capability \\[sa\\_host\\_class\\_to\\_capability\\]\n\n | \n\nContains information that maps the type of host to MID Server capabilities. For example, the Linux OS is mapped to the SSH WMI capability.\n\n |
| \n\nMapping Discovery Commands \\[sa\\_mapping\\_ext\\_commands\\]\n\n | \n\nContains customizable operations for the Pattern Designer.\n\n |
| \n\nHorizontal Discovered Paged Payloads \\[sa\\_paged\\_payload\\]\n\n | \n\nContains the IE output payload if the split mechanism is deployed.\n\n |
| \n\nDiscovery Patterns \\[sa\\_pattern\\]\n\n | \n\nStores published patterns.\n\n |
| \n\nService Mapping Draft Pattern \\[sa\\_pattern\\_draft\\]\n\n | \n\nStores modified version of patterns.\n\n |
| \n\nPattern Extensions \\[sa\\_pattern\\_extension\\]\n\n | \n\nStores pattern extension sections.\n\n |
| \n\nPattern Pre/Post Script \\[sa\\_pattern\\_prepost\\_script\\]\n\n | \n\nStores pre/post/pre execution scripts for patterns.\n\n |
| \n\nHorizontal Discovered Payloads Snapshot \\[sa\\_payload\\_snapshot\\]\n\n | \n\nStores the IE output payload for the delete per main CI.\n\n |
| \n\nTracked File Definition \\[sa\\_tracked\\_file\\_definition\\]\n\n | \n\nStores the definitions of the file tracking feature.\n\n |
| \n\nUploaded File \\[sa\\_uploaded\\_file\\]\n\n | \n\nStores scripts and files that are used by the pattern engine.\n\n |
| \n\nProperty\n\n | \n\nDescription\n\n |
|---|---|
| \n\n \n\n | \n\n \n\n |
| \n\nsa.max\\_relations\\_in\\_service\n\n | \n\nThe maximum number of CI relations for a service. Exceeding the value automatically prohibits some services from displaying in the map view. Very large application services may cause performance issues. Instead of maps, users can view CI lists for large application services.- **Type**: integer\n- **Default value**: 5000\n- **Limit**: 10000\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nbest\\_practice.check\\_connectivity.expand\\_listening\\_port\n\n | \n\nThis property controls which PIDs Service Mapping checks during the hop operation in the connectivity check. This property is true, then Service Mapping only checks connectivity on PIDs whose ports are in the **listening** state, not **connected**.- **Type**: boolean\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\ncom.snc.sw.mapping.reaper.checkpoints\\_to\\_keep\n\n | \n\nThe maximum number of change marks maintained in the history timeline of the service. Setting the value to zero or any negative integer overrides the default setting and maintains all change marks for a three-month maximum. Using the property 'com.snc.sw.mapping.reaper.ignored\\_services\\_from\\_optimization' allows the exclusion of specific services and returns to the removal of change marks based upon intervals.- **Type**: integer\n- **Default value**: 1000\n\n |
| \n\ncom.snc.sw.mapping.reaper.ignored\\_services\\_from\\_optimization\n\n | \n\nThis property contains the service IDs separated by commas. Instead of the number specified by the property 'com.snc.sw.mapping.reaper.checkpoints\\_to\\_keep' these services retain all change marks for a three-month maximum. **Type**: integer\n\n |
| \n\ncom.snc.sw.mapping.reaper.max\\_reap\\_size\n\n | \n\nThe maximum number of change marks deleted each time the system removes old and unused records from the history of changes to the service. Setting the value to zero or any negative integer overrides the limit and allows the removal of all unnecessary change marks.- **Type**: integer\n- **Default value**: 100000\n\n |
| \n\nglide.service\\_mapping.computation\\_depth\n\n | \n\nThis property controls the maximal depth of the service instance map.\n\n - **Type**: integer\n- **Default value**: 25\n- **Other possible values**: any number higher than 1\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa\\_ml.connection\\_suggestions.active\n\n | \n\nEnable generation of the connection suggestions feature that is based on traffic-based discovery. Service Mapping generates connection suggestions using data analyzed by Predictive Intelligence. When this feature is enabled, you can [use connection suggestions to manage CI connections in application services](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/add-remove-ci-connections-services.md).- **Type**: boolean\n- **Default value**: true\n\n**Note:** If traffic-based discovery was enabled in your deployment prior to Quebec and you used it to discover at least one application service, the default value is **false**.\n\n- **Other possible values**: false\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.debugger.max\\_timeout\n\n | \n\nMaximum timeout \\(in seconds\\) since the last server activity during a Pattern Debugger run.- **Type**: integer\n- **Default value**: 120\n- **Other possible values**: any number higher than 60\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\nFor more information, see [KB0854603: Pattern Debugger Session Timed Out](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0854603).\n\n |
| \n\nsa.discovery\\_task\\_timeout\\_min\n\n | \n\nMaximum time for a Service Mapping task in minutes \\(including waiting for execution in internal queues and ECC queue\\).- **Type**: string\n- **Default value**: 120\n- **Other possible values**: any number higher than 30\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.enable\\_gray\\_out\\_on\\_resume\\_discovery\n\n | \n\nEnable sub-tree to be grayed out after Service Mapping resumes discovery on an edge, or rerun discovery on the entire topology.- **Type**: boolean\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.excluded\\_discovery\\_sources\n\n | \n\nAdd this property to exclude discovery sources during host detection.- **Default value**: EventManagement\n- **Other possible values**: additional discovery sources, added after EventManagement, separated by a comma\n\n |
| \n\nsa.map.enable\\_loops\\_on\\_service\\_split\n\n | \n\nEnable you to connect a service instance to another, already existing, service instance even if the CI connection \\(endpoint\\) that you are connecting is part of this other service instance. This property helps to avoid loops or cycles in service maps.- **Type**: boolean\n- **Default value**: false\n- **Other possible values**: true\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.mapping.legacy\\_mid\\_selection\n\n | \n\nControls the MID Server selection algorithm used during top-down discovery. Keep this legacy property set to **False** to use the current MID Server selection algorithm.\n\n When set to true, Service Mapping uses the legacy MID Server selection algorithm and the MID affinity features have no effect, regardless of their configuration. This can result in incorrect MID Server identification in networks with overlapping IP ranges or reused IP addresses.\n\n - Type: boolean\n- Default value: false\n- Location: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa\\_ml.connection\\_suggestions.lb.routing.enabled\n\n | \n\nState if a target host is a load balancer member or not in the [Connection Suggestions list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/connection-suggestions-list.md). - **Type**: true/false\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: System Property \\[sys\\_properties\\] table.\n\n |
| \n\nsa.network\\_path\\_calculation.arp\\_enableadded per DOC 1074513 in Vancouver\n\n | \n\nControls queries to the ARP table. Data is only calculated when the value is set to true. **Note:** For more information about querying the ARP table, see the [ARP property documentation for Service Mapping \\[KB1311037\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1311037) article in the Now Support Knowledge Base.\n\n- **Type**: true/false\n- **Default value**: false\n- **Other possible values**: true\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.network\\_path\\_calculation.active\n\n | \n\nEnable network path calculation.- **Type**: true/false\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.rediscovery.batch\\_size\n\n | \n\nNumber of discovery tasks executed in a single batch.- **Type**: integer\n- **Default value**: 100\n- **Other possible values**: any number higher than 10\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.service\\_history.max\\_allowed\\_bubbles\n\n | \n\nNumber of changes that the history scale and the Changes tab display. - **Type**: integer\n- **Default value**: 3000\n- **Other possible values**: any number higher than 3000\n\n**Important:** Increasing the value for this property may cause performance issues with loading service instance maps.\n\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.service.max\\_ci\\_service\\_population\n\n | \n\nThe maximum number of CI connections added to application services during the following operations: Converting manual services created in Event Management into application services with changes from the CMDB.- **Type**: integer\n- **Default value**: 1000\n- **Limit**: 2000\n- **Location**: [Add to System Properties \\[sys\\_properties\\]](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_AddAPropertyUsingSysPropsList.md) table.\n\nIncreasing the default value may cause performance issues.\n\n\n |
| \n\nsa.storage\\_path\\_calculation.active\n\n | \n\nEnable storage path calculation. - **Type**: true/false\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.topdown.mapping\\_with\\_acc\\_mode\n\n | \n\nThis property enables top-down discovery and service mapping using Agent Client Collector by defining the MID Server selection mode for top-down discovery. - **Type:** integer\n- **Default value:** 0\n- **Other possible values:** 1,2\n\n0: Top-down discovery runs using the MID Server exclusively.\n\n1: Top-down discovery initially attempts to run using Agent Client Collector. If no agent is available, then it defaults to using the MID Server.\n\n2: Top-down discovery runs using Agent Client Collector exclusively. If unsuccessful, the process terminates.\n\n |
| \n\nsa.traffic\\_based\\_discovery.active\n\n | \n\nTraffic-based discovery - **Type**: true/false\n- **Default value**: false\n- **Other possible values**: true\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n**Note:** This property applies only to legacy traffic-based connections. If machine-learning \\(ML\\) connection suggestions are enabled, ensure that the property value remains set to `false`.\n\n |
| \n\nsa.traffic\\_based\\_discovery.conn\\_aging\\_time\n\n | \n\nTime period in hours for a Traffic Based Connection to remain active since last discovered. - **Type**: integer\n- **Default value**: 72\n- **Other possible values**: any number higher than 24\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsa.traffic\\_based\\_discovery.ignored\\_ports\n\n | \n\nPorts to ignore when found by traffic-based discovery. This property is available in the System Property \\[sys\\_properties\\] table.\n\n Change this property to define ports that Service Mapping ignores while performing traffic-based discovery. It makes discovery more efficient since resources are not wasted on discovering irrelevant connections.\n\n - **Type**: string\n- **Default value**: 445, 139, 111, 2049, 860, 3260, 135, 53\n- **Other possible values**: any relevant port numbers\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.traffic\\_based\\_discovery.max\\_connections\n\n | \n\nMaximum number of traffic-based connections from a single CI.This property is available in the System Property \\[sys\\_properties\\] table.\n\n This property helps to keep the map size reasonable by limiting the number of possible CI connections.\n\n - **Type**: integer\n- **Default value**: 30\n- **Other possible values**: any number higher than 1\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsa.update\\_paths\\_in\\_service\\_model.active\n\n | \n\nUpdate network and storage paths in Service Model.- **Type**: true/false\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nservice\\_watch.implied\\_match.endpoint.black\\_list\n\n | \n\nA list of endpoint types for which Service Mapping does not apply process matching logic utilized during the top-down pattern execution.- **Type**: string\n- **Default value**: cmdb\\_ci\\_endpoint\\_ssis\\_mssql, cmdb\\_ci\\_endpoint\\_ssas\\_mssql\n- **Other possible values**: comma-separated list of endpoints\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.blacklist\n\n | \n\nExcludes these fields from the record in the service definition export file.- **Type**: string\n- **Default value**: \\[empty\\]\n- **Other possible values**: comma-separated list of fields\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.blacklist.cmdb\\_ci\\_endpoint\n\n | \n\nExcludes these fields from the entry point record in the service definition export file.- **Type**: string\n- **Default value**: \\[empty\\]\n- **Other possible values**: comma-separated list of fields\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.blacklist.cmdb\\_ci\\_service\\_discovered\n\n | \n\nExcludes these fields from the application service record in the service definition export file. - **Type**: string\n- **Default value**: discovery\\_status,operational\\_status,process\\_status,work\\_notes\n- **Other possible values**: comma-separated list of fields\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.blacklist.cmdb\\_ci\\_service\\_group\n\n | \n\nExcludes these fields from the service group record in the service definition export file. Use comma to separate fields. - **Type**: string\n- **Default value**: \\[empty\\]\n- **Other possible values**: comma-separated list of fields\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.max\\_services\\_limit\n\n | \n\nDefines the maximum allowed number of services to export. - **Type**: integer\n- **Default value**: 100\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.skip\\_empty\\_fields\n\n | \n\nExcludes fields with an empty value from the record in the service definitions export file.- **Type**: boolean\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.skip\\_reference\\_fields\n\n | \n\nExcludes reference fields from the record in the service definitions export file. - **Type**: boolean\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.export.skip\\_sys\\_fields\n\n | \n\nExcludes fields beginning with “sys\\_” from the record in the service definitions export file. - **Type**: boolean\n- **Default value**: true\n- **Other possible values**: false\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsm.service.import.auto\\_start\\_discovery\n\n | \n\nEnable automatic discovery on all successfully imported entry points.- **Type**: boolean\n- **Default value**: false\n- **Other possible values**: true\n- **Location**: **Service Mapping** > **Administration** > **Properties**.\n\n |
| \n\nsn\\_cloud\\_migration.categories.inclusion\\_list\n\n | \n\nA comma-separated allow list of categories for cloud migration. Only resources assigned to categories that are listed here can participate in the migration process.- **Type**: string\n- **Default value**: Physical,VMware,HyperV,IBM HMC,OpenStack,Solaris,Nutanix,Amazon AWS,Microsoft Azure,Google Cloud,IBM Cloud\n- **Location**: **Cloud Migration** > **Cloud Migration Workspace** > **Administration** > **Properties**\n\n |
| \n\nsn\\_cloud\\_migration.server\\_status.inclusion\\_list\n\n | \n\nA comma-separated allow list of server status for cloud migration. Only servers with the listed here install status can participate in the migration process.- **Type**: ?\n- **Default value**: 1\n- **Other possible value**: Installed=1, On Order=2, In Maintenance=3, Pending Install=4, Pending Repair=5, In Stock=6, Retired=7, Stolen=8, Absent=100\n- **Location**: **Cloud Migration** > **Cloud Migration Workspace** > **Administration** > **Properties**\n\n |
| \n\nsn\\_cloud\\_migration.os.exclusion\\_list\n\n | \n\nA comma-separated deny list of operating systems for cloud migration. The servers whose operating system is listed here are excluded from the migration process.- **Type**: String\n- **Default value**: ESX, Windows 2000,Windows XP.\n- **Location**: **Cloud Migration** > **Cloud Migration Workspace** > **Administration** > **Properties**\n\n |
| \n\nsn\\_cloud\\_migration.vm\\_state.inclusion\\_list\n\n | \n\nA comma-separated allow list of VM instance states for cloud migration. Only VMs with states that are listed here can participate in the migration process. - **Type**: ??\n- **Default value**: on\n- **Other possible values**: on, off, paused, scheduled, starting, stopping, retired, terminated, error, cancelled, pausing, terminating\n- **Location**: **Cloud Migration** > **Cloud Migration Workspace** > **Administration** > **Properties**\n\n |
| \n\n \n\n | \n\nThe number of CI relations, exceeding which application service is not displayed automatically in the map view. Very large application services may cause performance issues. Instead of maps, users can view CI lists for large application services. Setting a negative value results in not limiting the number of added CI relations. Setting an invalid value, like a string, is equivalent to the default value, 5000.- **Type**: Integer\n- **Default value**: 5000\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsvc\\_by\\_tags.classes.whitelist\n\n | \n\nThis property contains the list of allowed CI classes separated by commas. Tag-based mapping includes the CIs belonging to these classes. An empty ‘value’ field indicates the inclusion of all CI classes.\n\n |
| \n\nsvc\\_by\\_tags.install\\_status.blacklist\n\n | \n\nThis property contains the list of exclusions based upon the install status separated by commas. Tag-based mapping excludes any tagged CIs with the following install statuses:**Default value**: 7,100\n\n **Other possible values**:\n\n Installed=1, On order=2, In maintenance=3, Pending install=4, Pending repair=5, In stock=6, Retired=7, Stolen=8\n\n |
| \n\nsvc\\_by\\_tags.max.categories.per.family\n\n | \n\nSet the maximum number of categories allowed per service family.- **Type**: integer\n- **Default value**: 3\n\n |
| \n\nsvc\\_by\\_tags.max.traversal.rules.active\n\n | \n\nSet the maximum allowed number of CI relationships that can be in the active state. Service Mapping uses only active CI relationships for tag-based discovery. - **Type**: integer\n- **Default value**: 5\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsvc\\_by\\_tags.max\\_ci\\_limit\n\n | \n\nSet the maximum allowed number of CIs that a tag-based application service can contain.- **Type**: integer\n- **Default value**: 1000\n- **Limit**: 2000\n- **Location**: System Property \\[sys\\_properties\\] table\n\n |
| \n\nsm.topdown.reuse\\_mid\\_from\\_hd\\_schedule\n\n | \n\nUse the MID Server configured during horizontal discovery for top-down discovery.- **Type:** boolean\n- **Default value:** false\n- **Other possible values:** true\n- **Location:** **Service Mapping** > **Administration** > **Properties**\n\n |
| \n\nsm.network\\_location.detect\\_host\\_by\\_location\n\n | \n\nSelect the subnetwork location to allow for the identification of the appropriate host and MID Server.**Important:** For best results, you must enable this property and sm.topdown.reuse\\_mid\\_from\\_hd\\_schedule concurrently.\n\n- **Type:** boolean\n- **Default value:** false\n- **Other possible values:** true\n- **Location:** **Service Mapping** > **Administration** > **Properties**\n\n |