Environment configuration file location - Legacy

Environment files are stored on and collected directly from systems that support a general purpose file system.

The MID Server searches for environment files on every machine it discovers, using the location preferences described in this section. To provide flexibility in different environments, an administrator has several options for installing environment files in a file system. The MID Server checks specific locations on the managed systems it discovers in a particular order. When the MID Server finds a base environment file, the MID Server quits searching on that device.
Note: Never place the version file in the same directory as the environment file. Discovery treats all files found in that location as environment files and cannot parse the version file correctly.

UNIX

Place the environment files in one of the following locations. Discovery searches for the file in the order shown.
  1. Environment variable: Put the environment configuration file in a path such as /usr/local/APD and set the variable, $APDCONF, to describe the location of the file. How this environment variable is maintained is left to the administrators of the local environment.
  2. Discovery property: Navigate to Discovery Definition > Properties and set the file path in the Application Profile Discovery location for UNIX based systems property (glide.discovery.application_discovery.unix_location). The default path is /etc/opt/APD/.

Windows

Place the environment configuration file in one of the following locations on a Windows OS version that supports a local machine registry.
  1. Registry key: Before the MID Server retrieves a file from a managed Windows system, it checks the HKEY_LOCAL_MACHINE (HKLM) hive, in the key HKLM\SOFTWARE\APD\APD\CONFIGPATH for a REG_EXPAND_SZ or REG_SZ type registry value. The key value can require expansion for terms such as %CommonAppDataFolder%. See Microsoft’s CSIDL documentation for further details.
    Figure 1. APD Win Registry
  2. Discovery property: Navigate to Discovery Definition > Properties and set the file path in the Application discovery location for Windows systems property (glide.discovery.application_discovery.windows_location). The sample path is %ALLUSERSPROFILE%\Application Data\APD, in which %ALLUSERSPROFILE% is the environment variable for any Windows system. This variable points to different paths on different versions of Windows. For example, on Windows 7, %ALLUSERSPROFILE% opens C:\ProgramData, and on Windows XP, it opens C:\Documents and Settings\All Users.

Proxy Locations

Some managed systems, such as network routers, switches, and network load balancers, do not support locally stored files or general purpose file systems that could store APD configuration files. In this case, you can name the target managed system in an environment configuration file installed on a separate proxy server. Make sure to put the configuration XML file in one of the approved locations on the proxy machine. The MID Server searches for this file on every machine it discovers. When it finds an XML file in one of the expected locations, it identifies the correct managed system by parsing the value for <managed system name> in the following line:
<config version =" 1.0" application =" (optional ) application - name" type ="environment" system ="  (optional , if not local system ) managed system  name" >