System Properties |
![]() |
PureLoad
5.2 January 2015 |
http://www.pureload.com support@pureload.com |
There are a number of system properties that controls various setting for the PureLoad servers. These properties are defined in the install-home/bin/pureload.properties file (where install-home is where PureLoad is installed).
The properties file is edited using a text editor.
Note: PureLoad servers need to be restarted in order to use a
modified configuration.
Name |
Default |
Description |
---|---|---|
naming.host |
default OS host |
The name of the host or IP
address where the Naming server will run. This property is
used by all servers to locate the host where the naming
server is running |
taskspace.host |
default OS host | The name of the host or IP
address that the TaskSpace server should use. Typically used
when the computer has multiple network interfaces. |
manager.host |
default OS host | The name or the IP address
that the manager server should use. Typically used when the
computer has multiple network interfaces. |
runner.host |
default OS host | The name or the IP address that the runner server should use. Typically used when the computer has multiple network interfaces. |
external.host |
N/A |
Host name or IP address to be
used by servers when publishing server addresses. This
property is only
required if servers is between a NAT firewall. |
There are 2 different ports that can be defined for each server. One is the RMI registry port and one is the service port. Normally there is no need to change these, the exception is when setting up PureLoad over firewalls.
Name |
Default |
Description |
---|---|---|
naming.port |
1099 |
Port used by RMI registry for
naming server. |
naming.service.port |
dynamic |
Service port used by naming
server. |
taskspace.port |
1096 |
Port used by RMI registry for
taskspace server. |
taskspace.service.port |
dynamic |
Service port used by
taskspace server. |
manager.port |
1095 | Port used by RMI registry for
manager server. |
manager.service.port |
dynamic |
Service port used by manager
server. |
runner.port |
1999 |
Port used by runner server. |
Settings for the worker are specified using the worker.args property. The
following may be used:
Name |
Default |
Description |
---|---|---|
-Xmx<nnn>M |
256M |
Max heap size of the Worker
Java VM. Increase if running out of memory for the workers. |
-Xss<nnn>K |
256K |
Stack size of worker threads.
Normally no need to change this. |
-Dworker.error.stacktrace=true |
false |
Optional flag indicating that
worker should save stacktrace information for task execution
errors |
Typical examples:
To increase the Java VM heap size to 512MByte:
worker.args=-Xmx512M -Xss256K |
To use the custom scheduler:
worker.args=-Xmx256M -Xss256K -Dworker.scheduler=custom |
There are other settings available, that normally isn't any need
to change. For these settings see the comments in the properties
file.
For example to change the max heap size for the console edit the
file console.vmoptions and change the content to:
-Xmx512M |
This will increase the max heap size to 512Mbyte.
The license management system in PureLoad is based on a license
file that is installed into <install-home>/license/pureload.license.
The
license file lists information about the licensee and a seal which
is the binary representation of the actual license. The license is
handled by the Naming process and must be accessible by that
process. All other processes and the PureLoad Console do not need
the license installed in order to work.
The license restricts on the number of managers, workers and
worker threads that can be assigned using the PureLoad Console. It
also restricts which IP addresses that can host the Naming
process. It does not restrict any other functionality, such as
editing scenarios and saving these into a PLC (PureLoad
Configuration) file, etc.
Use the Help->License Info
menu choice in the Console to lists information about the current
license.