...

• Controllers makes use of two configuration files:
  • the general configuration file controller.conf which that is available from the following locations:
    • Windows: C:\ProgramData\sos-berlin.com\js7\controller\var\config\controller.conf
    • Unix /var/sos-berlin.com/js7/controller/var/config/controller.conf
  • the security configuration from private.conf which  that is available from the following locations:
    • Windows: C:\ProgramData\sos-berlin.com\js7\controller\var\config\private.conf
    • Unix: /var/sos-berlin.com/js7/controller/var/config/private/private.conf
  • The configuration format makes use of Typesafe Config, see JS7 - Configuration Format
  • Controller instances have to be restarted to apply changes to the configuration files.
• For HTTPS configuration consider the JS7 - Configuration Templates

Default Configuration

General Configuration File: controller.conf

...

• The Controller writes a journal of events that, for example, results from order state transitions such as an order starting, failing, completing etc.
• The journal file will grow indefinately indefinetely if events are not released. Typically events are consumed by JOC Cockpit and are added to the order and task history. Events are released from the Controller's journal once they have been stored persistently to the JOC Cockpit database. The Controller accordingly will free the space consumed by its journal files.
• users-allowed-to-release-events:  specifies the list of accounts that are allowed to send a command to the Controller to release events.
  • Typically the "History" account is specified, this account is used by JOC Cockpit.
  • If more than one account is specified then events are released only after all accounts have sent the command to release events to the Controller.

...