Create APD files for an SAP application on a server - Legacy

The first step in this example is to create APD files for an SAP application on a server (any OS) for which no credentials are available.

  1. Navigate to Discovery Definition > Properties and find the property for the proxy server's operating system.
    In this example, use the Application discovery location for UNIX-based systems property (glide.discovery.application_discovery.unix_location) for a Linux proxy server. This example uses the default path of /etc/opt/apd/, although it could use any path.
  2. On the Linux proxy server, create an APD folder in the default UNIX path: /etc/opt/apd/.
    Note: By default, Discovery looks for the environment file in this location on all UNIX machines.
  3. Use the template to create an SAP environment file for a Solaris server that does not have Discovery credentials.
    system: The namer of the inaccessible computer on which the SAP application is running. For this example, sol13.lab2 is the name of the Solaris computer with no credentials for Discovery.
    application_version_path: Specify the path to the SAP version file on the proxy server. For this example, enter/etc/opt/apd_version/sap_version.xml. The version file must be on the same computer as the environment file but in different directories.
    Figure 1. SAP Environment File Template
  4. Save the environment file to the /etc/opt/apd/ directory.
  5. Create the version file directory using the path specified in the environment file.
    For this example, create a directory called apd_version on the same level as the apd directory. Remember that the version file cannot be in the same directory as the environment file.
  6. Use the template to create a version file called sap_version.xml and save it to the /etc/opt/apd_version directory.
  7. Continue the process at Classify the Application.