Some OnBase deployments use desktop shortcuts that cannot be modified to allow command line switches, and adding command line switches to the onbase32.ini file may not be an acceptable solution because they affect all users on the workstation or because the deployment scheme cannot modify any file(s) other than those in the folder containing the OnBase executables.
A solution to this problem is to specify command line switches to be applied to the OnBase Client or Configuration module executables in the command.ini file. The command.ini file is optional, and must be located in the same folder as the OnBase Client or Configuration module executables. It consists of the following settings.
[Logon]
ClientCommand=
ConfigCommand=
|
Setting |
Description |
|---|---|
|
ClientCommand |
Allows you to specify any command line switches that you would like to apply to the OnBase Client module executable. Multiple command line switches must be separated by a space. For example, the following setting will automatically set the data source to OnBase and the user name to John Adams when the Client login screen is launched. ClientCommand=-ODBC=" OnBase " -UN="John Adams" CAUTION:
The command line switches applied to the OnBase Client module in the onbase32.ini file, like all onbase32.ini settings, are available to any user accessing the Client module from the workstation. |
|
ConfigCommand |
Allows you to specify any command line switches that you would like to apply to the OnBase Configuration module executable. Multiple command line switches must be separated by a space. For example, the following setting will automatically set the data source to OnBase and the user name to John Adams when the Configuration module login screen is launched. ConfigCommand=-ODBC=" OnBase " -UN="John Adams" CAUTION:
The command line switches applied to the OnBase Configuration module in the onbase32.ini file, like all onbase32.ini settings, are available to any user accessing the Configuration module from the workstation. |
Only these settings can be specified in the command.ini file; all other onbase32.ini settings can only be read from the onbase32.ini file.
These settings are only applicable when no command line switches have been applied to a desktop shortcut, and they will prevent any command line switches set in the onbase32.ini file from being applied to the OnBase Client or Configuration modules.