Technical instruction - Manager command line installer

Owned by Kenneth Jonsson
Last updated: 13 Oct 2023 by Thomas Sandström
2 min read

This option is available in version 5.3 and later

To install the Manager application without a UI, a separate install bootstrap is available in the Standard installation package.

Customization

Setup the Customize module before running the installer, to get all custom extensions installed as well; use Build\SignifikantDeploySetup.exe with Prepare option.

Bootstrap command

The installer is found in build as: \Build\Standard\Signifikant Manager Setup.exe. Here is an example of a command line to run the installer. This may be done by IT staff, with admin privilege or maybe when programs are put in packages and pushed to end users.

Signifikant Manager Setup.exe -q -s http://editorServer/AssertServer -i EditorSite -l en

When an end user later log on, they will have access to Manager and a setup-file to target it to selected server and site with the language selection.

Command parameters

 

  • h - Help page as above

  • q - Quiet install, no UI is displayed, the installer is “silent”. Else an interactive installer is shown.

  • a - Install for all users

  • c - Clear some user files.

Clear operation is related to the user running the installer, not to an end user starting Manager in a different session. Some setting files are deleted. Starting the Manager provide same function in the initial splash dialog.

  • l - Editor language selection; en-GB or else what is convenient to users.

  • d - Run installer in a folder

  • p - Log file target path

  • s - Server Url, as it is specified in Tools / Options in the Manager; https://server-name/AssertServer

  • i - Initial site selected for the user.

The site must be present on the selected server, else none or “first” site is selected when user starts Manager.

Installation parameters save in a file for Manager users

Parameter value for server/site/language is saved in an user-setting.config file for all users. If this file is younger the users normal configuration for the Manager, it will be used. A new installation will save the file again as a later/younger file to override users manual selection of server/site/language.