# Aleph Toolkit User's Guide

## Aleph Properties

Aleph maintains a set of properties, similar to System properties. When the console is started, any system property that starts with the string "aleph." is encorporated into the Aleph properties. Aleph properties can be created and queried by calls to `Aleph.setProperty()` and `Aleph.getProperty()`. When the console creates a new PE, all its current Aleph properties are passed to the PE.

The following properties may be useful, either as command-line arguments, or to check at run-time.

`aleph.batch` | If true, start application without the console.
`aleph.communicationManager` | Communication manager, see `Config.communicationManagers`
`aleph.directoryManager` | Directory manager, see `Config.directoryManagers`
`aleph.eventManager` | Event manager, see `Config.eventManagers`
`aleph.label` | PE's print name (default `PE[n]`).
`aleph.logging` | If true, log console interactions to a file.
`aleph.maxPEs` | Maximum number of PEs on console choice button.
`aleph.numPEs` | Number of PEs to start up.
`aleph.pathJava` | where to find `java`
`aleph.pathJava_g` | where to find `java_g`
`aleph.pathRsh` | where to find rsh (Unix shells only)
`aleph.profile` | If true, dump profiling information to file.
`aleph.transactionManager` | Transaction manager, see `Config.transactionManagers`
`aleph.useJava_g` | If true, run applications using `java_g.`
`aleph.verbosity` | Diagnostic messages: 0, 1, or 2 are sensible values.

Aleph uses other properties internally, and users are advised not to modify them.