Invantive Data Access Point is started from a shell, from a service manager or from a container. Almost everything it needs is configured in `appsettings.json` in the application root and in the [[Environment Variables]]; the command line carries what differs from one run to the next: the addresses it listens on, the environment it runs as, and the folder it reads its configuration from. An option is written as `--name=value`. The forms `/name`, `-name` and `--name` are accepted, a colon may be used instead of the equals sign, and the value may also follow as a separate argument. Options are not case sensitive and may be given in any order. ## Asking for the Usage ``` Invantive.DataAccessPoint.V2 --help ``` The usage is written to the standard output and the program ends with exit code 0, without reading the configuration and without checking the licence, so it also answers on a server which is not set up yet. `/?` and `/h` do the same. Available from release 27.0. ## Options The following options are accepted: - `--urls=<urls>`: listen on these addresses, separated by semicolons, for example `http://*:8080`. Defaults to the addresses in the configuration. - `--environment=<name>`: run as this environment, which selects `appsettings.<name>.json` next to `appsettings.json`. Defaults to `Production`. - `--contentRoot=<folder>`: read the configuration files from this folder, the application root `ROOT`. Defaults to the folder the program is in. ## Overruling a Setting of the Configuration File Every setting of `appsettings.json` can be overruled by naming its section and its key: ``` Invantive.DataAccessPoint.V2 --DataAccessPoint:RedirectHttps=false ``` The command line is read last and therefore wins: a value given there overrules the environment variables, which in turn overrule `appsettings.<environment>.json` and `appsettings.json`. The section is `DataAccessPoint`, as described in [[Invantive Data Access Point/Configuration|Configuration]]. A setting overruled this way is not remembered; a value which is to hold for every run belongs in the configuration file. ## See Also - [[Invantive Data Access Point/Installation|Installation]] - [[Invantive Data Access Point/Configuration|Configuration]] - [[Environment Variables]]