Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Application Dependency Mapping (ADM) for Discovery

Log in to subscribe to topics and get notified when content changes.

Application Dependency Mapping (ADM) for Discovery

Application dependency mapping (ADM) creates relationships between interdependent applications.

ADM identifies:
  • The devices that are communicating with one another.
  • The TCP ports these devices are communicating on.
  • The processes that are running on these devices.

For example, if a web server application uses a database server application, the web server "depends on" the database. The web server also "runs on" the host or server cluster. You can use the data from running processes to determine which devices to drill into to see more application-specific configuration data.

You can disable ADM and use the ADM probes and sensor to collect active connections and active process information without collecting all the Application Dependency Mapping information.


Your instance must meet the following requirements to use application dependency mapping.
  • ADM system properties are enabled.
  • ADM probes are configured.
  • Process classifications are configured.

Windows 2000 Server Requirements

The Windows - Active Connections probe associates running processes on Windows machines with the ports on which they communicate, using the netstat command. Windows 2000 Server and Windows workstations, in their default configuration, cannot associate process IDs with ports using the netstat command. This prevents Discovery from providing application mapping on these machines. To enable a Windows 2000 Server or workstation to support process-to-port connections in the ServiceNow system, apply this Microsoft hotfix. This hotfix enables these Windows machines to support the -o parameter of the netstat command, which enables Discovery to associate processes with TCP/IP connections.