Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.0 (Français) » SQL Anywhere Server - Programming » Deploying databases and applications » Deploying administration tools

 

Configuring the administration tools

You can control which features are shown or enabled by the administration tools. Control is done through an initialization file named OEM.ini. This file must be in the same directory as the JAR files used by the administration tools (for example, C:\Program Files\SQL Anywhere 12\java). If the file is not found, default values are used. Also, defaults are used for values that are missing from OEM.ini.

Here is a sample OEM.ini file:



[errors]
# reportErrors type is boolean, default = true
reportErrors=true

[updates]
# checkForUpdates type is boolean, default = true
checkForUpdates=true

[dbisql]
disableExecuteAll=false
# lockedPreferences is assigned a comma-separated 
# list of one or more of the following option names:
#    autoCommit
#    autoRefetch
#    commitOnExit
#    disableResultsEditing
#    executeToolbarButtonSemantics
#    fastLauncherEnabled
#    maximumDisplayedRows
#    showMultipleResultSets
#    showResultsForAllStatements
lockedPreferences=showMultipleResultSets,commitOnExit

Any line beginning with the # character is a comment line and is ignored. The specified option names and values are case-sensitive.

If reportErrors is false, the administration tool does not present a window to the user inviting them to submit error information to iAnywhere if the software crashes. Instead, the standard window appears.

If checkForUpdates is false, the administration tool does not check for SQL Anywhere software updates automatically, nor does it give the user the option to do it at their discretion.

If disableExecuteAll is true, then the SQL » Execute menu item and the F5 accelerator key are disabled in Interactive SQL. If the Execute toolbar button is configured for Execute All Statement(s), then it is disabled also. Therefore, you might want to set the Execute toolbar button to Execute Selected Statement(s) in Interactive SQL, and then set the executeToolbarButtonSemantics option in the OEM.ini file to prevent users from changing the Execute toolbar button. See Configuring the Execute Statements toolbar button.

 Preventing users from changing Interactive SQL option settings