APD Version file - Legacy The 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. An application on any given managed system can be fully described by one or more version files and one or more environment files. Never place the version file in the same directory as the environment file. You can install the version file in any other location on the managed system or proxy server that is visible to the MID Server. The MID Server locates the version information related to an application by following a path defined within the environment file. Install one copy of the version file per installed software version on a managed system. Version File Template Use the following XML template for the version file. <?xml version="1.0" encoding="UTF-8"?> <apd> <config version="1.0" application="application-name" type="version"> <version> <label>version-name-label</label> <description>version description</description> <ownership>software package ownership information</ownership> <subservices> <subservices_provided> <subservice> … label … </subservice> </subservices_provided> <subservices_consumed> <subservice> … label … </subservice> </subservices_consumed> </subservices> </version> </config> </apd> Version File Configuration The version configuration file contains the following information: Application details Application Details Detail Requirement Description Attributes version Mandatory The version must be unique to the installed version of an application. This label displays the application version or other distinguishing name. application Mandatory. Discovery uses the application name from the version file to populate the CMDB. Name of this application. Tags <label> Optional This label has information important to the organization, such as Production, UAT, QA, or Development. The label and description appear only in the Environment related list in the application record. You must personalize the form to add the Environment related list. <description> Optional This is a short description of the application. <ownership> Mandatory This value is typically a group-level ownership label that may be mapped to an existing group in the Group [sys_user_group] table. This value names the owner who is responsible for this software package or installation. If no value is specified in the environment file, then this value is used to record ownership of the environment as well. A group owner selected from the Group [sys_user_group] table appears in the Support group field in the ServiceNowServiceNow Environment record. To see this record, personalize the Application form to display the Environment related list, and then drill into the environment listed. <subservices_provided> Optional These values describe the individual services provided by this version of the software. Use this value to define additional services provided by a new version of an existing application already configured by an environment file. Discovery creates the relationships defined in the environment file first and then adds any sub-services listed in the version file. <subservices_consumed> Optional These values describe the individual services this application consumes from other applications. Use this value to define additional services consumed by a new version of an existing application already configured by an environment file. Discovery creates the relationships defined in the environment file first and then adds any sub-service relationships listed in the version file.