Skip to main content
Skip table of contents

Runtime Defaults

There are several DATPROF Runtime settings with an installation default.

Network port numbers

What

PortProperty nameRemark

Runtime Port number

7070


server.port

This is the main port to access your Runtime application.

It is the port Apache Tomcat is started with.

Active MQ

61616

broker.jms.port


Active MQ Stomp Support

61613

broker.stomp.port
HSQLDB Database9001

db.url

db.port


When using the default the url can be used without a port number.

When using an alternative port number it should appear in the url too.

So:

db.url=jdbc\:hsqldb\:hsql\://localhost:/runtime
db.port=9001

or

db.url=jdbc\:hsqldb\:hsql\://localhost/runtime
db.port=9001

Runtime Java vm Parameters

No special settings are provided.

All settings can be set in <RuntimeInstallationFolder>\bin\setenv.bat


Agent Java vm Parameters

No special settings are provided.

By default you cannot change the settings for the agents started from within Runtime.

Check the DATPROF knowledgebase  about a method to adjust Runtime agent vm settings when starting agents manually.



Application

Application Parameter


DPF_SCRATCH_DIRValue: <RuntimeDataFolder>/agents/<RunId>/scratch
Adjustable

yes, Add to Environment parameters.

This parameter is by default not visible in the Parameters screen!

To use it in your code or scripts: ${dpf.parameters.DPF_SCRATCH_DIR}

Application Parameter


DPF_ARTIFACTS_DIR
Value: <RuntimeDataFolder>/Projects/<ProjectId>/environments/<EnvironmentId>/runs/<RunId>/artifacts
Adjustable

No.

This parameter is not visible in the Parameters screen!

Any file saved in this location is shown in the Files section of Runtime History.

To use it in your code or scripts: ${dpf.parameters.DPF_ARTIFACTS_DIR}

Location of the License file


dpfruntime.licThe license file is located in the “conf” subfolder of the user defined Data folder of the installation.
<RuntimeDataFolder>/conf/dpfruntime.lic
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.