A server profile defines a format for the configuration of a server by combining the following files into a single, concrete structure:

  • dsconfig
  • Initial DIT
  • Setup arguments
  • Server SDK extensions
  • Additional miscellaneous files

The primary goal of a server profile is to simplify the deployment of PingDirectory server and related products by using deployment automation frameworks. When products support this capability, the amount of scripting that is required across automation frameworks–like Docker, Kubernetes, and Ansible–is reduced considerably. For more information, see Server profiles.

To run this tool from the administrative console:

  1. Start the administrative console.
  2. In the top-level navigation menu, select Status.
  3. Click Download Server Profile.
    A screen capture highlighting the "Download Server Profile" button in the Status section of the administrative console.
  4. In the Generate Server Profile window, enter path values according to the help text.
  5. Click the Run Task button.
  6. Wait for the task to complete.

    This can take several minutes.

  7. After the task is completed, the server profile is downloaded to the <directory>/profile-files directory.

    When the administrative console sends a request to the PingDirectory server to generate the server profile, <directory>/profile-files is the default path for storing the resultant file package. This default path can be modified in the <directory>/console/WEB-INF/classes/application.yml directory.