Skip to content

Differences between DPF 3 and DPF 4

This page describes how DPF 4 differs from DPF 3.

  • DPF 4 uses a collection of microservices with Consul or container orchestration and the configuration files (main.customer.xml, passwd.cfg) known from DPF 3 for compatibility reasons.

  • MongoDB instead of Postgres is used as a database.

  • Log files are optimized for the evaluation via Elastic Stack on Linux or Windows.

  • No SOAP interface, thus no SOAP Web Service, no Mail Service and no DPF SAP Retriever. The migration to REST based functions is planned.

  • No DPF Gate. (A solution is in the planning stages.)

  • No Watchdog. Services restart automatically.

  • DPF Admin Client has been replaced by DPF CLI. It is used outside of the DPF environment in a PowerShell or command line.

  • The microservices of DPF 4 use different ports than their equivalents in DPF 3.

  • The job type PDFLLSJob is not (yet) supported.

  • As of DPF 4.3.0, dpf-jobclient-api supports OIDC authentication. For more information, refer to Restrict Access to the Jobclient API via OIDC.

  • DPF 4 provides Prometheus metrics.

  • On Linux, DPF 4 is installed under the user seal. (DPF 3: plossys)

  • No licensing management. (A solution is in the planning stages.)

Back to top