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. Requirements 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. ADM probes and sensorsADM uses the following probes and sensors to explore applications and determine their relationships.Application relationships for Discovery ADMDiscovery maps application data automatically into upstream and downstream relationships.Access ADM dependency mapsAccess dependency maps to see application relationships.Discovery ADM upstream and downstream relationshipsIn upstream and downstream relationships, anything that happens downstream can have an adverse affect on upstream configuration items.ADM dependencies: example with JBoss and ApacheThis screenshot displays the application dependencies between three different JBoss application servers and the local Apache web site. Add CI relationships for Discovery ADMDiscovery automatically maps the dependencies between CIs that it finds in the network and assigns the appropriate type to each relationship. Pending Process ClassifiersPending process classifiers identify interdependent processes, based on TCP connections, that are not classified by the system-provided process classifiers, such as database or web servers, or even proprietary applications.Create a "No Classify" process handlerA "No classify" process handler prevents future discoveries from classifying matching processes, and also prevents creation of new Pending Process Classifiers and Pending Applications for that process. Delete ADM application instancesDeleting application instances deletes all application records that reference the given classifier. The classifier is also deleted.Create an ADM table using the application instance tableA new application instance table, with a classifier name suitable to the process or application, can be created by extending the Application instance table [cmdb_ci_appl] if a suitable table does not exist. Create pending processes classifiers for local connectionsBy default, Discovery does not create pending process classifier records for processes that communicate with one another on the same host.