...

• The License window displays licenses available for the JS7 Controller.
  
  • The Open Source License GPLv3 (General Public License) is available.
  • The SOS Commercial License can be used by adding a license certificate file that you receive from SOS after purchase of a license. For details see JS7 - FAQ - How to apply a JS7 License Key.
    
    

License Agreement

• The License Agreement corresponding to the license option selected has to be accepted before installation can occur.
  
  

...

• In the next window the Controller ID, which is a unique identifier for a Controller, is specified. You can use identifiers such as "controller-test", "controller-production" etc. Character case is significant, the characters a-z, A-Z, 0-9, underscore and hyphen are allowed. Spaces are not allowed in a Controller ID.
• If you intend to operate a Controller cluster with two Controller instances for the active and standby cluster members, then specify the same identifier during installation of each Controller instance as otherwise the instances will not be considered members of the same cluster. This identifier cannot be modified after installation, changes to the Controller ID require reinstallation of the Controller.
  • A checkbox allows the initial role of the current Controller instance to be specified - i.e. whether it starts with an active or a standby role. Do not select this checkbox if you are operating a standalone Controller instance.
  • Note that operation of a Controller cluster requires a license certificate to have been specified in the License Agreement step described above. See also JS7 - LicensingLicense.
• Add the HTTP port that is to be used by the JS7 Controller. Make sure that the HTTP port is available and is not otherwise used. If you run other applications that use this port then choose a different port.
• If you specify a Windows Service account then make sure that this account has "Log on as service permissions". Consider that credentials that you enter to this window are stored in clear text with the installer response file. It is considered more secure not to add credentials with this step, but to add credentials directly after installation using the Windows Service panel.
  
  

...

Automated Startup and Shutdown

For Unix systems startup and shutdown configurations apply that are executed by the root account e.g. from /etc/init.d scripts and by use of systemd.

• Consider use of the JS7_CONTROLLER_USER environment variable from the ./bin/controller_instance.sh script to run a Controller that is started by root for a different user account.
• For use with systemd find a sample service file from ./bin/controller.service-example.
• For details see JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems

For Windows systems operation of the Controller by a Windows Service is recommended as these such services can be configured to start/stop automatically on server startup and shutdown.

• Consider assigning to assign a service account to the JS7 Controller service with the Windows Service Panel.
• Consider allowing to allow the JS7 Controller service to be automatically started on server startup.

...

Further References

• Installation
  • JS7 - Controller - Headless Installation on Linux/Windows
• Operation
  • JS7 - Controller - Command Line Operation
  • JS7 - Initial Operation for Standalone Controller
  • JS7 - Initial Operation for Controller Cluster
• Configuration
  • JS7 - Controller Configuration
  • JS7 - Controller HTTPS Connections