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


  • 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