This article shows an overview of available client command line parameters, which support scripted installation and configuration of the client and it's folders, e.g. when using the client in a headless mode and setting up folders by a third-party system using scripts or direct executable calls.
Passing command line parameters to PowerFolder
To pass parameters to PowerFolder:
java -jar PowerFolder.jar <parameters>
Command line parameters for client configuration
For the general configuration of the client there are some nice command line parameters.
Those parameters can also be combined with each other if necessary.
Setting the default folder path
To set the default folder path, where the client creates new folders:
Specifying a configuration file
To specify the configuration file the client should start with:
The client will use <clientname> to create configuration files, keyfiles and others with that name in the same directory, where the configuration of the first client is located.
Viewing this help information
To show an overview of all command line parameters:
Specify language file
To specify a language file the client should use:
Where langfile is the path to the file that has to be named like translation_XX.properties where <XX> is the country code.
To specify the language to use:
Where countrycode is the extension of the langfile (XX – see above).
Shutting down the client
To shut down the client:
Setting the log level
Specify which level should be logged:
level can be on of:
Starting the client minimized
To start the client minimized to the system tray:
Starting in console mode
To start the client in console mode, eg. with disabled GUI:
Setting Username and Password
To set a username and password:
Starting multiple instances of the client
To start a second instance of the client on the same machine, skipping the "already running" warning:
Running the client on a terminal server under different user accounts
In that case it's recommended to place a desktop shortcut for all users on that machine and extending the executable the shortcut points to with the above mentioned parameter.
Running the client on the same machine under the same user account
In that case it's recommended to combine this parameter with the one to specify a configuration file and a default folder path to use (see below), so both instances will start up using a different configuration and different default folder path. Both instances will be running on the same machine then and will be able to find each other via network broadcasts using the local loopback adapter.
Command line parameters for folder configuration
Folders can also be created/removed using command line options.