Advanced settings

Host name and port

• slicebox.host - The host where slicebox will be run. For private instances and users on a single computer, localhost is a perfectly good choice. If you would like to accesss the instance from other computers, change this to the IP address or host name of the server where the instance is running. One option is 0.0.0.0 which means slicebox will accept connections to all IP addresses of the server (such as locahost, 192.168.1.1 and its public IP).
• slicebox.port - The port where the service is reached. Default is 5000. 80 is the standard port for web services and 443 is the standard port for web services over SSL/TLS (https).

Super user credentials

• slicebox.superuser.user - The username of the slicebox super user. The super user has administrator privileges and cannot be removed.
• slicebox.superuser.password - The password of the slicebox super user.

Session timeout

The user is logged out after an extended period of inactivity. The default session timeout setting slicebox.session-timeout = 3600s corresponds to 3600 seconds = 1 hour.

Memory consumption and settings

Slicebox runs on the Java Virtual Machine (JVM) and is subject to the settings and limitations for this machine. See e.g. http://docs.oracle.com/javase/8/docs/technotes/tools/#basic for details. Slicebox makes an effort to minimize memory footprint but there are circumstances, such as when uploading/importing files, where the entire dataset is read into memory. Since several requests may be processed simultaneously, this can lead to high memory consumption. The setting spray.can.server.parsing.max-content-length = 500m specifies the maximum size of datasets (or any other request) that is allowed (default is 500 Mb). To allow for several such requests simultaneously, the JVM heap size is set to 2 Gb. To change this, edit the start script for your platform in the bin folder. Look for the -Xmx2G setting and change it as required.

Purging empty anonymization keys

Anonymization keys help keeping track of how patient data has been anonymized, keeps anonymization of patients consistent between sessions, and makes reverse anonymization possible. For some users, anonymization keys are valuable in the long term, such as when slicebox is used as a research platform and there is a need to relate anonymous IDs to patient information long after the image data has been removed or archived. The default setting slicebox.anonymization.purge-empty-keys = false means that as image data is removed from slicebox, the corresponding anonymization information will remain until deleted manually. By setting slicebox.anonymization.purge-empty-keys = true, anonymization keys are removed as soon as corresponding image data is no longer present. This is convenient when the amount of protected health information in the system should be kept as small as possible.