All the configurations can be found in ClientDft.py. However, I strongly recommend you to have your own .actimrc with read only permission to yourself (not world readable). Your .actimrc file should consist of the following configurations:
[DEFAULT] emailAccount emailPassword emailAddress
The following is a list of all the configurations for clients:
| server | where the server is going to run |
| port | the port number talking to the server |
| requestResult | requests all the results of events that are submitted. |
| Possible values are 1 - on, 0 - off. | |
| resultAction | this is valid if the requestResult is 1 |
| Possible values are: | |
| - ResultCode.SAVE_RESULT | |
| - ResultCode.HOLD_RESULT | |
| - ResultCode.RESULT_BACK | |
| transmitMedia | default way to delivery the event. |
| only allows Delivery.SMTP at the moment. | |
| logStatus | 1 - switch on the logging, 0 - switch off. |
| logfile | defines where to write the log file, actim.log |
| Possible values are: | |
| - stdout (Log messages write to standard output) | |
| - stderr (Log messages write to standard error) | |
| Otherwise try to open as a log file | |
| logLevel | grandularity of loggings. Please refer to LogLevel.py |
| for all the possible settings. | |
| targetPath | indicates where the files are going to be stored in |
| file mode. This depends on -p or -g option. | |
| -p means target path on the remote machine, and | |
| local path for -g. | |
| compressFiles | in order to speed up the delivery, the file(s) |
| to be received or sent is(are) compressed before | |
| the delivery. | |
| eKey | encryption key to encrypt the serialised content before |
| sending via email | |
| xmlOutput | all the results are printed out in XML format. The |
| purpose of this option is to make integration to other | |
| applications easier. Possible values are 1 - on, 0 - off | |