Skip to content

Directories and Files on Linux

Digital Process Factory

The installation directory is specified during installation of DPF and saved in environment keys. The following directories and files are created:

  • Installation directory: %DPFROOT%
  • Server components directory: %DPFSRV%
  • Data and job directory: %DPFDATA%
  • Customer-specific configuration directory: %SEAL_CUSTOMDIR%
  • Service configuration directory: /opt/seal/etc
  • Log directory:
    • %DPFROOT%/data/log for legacy components such as Apache
    • /opt/seal/log for service logs
  • Home directory of the SEAL user: /var/lib/seal

Customer-Specific Files

Digital Process Factory reads the following customer-specific files from %SEAL_CUSTOMDIR%, in addition to the standard files in the templates directory below %DPFSRV%:

  • Workflows: files named wf-*.xml, in any subdirectory. A customer-specific workflow overrides a standard workflow with the same name.
  • Working unit definitions: files named wu-*.xml, in any subdirectory. A customer-specific working unit definition overrides a standard working unit definition with the same name.
  • main.xml and main.customer.xml: directly in %SEAL_CUSTOMDIR%, not in a subdirectory. Their values override the values from the templates directory, refer to Configuration of DPF Server - main.customer.xml.
  • passwd.cfg for the user rights of DPF Tracker, refer to Secure DPF Tracker.

The following rules apply:

  • Digital Process Factory reads these files when the services start. After a change, restart the affected services, refer to Administrate the DPF Services.
  • Digital Process Factory loads every file whose name matches, including copies. Do not keep copies such as wf-order - Copy.xml below %SEAL_CUSTOMDIR%. Rename them so that the name no longer matches, for example wf-order.xml.bak.
  • Define each workflow and each working unit only once below %SEAL_CUSTOMDIR%.
  • Digital Process Factory does not search working unit scripts in %SEAL_CUSTOMDIR%. The COMMAND attribute of the working unit definition specifies the script path.

Systemd

The following directories and files are created:

  • Configuration for Systemd: /usr/lib/systemd/system/<service_name>.service

sudo

The following directories and files are created:

  • Configuration for sudo: /etc/sudoers.d/<service_name>

Firewall

The following directories and files are created:

  • Configuration for the firewall on SUSE: /etc/sysconfig/SuSEfirewall2.d/services/<service_name>.service

Logrotate

The following directories and files are created:

  • Configuration for Logrotate: /etc/logrotate.d/plossys

Hint - MongoDB

For the directories and files used by MongoDB, refer to the SEAL-specific MongoDB documentation.

Hint - SEAL Elastic Stack

For the directories and files used by SEAL Elastic Stack, which includes Elasticsearch, Kibana and Filebeat, refer to the SEAL Elastic Stack documentation.

Back to top