Skip to content

DPF Tracker

Here, you find possible solutions to problems that can occur with DPF Tracker when installing or running Digital Process Factory.

DPF Tracker Shows No Jobs

DPF Tracker shows no jobs, although DPF processes them. This affects on-premise installations.

The rest.pm file of DPF Tracker contains a wrong default port. DPF Tracker requests the job list from seal-dpf-jobclient-api on port 4303. The correct service is seal-dpf-management-api on port 4304.

  1. Check that seal-dpf-management-api returns jobs. On the DPF server, enter the following URL in a Web browser:

    http://localhost:4304/rest/dpfmanagement/v1/jobs?limit=1

    If total in the response is greater than 0, jobs exist. Continue with the next step.

  2. Open the rest.pm file in an editor:

    • on Windows:

      C:\SEAL\applications\tools\dpf\tracker\storage\rest.pm

    • on Linux:

      /opt/plossys/tools/dpf/tracker/storage/rest.pm

  3. Replace the default port 4303 with 4304:

    my $servicePort = 4304;

  4. Save the file and reload DPF Tracker in the Web browser.

An update of DPF might overwrite rest.pm. In this case, repeat the change.

DPF Tracker URL of a Job Does Not Work

DPF Batch Client outputs a DPF Tracker URL for each started job, for example:

http://localhost:4343/cgi-bin/dpftracker?job=<job_id>

This URL does not work in on-premise installations. Port 4343 is the DPF Tracker port in container installations. On-premise, DPF Tracker runs in the Apache server. The Frozen Master installation specifies whether the Apache server uses HTTP or HTTPS. By default, the Apache server uses port 9125 for HTTP and port 9126 for HTTPS.

seal-dpf-jobclient-api creates the URL from the TRACKER_URL key. To get a working URL, set the key to the address of the Apache server:

  1. In a PowerShell, set TRACKER_URL for seal-dpf-jobclient-api:

    dpf config set TRACKER_URL <protocol>://<server>:<port> --service dpf-jobclient-api --insecure

    Replace the placeholders with the protocol, server name and port of the Apache server, for example https://<server>:9126. Do not add a path. seal-dpf-jobclient-api appends /cgi-bin/dpftracker?job=<job_id> itself.

  2. Stop seal-dpf-jobclient-api:

    dpf service stop seal-dpf-jobclient-api

  3. Start seal-dpf-jobclient-api again:

    dpf service start seal-dpf-jobclient-api
Back to top