Application Profile Discovery - Legacy Application Profile Discovery (APD) is deprecated in the Helsinki release. Instances upgraded from a previous release can continue to use APD, but the feature is not available for new instances. Application Profile Discovery (APD) enables Discovery to identify custom applications or applications that contain multiple processes and determine their dependencies by using pre-populated data. The information that Discovery uses to do this appears in an XML file, created by an administrator, and installed in your environment. The administrator saves this environment file to a location on a managed system (host, node, server, platform, or other device that is present in the CMDB) where probes launched by the MID Server are configured to look for it. Discovery uses the data in this file to establish the relationships between the application and the business services it supports. In addition to the environment file, the administrator creates a version file containing general information about the application and the version that Discovery uses to describe the application. The diagram shows a hypothetical relationship between the SAP application and another application created by a common business service. APD is able to discover both SAP and the dependencies created by the shared business service by using information contained in an environment file called sap.xml installed on the managed system. Version information is contained in the sap_version.xml file which is installed in a different location on the same managed system or proxy server.Figure 1. Application Discovery Instrumentation Diagram Rev Requirements Enable Application Profile Discovery: To enable APD, navigate to Discovery Definition > Properties and select Yes in the Application Profile Discovery property. Select a MID Server Included with Application Profile Discovery - LegacyThis is a list of elements included with Application Profile Discovery.Normalizing business service names - LegacyThe name of a business service used in an Application Profile Discovery environment or version file might not be an exact match for an existing business service name in the ServiceNowServiceNow CMDB.Environment file - LegacyThe XML file that contains the application environment information must be created by a system administrator who understands the relationships of the specified application.Environment file fields - LegacyProvide attribute and tag information in the environment configuration file.Environment configuration file location - LegacyEnvironment files are stored on and collected directly from systems that support a general purpose file system.APD Version file - LegacyThe XML file containing version information about the application is typically prepared as part of the software packaging and release process and is identical across all managed systems using that version of the software.Application Profile Discovery example in Linux environments - LegacyThe RCD Corporation wants to discover details of their custom human resources application called ResourceNow and create relationships to other processes in their CMDB. Application Profile Discovery example in Windows environments - LegacyThe RCD Corporation wants to discover details of their custom human resources application called ResourceNow and create relationships to other processes in their CMDB. Application Profile Discovery example with proxy servers - LegacyThe RCD Corporation wants to discover details of their custom human resources application called ResourceNow and create relationships to other processes in their CMDB. Application Profile Discovery customization - Legacy Application Profile Discovery (APD) enables administrators to define processes and dependencies for applications that Discovery cannot explore.