Skip to content

Digital Process Factory 4.0.0

New Features

  • With DPF 4.0.0, the internal architecture of Digital Process Factory has been changed to a microservice architecture, thus making it clusterable and faster. For this, the installation of MongoDB, SEAL NATS and SEAL Logrotate are required prior to the installation of Digital Process Factory. The list of services contained in DPF is available in the reference section of this documentation.

  • When installed on the same server as PLOSSYS Output Engine, Digital Process Factory will use the same infrastructure.

  • DPF Tracker reads the job list and history from MongoDB. (DPF-1680, DPF-1681)

  • The sysinit script is used to transfer the old environment settings for the new microservice architecture to Consul, refer to Update for on-premise Windows or Update for on-premise Linux. (DPF-1683)

  • DPF CLI is the command line tool for administrating Digital Process Factory. It is used for managing the system configuration and the services. (DPF-1692)

  • The JobID of a job is unique for the whole cluster. It is build of date, time and a four-digit sequential number. (DPF-1707)

  • Digital Process Factory uses the new SEAL System product icon. (DPF-1711, DPF-1761)

  • For the communication between DPF Tracker and MongoDB, a REST API is used. You can find the API specification in the reference section of this documentation. (DPF-1728)

  • As of DPF 4.0.0, folder service is no longer supported. (DPF-1742, DPF-1751)

  • DPF Admin Client has been replaced by DPF CLI. It is used outside of the DPF environment in a PowerShell or command line. The old function names like dpfclearjobs are implemented as aliases for the new DPF CLI commands. (DPF-1757, DPF-1883 TODO)

  • The new DPF bundle contains an install and a firewall script, refer to Installation for on-premise Windows and Installation for on-premise Linux. (DPF-1760)

  • When the LOG_LEVEL for dpf-process-manager service is set to info, the first line of job.log states if the new microservice environment was used for the job. (DPF-1762)

  • Parameter changes made by Modify working units are listed in the job history in MongoDB. (DPF-1788)

  • A firewall script is available to open the necessary firewall ports. The list of ports used by Digital Process Factory is available in the reference section of this documentation. (DPF-1808)

  • Standard Prometheus metrics are available to analyze the general health of the DPF server. (DPF-1841)

  • For Linux on premise, the required Frozen Master Convert has to run under the user seal. (DPF-1842)

  • Service log files are provided in machine-readable JSON format. Use Elastic Stack for a human-readable view. For how to install and configure Elastic Stack, refer to SEAL Elastic Stack documentation. (DPF-1877)

  • Node.js version 20.17.0 is used. (DPF-1885)

Bug-Fixes

  • The bug has been fixed, that prevented the creation of a result file when calling dpfclient via REST route with the -result option. (DPF-1892)

Known Issues

  • The SOAP interface and thus SOAP Web Service, Mail Service and DPF SAP Retriever are not working with DPF 4.0.0. (DPF-1726)

  • DPF Gate ist not working with DPF 4.0.0. (DPF-1744)

  • As of DPF 4.0.0, DPF Batch Client does not support the option -f to provide a directory or multiple files with a job. (DPF-1768)

  • If a sendback workflow is started by the DPF Batch Client via REST interface and the return files are to be placed in a subdirectory, the DPF Batch Client does not create this subdirectory. (DPF-1813)

  • The job type PDFLLSJob is currently not supported. (DPF-1853)

Back to top